On 12/06/2016 01:45 PM, Johan Ström wrote: > On 06/12/16 13:38, Martin Patzak (GMX) wrote: >>> By using the /latesttemp mentioned earlier, you only perform the read, >>> and should thus not suffer from timeouts (given that the bus is not >>> already backed up with previous queries). >>> Note that a convert must always be triggered by using the >>> /simultaneous/temperature endpoint before. >> yes, I do exactly as you say, but cannot read a 85 degC value! >> Why is it only me??? Others seem to read 85 degC fine >> >> Is anybody with a LinkUSB able to read 85 degC? > Based on the diff posted by Stefano 2h ago, it looks like it actually > rejects any 85 readings (invalidly, if I've understood everything > correct). So that should probably be patched, then it should work as > expected. I am glad, it is NOT only me then... >>> At least this is my understanding of it, I have not used latesttemp >>> myself.. :) >>> But as was mentioned by before, 85C is usually due to bad wiring/too low >>> power... Powered sensors ftw :) >> well, in my case I have real 85 degC the wiring and power-supply is ok. > Well, that is of course another valid reason to get 85C.. :) yes indeed it is :)
------------------------------------------------------------------------------ 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
