 | | NXT-G/ROBOTC Firmware Scheduler and Clump Priority
|
|
In a typical operating system (OS), tasks are scheduled on a priority basis. The highest priority task always executes ahead of lower priority tasks. If there are multiple tasks at the highest priority, then they are typically executed in a round (...) (17 years ago, 6-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)
|
| |
| | RE: Ooops! NXT Software Comparison correction / I2C Messaging Speed
|
|
(...) Nobody cheated or is dishonest. Everyone who writes firmware for the NXT is well-intentioned "good" people. Let's not mislabel good modern programming practice -- i.e. hardware device drivers integrated into the low-level firmware -- as (...) (17 years ago, 6-Sep-07, to lugnet.robotics.nxt)
|
| |
| | Re: Ooops! NXT Software Comparison correction / I2C Messaging Speed
|
|
(...) I think I understand. In this case, the limiting factor is the US sensor itself, how fast it can ing and interprete a return. Or from my standpoint (a physicist), it's a fundemental limitation of the physics of sound, not a limitation that has (...) (17 years ago, 5-Sep-07, to lugnet.robotics.nxt)
|
| |
| | Re: US-Sensor I2C-address
|
|
(...) To my knowledge the LEGO Ultrasonic sensor does not support changing its I2C address. IIRC it is hard-coded to 0x02. I do not think it is ADPA-compliant. John Hansen (17 years ago, 5-Sep-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: Ooops! NXT Software Comparison correction / I2C Messaging Speed
|
|
(...) The errors that occur are that the sensor does not properly report variable distances as it is positioned at varying distances from an obstacle. If you slow down the read rate then it works correctly (i.e., with a wait of ~15 ms between read (...) (17 years ago, 5-Sep-07, to lugnet.robotics.nxt)
|
| |
| | Re: pbLua GUI ???
|
|
(...) I forgot the screenshot ;-) (URL) me: which of the connected NXTs is real ? One of this NXTs is software only (pbLuaAPI). Bye Christian (17 years ago, 5-Sep-07, to lugnet.robotics.nxt)
|
| |
| | Re: pbLua GUI ???
|
|
(...) New Eclipse version EUROPA (3.3) with LuaEclipse, RSE Target Management, RXTX and pbLuaAPI works excellent with pbLua ! You have direct access to all serial connected NXTs (Bluetooth and USB) from the Eclipse Workbench. A perfect professional (...) (17 years ago, 5-Sep-07, to lugnet.robotics.nxt)
|
| |
| | Re: Ooops! NXT Software Comparison correction / I2C Messaging Speed
|
|
Hi Dick, (...) actually I2C runs at something close to 12kHz in the LEGO firmware (I forgot the exact value). Jürgen (17 years ago, 5-Sep-07, to lugnet.robotics.nxt)
|
| |
| | Electronics Prototyping with the LEGO NXT
|
|
Hi Folks, I've been exploring various ways to use the LEGO NXT in enhancing electronics through Robotics and I've just posted a short video on the subject matter at my blog (URL). I'll be writing an eZCIRCUITs application note on the construction (...) (17 years ago, 5-Sep-07, to lugnet.robotics.nxt)
|
| |
| | RE: Ooops! NXT Software Comparison correction / I2C Messaging Speed
|
|
(...) I wasn't aware of this firmware limitation. I could not duplicate it when using the ROBOTC firmware. I've done three different test runs of 500K messages each with perfect results each time. Each test run used a different sensor. The delay (...) (17 years ago, 5-Sep-07, to lugnet.robotics.nxt)
|
| |
| | leJOS NXJ 0.4.0 is Released
|
|
NXJ version 0.4.0 now includes a full suite of graphical widgets in the java.microedition.lcdui package, a multi-level menu system, wireless NXT to NXT communications using Bluetooth, primitive wav file sound support, and many more enhancements. (...) (17 years ago, 5-Sep-07, to lugnet.robotics.nxt)
|
| |
| | US-Sensor I2C-address
|
|
Hello Community, is there currently a known way to change the I2C-Address of the Ultrasonic sensor ? What's the magic with the ADAP ? Thanks for some informations Bye Christian (17 years ago, 4-Sep-07, to lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: pbLua GUI ???
|
|
(...) This is starting to look pretty promising as a standard IDE. I will do my part and install Eclipse here and get the instructions updated from Christian's instructions. Once we get a decent IDE the pbLua system may be almost ready for "everyone (...) (17 years ago, 3-Sep-07, to lugnet.robotics.nxt)
|
| |
| | Re: pbLua GUI ???
|
|
(...) ;-) currently I'm extending Eclipse with simple terminalprogram and pbLuaAPI... With pbLuaAPI-Wrapper(maps pbLua nxt.* to native Lua routines) you can test and run pbLua code at local PC before transfering to NXT... Christian (17 years ago, 3-Sep-07, to lugnet.robotics.nxt)
|
| |
| | 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)
|
