HI all, I have trouble with a couple of DO VAC Isolated charms IO that have "Bad - Faultstate Active" error status in DeltaV Diagnostic. Configuration and physical charm are equal and wiring of the physical charm is ok. I am not able to find anywhere any help about this error message. I have many other similar charms that dosen't cause any mistake. Dis anyone have an idea of what it could be?
Is this a new CIOC installation or project? I've seen this issue years ago caused by a a loss of comms between the CIOC and controller the CIOC is assigned to where you'd have to either reseat the controller if simplex or just do a double switchover (resets both controllers) if redundant controllers. I thought there was a hotfix that resolved this (haven't seen it happen recently), but if you have redundant controllers to where the CIOC is assigned to and the process allows, you might try to do a double switchover (switchover...allow the standby controller to be available....switchover). That's how I had to resolve these issues years ago.
In reply to Otto Von Steele:
Yes it is a new CIOC instrallation in a new project. I tried the switchover on the controller and also on the CIOC but I still have the same issue. I have a total of 25 DO VAC isolated CHARM on this CIOC and there is only 10 with this status. All other CHARMS (DO, DI, AI, AO) on this CIOC are ok. May it be caused by a wiring problem because I tried to switch DO Charm with one that is working well and at the moment that I push the charm this status is shown again.
In reply to Benoit Rene:
Did you switch the controller back to the original (2 switchovers) or just once? Is there anything common to the 10 (e.g. on the same baseplate, using ) and have you checked voltages across terminals you're using compared with the working one(s)? It's just hard sometimes with CHARMS b/c a communication issue with the controller will mask itself as a hardware.issue.
The Fault State Active condition is caused when the CHARM is no longer being written to by its host controller. It can also happen if for some reason the CIOC stops talking to the CHARM, but since your CIOC is communicating with CHARMS, it is likely controller communication related.
Are these CHARMs referenced in control modules? I'd start by focusing on one CHARM and confirm it is referenced and the module is downloaded and running. The Status of that reference would be BAD. If the module is out of service, the fault state on the channel would also occur.
First try swapping a functioning DO Charm with one reporting fault state. I expect this is not a CHARM issue, but I'd eliminate this as a possibility. If the issue is in the location, not the CHARM, it is a controller reference/communication issue.
Is this assigned to a different controller than those that are working? Are there any CHARMS working with that controller or are all the BAD channels from one controller and the Good channels in a different controller?
Another thing to verify is that you have flashed both the controllers and the CIOC to the same version of software. You may also want to check the versions of the CHARMs that are working and those that are not, and if different, flash the CHARMs to the same version. Note that CHARMS don't need to be flashed as part of a DeltaV upgrade, but if a later version of the CHARM exists, it is good to update it, especially if it is not performing as expected.
And you should file a call with the GSC. They'll need versions and such. Trouble shooting in a forum like this can waste a lot of your time as we are guessing with very little information to go on...
Andre Dicaire