Field Unit address used for process logic and obtaining RTDB data.

For the Generic-Registers process, the options include:

• Generic Data Block – generic process for creating Report out of RTDB or file data.
• DISABLE THIS ROW – use this to temporarily disable one or more process rows.

RTDB register address containing the first of 5 Field Unit communication status registers (register should contain 7=good, 0=bad comms). If the communication status is checked and found to be in a failed state, the processing on this row will be skipped.

Following the convention of the Field Unit's Comm Status Holdreg, use a 40,xxx register to point to the communication status register in the System Status RTU, or use a 30,xxx register to point to the communication status register in the Field Unit's own RTDB.

Set CommStatReg to 0 to check protocol status of the Master Channel's protocol driver instead of a Comm Status Holdreg register.

Set CommStatReg to -1 to ignore the communication status. Process logic for this row will occur regardless of comms status.

If this row uses a Process-RTDB-Report or Process-PBuf-Report type:

If DataRegs is non-zero, that RTDB register in Channel/RTU is used as the "base register" for Report generation. The Report defines offsets from DataRegs.

This option may be used when more than one block of similar data is stored in the RTDB; thus, the same Report can be reused by setting DataRegs to the starting register of each block of registers. (For example: Field Units 1 and 2 each have analogous blocks of data at 40001-40020 and 40101-40120. Four rows could be defined in Generic Registers with different RTU address (1 and 2) and DataRegs column (starting address 40001 and 40101), and Report defined with data elements at Offset 0 through 19; the same Report would be called four different times using data from different units and different blocks of data).

If DataRegs is zero, the Report must be defined using actual register addresses in the RTDB.

This option might be used, for example, if a set of numbered addresses with similar data is used in multiple Channel/RTU/RTDB. The registers do not have to be in a contiguous block of addresses. (For example: Field Units 1 through 10 each have an analogous data at 10001-5 and 40001-40020. Ten rows could be defined in Generic Registers with different RTU addresses, DataRegs set to 0, and the Report defined with data elements at fixed register locations 10001-10005 and 40001-40020; the same Report would be called ten different times using data from different units).

If this row uses a Process-FILE-Report type:

DataRegs should be the RTDB register of a STRING type value, where the Tag Name of the register must be defined as the name of the text file containing data to process. The directory "/tmp/director/" is added to the beginning of the Tag Name, plus a suffix "_CC_RRRRR" is automatically appended to the Tag Name (where CC is the Channel and RRRRR is RTU/Field Unit address configured on this row, each with leading zeros as needed). The contents of the specified DataRegs RTDB register is unused.

For instance, assume there is a text file containing ASCII data, stored with the filename of  /tmp/director/MyData_01_0005. For this row, configure Channel=1 and RTU=5. If DataRegs is configured as 48001, then the Channel 1, unit 5, Tag Names object should have register 48001 defined with a Tag Name of "MyData". The above filename will be opened and used to generate the output Report.

The TrigMode option selects a method for triggering the Report generation. See below for more information on the TrigMode options.

For instance, the Report generation logic could be triggered based on timing (day, minute, or hour), on a register value matching a certain condition, or any change in the value of any register in a block of registers.

If a Report generation logic is "triggered," the trigger value in the TrigReg can be modified based on the TrigAdjust option (e.g., to prevent the Report from being immediately triggered again). TrigAdjust options are:

• None - no modification to TrigReg after Report generation.
• REMOTE INCREMENT - Increment the trigger value and write it to remote Channel/RTU/TrigReg register. Set TrigWrap and Parm1 to handle roll-over.
• REMOTE DECREMENT - Decrement the trigger value and write it to remote Channel/RTU/TrigReg register. Once the value decrements to zero, it will not be decremented further.
• REMOTE ZERO - Set the trigger value to zero and write it to remote Channel/RTU/TrigReg register.
• RTDB INCREMENT - Increment the trigger value and set the Channel/RTU/TrigReg RTDB register. Set TrigWrap and Parm1 to handle roll-over.
• RTDB DECREMENT - Decrement the trigger value and set the Channel/RTU/TrigReg RTDB register. Once the value decrements to zero, it will not be decremented further.
• RTDB ZERO - Set the trigger value to zero and set the Channel/RTU/TrigReg RTDB register.

