 | | Re: NQC/BricxCC test
|
|
(...) Duh! I had 'only if active' ticked and I dont suppose that changes in my light sensor were enough to trigger it. I now have watching the brick & graphing working! I notice that (unused) counter 0 and 1 take on the values of var 0 and 1 and (...) (19 years ago, 18-Oct-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC/BricxCC test
|
|
(...) This seems to have fixed all the problems that I was having with the serial tower and Bricx. [It also downloaded new (Swan)firmware OK] The template right-click is great too :-) I wasn't able test out the new (Vers.10) graphing part as I dont (...) (19 years ago, 18-Oct-05, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC/BricxCC test
|
|
I could use some help testing a modification to NQC and BricxCC which is attempting to correct some problems I introduced with the serial IR tower and also the USB tower. Could a few adventurous souls download (URL) and try out the NQC and BricxCC (...) (19 years ago, 14-Oct-05, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC release 3.1r4
|
|
(URL) changed the Spybot program code generation slightly so that it matches that generated by the MindScript compiler. Tasks which are not empty are no longer ended with a Stop Task sequence. Empty tasks are ended (as before) by a Stop Task (...) (19 years ago, 13-Oct-05, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC release 3.1r3
|
|
(URL) a bug in expressions like a = a*2 + a*3; Thanks! John Hansen (19 years ago, 4-Oct-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Latest version BrixCC
|
|
(...) I have not yet made an official 3.3.7.9 release of BricxCC. My apologies for the delay. For now you can use the latest version in swan_test.zip. John Hansen (19 years ago, 29-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Latest version BrixCC
|
|
Hi, I found on the sourceforge.net the Brixcc version 3.3.7.7 and in the swan_test.zip the version 3.3.7.9. Is there a newer version? Regards, Jan Kromhout Hellevoetsluis-NL (19 years ago, 27-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: time sampling under the rcx standard OS
|
|
(...) Here's a code byte from my LegWay code. ---- int MotorSpeedArray[32] = {1,3,2,0}; // Speeds // ... later in the program... if (sys_time>CheckTime) // check system timer - is it time to check sensors again? { L1 = ReadSensor(SENSOR_1); L3 = (...) (19 years ago, 21-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: time sampling under the rcx standard OS
|
|
Hi Steve, As I'm quite new to BrickOS and to C programming, I'm sorry I'm not sure I understood what you meant, neither how you do this : (...) - Do you check the sensor at a higher rate, and only send a command to the motor at 1kHz ? - How do you (...) (19 years ago, 21-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: time sampling under the rcx standard OS
|
|
(...) Well, in BrickOS, my loops usually execute at > 1kHz, so I usually just set it to check the sensor, and set the motor every 1ms. So it just keeps checking the clock. (...) Yes. There's an option that lets you download an "SREC" type of file. I (...) (19 years ago, 19-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: time sampling under the rcx standard OS
|
|
(...) Sorry, I didn't explain. This program only aims at checking the loop frequency capability of the rcx firmware, implementing a PWM. The rotation sensor is only used as a potentiometer knob, allowing me to determine by hand the PWM pulse as (...) (19 years ago, 19-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: time sampling under the rcx standard OS
|
|
Thank you Matt, the RCX loops much faster with your advices : about 10 loops per second. But as this frequency depends on the calculations included in the loop, I’m afraid this will not be enough. So I tried to download (URL) but it just appears as (...) (19 years ago, 18-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: time sampling under the rcx standard OS
|
|
Thank you Dick, for advicing me to switch to the faster firmware, I’m sure I need both a 1-millisecond basic clock, and the 128 power level capability. So I tried to download it from (URL) but it just appears as a text file, which I don’t know how (...) (19 years ago, 18-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | RE: time sampling under the rcx standard OS
|
|
Here are some comments on how to improve your code for real-time performance. 1. Move the "SetUserDisplay" out of the loop and put it just before the loop. 2. I think the "OnFwd" macro is actually two instructions: "Fwd" and then "On". Replace this (...) (19 years ago, 17-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: time sampling under the rcx standard OS
|
|
(...) From what I've seen, the standard firmware takes about 3ms per command, and the same program will run on BrickOS about 100 times faster. I usually set up my BrickOS programs so they use the internal timer, and only update the motor setting (...) (19 years ago, 17-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: time sampling under the rcx standard OS
|
|
(...) Francois, I think you should be able to get much faster sampling. I can easily get 10-20 Hz, and others have claimed to get down to 3 ms. Whether it can be done at a constant rate, I'm not sure, and think it probably depends on what else is in (...) (19 years ago, 17-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | time sampling under the rcx standard OS
|
|
Hi list, I'm trying to implement a position regulation (using a motor and a rotation sensor), using for instance a PID (Proportional-Integr...erivative) regulation. I tried to code it in NQC, using the standard OS, but it seems that the RCX loops at (...) (19 years ago, 17-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | IR-based proximity measurement
|
|
I'm changing the subject line in the middle of the thread. Wonder what the server will do with that... I tried out Brian's "Max-picking" ping method, as well as a few other things. Here's a summary of what I found: 1) If the active sensor readings (...) (19 years ago, 16-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: direct manipulation of bits in RCX registers using NQC
|
|
(...) Correct. A NQC command (say, "Wait(10);") is converted to one or more "bytecodes" (in this case, one bytecode, namely a string of 4 bytes (0x43 0x02 0x0a 0x00), the first of which is a command (0x43) while the following three are information (...) (19 years ago, 16-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: direct manipulation of bits in RCX registers using NQC
|
|
Hey, Thanks for all the helpful responses, everyone. Brian: (...) I guess that "firmware" must be the code that tells RCX how to interpret user instructions (NQC, C, IC, opcodes, or whatever), and convert them to binary machine-specific code. Right? (...) (19 years ago, 16-Sep-05, to lugnet.robotics.rcx.nqc)
|
