Hello Jan,

Thank you for the answer and the help!

I understand this so:
owfs does not knows on which bus a device is connected (only it is 
cached). when I access with /<ADDRESS> owfs must check all buses where 
this decvice is connected. This maybe a problem for the w1-kernel-modul, 
when I use more than one bus-master.
When I access with /<BUS>/<ADDRESS> owfs access only to this one bus, 
without checking presence/reset the bus.

This mean, it is always better to access over /<BUS>/<ADDRESS>, in order 
to avoid problems with w1-kernel-modul and also for the performance.

Thank you verry much for the help, to understand this behavior

best regards
  eni

On 05.11.2016 22:31, Jan Kandziora wrote:
> Am 05.11.2016 um 21:54 schrieb Enrico Hoepfner:
>> Hello Jan,
>>
>> Thank you for the answer!
>>
>>    I have 4 buses because
>> 1) DS18B20 an DS2408 need different pullup-resistors
>>
> How? Both should be fine with 1.5k to 3.3V.
>
>
>> 2) the 4 buses goes to different locations
>>
> Star topology. Okay.
>
>
>> I dont understand why owfs is checking presence of the device of all
>> buses - seems like owserver has forgotten where the device is connected
>> and check all buses, if there is presence this one.
>>
> This is a deliberate choice. Owfs does not remember where a device was
> connected. Because it could have been moved since last access. It's up
> to the application to keep track.
>
> 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
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers


------------------------------------------------------------------------------
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
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to