Emerson Exchange 365

• Not Answered

CHARMS CSLS periodic IO fault every 24hrs

CHARMS CSLS IO cards periodic failure at every 24hrs intervals which causes an OSD trip at every 11:14 AM on daily basis.

At this particular time 11:14 am all the CHARMS CSLS IO cards red lights flashes within some seconds and then all the AI cards and some few DO cards will

normalize while about 90% DO cards will go completely powered OFF and shall require re seating the affected DO cards before they will normalize to start up.

Initially when this issue started at every exact time it will occur all the CHARMS CSLS IO cards (AI & DO) flashes red and normalizes within a few seconds and

all the CHARMS CSLS IO cards will recover but presently only the AI cards recovers and the DO cards will require a re-seat to normalize.

Both CHARMS IO (AI & DO) shares the same back plane.

Both active and redundant CHARMS CSLS has been changed,decommissioned and commissioned again and the issue persist.

Observation: When the CLS was decommissioned, power cycled, commissioned and downloaded all the AI cards will normalize but the DO cards must be re seat

before the normalize.

Please I need some help.

• CHARMS

obinna benedict

• 10 Feb 2020 8:55 AM
• Cancel

2 Replies

• Jerry Harris

  

  • 10 Feb 2020 1:52 PM

  We experienced a similar problem last year on a new CSLS installation. Although we didn't actually trip an interlock or have any DOs lock up, we did get an integrity alarm every 24 hours when the CSLS went through a self test. Initially, we noticed periodic comm errors on diagnostics for the HART variables for all the LSAI CHARMS. We also noticed that one particular LSAI CHARM would go through a proof test at the same time as the CSLS self test every day. We thought that LSAI CHARM was the issue. Below is an excerpt from an email to GSC outlining all the troubleshooting steps we went through and components we changed out. Eventually, we disabled the line fault detect for one particular LSDO CHARM and ALL problems went away. There were no comm errors on the LSAIs and no daily alarms when the CSLS ran its self test. There possibly is an issue in the wiring between that LSDO CHARM and the solenoid it drives, but we can't find anything. It functions fine (opens/closes the associated block valve as needed). GSC recommended that ultimately there might be an issue with power and grounding. We checked the wiring and found one potential issue with grounding on the CSLS carrier, but haven't corrected it yet. In the meantime, we continue to run without the line fault detect enabled on that one particular LSDO. Don't know the potential ramifications of leaving it that way, but it fixed our problem.
  
  1. Swapped the active CSLS from the left one to the right one. This did not resolve the HART comm issues.
  2. Replaced the cables between the CSLS’s and the first baseplate. This did not help.
  3. We removed the LSAI CHARM at baseplate 1, channel 2 (the one that always went through the proof test), but the
  HART comm issues continued on all other LSAI CHARMS.
  4. We replaced baseplate #1. This did not help.
  5. We replaced baseplate #2. This did not help.
  6. Upon power up from replacing baseplate #2, we noticed that the DO CHARM at baseplate #2, channel 2 took a lot
  longer than all the other CHARMS to come back good (go from red to green).
  7. We pulled this DO CHARM out, and immediately the HART comm errors went away.
  8. We replaced this DO CHARM with a new one, and the HART comm errors started again.
  9. We replaced the term panel for this DO CHARM, but the HART comm errors continued.
  10. We tried moving this DO CHARM and termination panel to another channel (channel 6), but this didn’t help.
  11. We put the DO CHARM back to channel 2 and lifted the wires. Immediately the HART errors went away.
  12. We hooked the wires back up and the HART errors started back.
  13. We disabled the LINEFAULT_DETECT for that DO CHARM and the HART errors went away and have stayed away.

  • Cancel
• Andre Dicaire

  

  • 10 Feb 2020 4:51 PM

  In reply to Jerry Harris:

  First, I strongly urge you to contact the GSC and work through this issue in a structured and deliberate manner.
  
  The first thing to verify is installed Firmware of your CSLS processors, and from their confirm if this issue has been logged and addressed already.
  
  Verify the Alarm and Events logs to confirm what issues have been reported by the Logic Solvers. This coupled with the firmware/hardware information is important to focus quickly on any known issues.
  
  In addition to getting the GSC to investigate your symptoms, the issue is also recorded and known to the factory. If this is a new issue, the GSC needs to be made aware and will investigate more deeply. I would not use this forum to advance your resolution.

  Andre Dicaire

  • Cancel