[arm-allstar] [1.2.1]pcsensor possible issue

David McGough kb4fxc at inttek.net
Sat Nov 8 20:06:45 EST 2014


Hi Joel,

Thanks for finding this info. I've been using the older "Temper1" units.  
I haven't yet used the "Temper1F" version.  However, I understand from the
manufacturer that the older sensors are no longer available for sale and
the Temper1F is the replacement model.

I've looked over the updated source code, listed below, and noticed that
it seems to loose some functionality included in the original version--in
particular the "-n" (allows querying multiple units) and "-a"  
(correction factor) options seem to be missing. So, a little hacking may 
be in order, since I'm using these options. I've got several sensors in 
cabinets monitoring heatsink temps, etc., at different spots.

We'll plan to include an update in the next release to support the 
"Temper1F" (and perhaps a few other models now available) correctly.


Thanks again-

73, David KB4FXC


On Sat, 8 Nov 2014, Joel Jameson wrote:

> I just hooked up a TEMPer1F device to play around with, and noticed the
> sensor temp readouts were a tad high.
> 
> [root at bbb41187]# pcsensor
> 2014/11/08 16:03:59 Temperature 492.79F 256.00C
> 
> I dug this up on google about this behavior:
> http://lee.smallbone.com/2014/10/using-temper1f-usb-temperature-probe-on-raspberry-pi/
> 
> As my temp outside is close to 0C, that page pointed me to this patch:
> https://github.com/petechap/usb-thermometer
> 
> after making/installing the file, the temp is now correct and lists as:
> 
> [root at bbb41187]# pcsensor
> 2014/11/08 16:05:53 Temperature 31.99F -0.00C
> 
> I'm not sure if it's just the unit I have, or if this should be included
> for the 1.2.1.1 release :) It could be I should move the whole rig and
> myself south as a workaround...
> 
> Cheers,
> Joel
> W0KGW
> 



More information about the arm-allstar mailing list