Ahha! Found the problem! (Rather embarrassing for me).
The default package for owfs ships with a "fake" configuration file.
Literally it uses the "fake" bus-master -- a bus master that returns random
results to test the software rather than hardware.
Clearly the change shouldn't be difficult -- the file is in /etc/owfs.conf
and needs to be modified for your bus-master.
Here is the default "fake" owfs.conf:
----------------------------------------------------------------------------------
# Sample configuration file for the OWFS suite for Debian GNU/Linux.
#
#
# This is the main OWFS configuration file. You should read the
# owfs.conf(5) manual page in order to understand the options listed
# here.
######################## SOURCES ########################
#
# With this setup, any client (but owserver) uses owserver on the
# local machine...
! server: server = localhost:4304
#
# ...and owserver uses the real hardware, by default fake devices
# This part must be changed on real installation
server: FAKE = DS18S20,DS2405
#
# USB device: DS9490
#server: usb = all
#
# Serial port: DS9097
#server: device = /dev/ttyS1
#
# owserver tcp address
#server: server = 192.168.10.1:3131
#
# random simulated device
#server: FAKE = DS18S20,DS2405
#
######################### OWFS ##########################
#
#mountpoint = /mnt/1wire
#allow_other
#
####################### OWHTTPD #########################
http: port = 2121
####################### OWFTPD ##########################
ftp: port = 2120
####################### OWSERVER ########################
server: port = localhost:4304
On Fri, Apr 11, 2014 at 11:47 AM, Paul Alfille <paul.alfi...@gmail.com>wrote:
> This is an interesting error -- I haven't seen it before.
>
> For the record, the DS2405 isn't a bus master -- it's a one-pin quirky
> switch.
>
> I gather you are running the file system (owfs) and logging in remotely
> with ssh.
>
> There are a number of possibilities -- floating point endian errors might
> be widely distributed like this. The catch is that temphigh and templow are
> essentially constants unless you actively change them, so should give the
> same value every time they are read. Even more, all these values are cached
> briefly (15seconds for temperature by default) so a rapid re-read should
> give the same value.
>
> Perhaps other people have thoughts on this. I'm baffled.
>
> If I needed to duplicate your setup, which bus-master and which owfs
> version are you using?
>
> Paul Alfille
>
>
> On Fri, Apr 11, 2014 at 10:18 AM, Chris Green <c...@isbd.net> wrote:
>
>> I have owfs running on a Beaglebone Black, apparently working OK. The
>> 1-wire bus is connected via a DS2405 based USB device. It all
>> *appears* to be working OK and I get the expected directories as
>> follows:-
>>
>> /mnt/1-wire/05.4AEC29CDBAAB for the DS2405
>> /mnt/1-wire/10.67C6697351FF for the DS18S20
>>
>> The 'type' file in each directory is correct but the temperature,
>> temphigh and templow files in the DS18S20 directory just jump all ove
>> the place:-
>>
>> root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
>> 99.7799
>> root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
>> 5.40576
>> root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
>> 87.054
>> root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
>> 7.23288
>> root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
>> 0.416161
>>
>>
>> The system is remote from me at the moment but I will be back there in
>> the next few days. What should I check?
>>
>> --
>> Chris Green
>>
>>
>> ------------------------------------------------------------------------------
>> Put Bad Developers to Shame
>> Dominate Development with Jenkins Continuous Integration
>> Continuously Automate Build, Test & Deployment
>> Start a new project now. Try Jenkins in the cloud.
>> http://p.sf.net/sfu/13600_Cloudbees
>> _______________________________________________
>> Owfs-developers mailing list
>> Owfs-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>
>
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
