- Netduino Forums
- → Viewing Profile: Posts: The3dman
The Netduino forums have been replaced by new forums at community.wildernesslabs.co.
This site has been preserved for archival purposes only
and the ability to make new accounts or posts has been turned off.
Community Stats
- Group Members
- Active Posts 9
- Profile Views 2795
- Member Title New Member
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Not Telling
0
Neutral
User Tools
Friends
The3dman hasn't added any friends yet.
Posts I've Made
In Topic: Grove OLED Display 128*64 on Netduino Plus
12 October 2012 - 08:00 AM
I found that was easier than I thought. You need always to send 2 bytes.
If you send a command 0xYY you type:
myDisplay.sendCommand(new byte[] { 0x80,0xYY });
If you send a data 0xYY you type:
myDisplay.sendCommand(new byte[] { 0x40,0xYY });
It's all folks!!!
In Topic: Grove OLED Display 128*64 on Netduino Plus
11 October 2012 - 10:17 PM
Ok, I managed to power it on and off. But things get more complicated.
It seems that it understand a command only if you send it twice in the same connection
i.e.
- to power on I use myDisplay.sendCommand(new byte[] { 0xAF,0xAF });
- to power off I use myDisplay.sendCommand(new byte[] { 0xAE,0xAE });
public void sendCommand(byte [] command)
{
I2CDevice.I2CWriteTransaction writeTransaction = I2CDevice.CreateWriteTransaction(command);
//execute transaction
I2CDevice.I2CTransaction[] transactions = new I2CDevice.I2CTransaction[] { writeTransaction};
int transferred = 0;
transferred = device.Execute(transactions,
this.transactionTimeout //timeout in ms
}
and this is very strange.
In Topic: Grove OLED Display 128*64 on Netduino Plus
11 October 2012 - 05:49 PM
It on 5V and I tried also 3.3V.
Also I connected directly analog pins 4-5 to the screen without other resistors.
I don't know if it is correct but I think that there are already resitors on the display.
In Topic: Ethernet device fail to connect
10 October 2012 - 04:42 PM
I successfully ran my web client on the netduino+ for two days and an half.
It was sending correctly data to the server every 3 seconds during these days.
Then this morning, I noticed that the data flow interrupted roughly during the night for 8 hours.
The netduino got stuck during these 8 hours doing nothing.
I think that it got stuck on the HTTP call "(HttpWebRequest)WebRequest.Create(requestUri)" not even returning an exception!!!
I think this should be possible because a DHCP polling.
Andrea
I forgot to say that to fix it, it was enough to unplug and plug again the ethernet cable. Without restarting the netduino+.
In Topic: Ethernet device fail to connect
10 October 2012 - 04:40 PM
I successfully ran my web client on the netduino+ for two days and an half.
It was sending correctly data to the server every 3 seconds during these days.
Then this morning, I noticed that the data flow interrupted roughly during the night for 8 hours.
The netduino got stuck during these 8 hours doing nothing.
I think that it got stuck on the HTTP call "(HttpWebRequest)WebRequest.Create(requestUri)" not even returning an exception!!!
I think this should be possible because a DHCP polling.
Andrea
- Netduino Forums
- → Viewing Profile: Posts: The3dman
- Privacy Policy