 | | Re: Problems with RCX Robolab and PowerMacs 6400/200 and 5500/225
|
|
I had a similar problem and suggested used the three cable method you mentioned with great success. Before I tried this I sent an inquiry to Dacta and got this response "There is an issue with some Macintosh serial ports that we are currently (...) (26 years ago, 3-Jan-00, to lugnet.robotics, lugnet.robotics.edu, lugnet.robotics.rcx.robolab, lugnet.edu, lugnet.robotics.rcx)
|
| |
| | Re: Speed of RCX interpreting bytecodes: slow
|
|
(...) Are you sure you mean each of the POSSIBLE threads? I did test to see whether it was slower to count to 1000 with another task running, and it was. Not half as fast, only about 30% slower. --Ben (26 years ago, 3-Jan-00, to lugnet.robotics.rcx)
|
| |
| | Re: Speed of RCX interpreting bytecodes: slow
|
|
(...) Yes. It is important to realise, that the RCX, does not perhaps do the interpretation in the way you think. In each 'loop', it executes one instruction from each of the possible threads, and also reads the A-D's, on each sensor, and updates to (...) (26 years ago, 2-Jan-00, to lugnet.robotics.rcx)
|
| |
| | RE: Speed of RCX interpreting bytecodes: slow
|
|
Ben jackson wrote... (...) Yes, that's why pbForth is "almost ANSI" which means that it is as close to standard ANSI Forth as I could get. And PS is NOT Forth, it is Forth-like. (...) That just adds about 4 items to a datalog, (once every 256 loops, (...) (26 years ago, 2-Jan-00, to lugnet.robotics.rcx)
|
| |
| | RE: Speed of RCX interpreting bytecodes: slow
|
|
(...) OK, I did some basic timing experiments....for pbForth. : TEST1 10000 0 DO LOOP ; \ This is a hard loop of 10000 iterations : TEST2 10000 0 DO I DROP LOOP ; \ Same loop except the loop index is put on the \ stack and dropped - a no-op (...) (26 years ago, 1-Jan-00, to lugnet.robotics.rcx)
|
