 | | Re: Problem of comm. btw. PC & RCX in lejos2.0!?
|
|
Thank you very much, Paul! Laurence (24 years ago, 14-Aug-02, to lugnet.robotics.rcx.robolab)
|
| |
 | | Re: Problem of comm. btw. PC & RCX in lejos2.0!?
|
|
(...) It sounds as though you don't have the rcxcomm shared library on your LD_LIBRARY_PATH. Details should be in the readme's in the rcxcomm directory in the distribution. In general you'll get better answers to this sort of question if you (...) (24 years ago, 14-Aug-02, to lugnet.robotics.rcx.robolab)
|
| |
 | | Re: 0.2.4 and W2k...I really need help...
|
|
(...) ... (...) Did you try to use a current version of cygwin ? looks like cygwin-B20 which is a little bit stoneaged -Volker (24 years ago, 14-Aug-02, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: Brainstorms -- A Simple Unique Addressing Scheme
|
|
(...) [snip DCC references] (...) That might be workable. I2C does not really have a broadcast message (General Call is close, but not quite). However, just scanning the I2C bus for 1024 addresses to find what the current address of the module is (...) (24 years ago, 14-Aug-02, to lugnet.robotics)
|
| |
 | | Re: Brainstorms -- A Simple Unique Addressing Scheme
|
|
There's been a lot of messages on how to determine unique addressing for intelligent peripherals. Model railroading has solved this problem in a fairly easy way. THe NMRA (National Model Railroading Association) defined the DCC (Digital Command (...) (24 years ago, 14-Aug-02, to lugnet.robotics)
|
| |
 | | Re: Brainstorms
|
|
(...) Andy: I can understand not wanting to read the I2C spec., I haven't done it in a while myself. However, you are going to have to do a little homework on I2C. There is no real way around it, the bus is sufficiently complex that one's intuition (...) (24 years ago, 14-Aug-02, to lugnet.robotics)
|
| |
 | | pc mouse
|
|
Does anyone have schematics for making rotation sensors from an old pc mouse? Scott ___...___ Chat with friends online, try MSN Messenger: (URL) (24 years ago, 14-Aug-02, to lugnet.robotics)
|
| |
 | | Re: Scout and USB Tower
|
|
Make sure that you tell nqc (or MacNQC) that you are using a Scout. You can do this by adding -Tscout to the command line (NQC) or selecting the appropriate target in the preferences dialog for MacNQC. The USB tower and Scout seem to be very (...) (24 years ago, 14-Aug-02, to lugnet.robotics.scout)
|
| |
 | | Faulty Output
|
|
I am writing to see if anybody has any idea on how to fix a badly functioning output on my RCX 1.0 . The problem that I have encountered is that output C does not respond to any forward commands. However, it does respond to backwards commands. I (...) (24 years ago, 13-Aug-02, to lugnet.robotics)
|
| |
 | | Re: Brainstorms
|
|
(...) There are only 1024 maximum addresses. There are more than 1024 I2C chips out there. Ergo, there are address conflicts between some of the chips out there. Unfortunately, there is no requirement that 2 chips at the same address implement the (...) (24 years ago, 13-Aug-02, to lugnet.robotics)
|
| |
 | | Re: Brainstorms
|
|
(...) I thought Philips kept a master registry of all the hardwired I2C addresses allocated to each chip vendor? That should mean that just reading the hardwired address is enough to tell you what *kind* of device you've found. ---...--- Steve Baker (...) (24 years ago, 13-Aug-02, to lugnet.robotics)
|
| |
 | | Re: Brainstorms
|
|
(...) I have read this dicsussion, and have been most interested. From what I can understand (I have no current desire to read the I2C spec) the random ID number will identify that device on the bus once it is detected (or the permenant number, (...) (24 years ago, 13-Aug-02, to lugnet.robotics)
|
| |
 | | Re: Brainstorms
|
|
(...) There are many more options available than the three you list above. Note that there are far more microcontrollers in small packages with UART's than there are ones that have built in I2C. The UART only ones cost way less too. Many of the (...) (24 years ago, 13-Aug-02, to lugnet.robotics)
|
| |
 | | Re: Brainstorms
|
|
(...) [snip hot pluggable] (...) That is only a partial bus scan. It does not tell you what is at each address. A full bus scan allows people to plug arbitrary devices into the bus and allows the bus master to to reliably figure out what has been (...) (24 years ago, 13-Aug-02, to lugnet.robotics)
|
| |
 | | Re: Brainstorms
|
|
(...) I will contrast the decisions made by the Cricket team with the decisions made by the RoboBrick team. For reference purposes the RoboBrick home page is at: (URL) reasons for avoid centralized solution] (...) The RoboBrick team also asked (...) (24 years ago, 13-Aug-02, to lugnet.robotics)
|
| |
 | | Re: Brainstorms
|
|
Hi, (...) Weird idea ... (...) It's way simpler: You just send the address and wait for the acknowledged via the data line. Then you just don't continue ... you don't even need read access to the clock line for this. IMHO something that can carry (...) (24 years ago, 13-Aug-02, to lugnet.robotics)
|
| |
 | | Problem of comm. btw. PC & RCX in lejos2.0!?
|
|
Hi, all! | |Under the instream directory (of lejos 2.0 package), I'd like to |download Read.java to RCX to |read the value sent from PC with Write.java running on it in order to |write a number to RCX. However, when I tried to execute the |bytecode (...) (24 years ago, 13-Aug-02, to lugnet.robotics.rcx.robolab)
|
| |
 | | Re: Brainstorms
|
|
(...) Since I had to support hot-pluggable devices on the bus (not my idea), I had to continually scan the bus. Unfortunately, that was several years ago and I don't remember all of the details. It took either a zero-length read or a zero-length (...) (24 years ago, 13-Aug-02, to lugnet.robotics)
|
| |
 | | RE: Brainstorms
|
|
<snipped Fred's excellent Cricket description> (...) Again, I need to go back to my real-world fire alarm experience and say that this makes very good sense. Nobody gives much thought to the alarm systems in their building. They must meet very tough (...) (24 years ago, 13-Aug-02, to lugnet.robotics)
|
| |
 | | josx.rcxcomm.SocketProxy
|
|
Hi there, I'm using OSX with lejos and have got it working fine, but am wanting to get using the "rcxcomm" part, i can compile the examples, but can't start up the SocketProxy, does anyone know how to do this in OSX/linux? they say you have to: "Add (...) (24 years ago, 13-Aug-02, to lugnet.robotics.rcx)
|