 | | Re: pbLua GUI ???
|
|
Zitat von Christian Mock <chrimo-@-moccy.xdsnet.de>: (...) pbLua/NXT support there is rather sparse, isn't? Matthias "why don't I do that myself, though?" ---...--- This message was sent using IMP, the Internet Messaging Program. (17 years ago, 3-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
|
|
(...) 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
|
|
(...) Nearly all of the speed test numbers on Steve's page are wrong. That's because Steve's loop boils down to "how fast can you reliably read the LEGO Ultrasonic Sensor". You can't reliably read a value from that device faster than about once (...) (17 years ago, 2-Sep-07, to lugnet.robotics.nxt)
|
| |
| | Ooops! NXT Software Comparison correction
|
|
My bad. When I fiddled with the pbLua code I forgot to turn on the motors and neglected to change the Motor A speed. So when you ran the program, the motors didn't move. I also had uploaded the wrong version to my web site of the version that shows (...) (17 years ago, 1-Sep-07, to lugnet.robotics.nxt)
|
