Jan Kandziora wrote
> Then maybe you don't have a shorted diode in the DS9503, but a burned
> series resistor in the same chip. That's a common mode of failure, too,
> I had them a while ago.
>
> This problem is usually created by connecting something to the Pin 2 GND
> of the DS9490R. -> CHECK YO
vermus wrote
> ps. Can you give a bus voltage from DS9490R ? In my case it ~ 1 Volt (3
> and 4 pin), but AFAIK sensors on parasite power needs 3-5V...
i was right..
"Typically, 1-Wire slave devices operate over the voltage range of 2.8V
(min) to 5.25V (max)."
Something wrong
Paul Alfille-2 wrote
> Page 5 of the datasheet (
> http://datasheets.maximintegrated.com/en/ds/DS9490-DS9490R.pdf) has a
> schematic including the DS9503 diode that might be a problem.
>
> On the other hand, it's probably not worth your time chasing this down,
> rather than just buying another 949
Paul Alfille-2 wrote
> For reference I've included the initialization sequence for a functioning
> DS9490R:
>
> DEBUG MODE
> libow version:
> 2.9p3
>
> .
>
> CONNECT: ow_usb_cycle.c:(68) Bus master found: 1:6
> DEFAULT: ow_usb_msg.c:(295) Opened USB DS9490 bus master at 1:6.
>CALL: ow_
>A possible bug is a shorted DS9503 protective diode in the device. This
>happens after static overvoltage on the bus line, e.g. wrongly connected
>+12V to 1W. Static discharge is unlikely, the diode is designed to
>survive a short peak.
>Open the DS9450 (TX5 screw under the label, two clips at th
I have DS9490R and "1-wire bus short circuit" in logs.
Cable don't connected. What is this mean? How to test device?
logs:
Apr 13 10:37:18 localhost OWFS[2461]: DEBUG: ow_select.c:(66) Selecting a
path (and device) path=/ SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00
00 00 00
Apr 13 1
just for memory.
you need to add to owfs.conf:
# With this setup, any client (but owserver) uses owserver on the
# local machine...
! server: server = localhost:3000
--
View this message in context:
http://owfs-developers.1086194.n5.nabble.com/owfs-not-able-to-connect-to-owserver-when-usin
Paul Alfille-2 wrote
> can you start with --debug ?
full line:
# /usr/bin/owserver --debug --error_level=9 --error_print=2 --foreground -c
/etc/owfs.conf --pid-file /var/run/owfs/owserver.pid
DEBUG MODE
libow version:
2.8p15
or
# /usr/bin/owserver --debug --error_level 9 --error_prin
Rick Bolen(gm) wrote
> /usr/bin/owserver -c /etc/owfs.conf --pid-file
> /var/run/owfs/owserver.pid --error_print=2 --error_level=4 --foreground
>
> I've read a few other reports of this lack of output, but found no
> solution.
>
> What am I doing wrong?
+1
Did you found solution?
--
View
Mark Phillips-2 wrote
> Thanks for the quick responses. I am running everything as root, I have
> created the mount point directory, and I am using --foreground, but
> owserver still exits immediately with no output.
Same problem on cubietruck (RP analogue) . may be it is neccesary to install
som
10 matches
Mail list logo
