Netduino home hardware projects downloads community

Jump to content


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.

Jon Henry

Member Since 27 Feb 2011
Offline Last Active May 13 2013 11:15 PM
-----

Posts I've Made

In Topic: New here - feasable project?

16 April 2013 - 04:22 AM

If you really wanted to get creative, you could throw in a remote temp sensor somewhere in the room and implement a sort of quasi-temperature control of the room using the blind.


In Topic: I2C works under the debugger, but not standalone?

16 April 2013 - 03:59 AM

Hi Alex. I use the MinIMU-V2 from Polulu which uses the LSM303DLHC chip as well as a L3Gd20 Gyro. I run this board along with a Lassen LS20031 GPS and BMP085 with no issues. I run my I2C bus at 100kHz. You shouldnt have to sleep for anything on the LSM303 board.

 

I had what I thought were I2C issues when I switched to the N+2 but it turned out to be buffer overrun issues with the UART. Once I handled that, my I2C ran flawlessly on 4.2.2.0. I also switched from the I2C code you are using to the toolbox.NETMF multiI2C class and have found much fewer hiccups.

 

As far as pullups go, I did have to add 880 Ohm pullups to get under 300ns even with both my MinIMU-V2 and BMP085 boards having onboard pullups. I was at about 340ns, which worked but did hiccup now and then. Ive had the board spitting out data continuously for three days now with no hiccups with the extra pullups.


In Topic: NP2 not responding

05 April 2013 - 03:52 AM

Same thing happening for me, Im having to reflash the board anytime I hit an unhandled exception.


In Topic: Does I2C actually work on the N+2?

03 April 2013 - 04:34 AM

So i used the new program with the one sensor and slowly started copying code and libraries over and running the program after each transfer. I also connected the rest of the I2C sensors. They all work perfectly.

 

Naturally, the very last piece of code I copied over is where I found the problem.

static void spComm_TransmitTelemetry()        {            led.Write(true);            UTF8Encoding enc = new UTF8Encoding();            navData = enc.GetBytes("$TELEM," + nmea[0] + "," + nmea[1] + "," + nmea[2] + "," + nmea[3] + "," + nmea[4]                + "," + nmea[5] + "," + nmea[6] + "," + nmea[7] + "," + nmea[8] + "," + nmea[9] + "," + nmea[10] + ","                + nmea[11] + "," + nmea[12] + "," + nmea[13] + "rn");            //nmea[0] = UTC                       nmea[10] = Target Bearing            //nmea[1] = Latitude                  nmea[11] = Temperature            //nmea[2] = N/S                       nmea[12] = Pressure Altitude            //nmea[3] = Longitude                 nmea[13] = Fuel Gauge            //nmea[4] = E/W                       nmea[14] =             //nmea[5] = Altitude                  nmea[15] =             //nmea[6] = Ground Speed              nmea[16] =             //nmea[7] = Course                    nmea[17] =             //nmea[8] = Date                      nmea[18] =             //nmea[9] = Target Distance           nmea[19] =             //spComm.Write(navData, 0, navData.Length);            Debug.Print(sensor.GetHeading().ToString());            led.Write(false);        }

It seems the N+2 doesnt like my line navdata = enc.GetBytes..................

Commenting this out lets my original program run fine. Uncommenting locks it up and forces a firmware reprogramming of the N+2.

With the Netduino 1, this ran fine uncommented.

Should this be?

 

 

UPDATE (3/3/13):  Its not the UTF8 encoding itself, its my data it doesnt like.

Adding this and the program runs fine. Just have to add the rest of my payload in somehow.

UTF8Encoding.UTF8.GetBytes("$TELEM", 0, 6, navData, 0);

In Topic: Does I2C actually work on the N+2?

03 April 2013 - 02:47 AM

Yeah I had caught that after taking the pic. Its actually only the right one. I had pulled it out just to measure it and post the right value in that post and put it back in the wrong place. In that pic, both resistors are actually connected to the clock line with the other ends positive and negative respectively. It was only wrong for the pic and as soon as i hooked the netduino 1 back up and had a problem i caught it and fixed it. It isnt the cause of my N+2 problem.

 

I did get the N+2 working with only the MINIMU-9 V2. Here is the clock line on the scope.

Attached File  ADS00001.BMP   329.12KB   14 downloads

 

And exploded

Attached File  ADS00002.BMP   329.12KB   8 downloads

 

Should the clock be intermittent like it is in the first pic? It only shows one burst in the pic, but it is consistent...burst.high.high.high.burst.high.high.high.

 

Im gonna put the N+2 back on my main board and connect to the i2c bus I have setup there with all the sensors connected but only run the software which initializes and uses the MinIMU-9. This should at least verify if I have a physical bus problem or not.


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.