Fred007

I have netduino experience on 1,Plus1 and Plus2 and have some questions on a future project. I'd like to stay with the whole netduino / VS platform, (makes it very easy for me) but am looking to develop two projects. One will consume data from two CAN bus systems in my car. The other would be a CAN device simulator that could be used during development/testing.

I have a CAN shield but have not assembled it or worked with it on netduino yet.

My question is what you think would be a good way to proceed? Should I take the existing stuff I have and get it working? (i don't need a plus in the car, but a bluetooth would be nice)

Or, would something like the GO be a better platform for this? And, is there a module for the GO that already does the CAN protocol?

Any ideas would be appreciated. Thanks!

Is this implemented in 4.3.1 on a plus 2? I have the following simple code but it does not appear to be working.

I have an app running on a plus, and working to bring another instance up on a plus2. It talks to the HA7S and to the temp sensors on the one-wire bus. On the new plus 2 setup, it looks like the serial buffer is getting over written. when I issue the 'S' get all devices command, I get a return that is different lengths but never the 16 characters I am looking for. It feels like a timing issue, but can't confirm/deny that. I am using the following serial settings.

Com1:9600,8,1,None

I swapped out the plus 2 for another one, no difference. Have used different temp sensors too, no joy. Am thinking now it may be the HA7S chip.

Thoughts?

I think I am missing a step. Trying to read a voltage on Analog0 and measured with a meter its 1.77v but when I read in program I get .5079 (float from .Read()) or 2074 from .ReadRaw(). Is there a calibration setting I am missing? I read about having to pull up the AREF but thought on the Plus 2's that is not necessary. Thanks for any pointers.

(wont be reading anything beyond 3.3v, had a voltage dividing in the circuit but don't really need it)

I have a program that communicates over the net via sockets, and uses COM1 to talk to a OneWire bus. I also monitor the digital IO ports for simple circuit monitoring. Using a Netduino Plus 2 with 4.3 firmware, when I open a closed circuit, it will cause the PC to rediscover the Netduino over USB. (i get the unplug and plug in sounds). This causes the network connection to be reset. I have catches all over the code and can't see anywhere in my code where the socket would be closed, but that is what is being reported on the other end.

I also posted a note about very slow debug performance (when you step lines of code) and when I attach the debugger I get the USB reset sounds a couple of times. Things appear to be working, but I wonder about the Netduino driver. This is on a Windows 8.1 Update x64 machine.

Any ideas on why just opening/closing a digital port circuit would cause the connection with the PC to reset?

Thanks.