Netduino home hardware projects downloads community

Jump to content

The Netduino forums have been replaced by new forums at This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.


Member Since 05 Mar 2013
Offline Last Active Feb 12 2016 11:18 PM

Posts I've Made

In Topic: Netduino Plus and LV-MaxSonar-EZ3

23 June 2014 - 12:27 AM



I am in the middle of moving, so it will take me a bit to find the code.  However, the main issue turned out to be that I had wired the RS-232 to TTL converter incorrectly (see above).  You can't just connect the Netduino directly to the sonar for serial data transfer.


For the serial port, I had the problem mostly solved by just reading 5 bytes and discarding them if it didn't read correctly, but then my Create developed a problem sending serial data, so I switched to the sonar analog output--I haven't had a chance to get back to the serial transfer yet.  Important to remember that the Netduino analog input will NOT tolerate 5V--you have to use 3.3V.


--John Mc

In Topic: Netduino Plus 2 and SerLCD LCD-09067

02 February 2014 - 06:41 AM

I do get the banner.  Also found my 3.3v power supply.  Before I remembered that the power supply ground and serial Rx both needed to be common, the board went a little crazy and showed every symbol in the book all across both lines, but that suggests the display is capable of displaying the symbols.  I also noticed it isn't exactly two vertical lines--the rightmost line has one extra pixel sticking out of the right side.


Figuring I could've garbled the baud rate, I sent the 9600 baud reset (124 then r) during the splash screen display, but still no luck.


I'll ask at Sparkfun, too.  They might be able to identify if this is symptomatic of something.

In Topic: Netduino Plus 2 and SerLCD LCD-09067

01 February 2014 - 12:07 AM

This is the 3.3 volt board.  9600, 8, None, and 1.  The only connections are power, ground, and D3 out of the Netduino (Com 2 Tx) to Rx on the LCD.  Seems like it couldn't be any simpler...


public static SerialPort serialLCD = new SerialPort(SerialPorts.COM2, 9600, Parity.None, 8, StopBits.One);


I was wondering about the power since the spec sheet says the board wants 60mA with the backlight on, and the Netduino pins are rated for 25mA.  Looking at others' comments on this LCD board, though, I haven't seen any reference to using external power, and the backlight seems quite bright.

In Topic: Netduino 2 Plus loses firmware

24 November 2013 - 08:42 AM

It took a little longer to get back to this than I'd seems the problem was Netduino versus NetduinoPlus using directive and reference.


Grabbed my old PC and completely rebuilt it from a bare hard drive to WinXP SP3 and Visual Studio C# 2010 with the MicroFramework 4.2, the Netduino 4.2.2 SDK.  (The bad news here is that my Win7 disc has gone missing, but that's a different problem...)  Created a NEW NetduinoPlus2 application, and was able to make the LED blink consistently.


Then copied the code over from the larger "problem" project into the new project; again the board worked.


Next, loaded the entire problem project copied over from my main computer; it immediately locked up the board.  Tried this 3 times to be sure I wasn't doing something different each time.  By "locked up" I mean that it won't even answer an MFDeploy ping.  (I'm also becoming quite proficient at erasing and flashing the firmware...)


I finally noticed that the new NetduinoPlus2 application actually adds "using SecretLabs.NETMF.Hardware.Netduino;" NOT "NetduinoPlus."  Tried changing out both directives and references--with just a Blinky routine, either one works.  With something more complicated, using NetduinoPlus and its reference locks the board immediately; the only solution seems to be reflashing.


Ultimately, this seems odd, since it's a Netduino 2 Plus, not a Netduino 2.  Does it make sense to you?


The project that fails has the following using directives:









SecretLabs.NETMF.Hardware.Netduino (or NetduinoPlus);




The next logical step seemed to be figuring out which using directives/references are causing the issue, but it occurred to me you might be able to tell at a glance. 


I also couldn't tell if there was a reason to use the .dll in the base Assembliesv4.2 directory or the le directory; they seemed to be the same file.  Without a reason to do otherwise, I stuck with the base directory version.


Very curious about whether the using directives/references solution makes sense, but very glad the board is working!




John Mc

In Topic: Netduino Plus 2 Firmware v4.2.2 (update 2)

13 October 2013 - 08:49 AM

Hmm...interesting results.


Flashing with 4.3 beta 1 went smoothly, and the first time I started debugging, the program deployed without incident from Visual C# 2012.  (Silly side question--how is the onboard LED now declared?  Haven't looked for it since 4.1.)


The second time I deploy, Visual Studio gives "There were deployment errors--continue?"  The output window shows "cannot attach debugger engine."  After answering, "No," the error list shows "unable to connect to device."  Curious, I ran MFDeploy, it says there is "No debugger!" found, and "Cannot find any entrypoint," although the other Device Capabilities info seems to all say (beta 1).  The program I initially deployed is identified by name in MFDeploy.  The IP address of the device shows as in MFDeploy, if that matters.


I erased and re-flashed with 4.3 beta 1 to verify it wasn't a one-time event.  Same results.  As I recall, this is the same thing that happened with 4.2--it seemed to work the first time from Visual C# 2010, but didn't after that.


I'm hoping the answer is, "Oh, based on those symptoms, it looks like you forgot to do X," but I'm worried the answer is, "That's not supposed to be possible."




--John Mc

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.