 | | Re: NQC on Linux dilema...
|
|
(...) The first thing I'd try would be to add a pair of printf() statements before and after the tcdrain() call in PSerial_unix::FlushWrite() (in file platform/PSerial_unix.cpp). Call be paranoid, but calls like this always make me nervous...they're (...) (25 years ago, 18-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC on Linux dilema...
|
|
(...) the same thing is happening to me, and i did build it from source. i can recompile with changes, if you think it might be useful in figuring out whats going on, though. (25 years ago, 17-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | RCX For Sale.
|
|
Hi there, I do have for sale: Lego partnumber: - 1 ex. RIS 1.5 9747. - 1 ex. Extreme Creatures 9732. - 1 ex. Car 8432. - 1 ex. Pneumatic Submarine 8250. Additional to the above these parts: - 1 ex. RIS Remote Control 9738. - 1 ex. Touch Sensor 9757. (...) (25 years ago, 16-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Q: Determining state of outputs
|
|
(...) Yes, there is a 'data source' for motor status. I never bothered figuring it all out, so there isn't a defined API for it, but you can add it yourself: #define MotorStatus(motor) @(0x30000 + (motor)) use motor 0 for output A, 1 for B, 2 for C. (...) (25 years ago, 14-Apr-00, to lugnet.robotics.rcx.nqc) !
|
| |
| | Re: Q: Determining state of outputs
|
|
(...) I'm not the expert on this but... I've been playing with firmware 2.0 and I think you can read the state of your sensors directly. (The same way you read the Battery level? Dave?) Hopefully Dave will answer you for sure. Dean -- Coin-Op's For (...) (25 years ago, 13-Apr-00, to lugnet.robotics.rcx.nqc)
|
