Am 05.12.2016 um 16:39 schrieb Mick Sulley:
> OK more research and I have made a bit of progress.
>
> adding
>
> server: fake=10.053C8A010800,10.2AFE89010800,10.90F889010800
>
> to owfs.conf creates these devices with random values, different at each
> read. They can be split over different lines e.g.
>
> server: fake=10.053C8A010800
> fake=10.2AFE89010800,10.90F889010800
>
fake= is a hostadapter option. What you defined here is
* a fake hostadapter with a connected 10.053C8A010800 which can only be
seen by owserver.
* another fake hostadapter with a connected 10.2AFE89010800 and
10.90F889010800 which can be seen by all programs using owlib directly
(and having -c /etc/owfs.conf on their command line).
> Also you can limit the values -
>
> --temperature_low=20.1
> --temperature_high=22.1
>
Again, these are options used by all programs using owlib directly and
having -c /etc/owfs.conf on their command line.
> Is there any way to set individual temperatures for fake devices?
>
No. All fake devices share the same static data and do not have
individual properties.
>
> Using 'tester' in place of 'fake' creates the device with a consistent
> value, but there does not seem to be any way to control what that value
> is, --temperature_low=20.1, --temperature_high=22.1 has no effect. The
> values seem to be different for each device, but all are many hundreds
> or thousands of degrees.
>
IIRC tester is different from fake only in how the cache is handled.
Maybe someone else has more insight.
Kind regards
Jan
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
