 | | [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)
|
| |
| | RE: Displaying info while debugging
|
|
(...) Mario, I did some checking and I think the real issue is with the USB driver from LEGO. The serial tower does not exhibit this behaviour. It has its own problems, which include falling asleep after 2 seconds of inactivity. So, as far as I can (...) (22 years ago, 2-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: pbForth vs RCX 1.0
|
|
(...) Yes, please :-) I actually knew the EMIT and KEY words, but had never thought of using them to make two RCXs communicate. For some stupid reason in my head I was expecting some special API words was necessary to manage this communcation, while (...) (22 years ago, 2-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Linux driver for USB tower
|
|
(...) Richard, That's great, but I just realized there is no URL....how can we test it if we can't find it? :-) Cheers, Ralph (22 years ago, 2-Jul-02, to lugnet.robotics.rcx.nqc, lugnet.robotics.rcx.pbforth)
|
| |
| | RE: CPR for RCX?
|
|
(...) ld is a linker. It takes the object code generated by the assebles and "links" it together to form an image that can be loaded. The file: ld/h8300_rcx.ld specifies how the objects are stiched together. (...) No, the firmware uploader splits (...) (22 years ago, 1-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: CPR for RCX?
|
|
(...) I knew Assembler would come into play sooner or later. I have downloaded a copy of the H8/300 Assembly language spec. What I still don't understand is how you turn the object code into 'S'-type records with 'ld'? (...) Can I assume the RCX has (...) (22 years ago, 1-Jul-02, to lugnet.robotics.rcx.pbforth)
|
