 | | Re: Debugging
|
| (...) Oh, you're doing stuff inside the scheduler. Yeah, msleep doesn't work too well there :-) Yes, the pauses were only so I could see what was going on. Another thing you could do is print messages out the IR port; but I'm not sure how it would (...) (28 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
| | |  | | Re: Debugging
|
| (...) However, last night, I wrote a brute force (spin loop) msleep which works fine in the scheduler. I found that 800 iterations of an empty for loop with a 16 bit index comes pretty close to 1ms. Granted, I cheated a little, knowing that the (...) (28 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
| | |  | | Re: Electrical specs of RCX I/O ports
|
| (...) current, voltage, etc.) and input ports. The input ports are pretty well described on my page at: (URL) (28 years ago, 17-Mar-99, to lugnet.robotics)
| | |  | | Re: help please
|
| Compatible substitutions for: Digikey# P6305 6.3v 470uF NICHICON Aluminum Axial General Purpose Miniature VX Series Capacitance Value: 470 µF Capacitance Tolerance: ± 20% Capacitance Range: 376.00 µF to 564.00 µF DC Voltage: 6.3v DC Temperature (...) (28 years ago, 17-Mar-99, to lugnet.robotics.handyboard)
| | |  | | Re: Debugging
|
| (...) It's what I'm doing for now in my debugger work. I haven't tried it out yet, though. (...) I carefully looked at the opcodes, and found that the shortest opcodes are all 2 bytes, and hand-coded the 2 byte instruction that jumps to itself. The (...) (28 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
| |