Emerson Exchange 365

Can I read controller information and use in control modules?

We recently had a cabinet overheat due to an air conditioning system failure.   So we are thinking that if we could monitor the controller internal temperature in a control module we could setup alarming to have technicians resolve heat related issues before they cause a shutdown.  Any help would be appreciated.

Dave Stevenson

foxriver

• 9 May 2018 3:33 PM
• Cancel

7 Replies

• SimHogan

  

  • 10 May 2018 12:04 PM

  Hello Dave -
  I do not know the parms for the controller temp, but we are monitoring the smartswitch internal temperatures at:
  DV_SWITCH_$X/HAC_HITEMP_VAL (v12.3.1)
  
  The smartswitches trend running rather hot, normally ~104 F in a 70 F room. I would be interested in monitoring controller temperature as well.

  • Cancel
• foxriver

  

  • 10 May 2018 2:49 PM

  In reply to SimHogan:

  Thanks Sim, I will try this for our smart switches. I did find some previous discussion on how to get the internal temps from CIOC modules, which worked. The parameter is "CICO Node Name"/INTERNALTEMP.F_CV . In my case the CIOC node is CIOC_1 so the path was CIOC_1/INTERNALTEMP.F_CV . Unfortunately this only worked on the CIOCs and not the controllers. Also only worked on a graphic and not in a control module. I would still like to figure out how to do it with the controllers and if possible import into control modules. Is there some place that lists all the internal parameters inside all network devices? Seems like there is a lot more available than what I can see looking at the Diagnostic Parameter list.
  
  Dave

  • Cancel
• SimHogan

  

  • 10 May 2018 3:24 PM

  In reply to foxriver:

  Thanks Dave -
  I will add the CIOC temperatures to my diagnostic monitoring list!
  Hopefully someone will help out with the path's to the other parms.

  • Cancel
• Andre Dicaire

  

  • 11 May 2018 11:11 PM

  In reply to foxriver:

  The internal temperature parameter is not available in the DeltaV controllers. This was added to the CIOC as a means to monitor variations in the ambient temperature, in anticipation of their deployment in non HVAC equipped locations. Rather than use an IO channel and RTD or temperature switch. The CHARM logic solvers however do not possess this diagnostic value.
  
  We've monitored the external and internal JB temperatures along with the CIOC temperature for the last 4 years and have found the CIOC temperature runs a consistent 20 to 22 degrees hotter than the internal JB temperature on outside temperatures ranging from -30 to + 40 Deg C.
  
  Note that the rated operating Temperature for DeltaV hardware is typically -40 to +70 deg C for the ambient temperature. The internal CIOC temperature will be about 21 degrees higher. You can therefore infer the ambient temperature of the enclosure, with the CIOC.
  
  In cabinets with active cooling, such as with fans or in some cases cyclone coolers, the normal operating temperature can rise even if ambient conditions remain constant. In these cases, temperature monitoring is recommended. In cabinets that have only passive cooling, the internal temperature of the box will be directly related to the external ambient temperature and any effect of direct sunlight. In those cases, one can monitor the ambient environment for abnormal conditions.

  Andre Dicaire

  • Cancel
• foxriver

  

  • 12 May 2018 5:17 PM

  In reply to Andre Dicaire:

  Thanks Andre. I was able to get the temps setup for the CIOCs and the RM100 smart switches. I won't go any further looking to get it from the controllers. Do you know if the workstations have an internal temperature value that can be accessed?
  
  Dave Stevenson

  • Cancel
• Andre Dicaire

  

  • 14 May 2018 3:43 PM

  In reply to foxriver:

  Worksations don't expose their temperature data. There are apps that will get this information, but to get it into DeltaV, you would have to use and OPC DA client to write the data into a DeltaV module.
  
  I guess if it is available for a VBA script to access, you could add a scheduler event to read the value and write it to a module. This will create an Event log message every time the script writes, so you'll want to minimize the writes and do them by exception. Or even consider a data module that is in a plant area that is not assigned to the Event Chronicle. Then read the value from this module in your normal Hardware temperature monitoring module for alarm or event reporting.
  
  You can't prevent the Upload record in the pro plus, which will record the workstation write command as a parameter change for upload. You'll have to periodically discard this upload record.
  
  I am not aware of an OPC solution to get this data out of the Workstation OS tools, but with OPC, you won't have the Event Log and Upload records to deal with.

  Andre Dicaire

  • Cancel
• foxriver

  

  • 14 May 2018 3:58 PM

  In reply to Andre Dicaire:

  Thanks Andre for the information. Probably not worth pursuing given the effort it would take versus the value it provides us.
  
  Dave

  • Cancel