On 06/12/16 12:07, Martin Patzak (GMX) wrote: > > On 12/06/2016 11:31 AM, Colin Law wrote: >> In my code (in a node-red environment) if I get a value of 85 then I >> retry after a timeout (1 sec I think) and only if I get three 85 in a >> row do I accept it as 85. > my problem is, that I cannot read a value 85 degC at all, I do however > get error messages or time-outs, depending... When reading /temperature of a DS18x20, and the sensor returns 85, the owfs code will perform a re-read (including convert) up to 3 times in total. With 1s timeout, that will always be too short, and the client will timeout. Note that a client-side timeout does not abort the already issued query; if you called /temperature it will still try to convert+read 3 times, even if your client aborts after 1s. An immediately following query with 1s timeout may thus fail as well (since it just waits for the bus > 1s)
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. 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 :) ------------------------------------------------------------------------------ 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