If the TrigAdjust "INCREMENT" option is used, TrigWrap tells at what point the value should roll over to its low ("WrapTo") value. If TrigWrap is greater than 20000, it is used as a register point to a maximum "Increment" value. If less than 20001, it is a constant value.

For instance, if TrigWrap is set to 40001, and the value in 40001 is 30000, then if the TrigReg register will be incremented to 30000, then after the next Report trigger, it will be set to the value in Parm1.

If the TrigAdjust "INCREMENT" option is used, Parm1 contains the "WrapTo" value. Once the value rolls over at its maximum limit, it will be set to the constant integer contained in Parm1.

For instance, this may be used to set the minimum roll-over value to 1 instead of 0, if a particular trigger value requires it.

(This is the "Parm2" parameter.)

If the TrigMode "CRC" option is used, this value determines the number of sequential registers starting at DataRegs that will be calculated for the CRC, to determine if any of the registers has changed. See below for a discussion on the TrigMode options.

Field Unit address useof the Omni or Allen Bradley device.

For the Time-Syncs process, the options include:

• Omni Time Sync – special logic for sending time to Omni flow computer 
• DF1 Time Sync – special logic for sending time to Allen Bradley PLC
• Ignore This Row – use this to temporarily disable one or more process rows.

RTDB register address containing the first of 5 Field Unit communication status registers (register should contain 7=good, 0=bad comms). If the communication status is checked and found to be in a failed state, the processing on this row will be skipped.

Following the convention of the Field Unit's Comm Status Holdreg, use a 40,xxx register to point to the communication status register in the System Status RTU, or use a 30,xxx register to point to the communication status register in the Field Unit's own RTDB.

Set CommStatReg to 0 to check protocol status of the Master Channel's protocol driver instead of a Comm Status Holdreg register.

Set CommStatReg to -1 to ignore the communication status. Process logic for this row will occur regardless of comms status.

Starting register in the RTDB for the device timestamp registers polled from the Omni or Allen Bradley device. In the Allen Bradley, some custom programming is required to place the timestamp into six consecutive registers (Year, Month, Day, Hour, Minute, Second), and a seventh register is written to by the RediGate, which the PLC must take the new timestamp and store into the PLC's clock. For the Omni, the RediGate will read the standard six timestamp registers (Omni registers 3867-3872: Hour, Minute, Second, Month, Day, Year).

Unused

RTDB address in Channel/RTU containing a trigger to synchronize the time whenever the TrigReg register is non-zero. This can be used, for instance, to read the "Power Fail" flag (Omni register 1829).

(This is the "Run" parameter.)

Optional parameter, can be used to automatically write the timestamp to the device once/day at a certain Hour and Minute.

(This is the "Parm1" parameter.)

Optional parameter, can be used to automatically write the timestamp to the device once/day at a certain Hour and Minute.

Field Unit address of the Omni Modbus unit used for process logic and obtaining RTDB data.

For the Omni-Modbus-Archives process, the options include:

• OMNI Modbus Archive – logic to retrieve and publish batch/ticket archives for an Omni Modbus flow computer.
• Spirit Modbus Archive – logic for Spirit flow computer (same as Omni Modbus logic?)
• Ignore This Row – use this to temporarily disable one or more process rows.

RTDB register address containing the first of 5 Field Unit communication status registers (register should contain 7=good, 0=bad comms). If the communication status is checked and found to be in a failed state, the processing on this row will be skipped.

Following the convention of the Field Unit's Comm Status Holdreg, use a 40,xxx register to point to the communication status register in the System Status RTU, or use a 30,xxx register to point to the communication status register in the Field Unit's own RTDB.

Set CommStatReg to 0 to check protocol status of the Master Channel's protocol driver instead of a Comm Status Holdreg register.

Set CommStatReg to -1 to ignore the communication status. Process logic for this row will occur regardless of comms status.

If DataRegs is non-zero, that RTDB register in Channel/RTU is used as the "base register" for Report generation. The Report defines offsets from DataRegs. For the Omni-Modbus-Archives process, this will generally be the block of data containing the latest archive record.

