 | | Re: Pneumatic Quadraped 242
|
|
(...) snip (...) I started working on articulated head and tail. Quad242 has a very large footprint, and walks inefficiently. One of the reasons for large feet is center of gravity. The center of gravity on Quad242 is just a little behind the center (...) (22 years ago, 1-Dec-03, to lugnet.technic, lugnet.build, lugnet.robotics, FTX)
|
| |
| | Re: New LEGOTIC Hand
|
|
(...) Even more impressive now than the prototype I saw some time ago... Very clever use of Bionicle parts, would be a winner if a "Technic lame parts" contest was organized! XP to lugnet.robotics Philo (22 years ago, 1-Dec-03, to lugnet.technic, lugnet.robotics)
|
| |
| | Re: an idea, can someone tell me if this is possible/been done before/etc?
|
|
(...) Plenty of people have build eight legged walkers - that's not all that hard. However, the machine in WWW is supposedly very flexible and could climb near vertical cliff-faces, etc. You'd need at least two or three motors per leg to get that (...) (22 years ago, 1-Dec-03, to lugnet.robotics)
|
| |
| | an idea, can someone tell me if this is possible/been done before/etc?
|
|
Or, provide suggestions on how to do it? I saw Wild Wild West the other day and was looking at the giant spider robot and wondered if making such a "sipder" robot is possible with lego robotics? Would it be possible? Has anyone done it? Does anyone (...) (22 years ago, 1-Dec-03, to lugnet.robotics)
|
| |
| | 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" (...) (22 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 (...) (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)
|
| |
| | math library
|
|
Hello all. About a year ago I researched math functions so I could write some for the RCX. I found some power series functions that work really well. I see another message here posted by "nanobapt" has also posted some functions so I tested his (...) (22 years ago, 29-Nov-03, to lugnet.robotics.rcx.legos)
|
| |
| | "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
|
|
(...) 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++++$ (...) (22 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 (...) (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: 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 - (...) (22 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 (...) (22 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 (...) (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)
|
| |
| | 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 (...) (22 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: (...) (22 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 (...) (22 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 (...) (22 years ago, 28-Nov-03, to lugnet.robotics)
|
| |
| | 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: Opening COM port error
|
|
(...) Ahh, Garbage Collection. <rant soapbox="on" eyes="glazed" dinosaur="true"> In my mind the worst thing that has happened to modern compiler languages is excessive reliance on Garbage Collection. This is analogous to leaving half-empty soda cans (...) (22 years ago, 29-Nov-03, to lugnet.robotics.rcx.java)
|
| |
| | GP2D12 Please help
|
|
Please help. I just recently got a Sharp GP2D12 ir distance ranger plus RCX interface device from mindsensors. It is pretty cool, however I am getting alot of flucuation in the readings and in turn I think that i am losing out on range. The maximum (...) (22 years ago, 29-Nov-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Opening COM port error
|
|
(...) Hi Chris, Thanks for your reply. You're reply confirmed my suspicion about leaving the port object lying around. I think I'll try your first suggestion of 'deleting' the port object at the end of each routine. I hope you dont mind me asking (...) (22 years ago, 29-Nov-03, to lugnet.robotics.rcx.java)
|
| |
| | 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)
|
