Well my master piece is almost finished. Its got pressure transducers, accelerometer, thermopiles and LCD touch screen. Its a piece of avionics. Its awesome.
Now, I have accelerometer, thermopile and pressure on a single I2C with some low-pass filtering. This all runs on a thread. My routines for the display use the UART and they also run on their own thread. Then my main execution runs on the main thread. I have logging on yet another thread. And I'm currently using about 38kb of program space.
I was wondering if there was any way to determine the CPU load - I mean all those threads have thread.sleep in them at some point and if there is a speed limit my code hasn't reached it limited mainly by the speed of the display and the I2C devices.
I was thinking of sticking GPS for ground speed and heading information on the spare com port. This will require constant baby sitting of the NMEA sentences. The question is will the little netduino cope?
How to tell?
How to determine how busy my netduino is?
Started by DrJaymz, Mar 19 2012 09:30 PM
1 reply to this topic
#1
Posted 19 March 2012 - 09:30 PM
#2
Posted 12 April 2012 - 07:33 AM
Hello,
I am wondering about CPU load too… however, maybe consider configuring the GPS to only update say every 2-3 seconds to reduce the load on the netduino.
It also depends on how efficient your NMEA parser is really..
Sorry not to be a help, but just my thoughts…
EDIT: the netduino should cope, though you may get small delays in some of the code if it is getting busy…
Also concider changes to code to reduce the use of floating point numbers as I believe the netduino doesn't have a MCU...
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users