 | | Re: Gp2D12 Distance Sensor interface to RCX —Steven Nickle
|
| | | They don't need to be all active, just appear that way. I am assuming a dip switch to permanantly deactivate unused, ports. Software control of connected ones would be nice. Usage would go like this: 7 Global variables, a thread checks them on a (...) (23 years ago, 19-Oct-01, to lugnet.robotics)
|
| | | |
| | | | | Re: Gp2D12 Distance Sensor interface to RCX —Stephen Edwards
|
| | | | (...) Sounds like you have a fairly good idea of how you want to use it, and it all makes sense. The hardware can be simplified quite a bit if this is the typical usage pattern, though. (...) Since the RCX is already storing the values for use by (...) (23 years ago, 19-Oct-01, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Gp2D12 Distance Sensor interface to RCX —Steven Nickle
|
| | | | about 3 times a second is fine, for most applications. A continous power option would be handy sometimes. If I remember right the 50ms, is the charge time required for the cap to get to power to activate the gp2d12, not for it to actually startup (...) (23 years ago, 19-Oct-01, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Gp2D12 Distance Sensor interface to RCX —Philippe Hurbain
|
| | | | The 50 ms period _IS_ the startup time of the GP2D12 itself, and the time interval between two distance measurements. See oscilloscope trace (top of page): www.philohome.com/se.../scope.htm Philo (...) (23 years ago, 20-Oct-01, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Gp2D12 Distance Sensor interface to RCX —Rainer Balzerowski
|
| | | | (...) Just for your remembrance, i build something like that based on the schematics of Michael Gasperi. Please have a look here : (URL) (23 years ago, 20-Oct-01, to lugnet.robotics)
|
| | | | |
