Am 28.04.2016 um 19:53 schrieb Juliean Galak:
>
> Ok, I found owhttpd.init in that archive, in the rpm/src directory, and
> copied it to /etc/init.d/ I then rebooted. No apparent change - owhttpd
> doesn't seem to be running.
>
You have to activate the service. Installing that file should make the
"service" tool work as expected.
>> That's ok. Then what's the output of /sys/bus/w1/devices?
>>
>
> pi@raspberrypi ~ $ ls /sys/bus/w1/devices/
> 28-000007298911 28-0115655f03ff w1_bus_master1
>
Ah, 28-0115655f03ff is the same as /uncached/28.FF035F651501
There is a disagreement about byte order in chip IDs. Paul originally
chose to leave it as the bytes appear on the bus, but everyone else
(including Dallas/Maxim) seem to do it the other way around, flipping
the 6 middle bytes of the id. We cannot change this as not to break
existing installations.
As for the other devices listed, and some not listed, I expect your bus
to be electrically unreliable. Reading /uncached/ advises the w1
subsystem to do an extra "Search ROM" cycle and return the result, while
it does this automatically, too, and may get different results.
How do you wire your bus to the Pi? GPIO4 and nothing more? Level
shifter? DS2483 on I²C? Is there another owserver running on some device
in your network?
Which chips are connected, physically?
Kind regards
Jan
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
