Associated Action File Formats

The process of configuring Associated Actions for alarms is described in the topic 'Associating an Action with an Alarm' in the main Help.

The tables in this book specify:

Files

The files for storing and importing Associated Actions are held in the project folder as follows:

File name	Sub-folder	Contents
ACTION.DAT	C	Stored action records: one line per action.
XXXX.DAT	TP	Import: one line per addition, modification, or deletion.

Where XXXX is the name used in the ASSOCIATEDACTIONS instruction.

This table shows the storage format for an Associated Action for an alarm. Show table

No.	Description	Type	Size (bytes)	Values
1	Record type (optional)	Character	6	ACTION
2	Type of action (0 = action associated with alarms)	Numeric	2	0
3	Button for selection (LB = left, RB = right)	Character	2	LB or RB
4	Variable name	Character	40
5	Program/window flag (P= program, W = window)	Character	1	P/W
6	Name of program or window	Character	12
7	Branch	Character	30
8	Function	Character	30
9	Arguments (in quotes)	Character	2,047
10*	List of producer stations	Character	14
11*	List of consumer stations	Character	14
12*	Origin of the object (0 if local, >0 if remote)	Numeric	2
13*	Version number of the object	Numeric	2
14*	Comment on the object	Character	80

* New fields.

The record type is optional (i.e. the user can write a record with or without it).

The format for adding an Associated Action entry for an alarm is as follows. It starts with the keyword "AAA,0,".

Show table

No.	Description	Type	Size (bytes)	Values
1	Record type	Character	6	AAA
2	Type of action (0 = action associated with alarms)	Numeric	2	0
3	Button for selection (LB = left button, RB = right button)	Character	2	LB or RB
4	Variable name	Character	40
5	Program/window flag (P= program, W = window)	Character	1	P or W
6	Name of program or window	Character	12
7	Branch	Character	30
8	Function	Character	30
9	Arguments (in quotes)	Character	2,047
10	List of producer stations	Character	14
11	List of consumer stations	Character	14
12	Origin of the object (0 if local, >0 if industry standard)	Numeric	2
13	Version number of the object	Numeric	2
14	Comment on the object	Character	80

The example below shows the sequence of lines.

AAA,0,PAR,"action 1 label Fra","action 1 label Eng","action 2 label Fra","action 2 label Eng"

AAA,0,LB,"testAA",P,"x","","","","S1","C1",0,0,"action 1 test"

AAA,0,RB,"testAA",W,"mm","","","","S1","C1",0,0,"action 2 test"

AAA,0,LB,"ALARMAA",P,"X","","","","S1","C1",0,0,"test1"

AAA,0,RB,"ALARMAA",W,"mm","","","","S2","C2",0,0,"test2"

The format for deleting an existing Associated Action entry for an alarm is as follows. It starts with the keyword "DAAA". Show table

No.	Description	Type	Size (bytes)	Values
1	Record type	Character	6	DAAA
2	Type of action (0 = action associated with alarms)	Numeric	2	0
3	Button for selection (LB = left, RB = right)	Character	2	LB or RB
4	Variable name	Character	40
5	Program/window flag (P= program, W = window)	Character	1	P or W
6	Name of program or window	Character	12
7	Branch	Character	30
8	Function	Character	30
9	Arguments (in quotes)	Character	2,047
10	List of producer stations	Character	14
11	List of consumer stations	Character	14
12	Origin of the object (0 if local, >0 if industry standard)	Numeric	2
13	Version number of the object	Numeric	2
14	Comment on the object	Character	80

The sequence of lines depends on the desired effect:

The first line is required if you do not wish to delete all of the entries. (Without it, all of the actions will be lost.)
From the second line onwards, at least five fields per line are required.

DAAA,0,PAR,"action 1 label Fra","action 1 label Eng","action 2 label Fra","action 2 label Eng"

DAAA,0,LB,"testAA",P,"x","","","","","",0,0,""

DAAA,0,RB,"testAA",W,"mm","","","","","",0,1,""