 | | 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)
|
| |
| | 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)
|
| |
| | "Non-Robolab" LabView functions
|
|
I've been experimenting with some of the LabView icons available in "Investigator" mode in Robolab (under the "hourglass" item on the outermost menu). They seem to cause some odd behavior sometimes. It seems like it's especially a problem if one of (...) (22 years ago, 30-Nov-03, to 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, (...) (22 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
|
|
"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 (...) (22 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? (22 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 (...) (22 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) Should be legal, perhaps. But I was just suggesting that before sending him off to try to patch the firmware, he might want to make sure it was legal to do so. Although RIS and RoboLab may not use the same identical firmware, that doesn't (...) (22 years ago, 29-Nov-03, to 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 (...) (22 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
|
|
(...) 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 (...) (22 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> (22 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) My arguments would be: 1. The firmware/sensor arrangement is _broken_. Fixing it should be legal. 2. The FIRST rules permit using different firmware implicitly, because they permit using RIS or Robolab, which requires different firmware. 3. (...) (22 years ago, 29-Nov-03, to 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 (...) (22 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
Following up from my earlier post, I have completed a firmware patch for the rotation sensors. This post contains the patch with installation instructions followed by a technical description. A long post but hopefully more than made up by the value (...) (22 years ago, 29-Nov-03, to lugnet.robotics, lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) All this talk of patching firmware to correct for problems in rotation sensor readings is very interesting, but I think you may be approaching the problem a bit too directly. First, if the competition rules specify the programming environments (...) (22 years ago, 28-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
In lugnet.robotics.rcx.robolab, Claude Baumann wrote: <snip> (...) The main need is to return to the starting point after completing various challenges. I think the challenges also involve objects at known positions compared to the starting point (...) (22 years ago, 28-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
---...--->snip (...) I guess the competition asks you to run a certain distance as precisely as possible, or/and do some precise turns. We often experienced this kind of challenges in our school. The best way seemed to be to collect statistical (...) (22 years ago, 28-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) <snip> (...) I'm quite interested in the alternative firmware for myself. However, for this particular problem, if a correct rotation count is my "Apollo 13's needed filter", then Robolab is the "cover of the flight manual" - it's what I have (...) (22 years ago, 28-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) It really is. I do think somebody made a mistake specific to the rotation sensor, though. I haven't decided yet whether it's the firmware, the sensor, or just the overall mechanism. I can understand how it got past quality control - sometimes (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) Unfortunately, I fear the comparison is all too true! So, is my robot going to blow up? ;) (...) I'd appreciate some specifics. So far, I have not been able to find a way to do this in Robolab. I wrote some code to test raw sensor values and (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
