Issue/Rev. 0.1 (9/13) ║ MNFL003 • Page 11
Bit#
Bit 31
. . .
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Value
16
8
4
2
1
Recipe
N/A
R5
R4
R3
R2
R1
Example: If recipes 3 and 5 are the only valid recipes for this load, the value to write to
this register prior to authorization would be:
2
(5-1)
+ 2
(3-1)
= 2
4
+ 2
2
= 16 + 4
= 20
Range is 0-4095
Note:
The Communications Port Control must be set to Host Control for the Allocated Blend Recipes Function.
2.30
Batch Preset/Authorization Options
The batch can be reset by writing to register 40578. The value written selects the recipe
for the new batch as follows:
0 - Reset batch, new batch will be the same recipe as current batch
1 - Reset batch, new batch will be recipe 1
2 - Reset batch, new batch will be recipe 2
3 - Reset batch, new batch will be recipe 3
4 - Reset batch, new batch will be recipe 4
2.31
Read Transaction Log
The transaction data is read from the same Modbus locations for both current and his-
torical transactions. Hence, historical transaction data should only be requested during
idle periods. Also, to read current data the Transaction Select register MUST BE SET
TO 0. After reading historic transaction log data, be sure to set the host transaction
select register back to 0 to be able to read current run data.
To retrieve transaction data:
Write host transaction select register - 0=current, 1 or greater = number back in storage
Function 6, register 40587
†
(unsigned integer)
Read Modbus host command result to assure the retrieval was successful
Function 4, register 3594 (254 on success, an error code from 1-99 otherwise)
Read the transaction data areas as you would for a current transaction
Example - read transaction header info – end time text, start time text
Function 4, registers 2384-2399 (text)
Function 4, registers 2400-2415 (text)
Example 2 - read unsigned character batch run data – recipe number
Function 4, register 5632 (unsigned integer)
microFlow.net Liquid Modbus Communications Manual
Implementing Remote Host Functionality
