My interpretation for this was for what they call the "Communication Hardware", the DX80 Sensor-Node that they recommend connecting to the Sure Cross® U-GAGE K50U Ultrasonic Sensor
They write 1-Wire, why would they bother mentioning it's a wire and not say that for Ground (1-Wire ground ?)
if that was not the One-Wire ™ interface invented by Dallas (subsequently acquired by Maxim and then AD)
(the concepts of 1-Wire serial communications and 1-Wire serial device select are related to One-Wire ™ interface)
they mention as well that there is a Sensor Configuration Tool which can configure the device, so there is definitely a way to send information to it. The tool runs on windows and you need a specific USB cable to connect to the device
I've read in the past about "sinking input to sensing device" in the context of 1-Wire communication (A "sinking" input implies that the device expects a connected wire or circuit to provide a path to ground (i.e., it "sinks" current). so may be it's just an enable pin that you drive LOW to activate the component ?
Dang... y'all boys are good -- REAL GOOD! This is the info I was dreaming of getting, but doubted anyone would care enough to give... THANKS - this is great stuff.
Just using logic, is there a chance this thing might constantly be sending (TX) an 8-bit reading, but using 1-bit "start" and "stop" signals so the receiver would know when to start reading a particular 8-bit data-point? as in, it sends a singe "1", then delays 50ms and sends "10101010," then delays 50ms and sends "0" and delays 50ms -- repeat, repeat, forever...
That would eliminate the need for the sensor to receive any commands. Because the sensor only does ONE thing, it can just constantly do it and when you ask for the "reading," it already forthcoming.
if it's a Serial 9600 bauds 8N1 communication, chances are there is a protocol to send the information
for example, the A02YYUW distance sensor has two lines Rx and Tx
When "RX" floats or is HIGH, the module outputs processed value, the data is more steady but the response time can be 300ms. When Rx is LOW, the module outputs real-time value at 10Hz with no processing.
the frame sent has 4 bytes
so you need a small parser to extract the distance.
It sounds like a standard half-duplex RS232 (UART) interface, so there would have to be some protocol that determines when it sends, and when it listens.
Possibly this is where the 'device select' line comes in ... ?
MODBUS is also mentioned in that datasheet ...
EDIT
According to the datasheet, the Sensor sends its data when requested over the 1-wire serial interface::
Thanks to all y'all who helped on this, but here's THE OFFICIAL RESPONSE FROM BANNER:
Hello,
The 1-wire interface on our devices is the proprietary Banner interface. Our sensors with 1-wire interface only work with our wireless radios with 1-wire serial interface.
If you have any other questions, you can reply to this email, chat through the web site, or call 800-450-8144 and ask for me. If I'm unavailable, please leave me a voice mail, or if you need immediate assistance, any one of our other Application Engineers can help you out.
True, But at $300, it's an expensive hack. I think some of Y'ALL might be able to do it, but the risk of failure is to high for me.
I'm assuming these "reputable" sensor manufacturers are aware of our hacking skills and have built the newer models to not work with Arduino/Pi/ESP -- lot's of lost profits! Have you ever met anyone at the "national chain" electrical supply businesses that knows anything?? NOPE! This way only the "Banner Engineers" can help you and they lead you right to another "Banner product" -- The "salesmen" are just there to place the order.
the cost of hacking the device is probably higher than buying the node anyway
it would make sense only if you needed lots of sensors and of course as the protocol is proprietary it could break at every update.
They did answer the question you asked - which was, "is this the AD/Maxim/Dallas 1-WireTM ?"
As suspected, the answer is, "No."
I would ask the follow-up question of whether they would provide the specification(s) for their proprietary Banner interface, so that you can implement it on your own system.
They may well say no - but there's no harm in asking ...
More likely, they don't want the hassle of having to publish & maintain public documentation, and to provide support for people asking them questions about it. Much simpler (ie, cheaper) to just keep it all in-house.
I suspect that they also feel that there's going to be very little demand from the Arduino community for a sensor that costs $300!