id look at an existring driver for that display (netduino) so you can see the settings and such.

id also use an multi i2c class. (link in my signature)

that doesent look right:

new I2CDevice.Configuration(1, 1);

wich device it is? name

and what about pullups on i2c lines?

sounds like the stuff  http://www.wvshare.com offers. (except they dont offer netmf, and netmf Drivers for their modules)

the nRF24L01+ work very well, iam using them. on codeplex is a library for that device.

communication arduino <> netduino via the nrf i didnt got to work - i think its of the codebase, so its hard to find

out the right channel and addresses for each. theoretically it would work.

the 433 i suggest not to use, thats illegal in many countries, and there is also a lot of noise, and afaik

you have to filter the noise out yourself, while the nrf makes this for you.

I am not sure this is relevant, but ST-LINK/V2 included on the Discovery board can be used to debug and program other micros/boards via SWD, it is just needed to remove those two jumpers of CN3 connector (ST-LINK/DISCOVERY selector).

i told him in the chat

i meant 4.2.2.2 not the 4.3 beta

damn i thought its fixed in that version

it works fine with netduino v1 versions (iam using the mini, no problems there with i2c,spi and uart, but other bugs )

your code doesent look correct.

also, has your sensor pullups? if not you have to add 4.7kohm ones

ill add my classes, use them, i used it, they work.

...

IC_BMP085 press;

ress = new IC_BMP085(0x77);

...

 void print()   {   String logString =   "pressure: " + press.pressure + " " +   "altitude: " + press.altitude.ToString("F1") + " " +   "free mem: " + Debug.GC(false);   Debug.Print(DateTime.Now + ": " + logString);

}

it really shouldnt return 0's. if it has pullups on their board, than you dont need one.

maybe upgrade the a newer firmware version of your netduino. iirc there were i2c problems before 4.2.2.2

no i dont own one, and never have.

but i was active a lot and saw a lot of that i2c stuff, but from what i know it got fixed in 4.2.2.2, well doesent look like

actually its quite nice!

a little big, but thats becouse of the proto space wich is ok.

honestly i didnt even expect that you ever get a working version when i read the title. "Ulrimate"

maybe chris or so can fix this (?! i guess you mean ulTimate?!)

anyway, good job!

whats the price of one ?

you can get gthe time by timeserver.

and use a realtime clock as backup (the ds1307 chip even havs some battery backed sram - wich you can use to store a few timetables)

the netduino has no builtin rtc

i hope netduino 3 will have one

its is totally possible. smokingfish did this for the mini.

_but_ you have to change the firmware todo this.

you nearly got it

its: //PWM backlightPwm0 = new PWM(PWMChannels.PWM_PIN_D3, 1000, 0.6f, false);

you cant use too low frequenzy (iam not sure whats the smallest value is you can use, theres a thread about it, gutworks explained it there)

first value is the pin, second is the freuqenzy in hz, thrid is the duty cycle in percent, 4th is the inverting setting (like 0.1f duty gets to 0.9f than -

thats just that you can use the same code for different external circiuts, cos it makes a difference wich transistor and such you choose, npn, pnp)

you set the output to netmf 4.2 in properties?

no there isent, but you can save your data on a sd card, and if its smaller than 64kb on an eeprom.

there is also flash ic's with some mb (but i think they are unhandy, need to earse a whole sector a time.. and such stupido stuff )

it doesent warn you cos float is a lot of numbers, in fact 10(.0) is a float too.

in anohter thread chris mentioned to call pwm.Start();  -- so i think thats the problem here

you can also do that with serial comms, wich is very nice and easy to use.

a tutorial:

http://blog.codeblac...with-RS232.aspx

edit: i use serial comms for all win-duino communication, its way more lightweight than ethernet.

After using $670 on netduino go related stuff,

sounds like a lot. are you sure its only for the go? maybe you can use the stuff you bought for a normal netduino or even an arduino.

thats what i do with my electronic stuff, nearly all parts are compatible with all my different mcu's

for the pullups: id suggest using 4.7 kilo-ohm - that worked great for me.

when adding more devices you can lower that, but from my experience most modules have allready pullups included

i havent changed my 4.7k so far, and iam using like 5 devices on the i2c bus

its looks ok, what does tghe who am i register answer?

ill add my basic code for this module, its i2c, but maybe it helps

also try changing your spi speed, start with 1-2 mhz (idk the specs for the device now, but 10mhz sounds high)

now i can confirm that serial is not the most reliable, but it works quite well for me.

i noticed that when i send a lot of data very fast (115200) some byte gets lost/shifted by one byte.

i than implemented an packet framing, and also send the size of the packet. its very very reliable since than

like that

id remove all the thread.sleep in your sample code and stuff the bytes into a buffer.

i know you wanna work with a gsp shield, so encoding and stuff wount be of any help.

it totally likes this cable. its i/o is 3.3v (only the supply from the cable is 5v, dont use that)

in chat you just called this adapter. its an ftdi cable wich is good.

hmpf.. i thought what i said was clear..

use that:

AnalogInput pot = new AnalogInput(AnalogChannels.GPIO_PIN_A0);

i wonder whats the analoginput class your using is.

the microsoft one want AnalogChannels.yourpin and not Pins.yourpin.

secretlabs one, i _think_ (never used it) wants it the way you have it.