Re: APCC -- conflict using THUM device
A note from Practical Design Group: Readings can not be taken from the THUM faster than one reading every 3 seconds. Taking readings faster than this could raise the internal temperature of the sensor. This could skew the temperature and RH readings returned from the THUM.
Hi Ray and others,
As you wrote earlier and with many experimentations from my side, the THUM data is corrupted when more than one client is reading the THUM device at the same time. The THUM service from Practical Design Group should not be running when reading THUM data with APCC else data will be corrupted.
Just take a look at the Practical Design Group web site (THUM DLL section) and found something that could be interesting to try to bypass this king of behaviour.
In the Functions listing within THUM.DLL, maybe the Reset function could help in some way just before reading data values from the sensor. Having to reset the THUM sensor just before reading data from it could prevent corrupted data...who knows?
Best wishes to you all !!!
My two cents,
De : ap-gto@...
> -----Original Message-----
> From: ap-gto@... [mailto:ap-gto@...]
> Sent: Wednesday, December 30, 2015 11:50 PM
> To: ap-gto@...
> Subject: [ap-gto] Re: APCC -- conflict using THUM device
> Works great. Thanks.
> But I do need to add a test to check whether APCC is running or not, as otherwise
> trying to get the temperature this way starts APCC, which then exits after a few
> seconds. Better behavior is to just use the THUM directly when APCC isn't
> - Barry