 | | Re: Ooops! NXT Software Comparison correction
|
|
(...) So if I cheat I can move the I2C transaction out of the actual timing loop (which may be what some other folks are doing, effectively) then with a "read" of the Ultrasonic sensor value in the loop and all sensors and motors attached I get (...) (17 years ago, 2-Sep-07, to lugnet.robotics.nxt)
|
| |
| | Re: Ooops! NXT Software Comparison correction
|
|
I can further manipulate the numbers for this timing test by using the enhanced standard firmware's support for adjusting a thread's priority. Here's the results when I tweak priorities: W/O LCD LCD Priorities ---...--- 50617 22608 40/5 63211 27375 (...) (17 years ago, 2-Sep-07, to lugnet.robotics.nxt)
|
| |
| | RE: Ooops! NXT Software Comparison correction
|
|
(...) After tuning, NBC achieved 73K test cycles. It achieved these great results by setting the task "priority" to 200. Unfortunately, unless the NXT-G task scheduler has been rewritten, these results might be a little too high. A NXT-G task (or (...) (17 years ago, 6-Sep-07, to lugnet.robotics.nxt)
|
