 | | Re: Multiplexing 4 touch sensors on an RCX input port
|
|
(...) Good analysis. Series can work quite well as long as you know that the touch sensors are touched mutually exclusively, but you are right parallel doesn't work well. I remember trying to come up with good resistance values to do parallel, and (...) (21 years ago, 9-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Re: Multiplexing 4 touch sensors on an RCX input port
|
|
(...) While in theory, this sounds very cool, in pratice, I doubt it will work quite that well. The biggest problem will be that the standard touch sensors may not be 100% on when you press it. This means the sensor itself can provide some (...) (21 years ago, 9-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Re: Multiplexing 4 touch sensors on an RCX input port
|
|
(...) I don't think that would work very well, as the lights have a rather low resistance, lower than a pressed touch sensor ((URL) as a purist you can use the cybermaster sensors to multiplex three inputs ((URL) Jürgen Stuber <stuber@loria.fr> (...) (21 years ago, 9-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Re: Multiplexing 4 touch sensors on an RCX input port
|
|
(...) LEGO purists use LEGO light bricks as resistors. I created potentiometer bricks, where the resistance is variable for each brick. Two stacks of 4 potentiometer bricks can be seen to the left of the RCX. In this case each stack puts the (...) (21 years ago, 9-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Multiplexing 4 touch sensors on an RCX input port
|
|
You can use four touch sensors per input port on the RCX. The Cybermaster touch sensors have resistors in parallel, and this is how the Cybermaster knows which implement is attached to the tracked robot. It uses its sensor input as a temperature (...) (21 years ago, 5-Sep-03, to lugnet.robotics.rcx)
|
| |
| | RE: leJOS & BricxCC news
|
|
(...) OK, I've looked at your wish list and have the following comments with respect to how I see the pbForth implementation of DCC. 1. How important is it to have more than one port with DCC capabilities. The reason I'm asking is that it "would be (...) (21 years ago, 7-Sep-03, to lugnet.robotics.rcx, lugnet.trains, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: USB Tower Performance [was leJOS/BricxCC news]
|
|
(...) Doh! I forgot about Odd parity and the USB tower. I will see about fixing that little problem. Is your quad speed boot loader source significantly different from Kekoa's fastdl.s (with the parity disabling code removed)? I'd like to see it if (...) (21 years ago, 7-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Re: leJOS & BricxCC news
|
|
(...) Hmmm. I was seriously considering writing a leJOS package to support the LDCC IR Protocol. (Here's why: (URL) ) What capabilities were you going to add? Depending on your timeline, you might convince me to try FORTH. (21 years ago, 7-Sep-03, to lugnet.robotics.rcx.java, lugnet.robotics.rcx, lugnet.trains, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: USB Tower Performance [was leJOS/BricxCC news]
|
|
In a recent post, John Hansen raised some questions about USB Tower [1] quad speed downloading and [2] varioustimeouts and difficulty with certain optocdes. Here's a bit of an explanation. Lots of technical detail for those that are interested. (...) (21 years ago, 6-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Re: Lego Mindstorms Robotic Sumo Question
|
|
(...) Thanks Steve! Everything I wanted to know I found out on that website. Great information. Thanks again! David Perdue www.geocities.com/imroboguy (21 years ago, 6-Sep-03, to lugnet.events, lugnet.robotics.rcx)
|
