 | | color sensor
|
|
hi all, first for all a happy christmas to everybody. I just ran into this nice looking color sensor TCS230, which might be useful for detecting Lego colors. (URL) Mientki (19 years ago, 25-Dec-05, to lugnet.robotics.rcx)
|
| |
| | Re: Bluetooth
|
|
Beware of the fact that the outputs on the RCX output PWM. You will probably want rectification, and need smoothing to get a nice constant voltage (some regulator in the LM series) to power the board. Anyway - it sounds like a really good idea - I (...) (19 years ago, 2-Dec-05, to lugnet.robotics.rcx)
|
| |
| | Re: Bluetooth
|
|
(...) Have a look at (URL) Here you reach much higher baud rates Cheers (19 years ago, 2-Dec-05, to lugnet.robotics.rcx)
|
| |
| | Re: Bluetooth
|
|
(...) Great! I'll look forward to its development....any ideas on what you will use it on first? Chris (19 years ago, 2-Dec-05, to lugnet.robotics.rcx)
|
| |
| | Bluetooth
|
|
I’ve just started a little project of building an interface between a RCX and a Bluetooth. For power supply I’m thinking of using one of the outputs on the RCX and for communication I’ll use the IR port(2400-baud), similar to Mindsensors´s RCX to (...) (19 years ago, 1-Dec-05, to lugnet.robotics.rcx)
|
| |
| | Help me convert this train program to use events (NQC)
|
|
For Christmas I'm setting up a LEGO train on top of a narrow wall, so it has to operate like a shuttle -- stop at each end and reverse motor direction. My first attempt had a train regulator attached to a polarity switch, with the switch being (...) (19 years ago, 28-Nov-05, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc, lugnet.trains, FTX)
|
| |
| | Re: Problem with IR
|
|
(...) I tried adding -v & > output.txt but it didn't work. All it did was light up the towers LED for a bit then quit back to the command line. It did work when I used -v, showing all the sent bytes, but the download still failed. I also managed to (...) (19 years ago, 24-Nov-05, to lugnet.robotics.rcx)
|
| |
| | Re: Problem with IR
|
|
(...) Can you post the output generated by NQC when you add -v to the command line? nqc -Susb -TRCX2 -v -d filename.nqc > output.txt Or you could just email it to me directly. John Hansen (19 years ago, 24-Nov-05, to lugnet.robotics.rcx)
|
| |
| | Re: Problem with IR
|
|
(...) Ok, your right they are separate, so that if I left the second -Susb out, my program wouldn't download via the USB tower, but would go to my other RCX via the serial tower. My batch-file is this: nqc -Susb -firmfast c:\newrcx~1.lgo nqc -Susb (...) (19 years ago, 22-Nov-05, to lugnet.robotics.rcx)
|
| |
| | Re: Problem with IR
|
|
(...) Why couldn't it be that if the firmware downloads? When I download my firmware, it's completely seperate from when I download nqc progs. Hope you get it sorted soon. (...) (19 years ago, 22-Nov-05, to lugnet.robotics.rcx)
|
| |
| | brickOS on Mac OS X
|
|
Hello, I'm trying to get a recent brickOS (0.9.0) working on Mac OS X 10.4.3. I have an RCX 2.0 with the USB tower. I have a cross-compiler (gcc 3.2.2) that apparently works, and using the firmware download program included with lejOS (specially (...) (19 years ago, 22-Nov-05, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
| |
| | Re: Problem with IR
|
|
(...) Your correct, it isn't that. I know all about -Susb, because I'm using a serial and a usb tower simultaneously with respective rcx's. One sets in a box so their is no IR crossover. I have swapped over the towers. The USB worked perfectly in (...) (19 years ago, 21-Nov-05, to lugnet.robotics.rcx)
|
| |
| | Re: Problem with IR
|
|
(...) Since posting I found the old post reporting this problem and have since tried this fix. Alas it didn't work but I will try it again. Steve (19 years ago, 21-Nov-05, to lugnet.robotics.rcx)
|
| |
| | Re: Problem with IR
|
|
(...) This probably isn't it, but if you're using the command line, have you included the -Susb parameter to tell NQC you're using USB? (This will takes ages to post as my email isn't working, so sorry if you have 5 other replies before this one...) (...) (19 years ago, 20-Nov-05, to lugnet.robotics.rcx)
|
| |
| | Re: Problem with IR
|
|
(...) Possibly you are experiencing a problem with the USB Tower driver which I have heard several other users report. Other users who had this problem were able to fix it by editing the USB Tower timeout values using the LEGO USB Tower Control (...) (19 years ago, 21-Nov-05, to lugnet.robotics.rcx)
|
| |
| | Problem with IR
|
|
For some reason I'm having a problem downloading with NQC. I previously had the serial tower set up at the end of a track. The rcx on my robot goes up and down it. I used to have occasional problems with the IR comms, but I'd change the battery and (...) (19 years ago, 19-Nov-05, to lugnet.robotics.rcx)
|
| |
| | RE: different light readings...
|
|
Hi David, I am sorry that I did not clarify my question. Thank you very much for taking the time out to help though! I fully understand that variations that light sensor produces, and I do make calibration the first thing to do before I run my bots. (...) (19 years ago, 15-Nov-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | Re: different light readings...
|
|
(...) Different light sensors will produce different readings. The range of readings you get will also vary between different light sensors (for example, between the same white surface, and the same black surface, one light sensor might have a (...) (19 years ago, 15-Nov-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | different light readings...
|
|
Hi, I have these 2 different light sensors. One reads "41" vs another reads "34" on the same area. I have troubleshoot it by switching ports, different RCX brick. The reading different stays the same. Is this reasonable because they might have a (...) (19 years ago, 14-Nov-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | Re: programming tips
|
|
(...) With the standard firmware, not that I know of. You *can* block all incoming signals by continuously broadcasting. Having a task repeatedly transmit a simple message endlessly means that the RCX can't recieve normal messages, possibly (...) (19 years ago, 2-Nov-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
