 | | Useful constants
|
|
\ I still need to figure out how the datalog and transfer progress \ segments work, I'll be spending some time inside Kehoa's disassembly I \ think BASE @ HEX ( codes for POWER_GET ) 4000 CONSTANT pwrOnOffButtonState 4001 CONSTANT (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: SENSOR_READ doesn't return 0
|
|
..and now I have the answer, after extensive grepping around Kekoa's disassembly and the pbFORTH .ASM files. SENSOR_READ should return only the bottom byte, the call to 0x14C0 only returns a byte so the high byte contains garbage (actually it seems (...) (25 years ago, 13-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: SENSOR_READ doesn't return 0
|
|
More information: (...) CONSTANT is working - easy to check by doing RawLight . which prints 1 (...) This last line is the problem, if I use a SENSOR_MODE of 80 as in TRACKER.TXT then I get a SENSOR_READ of 0, if I use SENSOR_MODE 0 then I never get (...) (25 years ago, 13-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: SENSOR_READ doesn't return 0
|
|
(...) I am just dabbling at the moment, trying a few words to try and get them debugged. In order to fully port the SpeedBot (currently in NQC) I'll need multitasking... (...) Oh, good - I wondered if I'd got versions mixed up somewhere. It would be (...) (25 years ago, 13-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: SENSOR_READ doesn't return 0
|
|
(...) AhA! Another victim within my clutches!!!!! Glad to hear you are trying things out, John. The more questions I get, the sooner I can get a FAQ out to help with the common ones. (...) That's a good sign, at least. (...) You have obviously had (...) (25 years ago, 13-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | SENSOR_READ doesn't return 0
|
|
I have been experimenting with the latest version of pbFORTH (102) Which announces itself thus: hhii hForth H8/300 for RCX RAM Model V1.0.0 by Ralph Hempel, 1998 All noncommercial and commercial uses are granted. Please send comments, bug reports (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: FORTH editor/IDE
|
|
(...) Yes, I forgot to turn it off after first downloading the firmware, and getting called away to do something else. Luckily they were rechargeables... (...) Thanks, I'll try it. I will be spending more time with FORTH over the next few weeks, (...) (26 years ago, 4-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Ir transmission
|
|
(...) My next project is to port the IR proximity dectector originally posted by Mark R. David (markdavid@mediaone.net) in sort-of-Spirit code which I reposted in NQC whan I had got it working. It is the best performing detector I have found so far. (26 years ago, 4-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | TRACKER script for pbFORTH
|
|
Hi All, I've been a busy man while my spouse is off in Florida. I've been building and programming robots with my two sons, and have got the TRACKER to work! It's basically the same chassis as the TOP SECRET PLANS at the back of the Constructopedia (...) (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | RE: Ir transmission
|
|
(...) YES!!! The standard FORTH word U. prints an insigned integer, while EMIT sends out an arbitrary byte. So, for a simple IR proximity detector, you would write something like: HEX 0 SENSOR_ACTIVE (labelled sensor #1) 3 1 SENSOR_TYPE (light (...) (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.pbforth)
|
