Search results

You are correct that all H1A/H2A packs contain the BPPB processor and that the BPPB processor is going end of life. However, not all of the new I/O Packs with BPPC processors (H1B/H2B IO Packs) will work on controlST v04.04. Please do not make that mistake. The document says that BPPCs are...

Djafer-QP The Terminal Boards do not have to be modified. They can stay the same version And the I/O pack can be updated to H1B. Note: your comment about 'V04.04 and later, BPPB-based I/O packs can be migrated to BPPC-based I/O packs' This ONLY applies to the PCAA module. Different...

All, These are great questions. And very pertinent today since the H1A IO packs and UCSBs are becoming harder to find. I would first point you to the GEH-6721 Vol II and Vol III that comes with your ControlST install software. Make sure that you only use that version! they make lots of...

RAF80, I do not know if this will directly answer your question, but this document is a good start: https://www.ge.com/content/dam/gepower-pgdp/global/en_US/documents/automation/GHT-200048.pdf. Don't try to follow it to order the dongles/licenses, just use it for knowledge purposes. the...

All, in order to support the PCAA H1B version, you must have controls version 4.04.xx or later. Otherwise, you will not have that drop down option to change from H1A to H1B. Please Note: this is the version needed for the PCAA. Other I/O packs may require different versions. Depending on...

It is somewhat easy to set up an Mark VIe HMI to communicate via Modbus to the Honeywell HMI. The diagnostic tools on the Mark VIe HMI are MUCH better than the diagnostic tools on the PSCA or the controller. Additionally, you don't have to muck with the controller. You have to know a little...

My comments might be too late, and you hopefully have solved the issue. I will agree, this is frustrating to get cimplicity errors. They tend to be very decrypted and don't shed a lot of help on the root of the issue. Try force rebooting your PC and then get the HMI back to running...

A few more Clarifying questions. What is your PC? Are you using ControlST/WorkstationST? What version of cimplicity? If you are using Mark VI with ETCSS and an HMB file, then for some reason the cimplicity to TCI connection has failed. I would start with Cimplicity's Status Log to find out...

IS the "Contact Input () not responding to self test mode" a pack specific alarm? or all IO packs getting this alarm? IT could be a TB issue. For now, do not worry about the Configuration mismatch issue. You resolve that later with a controller download.

I wanted to verify. that this is Mark VI not Mark VIe?? Can you please confirm? this will lead troubleshooting down a different path.

Are you looking at Mark VI or Mark VIe? If it is Mark VI, your block choice is a little more limited. I would have a 24 hr timer and then reset the flow totalizer every 24 hours. However, on reboot of the controller, you will need to reset the timer based on UTC.

It looks like a cimplicity problem, but further investigation is needed to pinpoint the issue. I would look at the Status.log file to see if Cimplicity is spitting out any more errors.

MUNOZLE, Can you be more specific on the error? There could be many issues with controllers or HMIs. If you provide detail on the issues, we can better help you.

Mark VI or Mark VIe? for Mark VI. There are 2 places to archive Trip logs in the Controller. Either using the Dynamic Data Recorder (DDR) or capture buffer blocks. For the DDR: - Open up your GT M6b file. Verify there are some DDRs are configured in the controller. - On the left...

Iqbal, In short, what CSA is saying is that one of the I/O packs is not talking to the controllers. This could be the new PDIO you installed or another pack that could have been bad for sometime. You will only see this 'inputs enabled' when you start up the controller. Go online with the...

Which one? Mark V or Mark VI or Mark VIe. Those PCs are very different on how they are configured. Get back to the group and let us know what version of Mark and What windows version of the HMI.

It is not possible to get the Mark VI serial #s from Toolbox. If you want the Terminal board Serial #, they you need to walk out and view them in person. However, I am not sure why you would need to know the Serial #. If you want to know the part # for re ordering, that is different.

VScontrol, how new is your turbine? For any GT installed over ~3 years, GE doesn't put HART IO into their design. This might be something that was accidentally 'enabled' on your HMI. I would double check that you do not have any 'PHRA' IO modules in the GT. I could go in a long...

Iqbal, What do you mean “the control doesn’t respond”? Can you ping the IP addresses of the controllers? I would like to see where the startup fails. The other thing you could do is connect in with a serial com cable and watch the controller boot up and view the...

Djafer, I assume from the above conversation that you guys are definitely using Mark VI HMIs? i.e. configuraitons with .hmb files? Any chance that you are using ControlST/WorkstationST HMIs (.tcw files) with your mark VI system? Like Demi and CSA said, Mark VIe HMI Modbus is easier. I...