we have MARKVie in 9FA Power Plant.
Question: Is it possible to create trend with specific signals and in case we have trip in the GT for any reason? this trend triggered start before specific time like half hour before and till half hour after the trip?
I know there is trip log we can have it for each trip.
But is it possible to do special one.
Thanks for supporting
Yes; it's possible. There is very good 'Help' in Trend Recorder/ToolboxST. And, there's a manual for Trend Recorder.
If you search the hard drive of the HMI for files with 'GEH' (without the quotes) in the filename, you will find at least one, if not several directories/folders with such files in them. I don't know what the name of the Trend Recorder GEH file is (it will be something like GEH-nnnn, where nnnn is a series of digits). They don't make it easy to find the files, because the filenames are all GEH-nnnnn. But, you can open each file, and if you find information that you find useful, you can save it to the Desktop (I suggest you ultimately create a folder on the Desktop for these files) using the title of the GEH, which might be 'Using Mark VIe Trend Recorder'. When you click on File|Save As just be sure to point to the Desktop and change the file name--but NOT the file type (.pdf). Changing the file name ONLY causes the filename to change, and if you save it to the Desktop creates a copy of the GEH-nnnnn file with the new name--and doesn't disturb the original file (of while there are usually at least two copies on the hard drive).
So, search the HMI for copies of manuals and GEHTs--GE How To .pdf files with all kinds of useful information.
Hope this helps!
By the way, you're looking for 'triggered trends.' Using a logic signal as a trigger, you can start a trend with a specified amount of data (in seconds) before the trigger, and I believe also with a specified amount of data after the trigger.
There are also VERY useful functions which can be added to the application code using ToolboxST called 'Dynamic Data Recorders' which have their own manual (GEH-nnnnn).
And, most of the information in the GEH manuals is duplicated from the GEH-nnnnn files. So, it's really in several places--you just have to willing to search for it. If you have a ToolboxST file open without any change privileges, you CAN'T trip the turbine or cause a problem or download or upload or make any changes. Just remember, when you close the file if all you were doing was "looking around" if it asks if you want to save any changes, JUST SAY NO! and if you made any unwanted or inadvertent changes, nothing will be saved.
I always recommend technicians (and permitted operators) to make a read-only copy of the Mark VIe files in a separate folder, and open that copy when wanting to "look around" and learn. You can still connect to the Mark VIe and see live data--but you can't hurt anything if the copy you're looking at is NOT the copy used for configuration and troubleshooting and is in read-only format.
Thank you Mr CSA for the information.
i found the below document number related to the trender. Trender for the ToolboxST Application Instruction Guide GEI-100795.
I will check if i can find how to trigger trend with other signal than the Trip Signals.
There 2 features on the ToolboxST to record trends of any parameter.
First one is the ToolboxST Trender which can be configured with needed signals. This trender has to be started and stopped manually. Details about configuring and using the trenders will be available on the HMI PC or any other PC which has ControlST installed in it. You will be able to find all the help files related to ControlST in the following path of the PC.
Start Menu->Programs->GE ControlST->Documentation
Second option is to configure an automatic data capture like Trip log. This has to be used for debugging any critical machine sequence change (like Trip). It needs a configuration change in the Application code of MarkVIe controller. The condition that triggers the logging, Log duration before and after the event etc can be configured on the application code.Basically what happens is that the controller logs the values of all signals configured on every scan and saves it to a location on HMI PC when the trigger event occurs.
Any changes on the capture buffers of the controller will cause a Major difference in the application code which will need a restart of the controller after download. My recommendation will be to avoid this automatic data capture feature for any operational monitoring.
1. You will need an offline download of modified files.
2. Addition of new signals in capture buffers will cause the controller memory to be loaded (because it has to record all of them in each scan) and reducing the idle time of controller (which is not a good thing).
There is always the best option of installing a Historian which records all the required data for a long period of time. I believe that this will be the best solution for your requirements on operations.
The information you are asking for should already be part of your triplog files if they were properly configured when the plant was commissioned. There are files created every hour that are part of the "Triplog Live". These files are created and stored every 1 hour and are a collection of signals on a 1 second rate from all of the capture blocks configured in the controller. These files are stored for a period of 3 days on the HMI and then deleted on a first in/first out basis.
Triplog files are a 24 hour snapshot collected each time the unit trips or generator breaker opens from each controller. The same signals configured for each capture block are collected at 40 ms time stamps at the time of the trip and for a period of time before and after the trip. The further out from the trip the less often the samples are collected. Alarms and events should also be stored in the triplog to assist with diagnosing the cause of the trip.
If there are signals that you want captured they can be added to existing capture blocks if there are spare pins not used, each capture block can collect 32 signals. If there are no spare pins then additional capture blocks can be added but this does take a little more effort. Adding signals to the capture block or adding additional capture blocks has never caused a "Major Difference" in my experience.
Changes to the capture blocks requires an online download to the controller, and an update to the data historian service or download to the HMI depending on what version of Toolbox or Workstation you are using.
You can also create DDR's, Dynamic Data Recorders to capture data when a particular signal goes true or false.
Lastly you can create a triggered trend to collect data when a signal changes state, but the trend must be started and waiting for the trigger to start the trend.
But I would still suggest that the Triplog when properly configured should be collecting the signals needed to diagnose a trip.
thanks for useful reply...... just for the last part you mentioned that we can make triggered trend it will start with signal trigger do you have any idea how to do it?
Add sequence using CAPTURE block.
The data capture block collects samples of up to 32 signals in a buffer that may be uploaded by the toolbox for display and analysis. It supports a variety of triggering and sampling options.
First, open Trend recorder and setup the variables you want to trend. Then click the Trender Properties button on the bottom toolbar (Or File->Properties menu). The Triggered Recording option is the last one in the Properties window that comes up. Set it to Level or Edge trigger, and you'll get more options to configure the trigger variable and pre/post time.
This is most useful while debugging a re-creatable issue, since you have to have Trender setup and waiting. For issues that happen infrequently, the DDR feature in ToolboxST might be better, as it collects on the controller and can be uploaded by WorkstationST automatically when an event occurs. DDRs work much like CAPTURE blocks except that they do not make any change to the application code on the controller (they build and download separately).
For setting up a standard set of data for any trip, you should probably build it into your application code using CAPTURE blocks and Trip Logs. There is a section on Trip Logs in the How To guide, GEH-6808.
can you please explain what is snap shot collected and 24 hours?
>Triplog files are a 24 hour snapshot collected each time the
>unit trips or generator breaker opens from each controller.
>The same signals configured for each capture block are
>collected at 40 ms time stamps at the time of the trip and
>for a period of time before and after the trip.
>Lastly you can create a triggered trend to collect data when
>a signal changes state, but the trend must be started and
>waiting for the trigger to start the trend.
Here again if "I start trend and wait for trigger to start the trend" is confusing. Suppose trend already started and waiting for trigger to start the trend is confusing.