DeltaV Communication problem between CPU and IO card

Following problem reported:

A redundant controller connect with 4 IO carrier. The controller is redundant but all IO cards are simplex. the IO card are in carrier as follows:

from slot 1   to 15: 8 channel DI

from slot 16 to 24: 8 channel DO

from slot 25 to 28 : 8 channel AI(HART)

slot 26 : 8 channel AO(HART)

from slot 30 to 32 : spare

Problem: Sometime the IO card in working time will isolate themselves from system.

The report for one time for this problem detailed as:

The IO cards of first slot of each carrir is isolated, cards red LED was ON, they couldn't be recognized in diagnostic and the related module has gone to MODBAD.

so the process disruppted and shutdown happened.

remedy: when the maintenance staff removed the card and inserted the card, system got back to normal and this card and all other cards worked as normal. green led go to ON and red LED gone to OFF and card have been recognized in diagnostic and relebant control modules.

Please help thsi matter by if:

1- Is therse  any report like this?

2- What is the rason?

3- what have to do to prevent this problem?

4- Is there a software patch for this problem?

DeltaV Version: 8.4.1

Thanks.

Be part of solution, not part of problem

6 Replies

  • > Quote:
    The IO cards of first slot of each carrir is isolated, cards red LED was ON,
    they couldn't be recognized in diagnostic and the related module has gone to
    MODBAD.
    <
    Looks like one of the pins between either the active controller and the
    carrier or between the 2-wide carrier and the first 8 wide carrier is bad.

    Did you make contact with Emerson? They can help finding the cause.
  • In reply to Maarten van der Waal:

    Dear Maarten,

    I don't think problem is in hardware, as the card removed and then inserted in slot problem is solved. It seems the card isolated itself from carrier by happening a problem inside the card or from outside. But I am wondering:

    1- The card is simplex not redundant and if it was redundant, we could reasoning the card switchover-ed and faulty card go to isolated, but why in simplex form.

    2- why all card in first slot of each carrier.

    It may be a software type problem. But about contacting Emerson, still not.

    thanks for your reply.

    Be part of solution, not part of problem

  • We suffered a similar problem last week, all cards on in the second position on all five (5) carriers went into fault and couldn’t be seen in diagnostics “configured but not present”.  It is suspected that the pins to track 2 of the carrier are a problem resulting in all 2nd cards from failing.
     
    Luckily we had spare slots on the carriers, so we moved the cards to new slots and they worked.  Requiring IO to be moved from DeltaV Explorer, but this was easier than a shutdown!
     
    The plant was running and we couldn’t shutdown so this was our only available solution.
     
    From: brenet_1345 [mailto:bounce-brenet_1345@community.emerson.com]
    Sent: Tuesday, October 15, 2013 8:24 AM
    To: DeltaV@community.emerson.com
    Subject: RE: [EE365 DeltaV Track] DeltaV Communication problem between CPU and IO card
     

    Dear Maarten,

    I don't think problem is in hardware, as the card removed and then inserted in slot problem is solved. It seems the card isolated itself from carrier by happening a problem inside the card or from outside. But I am wondering:

    1- The card is simplex not redundant and if it was redundant, we could reasoning the card switchover-ed and faulty card go to isolated, but why in simplex form.

    2- why all card in first slot of each carrier.

    It may be a software type problem. But about contacting Emerson, still not.

    thanks for your reply.

  • Hi Brenet,

    From this description the conclusion may be that it is not the pins that are
    wrong, but one of the cards.

    Still using the mechanism where all cards should detect when to communicate,
    I guess one of the cards is not 'obeying' the communication principle. So
    when one of the first cards has time to communicate, another first cards
    also communicates on the bus. This disrupts communication and apparently
    stops all other first cards.

    Remember there are 2 times 8 wires in the 8 wide carriers next to the
    communication bus.
    One set of 8 wires determines which 8 wide carrier may communicate, the
    other set determines which cards on the 'assigned' carrier may communicate.
    There is however only one communication bus.

    Hope this helps.

    -----Oorspronkelijk bericht-----
    Van: brenet_1345 [mailto:bounce-brenet_1345@community.emerson.com]
    Verzonden: dinsdag 15 oktober 2013 07:24
    Aan: DeltaV@community.emerson.com
    Onderwerp: RE: [EE365 DeltaV Track] DeltaV Communication problem between CPU
    and IO card

    Dear Maarten,

    I don't think problem is in hardware, as the card removed and then inserted
    in slot problem is solved. It seems the card isolated itself from carrier by
    happening a problem inside the card or from outside. But I am wondering:

    1- The card is simplex not redundant and if it was redundant, we could
    reasoning the card switchover-ed and faulty card go to isolated, but why in
    simplex form.

    2- why all card in first slot of each carrier.

    It may be a software type problem. But about contacting Emerson, still not.

    thanks for your reply.

  • In reply to Maarten van der Waal:

    Well, the first step is to log this with the GSC and drive this to a resolution.  You need to take a methodical approach to isolate the problem.  This forum is not the right venue for this as many may offer you suggestions, and some could be unnecassarily distruptive.

    It looks pretty clear that a carrier is affected, and this points to an issue on the select line for that carrier.  It could be related to the hardware series of IO, so you need to evaluate your hardware, and possible known issues with that hardware.  This is a GSC activity.  Make the call.

    Other than ensuring all your carriers are securely connected together, (nothing has vibrated appart possible causing intermittent contact)  It is likely you have an issue wtih a Series 1 card and its rail bus connection circuitry.  It could be a controller select line issue, but I doubt that.  The GSC can research these issues and provide an action plan.  

    Andre Dicaire

  • Hi All,
    I seen in DeltaV AI card 8 channels the execution time 25 ms but I am not able to find information on AI 16 channel and AO. Anyone has the information or care to share the execution time for the mentioned card.
     
    Regards.