 | | 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: 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)
|
