 | | Re: Speed of RCX interpreting bytecodes: slow
|
|
(...) From memory, the NQC was: int count; task main() { count = 0; CreateDatalog(100); ClearTimer(Timer(0)); while (count <= 1024) { if (count & 0xff == 0) AddToDatalog(Timer(0)); count += 1; } } The downloaded datalog will show the last log entry (...) (26 years ago, 5-Jan-00, to lugnet.robotics.rcx)
|
| |
| | Re: NQC wishlist
|
|
(...) [Snip] (...) Okay. Is sending these commands (and which ones that are/can be "immediate") in your book? <G> While I don not have something in mind right this second, the more complex programs get the higher the possibility of someone using (...) (26 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Speed of RCX interpreting bytecodes: slow
|
|
(...) What is in a "counter loop iteration" ? Please share the NQC program you used to measure this with us. I fail to believe that a simple loop runs this slow. 16000 cycles per loop iteration does not sound right to me. -Kekoa (26 years ago, 4-Jan-00, to lugnet.robotics.rcx)
|
| |
| | Re: NQC wishlist
|
|
(...) I'm not sure if the terminology from LEGO is "direct" or "immediate" commands, but either way the idea is that some of the bytecodes can be sent to the RCX and the RCX will execute them immediately. There's a lot of overlap between the direct (...) (26 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
(...) I am kind of new to this, but what is meant by direct command? How would tasks downloaded in another slot be assessable to some other task to start up? --- DonC donc@cccd.edu (26 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | RE: NQC wishlist
|
|
(...) This might be a good idea. The pbForth thing is working out well too. Maybe a C to FORTH translator would be useful. In the other hand, making a custom bytecode interpreter means having to write the interpreter and support it on different (...) (26 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
(...) To me, one of the important features of such a thing would be compatibility with the existing firmware. Otherwise, why not just use LegOS? (26 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
If anyone is seriously considering this I'd ask two things... 1) Have you considered porting the p-code interpreter used by Interactive C or something like a stripped down Java bytecode interpreter instead? The idea here would be that the RCX (...) (26 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
(...) Yeah, this was discussed way back at the beginning of the reverse-engineering effort. It's something I'd like to see too. (26 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
I was jut wondering, has anybody tried to implement a "better RCX-code"? It must be possible to write something very similar to RCX-code in LegOS, only faster and implementing the "missing" array structures and more variables. Mayby compatible with (...) (26 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Re: USB->Serial Converts and IR Tower
|
|
Is that on a PC? I have one running with the latest drivers from their site. It works fine for small snippets of code, but always times out, when trying to download larger segments or firmware. What exact driver version do you have. What exact (...) (26 years ago, 4-Jan-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | Re: Problems with RCX Robolab and PowerMacs 6400/200 and 5500/225
|
|
(...) This one works for me just fine. Dw (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
|
|
(...) half (...) Yes, it seems to switch between two 'modes', one being effectively single tasking, and the other multi-tasking. This gives the change you are seeing. The 'loop' time, can be measured very easily with a scope, by setting a motor (...) (26 years ago, 3-Jan-00, to lugnet.robotics.rcx)
|
| |
| | Re: Problems with RCX Robolab and PowerMacs 6400/200 and 5500/225
|
|
Hello to all, Thanks for all those who wrote in with suggestions for how to get my RCX bricks to work with the PowerMac 5500s that I was having trouble with. Here's a summary of my experiences and how I eventually got enough working machine to teach (...) (26 years ago, 3-Jan-00, to lugnet.robotics, lugnet.robotics.edu, lugnet.robotics.rcx.robolab, lugnet.edu, lugnet.robotics.rcx)
|
| |
| | Re: Problems with RCX Robolab and PowerMacs 6400/200 and 5500/225
|
|
I believe Fred Martin ran into similar problems and the serial extension did indeed help. I think his write-up of the issue is somewhere on his site: (URL) Baum (...) (26 years ago, 3-Jan-00, to lugnet.robotics, lugnet.robotics.edu, lugnet.robotics.rcx.robolab, lugnet.edu, lugnet.robotics.rcx)
|
| |
| | 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)
|
