|
| | Display the value of Scout sensors
|
| Scout is cheaper, but when you debug NQC program in Scout, you have no way to watch the value of its sensors, I made a small program that can show sensors value in a RCX LCD, you can use remote to change watching sensor, message 1 for sensor1, (...) (23 years ago, 26-Jul-01, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
| | | | About SensorValueRaw(SENSOR_3) in Scout
|
| I tried to get raw value of sensors in Scout, the SensorValueRaw(0/1) is ok, I get the raw values of Sensor1 and Sensor2, but I found SensorValueRaw(2) doesn't work, no value is returned. Then I found a example in NQC Guide Version 2.3 r1, it is (...) (23 years ago, 14-Jul-01, to lugnet.robotics.rcx.nqc)
| | | | Re: Strange happenings
|
| (...) I'll consider adding those in the next release. To be honest, its probably more work from a documentation side than from a code perspective. (...) If its working, don't bother sending the code. But if it stops working again, then send the code (...) (23 years ago, 14-Jul-01, to lugnet.robotics.rcx.nqc)
| | | | Re: Strange happenings
|
| (...) It was very odd, I've been having a lot of problems with that onfor command. I had a command that was supposed to go for 1 second. OnFor(AOUT_B,100); and it would NEVER stop. I changed it to 10 and it worked for a bit then stopped. It just (...) (23 years ago, 13-Jul-01, to lugnet.robotics.rcx.nqc)
| | | | Re: Strange happenings
|
| Looks straighforward. Perhaps an NQC bug. Can you email me the complete program and also compile with the -l option and send me the listing (or if you're using an IDE, then there should be some menu choice to produce a disassembly list)? Dave Baum (...) (23 years ago, 13-Jul-01, to lugnet.robotics.rcx.nqc)
| |