 | | [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)
|
| |
| | RE: pbForth vs RCX 1.0
|
|
(...) What you describe would work exactly. Normally, the "outer interpreter" of pbForth waits for input using "KEY" - which of course is just a char from the IR. You can make a special word that waits for anything you like... Cheers, Ralph (22 years ago, 30-Jun-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: CPR for RCX?
|
|
(...) You're pretty much OK until point 4. TCL is used to compile the pseudo code for pbFOrth into assembler source code. From there the GNU as program assembled the object code and ld links it and eventually produces the S records. S records are (...) (22 years ago, 30-Jun-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Linux driver for USB tower
|
|
(...) Richard, this is great! What device name does the new tower driver use. I hope to be able to use my Tcl/Tk GUI for this purpose. It would be really great to get USB support for pbForth into the Linux world. The serial port has always been (...) (22 years ago, 30-Jun-02, to lugnet.robotics.rcx.nqc, lugnet.robotics.rcx.pbforth)
|
| |
| | FW: pbForth vs RCX 1.0
|
|
-----Original Message----- From: rhempel@bmts.com [mailto:rhempel@bmts.com] Sent: Thursday, June 27, 2002 4:21 AM To: Mario Ferrari; lugnet.robotics.rcx....lugnet.com Cc: rhempel@bmts.com Subject: Re: pbForth vs RCX 1.0 Can RCX 2.0 communicate with (...) (22 years ago, 30-Jun-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Linux driver for USB tower
|
|
Hi, I have a working linux driver for the lego USB tower; so far it has only been tested on kernel 2.4.14 on a uhci system, where it has worked without any problems. Anyone feel like testing it out on their own system (to use it, you will need to be (...) (22 years ago, 28-Jun-02, to lugnet.robotics.rcx.nqc, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: pbForth vs RCX 1.0
|
|
Thanks, Just to make sure, let's take an example. Let's say that I have two RCX, named A and B. What if the program in RCX B is waiting for a character on the instruction KEY and RCX A sends a character, let's say '5' (ASCII 52) with 52 EMIT ? That (...) (22 years ago, 27-Jun-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: pbForth vs RCX 1.0
|
|
"Mario Beaulieu" <mariobeaulieu@videotron.ca> writes... (...) Yes. I run pbForth on RCX 1.0, 1.5 and 2.0. No differences. (...) No, to my knowledge. In pbForth the IR port is entirely devoted to communication between the brick and the terminal. (...) (22 years ago, 27-Jun-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | pbForth vs RCX 1.0
|
|
Hi, Is pbForth fully compatible with RCX 1.0? Can RCX 2.0 communicate with RCX 1.0 in pbForth (using IR ports)? Thanks Mario (22 years ago, 26-Jun-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | pbForth questions
|
|
The output of my compiler typically looks like: \ Begin code sample FORTH CODE ... ... : ENTRYPOINT ... ; 0 ENTRYPOINT \ End code sample Or, in other words, I'm currently (and this isn't permanent) not allowing programs to be compiled that do not (...) (22 years ago, 26-Jun-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Displaying info while debugging
|
|
Mario (and all other pbForth users - both of you :-) I'm very happy to include ANY contributions that you may have in the source archive. Even if I don't update the actual core, I still add useful scripts to the distribution all the time. Any (...) (22 years ago, 17-Jun-02, to lugnet.robotics.rcx.pbforth)
|
