 | | 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)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
OK You do something great, and all the world is looking at it, finding the finest detail one could have made much better. That's the power of internet-exchange. Don't take this personally. I only wanted to remind the great job they did at LEGO's (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) Please don't take my post as a criticism of the original firmware, I merely wanted to point out alternatives. I agree, the 3ms sample rate is more than adequate for most applications. (...) Yes, the RCX is rugged in many respects, but I think (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) We should not forget that the RCX has initially been designed for kids. So the standard firmware should be considered according to the initial aims, which were to provide a really great tool - toy for children. Therefore the firmware designers (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) By contrast, BrickOS continuously samples each sensor at a rate of about 6.7 samples per millisecond. This is 20 times more often than the standard firmware. It's no wonder it's more accurate at higher rotation rates. Of course, it also (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
---...--->snip (...) Welcome to LEGO Mindstorms robotics: do great things in real world with imperfect tools and objects. That's what makes it so interesting. It's always the Apollo 13 challenge: "Here guys, that's what they have on bord! Come on (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
