 | | RE: Brainstorms GUID
|
|
Quoting "Russell C. Brown [RR-1]" <rcbrown@austin.rr.com>: (...) Well, one easy answer is to use a Dallas serial number chip. They are way less than a dollar in quantity. Actually each 1Wire device has a guaranteed unique ID. Some have EE memory for (...) (22 years ago, 12-Aug-02, to lugnet.robotics)
|
| |
| | Re: Brainstorms GUID
|
|
(...) > somewhere must administer who gets what ID numbers. (...) The trouble with all these fancy approaches is that they all require additional logic. It might not seem like *much* additional logic - but if the goal is to fit most kinds of (...) (22 years ago, 12-Aug-02, to lugnet.robotics)
|
| |
| | Re: Brainstorms GUID
|
|
All: I'm not sure I really understand what point is trying to be made. I thought that a globably unique id was a good idea and put them into RoboBricks. My choice was to use a 128-bit random number. There are other solutions. All of the other (...) (22 years ago, 12-Aug-02, to lugnet.robotics)
|
| |
| | Re: Brainstorms GUID
|
|
(...) Maybe I completely missed the point myself? I like your idea of intelligence so small it can fit into a brick, and then tie into upper levels of higher intelligence. That sounds like true distributed processing (a good thing) to me. Here's the (...) (22 years ago, 12-Aug-02, to lugnet.robotics)
|
| |
| | Re: Brainstorms GUID
|
|
(...) Presuming they can use different seeds, 32 bits is one chance of collision every 4,294,967,296 attempts. If they don't have random seeds then it doesn't matter a damn how many bits you have. The chances of collision on each reboot go up (...) (22 years ago, 13-Aug-02, to lugnet.robotics)
|
| |
| | Re: Brainstorms GUID
|
|
(...) That's what we thought as well. (...) If you use a pseudo random number generator with the same seed you will get the same `random' number. The obvious answer is don't do that. I personally use the /dev/random device on Linux which collects (...) (22 years ago, 13-Aug-02, to lugnet.robotics)
|
