 | | RE: Ooooops!
|
|
(...) You're right Mario. Like everyone else, I'm busy at my real job, but when I get time here and there I'm making improvements to the kernel. One idea was to provide multi-tasking built-in and having a standard button driver will help with (...) (24 years ago, 22-Mar-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Ooooops!
|
|
(...) it? (...) From what I understood (I might be wrong) while the pbforth kernel is running the buttons have no predefined action, so there's no way to make the RCX sleep without using the terminal console. Of course you can do that in your own (...) (24 years ago, 22-Mar-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | Ooooops!
|
|
Ingore the message where I wrote that the RCX didn´t start. It started without showing the "4th" on the lcd screen. Does anyone know how to do that? I mean that when you press the "ON - OFF" button it beeps and shows the "4th" or something. Just so (...) (24 years ago, 21-Mar-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: RCX Crash!
|
|
Well, acually I wanted to download the pbForth into the RCX because I was reading the book EXTREME MINDSTORMS that you wrote with Dave Baum. In the pbForth chapter I just read trough until I got to the second part. There I needed to test for myself (...) (24 years ago, 20-Mar-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: RCX Crash!
|
|
Henrik, Don't panic. To make sure that you have actually killed the pbForth firmware, you need to take out the batteries while it's actually running a program. I've had it showing "4th" on the display for over 1 month just on batteries. If it's (...) (24 years ago, 20-Mar-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | RCX Crash!
|
|
I have downloaded the latest version of pbForth and when I downloaded it to the RCX the "4th" appeared on the screen. Later I wanted to go back to the standard RCX 2.0 firmware. I took out the batteries to clear the memory from pbForth, but when I (...) (24 years ago, 20-Mar-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: OmniRemote and Mindstorms Update
|
|
From what I've been able to figure, you need to bypass the irDA queue on the Palm to send straight bits over the IR port. This is possible by going to the hardware itself. OmniRemote can do it, and so can we (if we figure out how!). It's been in my (...) (24 years ago, 7-Feb-01, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | RE: OmniRemote and Mindstorms Update
|
|
(...) I don't. I never got beyond using a Terminal Emulator (I forget which one) to send a text file from the Palm to the Tower over the serial port. Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for LEGO Mindstorms at: (URL) Buy "Extreme (...) (24 years ago, 7-Feb-01, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: OmniRemote and Mindstorms Update
|
|
Ralph, to what extent do you have QForth communicating to the RCX? I just started writing (again, I started this last year and didn't get around to it) a QForth program to communicate with the RCX. Do you have any QForth code that would get me (...) (24 years ago, 7-Feb-01, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | RE: OmniRemote and Mindstorms Update
|
|
(...) No, it's way simpler than that. The text files on the Palm are source code for Quartus Forth on the Palm. The idea is that the *same* source gets sent to the RCX via the IR link - you can do it now with a serial link, a terminal emulator, and (...) (24 years ago, 7-Feb-01, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | RE: OmniRemote and Mindstorms Update
|
|
(...) Well, actually, the idea was to be able to write Forth source on the Palm and upload it using a terminal emulator from the Palm. If we can integrate the IR into Quartus Forth, then it would indeed be cool to upload firmwarwe and code from the (...) (24 years ago, 7-Feb-01, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Confusion regarding the POWER_OFF command.
|
|
(...) I was too. It's a bit goofy, so I'll try to explain as I go... (...) That's fine - the only thning you need to do (I think - I'm away from my RCX) is to put POWER_INIT just before POWER_OFF. The POWER_INIT word initializes the interrupt (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | Confusion regarding the POWER_OFF command.
|
|
I'm a little confused with the POWER_OFF word. From reading the documentation, I would have though the following would work: POWER_INIT : test BEGIN DO-WORK POWER_OFF 0 UNTIL ; When 'test' is executed, both 'DO-WORK' and 'POWER_OFF' are executed, (...) (24 years ago, 25-Jan-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: pbForth is fun!
|
|
(...) We all suffer from the same problem, Mario, we work with the tools we know! (...) <snip> Thanks Mario. This kind of praise is hard to come by, especially from someone who really knows how to tinker! I have been pretty slack about updatingthe (...) (24 years ago, 22-Jan-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | pbForth is fun!
|
|
I had approached pbForth two or three times in the past, always failing to manage what I thought was a steep learning curve. The truth is I probably was too lazy to put the necessary attention into it, or I was in a hurry to program my robots to (...) (24 years ago, 22-Jan-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Firmware loading failure
|
|
I am able to download using native NQC - so NQC CC was the problem. (...) (24 years ago, 16-Jan-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | Firmware loading failure
|
|
I have a repeating failure trying to download the firmware. I'm using RCX Command Center and pbforth 121. It fails in exactly the same spot - record 1638 - each and every time, with two different RCX units. The batteries are new and I can reload the (...) (24 years ago, 16-Jan-01, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Long range IR mode
|
|
(...) Disclaimer: I didn't try ANYTHING of this... According to Kekoa's Internals, the ROM routine 0x3250 (0x3266) with parameter 0x1770 sets the IR range to long (short). So you need to do something like: push 0x1770 jsr 0x3250 pop ; Stack should (...) (24 years ago, 27-Dec-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Long range IR mode
|
|
I've discovered the RCX is in long range mode UNTIL I send it a POWER_INIT pbForth command. Pity... what's the way around this, anyone ? (24 years ago, 27-Dec-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | transmission distances
|
|
When I muck about with Exploration Mars software, the RCX doesn't go out of range until it's out of the room. With pbForth, the RCX receives the commands over just as far a range, but can only send its "ok" feedback when it is quite close to the (...) (24 years ago, 19-Dec-00, to lugnet.robotics.rcx.pbforth)
|
