 | | RE: Useful constants
|
|
(...) <snipped constant descriptions> John, These constants are indeed useful, but would make the resulting srec file pretty big. I have tried to make a TCL script to allow a sort of macro substitution. You can always load the constants after the (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: SENSOR_READ doesn't return 0
|
|
(...) John, Thanks a lot for this catch. Sounds a lot like the email I exchanged with Kekoa regarding power down mode and external stacks, but that's another story... Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for LEGO Mindstorms at: (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: SENSOR_READ doesn't return 0
|
|
(...) OOPS, that SHOULD read 0x0080 since the mode is a BYTE value. Overzealous urge to get content into the website is to blame. For the light sensor, I generally use the percent of scale mode. My website has a page on tricks with the light sensor (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Ir transmission
|
|
(...) Perhaps EMIT? would do (...) I'm nearly done with my NQC to pbFORTH port of the IR proximity detector, but I'm stuck where I have at present got a 30ms delay (Sleep(3) in NQC). I expect it isn't critical but the current detector works so well (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | 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)
|
| |
| | Ir transmission
|
|
Hi, is there any way to send IR messages using pbForth. This is in order to use the IR proximity detector commonly used with nqc programs. Also I think that with alternative firmware such as pbForth and nqc, it should be possible to do it without (...) (26 years ago, 29-Mar-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Light Sensor Non Destructive Mods
|
|
Hi All, I've just added a new page to my website that describes a non-destructive mod to the light sensor that actually allows it to read ambient light! (URL) The range is <10 for a dark box and >90 for a halogen lamp about 6 feet away. It's really (...) (26 years ago, 28-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Why do it? Was: multi-device output controller
|
|
(...) Measuring PWM is not difficult, but it would involve a micro (PIC12C508 anyone?) dedicated to the task and then you would have to get it to drive the RCX, which means motor drivers, etc. If you are willing to spend $50 and LOTS of time, then (...) (26 years ago, 27-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Why do it? Was: multi-device output controller
|
|
Ralph, Thanks for reigning in the rabbit chase! As the originator of this thread I'd like to respond to the 'why'... I keep running out of ports on my creations. I see 5 or 6 as a practical limit. My criteria for a solution: 1. Entirely compliant (...) (26 years ago, 26-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | Why do it? Was: multi-device output controller
|
|
(...) I have checked this out, and if you use the standard RCX firmware (or other firmware that uses the RCX ROM, then you get the waveforms you are talking about at 125Hz 1/(1ms x 8). You also get polarity information - oh no, I've said too much. (...) (26 years ago, 26-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | RE: FORTH editor/IDE
|
|
(...) I'm not in the process of writing an IDE, but I'm not sure you need one either. (...) I'm going to make the pbFORTH a bit more user friendly shortly, by adding a MARKER word that essentially clears out all of your own definitions. (...) The (...) (26 years ago, 25-Mar-99, to lugnet.robotics.rcx.pbforth)
|
