 | | 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 (...) (23 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 (...) (23 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 (23 years ago, 30-Nov-03, to lugnet.robotics, 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 (...) (23 years ago, 30-Nov-03, to lugnet.robotics, FTX)
|
| |
 | | 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 (...) (23 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
 | | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
(...) Doesn't that mean that at any given count, you could still be off by 1, but now the odds of having an incorrect count are 50-50 instead of about one in 500? (...) There has been some discussion about whether this patch will work with Robolab, (...) (23 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
 | | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
(...) If FIRST doesn't allow NQC - I can't see it allowing patched RCX firmware. ---...--- Steve Baker ---...--- HomeEmail: <sjbaker1@airmail.net> WorkEmail: <sjbaker@link.com> HomePage : (URL) : (4 URLs) GEEK CODE BLOCK----- GCS d-- s:+ a+ C++++$ (...) (23 years ago, 30-Nov-03, to lugnet.robotics)
|
| |
 | | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
"Philippe Hurbain" <philohome@free.fr> wrote in message news:Hp4JAs.oK8@lugnet.com... (...) Much to my embarassment, I have to agree with Philippe that the patch doesn't work very well. I try to figure out what went wrong. (...) This is the expected (...) (23 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
 | | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
(...) <snip> That would be disappointing! I discarded the RIS software very early on. Dick, can you clarify this issue? (23 years ago, 30-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
 | | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
(...) I think RoboLab uses its own firmware, so patching FIRM0328.LGO won't help you unless you use the RIS programming environment. (Or NQC, but that apparently isn't allowed by FIRST?) (...) I've used FIRM0328.LGO with older (version 1.0) RCXes (...) (23 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
 | | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
Hello Don, (...) firm0309.lgo is firmware from RIS 1.5, while firm0328.lgo comes from RIS 2.0. Maybe RIS 1.5 can't download 2.0 firmware, never tried that... (...) I suggest you download BricxCC from (URL) and use its download utility (located in (...) (23 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
 | | Re: Universal Remote vs Lego remote
|
|
(...) Yes. I taught my Sony learning remote from the Lego remote and it works perfectly. (...) > remote be used to save additional commands? Yes - it can learn from the IR tower or from the RCX itself. (...) > Possibly a macro of sorts. (...) Yes - (...) (23 years ago, 29-Nov-03, to lugnet.robotics)
|
| |
 | | Re: Universal Remote vs Lego remote
|
|
Yes it works! I was curious and have done this last week... The 'learning' remotes are capable of remembering the codes needed for your IR bricks. You can programm the RCX to sent a code (message) and let the remote learn this. Later on your RCX can (...) (23 years ago, 29-Nov-03, to lugnet.robotics)
|
| |
 | | Re: Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
(...) I'm having trouble downloading the patched firmware. Robolab doesn't have a .lgo file anywhere in the program directory structure, so I don't have a filename to replace with the patched file. Downloading in Robolab seems to work, but I see no (...) (23 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
 | | Re: Robolab, byte codes and assembler
|
|
(...) Wow, that's far more than I expected! And thanks for the detailed explanation. I may have to look at it tomorrow - my daughter's birthday is today. <snip> (23 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
 | | Patched firmware to improve rotation sensor, was Re: Robolab, byte codes and assembler
|
|
Hello Dick, Looks great, but it doesn't seem to work well here: - counts up 2 by 2, but counts down correctly one by one - loses count, especially when counting up. My tests were done with a brand new, unmodified rotation sensor. I mounted a wheel (...) (23 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
 | | Universal Remote vs Lego remote
|
|
I'm very new to the whole robotics thing so forgive me if the answer to my question is obvious. Can a universal remote, the type that "learns" the function of other remotes, be used to "learn" the functions of the Lego remote? and.. If the IR tower (...) (23 years ago, 29-Nov-03, to lugnet.robotics)
|
| |
 | | Re: Robolab, byte codes and assembler
|
|
(...) Wow! This is a truly wonderful gift to the group. I know how hard it can be to patch raw binary like that. Many thanks for your efforts. I'm off to try it **now** ! ---...--- Steve Baker ---...--- HomeEmail: <sjbaker1@airmail.net> WorkEmail: (...) (23 years ago, 29-Nov-03, to lugnet.robotics)
|
| |
 | | Re: robotics
|
|
I found an Adobe PDF describing the 'AI Motor' part in English - there is some great detail there: (URL) that this unit is a motor with an integrated position sensor and a torque sensor with a daisy-chained serial bus to allow either a PC or their (...) (23 years ago, 28-Nov-03, to lugnet.robotics)
|
| |
 | | Re: robotics
|
|
(...) Wow! It seems to be exactly what I've been hoping to see for *years*. Motors and sensors daisy-chained together with some kind of serial protocol for addressing them. This system seems to allow you to have 31 sensors and motors connected (...) (23 years ago, 28-Nov-03, to lugnet.robotics)
|