 | | Re: using nqc for first time —Kevin Carlson
|
| | | (...) Cool. Thanks for checking this out. I did get one failure, and then one success, and here are the outputs: nqc -d -l -v test.nqc *** Task 0 = main 000 InType 0, Switch 32 00 01 003 InMode 0, Boolean 42 00 20 006 OutDir A, Fwd e1 81 008 OutMode (...) (25 years ago, 21-Jun-99, to lugnet.robotics)
|
| | | |
| | | | | Re: using nqc for first time —Dave Baum
|
| | | | The traces confirm a couple of things: 1) Normally the IR tower will "echo" all data that it sends (just a side effect of the LED blasting out the light and the phototransistor picking it up). In your case there are a significant amount of bit (...) (25 years ago, 23-Jun-99, to lugnet.robotics)
|
| | | | |
| | | | | | Re: using nqc for first time —Kevin Carlson
|
| | | | (...) Voila! Everything seems to work fine on the modem port! I just assumed it would make no difference. Not only does nqc work, but my RoboLab software now works also. I wonder why? I always thought that these two ports were basically the same - I (...) (25 years ago, 24-Jun-99, to lugnet.robotics)
|
| | | | |
| | | | | | Re: using nqc for first time —Dave Baum
|
| | | | (...) My first guess would be that its a software issue and not hardware. The ports should be nearly identical hardware-wise (unless you have a geoport enabled modem port). It could be that something else (AppleTalk?) is munging with the port. I can (...) (25 years ago, 24-Jun-99, to lugnet.robotics)
|
| | | | |
