|
|
EPICS on Google+
Experimental Physics and
| ||||||||||||||
|
|
Hi David, devIocStats is meant for things that are common across BSPs (for RTEMS and VxWorks) and OS types (for linux, solaris, and darwin). I think something like CPU temperature, which is monitored differently on different BSPs or flavors of OSs, should be in a different module. But feel free to look at the devIocStats (especially devIocStats/os/Linux) for ideas of how to read the /proc files and stuff information from them into PVs. Other people probably have better examples. Stephanie Allison SPEAR Controls saa@slac.stanford.edu > -----Original Message----- > From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of > David Morris > Sent: Monday, November 29, 2010 5:21 PM > To: tech-talk@aps.anl.gov > Subject: Monitoring CPU temperature for small IOC > > Hello all > I have a Linux based IOC running on a dedicated small hardware > platform (Atom CPU in Mini-ITX form factor) We would like this to have > no moving parts, which means monitoring the CPU state becomes critical > on hot summer days. Is there support for monitoring CPU temperatures > using the /proc/acpi service? It seems like this would be something that > devIocStats could provide, but perhaps it is too system dependent. > > Is there an easy way to collect information from the IOC host system > and place it into PVs? Regular reading of /proc/acpi/thermal_zone/THRM > will give an updated CPU core temperature, but it is not clear to me how > to place this into a PV. > > Thanks in advance. > > David > > -- > > David Morris TRIUMF > Systems Designer 4004 Wesbrook Mall > Ph 604-222-7450 Vancouver, B.C. > Fax 604-222-7307 V6T 2A3, Canada > >
| ||||||||||||||
| ANJ, 30 Nov 2010 |
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |