 | | Re: Breaking from infinite loops
|
|
(...) Hi, if you just want to stop your "own" program use the Forth word ABORT or ABORT" : TEST 1000 0 DO \ do something run-button-down? ABORT" Aborted by user!" LOOP ; or if you want what looks like a "reset" use COLD: run-button-down? IF (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
Ah I see... intriguing idea :) Rereading your original post it should have been quite clear what you wanted. Unfortunately (as far as I know) Mario is right, there doesn't seem to be a clean solution other than manipulating the return stack. I've (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Breaking from infinite loops
|
|
This feels vaguely similar to a question just recently posed, almost. I need a way to get out of a user program that intentionally defines an infinite loop. My best attempt so far at an exit word : exit POWER_OFF LCD_4TH LCD_REFRESH ; in the context (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
(...) I see. Tired of re-booting hey? :o)) There's no way already available that I know of. I think that Mr. Hempel is looking into this. Maybe if we play with the return stack... (...) The way Forth works is that it is running the program. If you (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Light sensor question
|
|
Hi Matt, I'll try to help. :o) First, you have to specify the type of sensor that is hooked on the port. You do that with: type port SENSOR_TYPE Let me know if you need to know the different values for 'type'. 3 is a light sensor. Ports are numbered (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
Hi, (...) My questions were a bit ambiguous. I don't want to abort the routine running on the ISR; I want (from the ISR routine) to abort a currently running user routine - eg abort something started from the console. So, for example, if a program (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Light sensor question
|
|
(...) With obvious mappings, of course. (...) Put another way, at no point does the red LED on the light sensor light up, and I consistently read the same value from the light sensor, regardless of whether I set the mode to RAW or percent value. In (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Light sensor question
|
|
I want to expand the Scheme procedure (get-light-value <sym | num>) where <sym> is one of 'PORT1, 'PORT2, 'PORT3 and num is either 0, 1, or 2 to the FORTH code 128 <port> SENSOR_MODE <port> SENSOR_CLEAR <port> SENSOR_READ <port> SENSOR_VALUE So, if (...) (22 years ago, 15-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
(...) This should be : IsISRFree? 'UserISR ['] NoOp = ; of course. (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
(...) To remove your program from the UserISR just set 'UserISR to ['] NoOp - or even better: to the previously stored old value. (...) Yes, you just have to read the current value of 'UserISR. If no other program is hooked to the ISR this is the (...) (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Aborting from ISR
|
|
Hi, Is there any way of ABORTing the current program from the ISR ? I want to attach a routine to 'UserISR and have it ABORT and then execute POWER_OFF when the off/on button is pressed. I would also like to know whether a user program or the idle (...) (22 years ago, 14-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: [ANN] pbForth Version 2.1.5 Release and IR Data Tutorial
|
|
(...) Mario, I'm glad that this has fixed the problem. I hope that you are making good progress with pbForth and that you're enjoying yourself... Cheers, Ralph (22 years ago, 9-Jul-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: [ANN] pbForth Version 2.1.5 Release and IR Data Tutorial
|
|
Hi Ralph, I don't know if you remember, but I had problems with SAVE-SYSTEM (see msg# 508)... until now! Just to let you know, with pbForth V2.1.5 and (more likely) GUI V2.1.3, it works fine! Thanks Mario (...) (22 years ago, 9-Jul-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx.legos)
|
| |
| | RE: [ANN] pbForth Version 2.1.5 Release and IR Data Tutorial
|
|
(...) Stupid cut and paste error on my part. It's fixed now... Cheers, Ralph (22 years ago, 8-Jul-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx.legos)
|
| |
| | Re: [ANN] pbForth Version 2.1.5 Release and IR Data Tutorial
|
|
Hi Ralph, I just tried the latest version and I can't setup the IR port (mine is USB). I get the following message: Error: can't read "portID": no such variable Works fine with the previous version. Thanks Mario (...) (22 years ago, 8-Jul-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx.legos)
|
| |
| | [ANN] pbForth Version 2.1.5 Release and IR Data Tutorial
|
|
The new 2.1.5 Version of pbForth has a minor fix that affected programmers using the MARKER and LEAVE words. Thanks to Alexander Cech of Austria for supplying great bug reports! I recommend you get the new 2.1.3 GUI while you're at it because it (...) (22 years ago, 8-Jul-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx.legos)
|
| |
| | Re: Displaying info while debugging
|
|
Hi Ralph, I mentionned a while ago (see msg #508) that I have a problem with SAVE-SYSTEM. Could it be the same problem? Could it related to the USB driver and that, while saving the system, there is no period of inactivity and the buffer gets full (...) (22 years ago, 4-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Linux driver for USB tower
|
|
Hi, (...) Good point. The tar file can be found at (URL) (22 years ago, 2-Jul-02, to lugnet.robotics.rcx.nqc, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Displaying info while debugging
|
|
Here it is... : wait 15 0 timer_SET BEGIN 0 timer_GET 0= UNTIL ; I go with 0,15 seconds to be on the safe side; 0,10 seconds is too border line. So now, the first example becomes: : TEST 100 0 DO I CR . wait 7 1 0 MOTOR_SET LOOP 7 4 0 MOTOR_SET ; (...) (22 years ago, 3-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Displaying info while debugging
|
|
Thanks a lot Ralph, And I'm sure you're right. I tried this: 10000 VALUE CTR : test 100 0 DO I CR . CTR 0 DO LOOP LOOP ; For CTR > 11000, the numbers are displayed one at a time. Below 11000, they're displayed in batch. So, it probably means that (...) (22 years ago, 3-Jul-02, to lugnet.robotics.rcx.pbforth)
|
