 | | 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)
|
| |
| | Re: Strange happenings
|
|
(...) This almost sounds like a mechanical problem. Try the program with jsu the brick connected to motors or lights and see if you get the expected result. Lester (23 years ago, 12-Jul-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Strange happenings
|
|
I'm using NQC 2.3r1 with the following code bit. task Fidget() //The Fidget task { while (true) { Wait (FidgetTime); Fwd (OUT_B); OnFor (OUT_B,100); HeadPos = 1; Wait (FidgetTime); Rev (OUT_B); OnFor (OUT_B,100); HeadPos = 0; Wait (FidgetTime); Rev (...) (23 years ago, 12-Jul-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Firnware 2.0 and RCXCC
|
|
Hi Rob, You can get the original version of RCXCC to support the RCX2 firmware. The main change is to add the following line to your autoexec.bat: SET NQC_OPTIONS=-TRCX2 Of course, you also need the new firmware and a version of NQC that supports (...) (23 years ago, 10-Jul-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: RCXcc Missing "disconnect commport"
|
|
hi John, thanks for your fast respons, just what I needed (at this moment ;-)) (...) best regards, Stef Mientki (23 years ago, 9-Jul-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Firnware 2.0 and RCXCC
|
|
Hi Everyone, Like the subject says, I am looking for some info on using the new firmware with RCXCC. Up until now, I have found the old version of NQC written by Mark Overmars to be more than enough for what I need. Just recently, though, I built a (...) (23 years ago, 9-Jul-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: RCXcc Missing "disconnect commport"
|
|
(...) I just uploaded a new zip containing version 3.2.9.7 of RcxCC which now has a menu option available to disconnect the COM port. I'm considering adding COM Automation support to RcxCC so that much of its functionality can be scripted. If anyone (...) (23 years ago, 9-Jul-01, to lugnet.robotics.rcx.nqc)
|
