Emerson Exchange 365

BAD signal in a LSDO output

We aare facing an issue in a LSDO out signal connected to the heater TRIP signal.

For the past five days exactly at 9:40 PM bad signal is originated from a LSDO block.

The BAD signal is active for only one second and goes to normal state. In the filed RED LED is let for one second in the DO charms.

After one second all output signal and charms are back to normal.

I thought that this is because of the BAD signal in the charm and I changed the charm but still the BAD signal is appeared in the same time. T

here is no timer implemented in the logic. Please give your suggestion to rectify this issue.

arulgeorge

• 17 Jul 2022 6:12 AM
• Cancel

5 Replies

• Bryce Elliott

  

  • 19 Jul 2022 7:16 PM

  It doesn't seem likely, but we had a weird bad output situation on an LSDO several months back. When the input to LSDO has bad status, the default behavior is for it to trip after 5 minutes. If someone set it to 1440 minutes and you have a few other appropriate logic things in there, I can see where it might trip every day for a second. You would have to have the trip cause the status to go back to normal for a second. Again, this seems unlikely because there are a lot of "ifs" in there, but you can check it to rule it out.

  - Bryce H. Elliott, P.E.

  • Cancel
• Tadeu Batista

  

  • 19 Jul 2022 8:13 PM

  How many LSDO's do you have?
  Are they all Simplex or Redundant?
  Does it happen to a single LSDO or to all of them?
  Do you have other CSLS nodes with LSDO's on them?
  Are you facing any issues on them?

  • Cancel
• arulgeorge

  

  • 21 Jul 2022 1:19 PM

  In reply to Tadeu Batista:

  We have 29 LSDO connected in the particular CSLS.
  All are redundant modules.
  The issue is happening to all LSDO.
  We have other 13 CSLS coneected to the SZ controller and we have issue in 2 CSLS.
  
  Identified Issues :
  • All LSDO module in a particular CSLS goes to fault state ( RED LED) for one second and back to normal
  • I checked the same signal in the DeltaV explorer online and found that the same LSDO module status goes to “YELLOW ?” mark and the output goes to BAD state ( RED) for one second and back to normal state .
  • The BAD ERROR appeared once in 24 Hrs and Every day the BAD state is appeared in the same time.
  
  OBSERVATION :
  • In the process history log “An output block or secure parameter has Bad status on its output” is reported first.
  • BAD Signal in the LSDO OUT_D . The input is normal.
  • All LSDO Charms status went to BAD(RED) in the field.
  TRIED OPTIONS :
  1) Change the charm
  • The first bad signal is reported in a SIS module “HEATER1” and I changed the LSDO charm module but still the BAD signal appeared.
  • Checked the relays in the heater and the connections,the connected relays are OK.
  2) FORCE the signals in Debug mode
  • I entered into the debug mode and force all the input signals connected to the LSCEM module but still the BAD signal appeared
  • I forced the LSDO inputs and secure parameters but still the BAD signal appeared.
  3) FAULT STATE OPTION
  All LSDO fault detection are disabled in the LSDO properties but still the BAD signal appeared.
  4) Power On Reset the CSLS in the field
  • The BAD signal appeared every day at 9:40 PM
  • We reset the CSLS module by power off/on reset and the time for the reset is 2:37 PM
  • The BAD signal is appearing at 2:37 PM every day.
  We tried all the possible way to identify the root cause for the issue but unable to locate the issue.
  Since this issue is appeared in every 24Hr time the CSLS module is creating problem in the self-test( Need clarification).
  Does Emerson has any Patch file / Bug fix to address this issue.
  Please check our analysis and give your suggestion to rectify this issues.

  • Cancel
• fkitzmann

  

  • 21 Jul 2022 4:39 PM

  In reply to arulgeorge:

  Is it possible that it is a communication issue between CHARM carriers and the CSLS or something that is happening on the network connection side?
  What is the firmware revision of the two CSLS that are giving this issue versus the other CSLS that are working correctly?

  • Cancel
• Tadeu Batista

  

  • 21 Jul 2022 5:11 PM

  In reply to arulgeorge:

  arulgeorge
  You said you have 29 redundant LSDO, when the system allows either 48 Simplex LSDO or 24 Redundant LSDO.
  You said you're having issues with 2 out of 13 CSLS, if the issue were occurring on all the 13, then maybe it should be a Bug/Hotfix situation.
  You mentioned the self-test diagnostic, it could be related, but it's hard to say without the proper troubleshooting, if you want Emerson to help with it, which we're more than glad to do, I would ask you to log a call with Guardian.
  
  Rgs,

  • Cancel