This option may be used when more than one block of similar data is stored in the RTDB; thus, the same Report can be reused by setting DataRegs to the starting register of each block of registers. (e.g., Field Units 1 and 2 each have an analogous block of data at 40001-40020 and 40101-40120. If more than one archive is obtained, multiple rows can be defined in this table for the same RTU address, and rows for each Modbus flow computer, with each row calling one or more Report definitions.

If DataRegs is zero, the Report must be defined using actual register addresses in the RTDB.

Unused

Unused

(This is the "Parm1" parameter.)

This must be set to the RTDB register used in the SOS table that enables and disables the poll for the actual archive data record. The processing logic will set this register to True (or 1) to enable the archive poll, and set it to False (or 0) once the record has been received.

Field Unit address of the Omni Modbus unit used for process logic and obtaining CMD 65 file data.

For the Generic Registers process, the options include:

• OMNI-7K Batch ASCII Archive – logic to retrieve and publish batch/ticket archive for Omni 7000 using Cmd65.
• OMNI-7K Snapshot ASCII Archive – logic for to retrieve and publish Snapshot archive for Omni 7000 using Cmd65.
• OMNI-6K Batch ASCII Archive – logic to retrieve and publish batch/ticket archive for Omni 6000 using Cmd65.
• OMNI-7K ALARM – logic to retrieve and publish Alarm archive for Omni 7000 using Cmd65.
• OMNI-7K AUDIT MEASUREMENT – logic to retrieve and publish Measurement Audit archive for Omni 7000 using Cmd65.
• OMNI-7K AUDIT SYSTEM – logic to retrieve and publish System Audit archive for Omni 7000 using Cmd65.
• Ignore This Row – use this to temporarily disable one or more process rows.

RTDB register address containing the first of 5 Field Unit communication status registers (register should contain 7=good, 0=bad comms). If the communication status is checked and found to be in a failed state, the processing on this row will be skipped.

Following the convention of the Field Unit's Comm Status Holdreg, use a 40,xxx register to point to the communication status register in the System Status RTU, or use a 30,xxx register to point to the communication status register in the Field Unit's own RTDB.

Set CommStatReg to 0 to check protocol status of the Master Channel's protocol driver instead of a Comm Status Holdreg register.

Set CommStatReg to -1 to ignore the communication status. Process logic for this row will occur regardless of comms status.

(This is the "DataRegs" parameter.)

The FileNameReg should typically be a STRING type register in the RTDB, which is used by the Poll Table to specify the name of the file created by the Modbus CMD 65 data acquisition of the raw ASCII report. The Tag Name of this register identifies the filename; the retrieved file to be processed will be stored in /tmp/director/ with a filename of TagName_CC_RRRRR, where "TagName is the tag of the FileNameReg, "CC" is the Master Channel number and RRRRR is the Modbus unit ID (the Omni CMD 65 poll automatically appends these numbers with the underscores).

Unused

RTDB address in Channel/RTU containing data to trigger when the raw ASCII text file has been acquired and is ready to be processed.

• For Omni 7K (Batch, Prover): TrigReg must point to the 1st of 9 registers in the RTDB used by Cmd65 data acquisition (1st register=Request ID, 8th register=Number of records, 9th register=Newest record ID).
• Omni 7K Snapshot: TrigReg indicates when new Snapshot ASCII file has been acquired (for instance, the first 128 bytes of Snapshot report could be polled, containing header lines of ASCII file, and use Timestamp option to update 32-bit timestamp when the header data changes → use the Timestamp for TrigReg).
• For Omni 6K: TrigReg is a register that changes when a new ASCII report is available (for instance, could be a Timestamp register generated based on data changing in the poll for ASCII data from Omni).

Unused

(This is the "TrigWrap" parameter.)

• Omni 7K – RTDB register containing feedback of requesting ASCII file report ID, to indicate when the report is ready. Register will contain 0=Report ready, 1=Pending (in process), 2=Error.
• Omni 6K – Unused

(This is the "Run" parameter.)

RTDB register for writing the "Count HistRecords" parameter, below, used to request a count of historical archives for certain types of Cmd65 reports (Alarm, Audit).

Otherwise, the HistRecord parameter is unused, other than optional use in an MQTT topic using the "${RUN}" variable.

(This is the "Parm1" parameter.)

This must be set to the RTDB register used in the SOS table that enables and disables the poll for the actual archive data record. The processing logic will set this register to True (or 1) to enable the archive poll, and set it to False (or 0) once the record has been received.

(This is the "Parm2" parameter.)

This is the count of historical records needed in the request for certain types of historical archives. This is the value written into HistRecord, above.