 | | Re: Some comments (long)
|
|
(...) Unfortunately, the ROM code (as I understand it) does not implement any mechanism other than polling. I would like to do things like block a thread until a sensor value matched some criteria. The only efficient way to do that is to have the (...) (25 years ago, 6-May-99, to lugnet.robotics)
|
| |
| | Re: Some comments (long)
|
|
(...) What is your point? If you want to make sense of the raw values, and want to leverage the ROM code to process the existing sensor types/modes, you need to call a ROM sensor-processing function every time an a/d completes. That was the point I (...) (25 years ago, 6-May-99, to lugnet.robotics)
|
| |
| | Re: Some comments (long)
|
|
(...) Obviously you have spent much more time deciphering the ROM than I have. I wasn't aware that the ROM supported native threads, only multiplexing the bytecode streams it executed. How can replacement firmware hook into this sensor-processing (...) (25 years ago, 6-May-99, to lugnet.robotics)
|
| |
| | Re: Some comments (long)
|
|
(...) I've mislead you. The ROM does not support native threads. The firmware simulates cooperative threads. The firmware selects one of six functions to run based on priority and whether or not a run flag has been set for that function. The run (...) (25 years ago, 6-May-99, to lugnet.robotics)
|
| |
| | Re: Some comments (long)
|
|
(...) I didn't answer your question with the last message. The ROM does not execute byte codes, the firmware does. The firmware multiplexes between byte codes. I'm not sure what you mean by how can replacement firmware hook into the sensor (...) (25 years ago, 6-May-99, to lugnet.robotics)
|
| |
| | Re: Some comments (long)
|
|
(...) Thanks, I think I understand how it works. John A. Tamplin Traveller Information Services jat@LiveOnTheNet.COM 2104 West Ferry Way 256/705-7007 - FAX 256/705-7100 Huntsville, AL 35801 -- Did you check the web site first?: (URL) (25 years ago, 6-May-99, to lugnet.robotics)
|
