 | | 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)
|