 | | Re: Rotating through a four-bit nibble
|
|
(...) With that limitation we'd be creating a register (or Turing) machine simulator, too. It would be interesting to see a real-world processor that only has increment and decrement instructions. I'm thinking the LEGO firmware doesn't support these (...) (21 years ago, 29-Sep-05, to lugnet.robotics, FTX)
|
| |
 | | Re: ROBOLAB Questions
|
|
Andrew, To the best of my knowledge the wait commands never turn off any motors. To do so would require that you could attach a motor modifier to the command. It would also limit the commands usefulness. If you really want a wait for distance (...) (21 years ago, 29-Sep-05, to lugnet.robotics)
|
| |
 | | Re: Can't upload new program after I have used LNP under brickos
|
|
(...) Well, thanks for the help, that didn't actually work. But I found it out, what was my fault. In my Program I changed the LNP Base adress of the robot. After that the robot did not react to the default adress 0. So, at the end of the program I (...) (21 years ago, 29-Sep-05, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: New technique: three position piston control
|
|
(...) <snip> I used some axle joints to optimise cylinder position limiting in normal logic (...) Do you have a website where I can peruse your work? (...) (21 years ago, 28-Sep-05, to lugnet.technic, lugnet.robotics)
|
| |
 | | Re: New technique: three position piston control
|
|
(...) No, I was so busy at work that I missed a couple of days online! I had a look at both, but a dual piston scheme works better for steering because of equalising the piston area and pushing at least 3 switches. In fact I have two cylinders in (...) (21 years ago, 28-Sep-05, to lugnet.technic, lugnet.robotics)
|
| |
 | | Re: Just a few highlights and points...
|
|
(...) Nodes I haven't seen have a value of zero. Every time I [re]enter a node, I add 1 to the value that's currently there. If there's no right turn (I follow the right "wall"), I add 2. When the total is 4, you're done searching that node. So, (...) (21 years ago, 28-Sep-05, to lugnet.org.us.laflrc, lugnet.robotics)
|
| |
 | | Re: Just a few highlights and points...
|
|
(...) Yes, I'm sure that's it - you just *imagined* you maze-solver worked ;-). (...) Hmm. OK, that's got me confused. I *know* I'm storing more information than needed, but each node in the path only takes 2 bits? If those two bits encode the (...) (21 years ago, 28-Sep-05, to lugnet.org.us.laflrc, lugnet.robotics)
|
| |
 | | Re: Just a few highlights and points...
|
|
(...) I must have done something wrong. I'm only keeping 2 bits per node, instead of 8. Steve (21 years ago, 28-Sep-05, to lugnet.org.us.laflrc, lugnet.robotics)
|
| |
 | | Re: Just a few highlights and points...
|
|
(...) I didn't read it. But if I had... (...) Agreed. although if we start running mazes with loops (like Alegomazer did) I think mapping, physically, the maze will likely be needed - if for no other reason than to know when you've closed a loop. (...) (21 years ago, 28-Sep-05, to lugnet.org.us.laflrc, lugnet.robotics)
|
| |
 | | Re: Just a few highlights and points...
|
|
Brian, don't read this. (he's trying to work it out for himself...) :) (...) While this is a good "brute force" method of mapping a maze, you'll be saving, and trying to use quite a bit of information that you don't need. Assuming you can identify (...) (21 years ago, 28-Sep-05, to lugnet.org.us.laflrc, lugnet.robotics)
|