 | | 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 (...) (22 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 (...) (22 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 (...) (22 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 (22 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 (...) (22 years ago, 30-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Building a RCX™-compatible temperature sensor
|
|
An easy one, that has already be done numerous times... anyway, here is my implementation of a fully RCX-compatible temperature sensor, that provides correct values when used with standard RCX temperature routines. (2 URLs) RCX-compatible (...) (22 years ago, 30-Nov-03, to lugnet.robotics, FTX)
|
| |
| | 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 (...) (22 years ago, 30-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | WTF: Broken RCX units
|
|
Anyone have or know where I can find broken RCX units for parts? Thanks, Rand (22 years ago, 30-Nov-03, to lugnet.robotics.rcx)
|
| |
| | Re: Opening COM port error
|
|
In lugnet.robotics.rcx.java, Chris Phillips wrote: Hahaha, Your passionate condemnation of GC makes entertaining reading in light of the amount of work I have to do with lejos,Java,C++, etc for my final year undergraduate project. I will certainly (...) (22 years ago, 30-Nov-03, to lugnet.robotics.rcx.java)
|
| |
| | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
(...) It took me some time to figure out why, but you are right, the ambiguous transitions occur only while counting up. What you could do though would be to count +1 while going from state3 to state2_ambiguous, and correct "phantom transition" by (...) (22 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
