On Wed, Aug 15, 2012 at 1:45 AM, Pedro Côrte-Real <[email protected]> wrote: > Hi Paul, thanks for looking into this. I've gotten the modules in the > mail today and did some initial setup. I still have the DS2480B on > order but the simple case of doing a point-to-point wireless > replacement of a serial line seems to work fine. Once I get the > onewire bus chips I'll try the simple case of running owfs over this > link to see how reliable it is. It should work fine as there seems to > be prior art from as far back as 2007: > > http://www2.buoy.com/pipermail/weather/2007-February/007437.html
So I've finally gotten the DS2480B wired up to a xbee board and have been trying to get owfs working with it. My setup is: PC-(usb)->XbeeA-(wireless)->XbeeB-(UART)->DS2480B XbeeA and XbeeB are working in transparent mode which means they just behave as a serial line replacement. The communication between Xbees seems to be working. I've tested: - Connecting both to PCs and running picocom on ttyUSB to check communication - Connecting the TX and RX pins on XbeeB and verifying that everything I send gets echoed back (so the UART works) - Opening picocom on XbeeA with the final setup and verifying that I'm getting responses from the DS2480B I can't seem however to get owserver to communicate with the device. Here's how I'm running it from the PC: $ owserver --foreground --debug -d /dev/ttyUSB0 --8bit I've tried various variations on it without any luck. Here's the beginning of the log: DEBUG: ow_daemon.c:(166) main thread id = 3078133440 CONNECT: ow_avahi_link.c:(72) No Avahi support. Library libavahi-client couldn't be loaded CONNECT: ow_dnssd.c:(82) Zeroconf/Bonjour is disabled since dnssd library isn't found CALL: ow_parsename.c:(95) path=[] DEBUG: owlib.c:(79) Globals temp limits 0C 100C (for simulated adapters) DEBUG: ow_ds9097U.c:(267) Attempt 0 of 3 to initialize the DS9097U DEBUG: ow_ds9097U.c:(356) Send the initial reset to the bus master. DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1 DEBUG: ow_ds9097U.c:(434) wrong response (70 not 00) DEBUG: ow_ds9097U.c:(449) Failed first attempt at resetting baud rate of bus master /dev/ttyUSB0 DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1 DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1 DEBUG: ow_ds9097U.c:(434) wrong response (70 not 00) It repeats itself a lot after that. It seems owserver is trying to do baud rate changes on /dev/ttyUSB0 when that's just the UART used to communicate to the local Xbee, it does nothing to the remote UART that communicates with the DS2480B. Are baud rate changes necessary to setup the DS2480B? If so then owserver will have to learn how to do the Xbee specific commands to change UART settings on the remote end. Long-term that's probably the best solution so you don't have to depend on the default UART configuration the module happens to have. Although I haven't had much success with the onewire part the xbee specific hardware is great. I made a wireless relay with just a buffer chip between the Xbee IO pins and the relay to handle the current the relay needed. Libxbee seems pretty straightforward too with it's socket like interface. Pedro ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
