 | | NQC's future
|
|
I'm very interested in hearing from NQC users what their needs/wishes are for future enhancements. Here's my current list of updates/enhancements that I am working on. 1. Built-in and documented Spybot API. 2. Fast firmware download via USB tower (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics)
|
| |
| | Broken Mindstorms motors
|
|
We have several broken mindstorms motors. Tw got the shafts broken. Two just stopped turning. So, we decided to steal the shafts from one set to fix the other set. However, putting them back together has stopped the working but shaftless ones from (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx)
|
| |
| | Re: failure in communicaton between RCX & IR Tower
|
|
Nathan, I have done this trouble shooting step, ie. changing the timing. Unfortunately, it did not work. But, thank you though. Well, the a W2Kpro virtual machine approach did not work either... I guess my only alternative will be getting the (...) (21 years ago, 1-Dec-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Opening COM port error
|
|
(...) Tyler, Happy to be of help! Regarding Garbage Collection, I'm not usually one to criticise without being able to suggest a better alternative. In this case, I think most GC systems could be improved by mimicking the concept of "smart pointers" (...) (21 years ago, 30-Nov-03, to lugnet.robotics.rcx.java, lugnet.off-topic.geek)
|
| |
| | Re: "Non-Robolab" LabView functions
|
|
(...) Disagree. It's a matter of habitudes. Once you're familiar with the whole environment, you may write extremely complex programs without getting lost. For example, in our recent "Mars-mission" telerobotics project the complete programming -the (...) (21 years ago, 30-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) They do work! But they are usually used with two quadrature outputs (hence the name), while on RCX only one wire is used and the 4 states are encoded as 4 voltages levels. (URL) (Image courtesy Michael Gasperi) The sequence (clockwise) is (...) (21 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab, FTX)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) The way I understand it, it's really not the sensor's fault. The RCX and firmware together either can't or doesn't deal with the ambiguous voltage levels sometimes returned during two of the four transitions. If the RCX were fast enough that (...) (21 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
Could someone explain to me technically why this sort of of problem with the rotation sensor occurs? I know how quadrature shaft encoders are _supposed_ to work, and I can't see why this sort of thing should happen in the first place. >> Mark (21 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: "Non-Robolab" LabView functions
|
|
(...) Still waiting to hear from Dick about that. (...) I disagree that it's easier to understand and use. Possibly easier to learn or figure out without documentation, up to a point. But ease of learning is not the same as ease of use. Graphical (...) (21 years ago, 30-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: "Non-Robolab" LabView functions
|
|
(...) ---...--->snip I've not had the time yet to analyze the patch. Seems that you replace the first firmware handler. In Robolab the firmware is found under ..ROBOLAB\Engine\RCX1\Text. They simply have changed the extension .lgo to .txt and call (...) (21 years ago, 30-Nov-03, to lugnet.robotics.rcx.robolab)
|
