 | | Re: Ultrasonic Sensor iS "Slow"
|
|
(...) The 15 ms that John reported is the time it takes for a sound pulse to travel 500 mm, the round trip distance at the maximum advertised range of the US sensor. An interesting coincidence? Roger Glassey (17 years ago, 11-Sep-07, to lugnet.robotics.nxt)
|
| |
| | Ultrasonic Sensor iS "Slow"
|
|
Original Thread title was "Re: Ooops! NXT Software Comparison correction / I2C Messaging Speed". I've renamed as worth a separate thread. (...) You're right!! If you poll the sensor too fast, it definitely reports wrong distances. I'm doing some (...) (17 years ago, 7-Sep-07, to lugnet.robotics.nxt)
|
| |
| | RE: NXT-G/ROBOTC Firmware Scheduler and Clump Priority
|
|
Holy cow! This is fun to read... I wish I have the time to further discuss this regarding the events handling with nxt. Follow up later. Thanks for such detailed info. --Elizabeth -----Original Message----- From: news-gateway@lugnet.com (...) (17 years ago, 7-Sep-07, to lugnet.robotics.nxt)
|
| |
| | RE: Ooops! NXT Software Comparison correction / I2C Messaging Speed
|
|
(...) I want to list both. First, the one-to-one mapping, and second (with some explanation) the code with a second task. Several other pieces of software have an "optimized" version of code, and it makes sense to do the same for NBC. Steve (17 years ago, 6-Sep-07, to lugnet.robotics.nxt)
|
| |
| | Re: NXT-G/ROBOTC Firmware Scheduler and Clump Priority
|
|
Wow! Very interesting posting. Thanks for revealing that, Dick! Zitat von Dick Swan <dickswan@sbcglobal.net>: (...) ---...--- This message was sent using IMP, the Internet Messaging Program. (17 years ago, 6-Sep-07, to lugnet.robotics.nxt)
|
| |
| | 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)
|
