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