Today is...
Wednesday, July 18, 2018
Welcome to Control.com, the global online
community of automation professionals.
Featured Video...
Featured Video
Watch an animation of a conveyor stacking operation demonstrating the use of a move on a gear command.
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Visit our Post Archive
A Different Counter Question
Editing of MarkV counters

I have a need to add "Peak Fire selected" Counter. I am a little shaky on how to proceed.

Here is the first few lines of our TOTD_Q.SRC:


;---- ------------ ----------------------------------------------
1 L30CMIS ; ACCUM_01 Manually Initiated
Starts Counter
1 L30CTS ; ACCUM_02 Total Starts Counter
1 L30CFLS ; ACCUM_03 Fast Load Starts Counter
(Not Used)
1 L30CFS ; ACCUM_04 Fired Starts Counter
1 L30CES ; ACCUM_05 Emergency Trips Counter

Accumulator 03 is a counter for Fast Load Starts, an option which is not enabled on our machine. I have checked and the counter MSW + LSW result is ZERO.

Can I just edit TOTD_Q.SRC and replace L30CFLS with L83P?

What steps are necessary to get this into the MarkV?

So that the existing counts are not ruined, should I:

1. upload TOTD (from what core)?
A. What files will I get?
B. Which of these should be saved somewhere else, just in case?

2. Compile (markvmake) using newly edited .SRC file?

3. Download TOTD (to what cores)?

I could use some moral support and shared expertise here.

MARKlaneV,

>I could use some moral support and shared expertise here.

Hmmm.... TOTT_Q.SRC is the file you want to edit (REGARDLESS of what it says in the comments at the top of the file; yet another example of consistent inconsistency). Suggest saving a back-up first (say, as TOTT_Q.ORI). You could just replace as you suggested, and change the comment to make it appropriate (the bit after the semicolon on the row after you make the change; it's not necessary, but it's nice for the next person!).

