Issue/Rev. 0.1 (9/13) ║ MNFL003 • Page 9
microFlow.net Liquid Modbus Communications Manual
Implementing Remote Host Functionality
09 Alarm Condition
10 Storage Full
11 Operation Out Of Sequence
12 Power Failed During Transaction
13 Already Authorized
14 Program Code Not Used
15 Display/Keypad In Remote Mode
16 Ticket Not In Printer
17 No Keypad Data Pending
18 No Transaction In Progress
19 Option Not Installed/Enabled
20 Start After Stop Delay In Effect
21 Permissive Not Met
22 Print Request Pending
23 No Meter Enabled
24 Must Be In Program Mode
25 Ticket Alarm During Transaction
26 Volume Type Not Available
27 Exactly One Recipe Must Be Enabled
28 Batch Limit Reached
29 Checking Entries
30 Product/Recipe/Additive Not Assigned To This Arm
31 Operation Conflicts With Arm Configuration
32 No Key Ever Pressed
33 Active Arm Limit Already Met
34 Transaction Not Standby
35 Swing Arm Out Of Position
36 Card-In Required
37 Data Not Available
38 Too Many Shared Additives
39 No Current Batch On This Arm
40 Must Use Minicomputer Protocol For This Operation
91 Communications Buffer Allocation Error
92 Keypad Locked
93 Data Recall Error
94 Not In Program Mode
95 Security Access Not Available
96 Internal Error
2.23
Program Mode Interface – Entering Program Mode via Modbus
Entry to Program mode via Modbus is done by simply writing a value to a configuration
register in the map (assuming all security requirements are met). Each write to the con-
figuration restarts the auto-logout timer. If three seconds transpire with no additional
updates (writes), it is assumed by the microFlow.net Liquid that the host has completed
the Program Mode session and the changes will be accepted and used (if all were valid).
See the Operator Reference manual for detailed descriptions of the various Program
Codes available for configuration of the microFlow.net Liquid.
2.24
Program Mode Interface – Explicit Logout Command
Register: 40577 (Function 6/16 – Write Holding Register) – word data
If it is not desired to wait for the three second period to expire, it is possible to force
the unit to exit program mode immediately by writing to the above register. If the value
1 is written, the preceding changes will be accepted and used. If the value 2 is written,
any changes made will be abandoned and the original values prior to entry into Program
mode by the Modbus host will continue to be used.
Note:
this immediate logout functionality is also assumed implicitly when host commands like Allocate Recipes
or Set Batch are issued when in Program mode via Modbus.
