 | | Re: bad motor output because of bad lego firmware?!
|
|
(...) The firmware (at least version 0328) intentionally prevents you going directly from forward to reverse (or vice versa). I guess the designers felt this would be too rough on the motors. Try inserting a Wait(50) in your first loop. It'll work (...) (20 years ago, 28-Oct-04, to lugnet.robotics.rcx.nqc)
|
| |
| | bad motor output because of bad lego firmware?!
|
|
Hi there, I've spent the last two days trying to write a function in NQC that transfers data to the Lepomux I/O-extender. The data transfer is normally done by connecting the Lepomux to one of the motor ports. Each transition from one motor state to (...) (20 years ago, 28-Oct-04, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Help installing brickOS
|
|
(...) Sure. The configure script tries to find the gcc cross compiler toolchain for the brick's hitachi processor. This chain is needed to compile brickOS to a program that can be run by the RCX. But it seems that you did not install the tool chain. (...) (20 years ago, 28-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Help installing brickOS
|
|
(...) I believe that I had the exact same problem a few weeks ago, but I found that using a pre-built package takes a lot of the hassle out of installing BrickOS. The pre-built packages can be found at: (URL) hope this helps, Timothy (20 years ago, 27-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | Help installing brickOS
|
|
I'm trying to install brickOS 0.2.6.10.6 on WIN NT. After unning "configure" it's busy for along time, and terminates with the message -"No Hitachi gcc compiler found. Please install compiler and try again." Any suggestions? Thanks, Jordon (20 years ago, 27-Oct-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Piggybacking sensors, but in a different way
|
|
(...) While you may be able to connect a touch sensor (passive) to two RCXs, I doubt that would work with a light sensor (any active sensor). Mainly, because one of them must be set to power the sensor. Normally, when the sensor is read by an RCX, (...) (20 years ago, 26-Oct-04, to lugnet.robotics.rcx)
|
| |
| | Piggybacking sensors, but in a different way
|
|
Is it possible to piggyback 1 sensor onto two rcx's? For instance, have one light sensor connected to port 1 of two different rcx's at the same time. The purpose would be for one rcx to control chassis movement, and another to control manipulator (...) (20 years ago, 26-Oct-04, to lugnet.robotics.rcx)
|
| |
| | Re: Rotation sensor limitation
|
|
(...) The simplest answer is to try it. Yes the limit that an RCX 16 bit integer can hold is 32767. From there things go to -32768 down to zero I think. (...) Kevin (20 years ago, 25-Oct-04, to lugnet.robotics.rcx.nqc)
|
| |
| | Robolab/RCX program code size and limits.
|
|
Hi, I'm using Robolab 2.5.3 and RCS firmware revision 03.01 03.28. I have a couple of questions: - I want to demonstrate the difference in code size between a program written using subroutines versus a program written using subVi's. How do I (...) (20 years ago, 24-Oct-04, to lugnet.robotics.rcx.robolab)
|
| |
| | Rotation sensor limitation
|
|
I use a rotation sensor for a brick sorting machine – hence I need to know the limitation of the rotation sensor. What happens when the rotation sensor exceeds 9999 as shown on the LCD display? Apparently the rotation sensor can still keep track of (...) (20 years ago, 24-Oct-04, to lugnet.robotics.rcx.nqc)
|