You should upload TOTD (TOTD_Q.xxx is the timers & cocunters data (values) file) from <R> (the Totalizer Data files should all be the same, but since <R> is usually the Designated Voter under normal circumstances it's the best processor to upload from). You can upload to a generic file (if given the option), which would be TOTD_Q.DAT or TOTD_Q.AP1, depending on whether or not the operator is an <I> or a GE Mark V HMI, respectively. I would also make a back-up first (say, TOTD_Q.ORI). (NOTE: If you upload to a processor-specific file, then any time TOTD is downloaded the processor-specific file will be downloaded--which can REALLY cause problems in the future. This applies for ALL Intel hex format files downloaded using the EEPROM Downloader, not just the Totalizer Data file--and can cause LOTS of problems for any EEPROM partition which has a processor-specific Intel hex format file.)

You DO NOT need to run MK5MAKE.BAT; you only need to run the Table Compiler:

     TABLE_C TOTT to simply compile the Totalizer Table file

(The result will be TOTT_Q.DAT or TOTD_Q.AP1, again depending on if the operator interface is an <I> or a GE Mark V HMI.)

Then you need to download only the TOTT partition to <T>, then <S>, then <R>. Then you need to reboot the processors, one at a time, waiting a full two minutes after each processor returns to A7 before re-booting the next processor.

There is a potential problem here, if the existing accumulator already has a non-zero number in it.... However, there's no way to solve that without a new TOTD_Q.DAT or .AP1 file from GE or one of its packagers.

Hope this helps.

The next problem is changing the display file to read 'Peak Fire Selected.' But, that's yet a(nother) Different Counter Question, and the answer depends on the type of operator interface. Isn't this fun?

Thank you for the discussion of the technical procedures for Counter/timer set-up.

I completely typo'd the filename that needs to be edited.

Here are my thoughts. Please tell me if these steps will cause any loss of existing counter / timer / accumulator values.

1. Save existing counter related files in case something goes
wrong.
a. Copy the existing files to a folder in the unit directory (Old
counter files).

2. Edit TOTT_Q.SRC
a. Change: 1 L30CFLS ; ACCUM_03 Fast Load
Starts Counter (Not Used)
To: 1 L30PS ; ACCUM_03 Peak Selected
Counter
NOTE: L30PS is a new signal created for this purpose
3. Upload TOTD from MarkV <R> core
a. eeprom up t1 r TOTD

4. Compile
a. TABLE_C TOTT

5. Download to all 3 cores
a. eeprom down t1 r tott
b. eeprom down t1 s tott
c. eeprom down t1 t tott

6.Reboot each core 1 at a time with 2 minute delay after reaching A7.

Questions:
1. Is step 3 the correct string to upload TOTD?

2. I am assuming I should upload it so it will be modified when TOT is compiled? Is this necessary?

3. Should TOTD be downloaded as well?

4. Will any of this cause a loss of existing counter or timer data?

MARKlaneV,

>Questions:
>1. Is step 3 the correct string to upload TOTD?

If you're going to upload TOTD file, you should FIRST save the existing TOTD_Q.DAT (or TOTD_Q.AP1) on the operator interface to a back-up directory, or give it a unique filename extension (like .SAV, or your initials). That way, you have a back-up in case something goes drastically amiss.

I believe that string is correct; if it doesn't work, there will be an error message. Most ALL command line executables of the Mark V operator interfaces have Help available--just type the command name followed by either HELP or /? and then press ENTER; for example:

     EEPROM /?
and then press ENTER. There may be more than one display/screen; just press the SPACEBAR until you get back to the command line ("DOS") prompt.

The EEPROM Downloader (which is also used for UPloading (isn't this FUN?!?) may ask if you want to save the TOTD_x.DAT file to a generic file (TOTD_Q.DAT (for <I>s) or TOTD_Q.AP1 (for GE Mark V HMIs)), or to a processor-specific file. DO NOT upload to a processor-specific file; that's only for special circumstances, and this ain't one of them.

There are NO guarantees when dealing with the Totalizer Data files. NONE. Just be careful, and you should be alright. Create a back-up of the existing TOTD_Q.DAT (or TOTD_Q.AP1 if you have a GE Mark V HMI), and then upload to a generic file if prompted by the EEPROM Downloader while uploading. And the file you upload to will be the back-up of the data from the Mark V EEPROM.

>2. I am assuming I should upload it so it will be modified
>when TOT is compiled? Is this necessary?

The Mark V Table Compiler does NOTHING to TOTD_Q.DAT (or TOTD_Q.AP1 for GE Mark V HMIs). Only the Mark V operating system on the DCC/SDCC cards or a GE-authorized facility can change the contents of a TOTD_Q.DAT or TOTD_Q.AP1 file. MK5MAKE.BAT doesn't; the Table Compiler doesn't. Only the OS on the DCC/SDCC cards or a GE-authorized facility can change the contents of totalizer data files.

(Having said that, if you upload to a generic file you will overwite the contents of the existing file on the operator interface--and that will change the contents of the file on the operator interface. And, if you download a totalizer data file that wasn't uploaded from the Mark V extremely recently, you run a risk of losing the totalizer data stored on the EEPROMs. Man, this is just plain FUN, isn't it?!?!?!)

>3. Should TOTD be downloaded as well?

ONLY if you download the uploaded file. (Again, isn't this FUN?!?!?!)

>4. Will any of this cause a loss of existing counter or
>timer data?

Again, there are no guarantees. But, if you upload the existing TOTD to a generic file, you should be good. [NOTE: ALL TOTD_Q.DAT (and TOTD_Q.AP1) files have the same size; just different dates and time. That's by design; they are Intel hexadecimal files with encoded data for the timers and counters. So, don't be shocked if you compare the size of back-up of the as-found TOTD_Q.DAT (or TOTD_Q.AP1) file to the size of the uploaded file and they are exactly the same--that's supposed to happen. The file dates and times will be different even though the values of timers and counters will be different in the two files.

Best of luck--let us know how you fare!

CSA,

>Best of luck--let us know how you fare!

Thank you. I think this modification went well and feel pretty confident that it will work like it should. Unfortunately, I am unable to test it at this time. I have to wait for our peak fire upgrade installation.