1 Module number | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 255 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Assigned module number |
2 Operation state | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Operating state of the module |
1 | Unknown | State of module is not known |
2 | Init | Module is initializing |
3 | Idle | Module is idle and not currently processing |
4 | Running | Module is functioning correctly with no faults |
5 | Standby | Module is standing by waiting for action to be requested |
6 | Prepurge | Module is in prepurge condition |
7 | Ignition | Module is igniting |
8 | Run | Module is operating in response to demand |
9 | Postpurge | Module is in postpurge condition |
10 | Hold | Module is waiting for a period of time or until a condition clears |
11 | Disabled | Module is currently disabled for operation |
12 | Unconfig | Module configuration is not complete |
13 | Fault | Module is in a fault condtion that can be cleared without human intervention |
14 | Lockout | Module is in a fault condition that requires human intervention to clear it |
15 | Lightoff | Module is in a lightoff condition |
16 | Modulating | Module is running and modulating |
17 | Normal | Module is operating in it's normal expected function |
18 | Limit event | Module has encountered a limit occurrence |
19 | Setup | Module is in setup mode |
20 | Curve edit | Curve editing is occurring in module |
21 | Configuration load | A configuration load is in-progress in the module. |
3 Fault reason code | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reason code why this module is in a fault condition |
1 | No event | No event is currently being reported. |
2 | NV storage not initialized | Non-volatile storage is not initialized. |
3 | Configuration parameters mismatch | Configuration parameters do not match with Base module. |
4 | Configuration file received | Configuration parameter setting file has been received by this module. |
5 | Service disabled | This module's service has been disabled. |
6 | Service enabled | This module's service has been enabled. |
7 | Safety verification file received | Safety verification file received by this module. |
8 | Module powered up %s | This module has just powered up and is initializing. |
9 | Autogen reserved 9 | Reserved for future use |
10 | Autogen reserved 10 | Reserved for future use |
11 | Setting error for parameter %d "%s" | Invalid configuration parameter setting for this register has been detected. |
12 | Safety verification needed | Verification of one or more safety parameter changes is needed. |
13 | Safety relay not in correct state | Safety relay output was ON when it should be off or OFF when it should be on. |
14 | Safety relay optocoupler error | Safety relay optocoupler feedback was not valid. |
15 | Safety relay test failure | Safety relay failed during self-test. |
16 | Interlock is OFF when it should be ON | Interlock (ILK) string is OFF when it should be ON. |
17 | Preignition Interlock is OFF when it should be ON | Preignition Interlock (PII) string is OFF when it should be ON. |
18 | Main valve is NOT in correct state | Main valve (MV1) is ON when it should be off or is OFF when it should be on. |
19 | Second Main valve is NOT in correct state | Second Main valve (MV2) is ON when it should be off or is OFF when it should be on. |
20 | Pilot valve is NOT in correct state | Pilot valve is OFF when it should be on or ON when it should be off. |
21 | Purge position is NOT proven by PPP | Purge position is NOT proven according to the PPP terminal. |
22 | Purge position is NOT proven by fan | Purge position is NOT proven by fan speed. |
23 | Lightoff position is NOT proven by LPP | Lightoff position is NOT proven according to the LPP terminal. |
24 | Lightoff position NOT proven by Fuel Air control | Lightoff position is NOT proven according to the Fuel Air control module. |
25 | Flame is ON when it should be off | Flame is present when no flame should be. |
26 | IAS/LOI input is OFF when it should be ON | IAS/LOI input is OFF when it should be ON |
27 | IAS input is ON during start check | IAS input is ON during start check |
28 | Flame ON when no flame should be present | Persistent flame is present during period when there should be no flame. |
29 | Manual Open Switch is OFF | Manual open switch (MOS) is OFF when it should be ON. |
30 | Forced recycle | Forced recycle time was exceeded in run |
31 | Flame is OFF | Flame is not present when it should be. |
32 | Safety relay feedback is OFF | Safety relay feedback is off when it should be on. |
33 | Reset button pressed | Reset button was pressed. |
34 | Fuel Air lockout requested | Fuel Air control module has requested a lockout. (%d) |
35 | Fuel Air hold requested | Fuel air control module requested a hold. |
36 | LCI/F1 and LCI/F2 were both ON | Both Fuel 1 and Fuel 2 inputs were ON simultaneously. |
37 | Fuel Air communications timeout | Communication with Fuel Air control module has timed out. |
38 | LCI/F1 was OFF | LCI/F1 input was OFF. |
39 | Purge time expired | Purge time has expired. |
40 | No demand | No demand is present. |
41 | Prepurge unproven by Fuel Air control | Prepurge rate was not proven by Fuel Air control module. |
42 | Flame is OFF early in run | Flame is OFF too early during run. |
43 | Ignition feedback error | Ignition relay is NOT in correct state. |
44 | PII start check failure | Preignition (PII) start check has failed. |
45 | Valve proving required | Valve proving is required. |
46 | VP leaky upstream | Upstream valve was leaky during valve proving. |
47 | VP leaky downstream | Downstream valve was leaky during valve proving. |
48 | ILK start check failure | ILK start check has failed. |
49 | Lightoff unproven by TACH | Lightoff unproven by tachometer feedback |
50 | Soft lockout expired | Soft lockout timer has expired. |
51 | Limit %d %s exceeded | Limit %d has been reached. |
52 | Limit %d %s communications failure | No communications or error in communication with limit %d socket. |
53 | Reset switch is stuck | It has been detected that the Reset switch is stuck in a pressed condition. |
54 | Weak flame in flame amp %d exiting PFEP | Weak flame detected by flame amplifier %d when exiting PFEP. |
55 | Weak flame in flame amp %d exiting DBI | Weak flame detected by flame amplifier %d when exiting DBI. |
56 | Weak flame in flame amp %d in Run | Weak flame detected by flame amplifier %d during Run. |
57 | IR flame amplifier NV storage not initialized | IR flame amplifier NV storage is not initialized. |
58 | IR flame amplifier DC voltage error | IR flame amplifier DC voltage error. |
59 | False flame in IR flame amplifier | False flame detected in IR flame amplifier. |
60 | IR flame amplifier HW error | IR flame Amplifier hardware error. |
61 | SSUV flame amplifier NV storage not initialized | SSUV flame amplifier NV storage is not initialized. |
62 | False flame in SSUV flame amplifier | False flame detected in SSUV flame amplifier. |
63 | SSUV flame amplifier invalid flame signal | Invalid flame signal in SSUV flame amplifier. |
64 | SSUV flame amplifier low duty | SSUV flame amplifier low duty cycle. |
65 | UV tube flame amplifier NV storage not initialized | UV tube amplicheck flame amplifier NV storage is not initialized. |
66 | False flame in UV tube amplicheck flame amplifier | False flame detected in UV tube amplicheck flame amplifier. |
67 | False flame in UV tube flame amplifier | False flame detected in UV tube flame amplifier. |
68 | UV tube shutter flame amp NV storage not init | UV tube shutter flame amplifier NV storage is not initialized. |
69 | False flame in UV tube shutter flame amplifier | False flame detected in UV tube shutter flame amplifier. |
70 | False flame in UV tube flame amplifier | False flame detected in UV tube flame amplifier. |
71 | Flame amplifier %d communications timeout | Communication with flame amplifier %d has timed out after several attempts. |
72 | Unknown internal flame fault | Internal flame fault is unknown. |
73 | Burner lockout in %s state | Burner was in %s state during lockout. |
74 | Burner lockout state time: %d | Burner state time was %d seconds at time of lockout. |
75 | Burner lockout cycles: %d | Burner lockout occurred in cycle %d. |
76 | Burner lockout run time: %d | Lockout occurred when burner running hours was %d. |
77 | Burner lockout: %s | Burner lockout: %s |
78 | Burner Soft lockout | Burner lockout is a Soft lockout. |
79 | Burner Hard lockout | Burner lockout is a Hard lockout. |
80 | LCI/F2 was OFF | LCI/F2 was OFF. |
81 | Opto strobe off test failure | Opto strobe off test has failed. |
82 | Vref terminal unpowered | Vref terminal is unpowered. |
83 | Timing cross check failure | Timing cross check has failed. |
84 | Limit %d %s sensor failed | Limit %d sensor failure has occurred. |
85 | External reset switch stuck | External reset input is stuck in the ON condition. |
86 | Flame sensor timing cross check failure | Flame sensor has timing cross check fault |
87 | Fuel/air position mismatch | Fuel Air control module has a position mismatch. |
88 | Fuel Air module challenge response failure | Fuel Air control module has a challenge response failure. |
89 | Fuel Air module timing cross check failure | Fuel air module has a timing cross check failure. |
90 | Safety relay pulse test failure | Safety relay pulse test has failed. |
91 | Safety relay MFO signal failure | Safety relay MFO test has failed. |
92 | Flame amplifier communications fault %d | Communication fault(s) %d with flame amplifier has occurred. |
93 | Secondary flame sensor fault | Secondary flame sensor has a fault. |
94 | Both LCI/F1 and LCI/F2 were OFF | LCI/F1 and LCI/F2 are configured as fuel select limits, and both were off. |
95 | Fuel mismatch with Fuel Air control | Fuel Air control module has a fuel mismatch with the burner control. |
96 | Rectification flame amp NV storage not initialized | Rectification flame amplifier NV storage is not initialized. |
97 | Rectification flame amplifier 18V fault | Rectification flame amplifier 18V power supply fault. |
98 | False flame in Rectification flame amplifier | False flame detected in Rectification flame amplifier. |
99 | Rectification flame amplifier HW error | Rectification flame amplifier hardware error. |
100 | SSUV flame amplifier HW error | SSUV flame amplifier hardware error |
101 | SSUV flame amplifier Low 18V | SSUV flame amplifier Low 18V |
102 | UV tube flame amplifier HW error | UV tube flame amplifier hardware error |
103 | UV tube flame amplifier Low 18V | UV tube flame amplifier Low 18V |
104 | Fuel Air module disabled | Fuel Air control module is disabled. |
105 | Fuel changed during cycle | Fuel selection has changed during a running cycle. |
106 | Interlock glitch detected | Interlock momentarily went OFF. |
107 | Invalid flame fault code | Invalid flame amplifier event/fault code. |
108 | Non-volatile storage not initialized in flame amp | Non-volatile storage not initialized in flame amplifier. |
109 | Conflict with parameter %d "%s" | Setting conflict with this configuration parameter and another one. |
110 | SSUV flame amp flame on threshold out of range | Flame on threshold for SSUV flame amplifier %d is out of range. |
111 | SSUV flame amp weak flame threshold out of range | Weak flame threshold for SSUV flame amplifier %d is out of range. |
112 | SSIR flame amp flame on threshold out of range | Flame on threshold for SSIR flame amplifier %d is out of range. |
113 | SSIR flame amp weak flame threshold out of range | Weak flame threshold for SSIR flame amplifier %d is out of range. |
114 | UV tube flame amp flame on threshold out of range | Flame on threshold for UV tube flame amplifier %d is out of range. |
115 | UVtube flame amp weak flame threshold out of range | Weak flame threshold for UV tube flame amplifier %d is out of range. |
116 | RECT flame amp flame on threshold out of range | Flame on threshold for rectification flame amplifier %d is out of range. |
117 | RECT flame amp weak flame threshold out of range | Weak flame threshold for rectification flame amplifier %d is out of range. |
118 | Flame amplifier type mismatch | Flame amplifier selected type does not match with installed flame amplifier. |
119 | Cross check setting error for parameter %d "%s" | Setting of this parameter is not consistent with the setting of another related parameter. |
4 Fault source | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | System source that requested the fault |
1 | Internal | Fault detected internally within this module |
2 | Burner control | Fault detected by a burner control module within the system |
3 | Fuel air control | Fault detected by a fuel air control module within the system |
4 | Limit | Fault detected by a Limit module within the system |
5 | Wire sheet | Fault detected by application wire sheet |
6 Alert display level | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte U8 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 Yes Yes - Configuration data No Yes - Can set up in AX |
|
Description: | Enable/disable alert output (0=Disable, >0=Alert context level) |
7 Install date | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 Yes Yes - Configuration data No Yes - Can set up in AX |
|
Description: | Date when this module was installed in this system |
8 Service enable | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes No - RAM data No (not applicable) |
|
Description: | Enable the module for operation |
1 | Service disabled | Service for module is not disabled. No functional operation is expected from this module. |
2 | Service enabled | Service for this module is enabled. |
9 OS number | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String R8001B2001 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: | Manufacturer part number |
10 Serial number | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: | Factory serial number |
11 Build code | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: | Software build code |
12 Module identifier | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String BCp.0101.01 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: | Module identification code |
13 Module type | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String BC |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 10 No - Read Only No - RAM data No (not applicable) |
|
Description: | Type of module |
14 Module version | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 101 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Module version (compatibility code) |
15 Module revision | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Module revision |
16 Module short name | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String Burner |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 10 Yes Yes - Configuration data No Yes - Can set up in AX |
|
Description: | Short module name for Base display use |
17 Module name | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String Burner Control |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 60 Yes Yes - Configuration data No Yes - Can set up in AX |
|
Description: | Full module name for display use |
18 LED control | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes No - RAM data No (not applicable) |
|
Description: | LED and Display On/Off control (0=Off, >0=On) |
19 Keypress event | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Indicates that a button was pressed |
1 | Select button pressed | Select button pressed |
2 | Reset button pressed | Reset button pressed |
20 Verification needed | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Indicates verification is needed in this module |
21 Rx comm diagnostics | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: | Rx diagnostic data |
22 Tx comm diagnostics | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: | Tx diagnostic data |
23 Hardware version | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Hardware version |
24 Software build description | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 24 No - Read Only No - RAM data No (not applicable) |
|
Description: | Software build description |
26 LED display software revision | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 8 No - Read Only No - RAM data No (not applicable) |
|
Description: | Identifies the software version of the LED display board microcomputer |
100 Driver relay state for T4,T5 | Category: System Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 Yes No - RAM data No (not applicable) |
|
Description: | Register used to control the K1 (T4,T5) relay when it is not used as a blower or hot surface ignitor output and is provided for wire sheet use. |
102 Rate command | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the rate command from BC during burner contol operation. |
1 | None | No command is currently provided. |
2 | Standby command | Burner Control is requesting the Standby position |
3 | Prepurge command | Burner Control is requesting the Prepurge position |
4 | Lightoff command | Burner Control is requesting Lightoff position |
5 | Modulate command | Burner Control is lit and requesting Modulate (follow curves) |
6 | Postpurge command | Burner Control is requesting the Postpurge position |
103 Selected fuel | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the currently selected fuel. If dual fuel is enabled this is driven by the LCI input that is on, or if both LCI inputs are off but there is history then the previous selection is reported, else the unknown value is reported. |
1 | Unknown fuel selection | Reported when dual fuel is selected, but LCI/F1 and LCI/F2 are both off, and the BC doesn't know anything about history (i.e. power up just occurred). |
2 | Selected fuel is F1 | A single fuel is selected, or a dual fuel is selected and LCI/F1 is on. |
3 | Selected fuel is F2 | A single fuel is selected, or a dual fuel is selected and LCI/F2 is on. |
4 | Selected fuel was F1 | Used when dual fuel is configured and both LCI/F1 and LCI/F2 are off. Reports the most recently selected fuel (useful during postpurge). |
5 | Selected fuel was F2 | Used when dual fuel is configured and both LCI/F1 and LCI/F2 are off. Reports the most recently selected fuel (useful during postpurge). |
104 Fuel Air control reported fuel | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Fuel selection status reported by the Fuel Air control module in it's safety packet to the Burner control. |
1 | Disabled | Fuel air control is reporting that it is disabled. Burner control should not start up. |
2 | Active fuel 1 | Curve set for fuel 1 is active. |
3 | Active fuel 2 | Curve set for fuel 2 is active. |
4 | Invalid fuel 1 | Curve set for fuel 1 is invalid. Need setup or verification. |
5 | Invalid fuel 2 | Curve set for fuel 2 is invalid. Need setup or verification. |
105 Fuel Air control reported position | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the position of the Fuel Air control to the Burner control. |
1 | Unknown | |
2 | Moving to Idle | |
3 | At Idle | |
4 | Moving to Standby | |
5 | At Standby | |
6 | Moving to Prepurge | |
7 | At Prepurge | |
8 | Moving to Light off | |
9 | At Lightoff | |
10 | Moving to throttle position | |
11 | At throttle position | |
12 | Moving to Postpurge | |
13 | At Postpurge |
106 Fuel Air control Lockout reason | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the Lockout reason provided by the Fuel Air control to the Burner control. |
1 | None | Fuel Air does not have an active Lockout request for the Burner |
2 | Selected fuel not commissioned | Fuel Air is requesting a Burner Lockout because the active fuel is not fully commissioned |
107 Fuel Air control Lockout parameter | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 0 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the parameter for the lockout code provided by the Fuel Air control to the Burner control. |
108 Fuel Air control Hold reason | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the hold code provided by the Fuel Air control to the Burner control. |
1 | None | Fuel Air does not have an active Hold request for the Burner |
2 | Fuel Air is disabled | Fuel Air is requesting the Burner to Hold because it is Disabled |
3 | User login required | Fuel Air is requesting the Burner to Hold because an adequately priviliaged user must login |
4 | Fuel Air fault detected | Fuel Air is requesting the Burner to Hold because it has detected a fault |
5 | Fuel selection unknown or invalid | Fuel Air is requesting the Burner to Hold because it the Fuel selection is Unknown |
6 | Actuator Setup incomplete | Fuel Air is requesting the Burner to Hold because Actuator Setup is incomplete |
7 | VFD Setup incomplete | Fuel Air is requesting the Burner to Hold because VFD Setup is incomplete |
8 | Safety Verification needed | Fuel Air is requesting the Burner to Hold because Safety Verification is needed |
9 | Fuel 1 commissioning incomplete | Fuel Air is requesting the Burner to Hold because Fuel 1 commissioning is incomplete (walking curves is required) |
10 | Fuel 2 commissioning incomplete | Fuel Air is requesting the Burner to Hold because Fuel 2 commissioning is incomplete (walking curves is required) |
11 | Burner Control module number invalid | Fuel Air is requesting the Burner to Hold because the Burner Module Number is not valid |
12 | Curve set loading in progress | Fuel Air is requesting the Burner to Hold because a Curveset Load is occurring |
109 Fuel Air control Hold parameter | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 0 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the parameter for the hold code provided by the Fuel Air control to the Burner control. |
110 Soft lockout enable | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Master enable for soft lockouts. If this parameter is value is disable, then all soft lockouts become hard lockouts. |
1 | Disable | Feature is not enabled. |
2 | Enable | Feature is enabled. |
111 Soft lockout power cycle action | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Action to follow when the control power cycles and it is in a soft lockout condition. |
1 | Preserved through power cycle | Limit status is non-volatile and state retained through power loss |
2 | Cleared by power cycling | Limit status is cleared upon loss of power |
112 Hard lockout power cycle action | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Action to follow when the control power cycles and it is in a hard lockout condition. |
1 | Preserved through power cycle | Limit status is non-volatile and state retained through power loss |
2 | Cleared by power cycling | Limit status is cleared upon loss of power |
113 Soft lockout delay time | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 60 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Length of time to delay after a lockout occurs before automatically clearing the lockout and resuming. |
114 Register demand sources | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data No Yes - Can set up in AX |
|
Description: | Identifies the registers used to request burner demand. |
1 | Do not use registers for demand | |
2 | Demand 1 Register | |
3 | Demand 2 Register | |
4 | Demand 1 OR Demand 2 Register |
115 Forced recycle time | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
hour U16 0 0 24 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
71 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Maximum length of time that the burner can continuously run before it is automatically recycled (0 = Disabled). |
116 K1 relay usage | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | This parameter specifies how the K1 relay will be used. If Wire sheet is chosen then the relay is not used by the burner control and may be controlled by wire sheet logic. If Hot Surface Ignitor is chosen then the relay is closed during the PreIgnition state and throughout the Direct Burner Ignition (DBI) state or Pilot Flame Establishing Period (PFEP), whicheve is enabled. Turning on the Hot Surface Ignitor option disables the IGN output: it remains off. If Blower is chosen then the relay is closed at the start of Prepurge and it remains closed up through the end of Postpurge. |
1 | Wiresheet | Relay is controlled by wiresheet logic. |
2 | Hot surface ignitor | Relay is used for Hot surface ignitor (HSI). |
3 | Blower | Relay is used for blower output. |
119 Fuel Air control module number | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 0 99 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the Fuel/Air control module that interacts with the burner control. 0 = disabled, no such Fuel Air control exists. |
120 Prepurge rate (RPM) | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
revolutions per minute U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
104 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | This parameter specifies the rate that will be used for prepurge when this rate is a direct RPM value provided by the burner control. Wire sheet logic may read this value to operate the rate output control. When rate proving is via RPM feedback, the value provided here is the value that is tested vs. the feedback. |
121 Prepurge rate proving | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Determines whether and how the modulation rate is proven during prepurge. |
1 | Disable | Prepurge does not need to be proven. |
2 | PPP switch | Prepurge is proven by an input switch. |
3 | Fuel air control | Prepurge is proven by data sent from the Fuel Air ratio control. |
4 | Fan RPM | Prepurge is proven by RPM feedback (e.g., a tachometer input). |
122 Lightoff rate (RPM) | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
revolutions per minute U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
104 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | This parameter specifies the rate that will be used for lightoff when this rate is a direct RPM value provided by the burner control. Wire sheet logic may read this value to operate the rate output control. When lightoff rate proving is via RPM feedback, the value provided here is the value that is tested vs. the feedback. |
123 Lightoff rate proving | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Determines whether and how the modulation rate is proven during lightoff. |
1 | Disabled | Lightoff does not need to be proven. |
2 | LPP switch | Lightoff position is proven by a switch. |
3 | Fuel Air control | Lightoff is proven by data sent from the Fuel Air control. |
4 | Fan RPM | Lightoff is proven by fan RPM feedback (e.g., via a tachometer). |
124 Rate proving delay | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 0 300 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies how long to wait for the modulation rate to be proven before giving up. If 0 is used the rate must be proven immediately. The maximum is 300 seconds (5 minutes). |
125 Fan speed tolerance | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
percent F32 0 0 100 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
98 4 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When prepurge and/or lightoff proving is configured to occur depending on measured fan RPM and when the measured speed differs from the specified speed by less than the value provided by this parameter and it has been in this range for 3 seconds, then fan speed is considered to be proven. It then remains proven as long as the speed remains within the tolerance band of this parameter. |
126 Ignitor duration | Category: Ignition Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | This parameter specifies how long a spark ignitor (IGN output) should be turned on during ignition. If a Hot Surface Ignitor is enabled then IGN must be disabled. Normal duration provides IGN power throughout the Pilot Flame Establishing Period (PFEP) or Direct Burner Ignition (DBI) time, whichever is enabled. Early termination tuns the IGN output off half-way through the PFEP period or one second prior to the end of the DBI time. |
1 | Disabled, use HSI | |
2 | Normal duration | |
3 | Early spark termination |
127 Ignition type | Category: Ignition Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Type of ignition system used. |
1 | Intermittent pilot | |
2 | Interrupted pilot | |
3 | Direct burner ignition |
128 Flame sensing system type | Category: Ignition Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Describes the number of flame sensors and how they are compared to determine whether successful flame is present. Valid values: Single flame sensor Two flame sensors with OR logic: flame detection is true if either sensor detects flame. Two flame sensors with AND logic: flame detection is true only if both sensors detect flame Two flame sensors delayed: the first flame sensor must detect flame within the normal time, then a second sensor must also detect flame after a dleay time expires. Four flame sensors with OR logic, delayed: same as the previous case, except that each sensor is now paired with another sensor, and within those pairs OR logic is used: a pair detects tht flame is present if either sensor detects flame Four flame sensors with AND logic, delayed: same as the previous case, except that each sensor in the pair uses AND logic with its partner: each pair detects flame only if both sensors in the pair are sensing a flame. For delayed options, the delay time (see Secondary flame sensing delay).may be set to zero to mean "no delay" which causes the evaluation to be done immediately. Doing this makes some of the options above equivalent. |
1 | Single flame sensor | Flame is detected using a single flame sensor only. |
129 Secondary flame sensing time | Category: Ignition Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | This parameter specifies the time until the second flame sensor must report a flame when a "delayed" flame detection option is used. The delay time starts at the same time that the non-delayed sensor's time starts, and it is subject to the same pilot test hold. Example: if PFEP is 10 seconds and this parameter's delay time is 18 seconds, then the second sensor must prove flame within 18 seconds after the start of PFEP. |
130 Flame failure response time | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Maximum length of time between a loss of the sensed flame characteristic (light for optical sensors, current for rectification sensors) and the turn-off of power to the main fuel valves. (The desired response characteristic is to respond as close to this maximum time as possible, without exceeding it, to maximize tolerance of momentary flame signal loss conditions.) |
1 | Unknown | |
2 | 0.8 seconds | |
3 | 1 second | |
4 | 2 seconds | |
5 | 3 seconds |
131 Pilot valve hold enable | Category: Ignition Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies whether Pilot Valve Hold (PVH) behavior is enabled or not. |
1 | Disable | Feature is not enabled. |
2 | Enable | Feature is enabled. |
132 Pilot valve hold transition time | Category: Ignition Setup |
Units; DataType: Max: Default Value: Min: |
second U16 5 5 60 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | This parameter specifies the timing that occurs to establish the Pilot valve hold condition. If the value is less than 5 seconds then 5 seconds is used. |
133 Manual open switch enable | Category: Ignition Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | This parameter specifies if a manual open switch is to be used. It is a configuration fault if this input and also Direct burner ignition (DBI) is enabled; this feature must be used with a pilot system. When enabled with a hold for MOS closure: then a hold occurs at the start of MFEP if this input is off. There is no limit to the hold time. During the hold the pilot remains on as normal, and all normal flame monitoring and input monitoring performed during MFEP still occur, however the MFEP timer is held and during this hold the Main Valve outputs are commanded off and monitored to ensure that they are off. As soon as the MOS input is detected as on (including if it is on upon entry to MFEP) then a normal MFEP state occurs: normal MFEP timing begins and proceeds without monitoring of the MOS input. When enabled with immediate MFEP: No hold occurs and MFEP proceeds normally as if MOS were not used at all. In both cases, when MOS is enabled in either form: at the end of MFEP and all throughout subsequent states while the main valve is commanded on (e.g. Run Stabilization, Run) a MOS fault response occurs (e.g. a lockout) if the MOS input is detected as off. |
1 | Disable | |
2 | Enable with MFEP hold for MOS closure | |
3 | Enable with immediate MFEP |
134 Auto ignition enable | Category: Ignition Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | The auto-ignition feature allows a Limit module to provide indication that the combustion chamber is at or above an autoignition temperature (typically 1400 degrees minimum), and in this case the flame signal from the flame amplifier can be ignored. For this feature to become active one of the limit sockets in the BC must be configured to accept auto-ignition status, and this status must actually be received. |
1 | Disable | Feature is not enabled. |
2 | Enable | Feature is enabled. |
135 Delayed main valve 2 enable | Category: Ignition Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | If this feature is enabled then MV2 is turned on after flame has been established via MV1 (i.e. upon entry to Run). It is a configuration fault to enable this feature for a fuel that is also enabled for valve proving. |
1 | Disabled | |
2 | Enable always | Enabled for a single fuel or for both fuels in a dual fuel system. |
3 | Enable for fuel F1 | |
4 | Enable for fuel F2 |
136 Prepurge time | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 0 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Length of time to prepurge the burner to clear out any possible leftover fuel (0=Disable). |
137 Preignition time | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 0 120 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | During the pre-ignition state the ignitor is on but neither main valve(s) nor pilot are powered. A time of zero disables the pre-ignition state. This period is typically used either to prove that flame is not simulated by spark, since no flame signal is allowed during pre-ignition, or it is used as pre-heat time for a hot surface ignitor. |
138 Pilot flame establishing time | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 0 30 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Length of time allowed before requiring a flame to be present during ignition, when a pilot is used. Ignored if direct burner ignition (DBI) is enabled. |
139 Fuel 1 main flame establishing time | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 0 30 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Length of time that an interrupted pilot is on along with the main valve for Fuel 1. At the end of this time an interrupted pilot is turned off and only the main flame provides proof of combustion. (This parameter is ignored for an Intermittent pilot because there is no MFEP, and for Direct burner ignition because DBI time is a separate parameter.) |
140 Direct burner ignition time | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 0 4 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Length of time that the main valve may be on before flame must be proven when direct burner ignition is used. This parameter is ignored for other ignition types. |
141 Postpurge time | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 0 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Length of time to wait for the burner to clear excess fuel after it has been running or attempted to ignite (0=No postpurge). |
142 Fuel selection setup | Category: Interlocks Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | If set to "N/A - No Fuel Air module" then the BC does not use Fuel air communication. In this case, if the "Fuel Air Control Module number" parameter is non-zero then a configuration fault exists and a lockout occurs. A configuration fault lockout also occurs if this parameter has any other value but the "Fuel Air Control Module number" is zero. If a single fuel is selected via "Always use Fuel 1" or "Always use Fuel 2", then the reported fuel selection sent to a Fuel Air control will be according to that selection, no matter how the LCI/F1 and LCI/F2 inputs are used (or not used).. If "Use Limits LCI/F1 and LCI/F2 to select the fuel" is selected then both LCI/F1 and LCI/F2 must be configured for Limit functions; it is a configuration fault lockout if they are not. Also in this condition both may be off or one may be on, but a configured response occurs if both are on at the same time (except for a brief transition tolerance of 1 second). |
1 | N/A - No fuel air module | Fuel selection not applicable and is ignored. |
2 | Always use Fuel 1 | Single fuel is selected and will be reported as F1. |
3 | Always use Fuel 2 | Single fuel is selected and will be reported as F2. |
4 | Use Limits LCI/F1 and LCI/F2 to select the fuel | Dual fuel operation is selected via LCI/F1 and LCI/F2. |
143 LCI/F1 enable | Category: Interlocks Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When used as Demand, then a call for heat is present when the input is energized and when it is off (and also there is no other source for a call for heat) then the system returns to an idle condition in Standby with no call for heat and no hold condition. (This return to Standby may include going through Postpurge, if the burner was igniting or firing, but eventually it becomes idle.) When used as a Limit the call for heat comes from some other source and this input must turn on before startup will proceed. During the time when demand is present but LCI is open, a hold is annunciated, describing the reason. An LCI input configured as a limit must remain on throughout the prepurge, ignition, and run states; if it opens during these states then the startup or run condition is aborted abnormally and a configured response occurs. |
1 | Disabled | The input is disabled and ignored |
2 | Use as demand | The input acts as a demand input, call-for-heat is true when it is on. |
3 | Use as limit | The input acts as a run-permissive input. This selection is required for dual fuel. |
144 LCI/F2 enable | Category: Interlocks Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When used as Demand, then a call for heat is present when the input is energized and when it is off (and also there is no other source for a call for heat) then the system returns to an idle condition in Standby with no call for heat and no hold condition. (This return to Standby may include going through Postpurge, if the burner was igniting or firing, but eventually it becomes idle.) When used as a Limit the call for heat comes from some other source and this input must turn on before startup will proceed. During the time when demand is present but LCI is open, a hold is annunciated, describing the reason. An LCI input configured as a limit must remain on throughout the prepurge, ignition, and run states; if it opens during these states then the startup or run condition is aborted abnormally and a configured response occurs. |
1 | Disabled | The input is disabled and ignored |
2 | Use as demand | The input acts as a demand input, call-for-heat is true when it is on. |
3 | Use as limit | The input acts as a run-permissive input. This selection is required for dual fuel. |
145 Demand hold limit time | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 0 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Maximum time to wait in a Standby hold condition when demand is present. If it fails to resolve for this amount of time then a configured response occurs. 0= no limit, wait forever. |
146 Pre ignition interlock enable | Category: Interlocks Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When "Disabled" the PII input is ignored. When "Enabled with no dynamic check" then the PII input is tested to ensure that it is energized whenever the main valves should be off. Whenever the main valve status changes from 1 or both valves on, to both valves off, then 5 seconds is allowed before checking for the energized state resumes, to give them time to fully close their proof-of-closure switches. If dynamic check is not enabled then the off condition of the PII is never tested, that is, normal operation occurs even if PII is continuously powered at all times. However if the PII input is "Enabled with dynamic check", then during the Run state the PII input must be de-energized. If any testing reveals that the PII is not in its mandated position then a configured response occurs. |
1 | Disabled | PII input is not monitored for any condition. |
2 | Enabled with no dynamic check | PII input is monitored for the On condition, but Off is not checked. |
3 | Enabled with dynamic check | PII input is monitored for both the On and Off conditions. |
147 ILK start check enable | Category: Interlocks Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies whether the interlock (ILK) input must be off at startup as a check that proves it is possible for it to signal the off condition. If ILK is on, the control waits for it to turn off before startup is allowed. If it fails to turn off for 4 minutes then a configured response occurs. |
1 | Disable | Feature is not enabled. |
2 | Enable | Feature is enabled. |
148 IAS start check enable | Category: Interlocks Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies whether the interrupted air switch (IAS) input must be off at startup as a check that proves it is possible for it to signal the off condition. If IAS is on, the control waits for it to turn off before startup is allowed. If it fails to turn off for 4 minutes then a configured response occurs. |
1 | Disable | Feature is not enabled. |
2 | Enable | Feature is enabled. |
149 IAS/LOI monitoring | Category: Interlocks Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | This input can be configured as either an interrupted air switch or a lockout input (primarily used in EC applilcations). When monitored as an IAS input then during Prepurge it is not a fault for the input to be off until the "Airflow proving maximum wait time" has elapsed. The measured purge timing does not begin until the IAS is energized. If configured as a LOI input then it must be energized at all times, except that during initialization it is given time to turn on. If the input is in an incorrect state then a configured response occurs. |
1 | Disable | IAS and LOI are not monitored. |
2 | IAS: Prepurge only | IAS is monitored during prepurge only. |
3 | IAS: Prepurge/Ignition | IAS is monitored during prepurge and ignition. |
4 | LOI: At all times including Standby | LOI is monitored at all times. |
150 ILK monitoring | Category: Interlocks Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies when the interlock (ILK) string is monitored by the control. This input can be configured as either an a normal interlock input or a lockout input (as is typically used in EC applilcations). When monitored as a normal interlock input then during Prepurge it is not a fault for the input to be off until the "Airflow proving maximum wait time" has elapsed. The measured purge timing does not begin until the ILK input is energized. If configured as a LOI input then it must be energized at all times, except that during initialization it is given time to turn on. If the input is in an incorrect state then a configured response occurs. |
1 | LOI: At all times including Standby | Use this input as a lockout input, such that if it ever turns off a configured response (such as a lockout) occurs. |
2 | During Prepurge, Ignition, and Run | Use the input as a normal interlock input, where the "Airflow proving maximum wait time" is used as a tolerance time during Prepurge. |
151 ILK/IAS proving maximum wait time | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 0 60 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | This parameter provides the time that a de-energized ILK (or IAS, whichever is configured) is tolerated measured from the start of the prepurge state. (In previous controls this time was fixed; however in this system it is programmable to accomodate VFDs which take a longer time to provide airflow.) If this time is exceeded without establishing the monitored input as energized, then a configured response occurs. |
152 Early purge proving delay | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 30 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | If purge proving is enabled and it is proven immediately upon entry to the prepurge state then an extra delay occurs that lasts for the duration defined by this parameter. 0=accept the proven condition with no delay. |
153 Early lightoff proving delay | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 30 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | If lightoff proving is enabled and it is proven immediately upon entry to the drive-to-lightoff state then an extra delay occurs that lasts for the duration defined by this parameter. 0=accept the proven condition with no delay. |
154 Purge rate proving failure response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to a failure to achieve the target firing rate during purge within the time provided by the "Rate proving delay" parameter. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
155 Lightoff rate proving failure response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to a failure to achieve the target firing rate during lightoff within the time provided by the "Rate proving delay" parameter. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
156 Valve proving failure response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to a failure to prove that the valve is functioning properly during the valve proving test. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
157 Pilot ignition failure response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response when the pilot fails to ignite. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
158 Main ignition failure response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response when a satisfactory main flame is not established during ignition. This response is used for flame failure during DBI, MFEP, and during the first 10 seconds of the Run state. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
159 Run flame failure response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to a loss of satisfactory flame after the burner has entered the Run state. This response is used for flame failures that occur after the first 10 seconds of the Run state. Prior to this, during DBI, MFEP, or the first 10 seconds of Run, the Ignition flame failure response is used. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
160 LCI open response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Only when LCI/F1 or LCI/F2 is defined as a Limit input, then this parameter identifies the action to take in response to LCI opening abnormally while it should be closed during the burner sequence. Does not apply if LCI/F1 or LCI/F2 is defined as a Demand input, because then its opening during a sequence is a normal indication of the end of demand. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
161 Demand hold limit response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to exceeding the "Demand hold limit time" when there is a call for heat. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
162 PII open response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to PII being open when it should be closed during the burner sequence. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
163 ILK open response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to ILK being open when it should be closed during the burner sequence. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
164 IAS / LOI open response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to Interrupted Air Switch being open when it should be closed during the burner sequence. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
165 ILK/IAS start check failure response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to a failure of the start check for the ILK and/or IAS inputs. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
166 PII dynamic check failure response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to a failure of the dynamic check of the PII input to ensure that it signals the Off condition during Run. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
167 Dual fuel fault response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to both LCI/F1 and LCI/F2 being energized (an invalid condition) when dual fuel is enabled. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
168 Flame amplifier fault response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to a failure in the flame detector system. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
169 MV PV IGN on should be off response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take if an input is on when it should be off (e.g. its shorted to power). |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
170 MV PV IGN off should be on response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to an input that should be powered but is not (internal fault). |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
171 Safety relay fault response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take if the safety relay is in the wrong state (internal fault). |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
172 Flame on should be off response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in when the flame is on when it should be off in any state. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
173 Manual open switch off response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take if the Manual Open Switch is off when it should be on (during MFEP and Run). |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
174 Fuel air communication fault response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take if the fuel air control does not have reliable communication with the burner control that is its partner. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
175 Limit communication fault response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to a failure in communication between the burner control and a limit module that is specified by the burner control to interact with the burner control. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
176 Stuck reset switch response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take if the Reset pushbutton is stuck. |
1 | Unknown | No specific response is determined for this failure. |
2 | Recycle 1 | Failure should perform a type 1 recycle response. |
3 | Recycle 2 | Failure should perform a type 2 recycle response. |
4 | Recycle 3 | Failure should perform a type 3 recycle response. |
5 | Soft lockout | Failure should perform a soft lockout. |
6 | Hard lockout | Failure should perform a hard lockout. |
177 Recycle 1 delay time | Category: Recycle Setup |
Units; DataType: Max: Default Value: Min: |
second U16 5 5 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the delay time that must take place while in Standby before retrying the burner sequence for the first recycle handler. The 5 second minimum ensures that the recycle reason has time to be displayed. |
178 Recycle 1 retry limit count | Category: Recycle Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 3 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Maximum number of recycle retries before giving up for the first recycle handler. Retry counting is cleared when the burner reaches the Run state or when call for heat disappears. |
179 Recycle 1 retry limit response | Category: Recycle Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to the number of recycles hitting the retry limit for the first recycle handler. When the response is "None" the recycles continue forever until successful or demand is no longer requested. |
1 | None | |
2 | Soft lockout | |
3 | Hard lockout |
180 Recycle 2 delay time | Category: Recycle Setup |
Units; DataType: Max: Default Value: Min: |
second U16 5 5 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the delay time that must take place while in Standby before retrying the burner sequence for the second recycle handler. The 5 second minimum ensures that the recycle reason has time to be displayed. |
181 Recycle 2 retry limit count | Category: Recycle Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 3 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Maximum number of recycle retries before giving up for the second recycle handler. Retry counting is cleared when the burner reaches the Run state or when call for heat disappears. |
182 Recycle 2 retry limit response | Category: Recycle Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to the number of recycles hitting the retry limit for the second recycle handler. When the response is "None" the recycles continue forever until successful or demand is no longer requested. |
1 | None | |
2 | Soft lockout | |
3 | Hard lockout |
183 Recycle 3 delay time | Category: Recycle Setup |
Units; DataType: Max: Default Value: Min: |
second U16 5 5 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the delay time that must take place while in Standby before retrying the burner sequence for the third recycle handler. The 5 second minimum ensures that the recycle reason has time to be displayed. |
184 Recycle 3 retry limit count | Category: Recycle Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 3 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Maximum number of recycle retries before giving up for the third recycle handler. Retry counting is cleared when the burner reaches the Run state or when call for heat disappears. |
185 Recycle 3 retry limit response | Category: Recycle Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Identifies the action to take in response to the number of recycles hitting the retry limit for the third recycle handler. When the response is "None" the recycles continue forever until successful or demand is no longer requested. |
1 | None | |
2 | Soft lockout | |
3 | Hard lockout |
186 Valve proving enable | Category: Valve Proving Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | If this feature is enabled then valve proving is performed when the configured fuel is selected. It is a configuration fault to enable this feature for a fuel that is also enabled to use a delayed main valve. "Enable always" causes valve proving to be performed always, either for a single fuel or for both fuels in a dual fuel system. "Enable for dual fuel LCI/F1" and "Enable for dual fuel LCI/F2" are allowed only if the "Fuel selection setup" parameter enables dual fuels; otherwise a configuration fault occurs. |
1 | Disabled | Valve proving is not enabled. |
2 | Enabled always | Turns on valve proving for a single fuel, or for both fuels in a dual fuel system. |
3 | Enabled for dual fuel selected by LCI/F1 | Turns on valve proving for dual fuel when LCI/F1 is selected. |
4 | Enabled for dual fuel selected by LCI/F2 | Turns on valve proving for dual fuel when LCI/F2 is selected. |
187 Valve proving occurrence | Category: Valve Proving Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Determines when valve proving occurs if it is enabled. Valve proving includes two tests: one where the short pipe between the two shutoff valves is pressurized (high pressure test) and one where it is depressurized (low pressure test. The Before and After options both perform both of these parts together, one after the other. Valve proving Before runs simultaneously with Prepurge and will delay lightoff if it lasts longer than Prepurge. Valve proving After run simultaneously with Postpurge (if any) and will delay re-entry to the Standby state until it is done, if it lasts longer than Postpurge. The Both option is the same as selecting both of those. The Split option performs the high pressure test before Run (simultaneous with Prepurge) and the low pressure test after Run (simultaneous with Postpurge). This has the advantage of reducing valve cycling and avoiding the emission of a small amount of unburned fuel. |
1 | Before Run | Both pressure tests BEFORE entering the Run state only. |
2 | After Run | Both pressure tests AFTER in the Run state only. |
3 | Both before and after Run | Both pressure tests before and after entering the Run state. |
4 | Split | High pressure test before Run and low pressure test after Run. |
188 Valve proving open time | Category: Valve Proving Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 5 60 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Determines how long one valve is commanded to be open to pressurize or depressurize the pipe between the two shutoff valves. A typical value is 5 seconds for a slow valve; shorter times may be used for faster valves. |
189 Valve proving time | Category: Valve Proving Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 0 65535 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Test time needed to prove that valve leakage is acceptable during a valve proving test. |
190 Fuel 2 main flame establishing time | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 0 30 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Length of time that an interrupted pilot is on along with the main valve for Fuel 2. At the end of this time an interrupted pilot is turned off and only the main flame provides proof of combustion. (This parameter is ignored for an Intermittent pilot because there is no MFEP, and for Direct burner ignition because DBI time is a separate parameter.) |
202 First demand source | Category: Operating Control |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 0 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes No - RAM data No (not applicable) |
|
Description: | If enabled via the "Demand source" parameter, then this input may be set to a true value to create burner demand. The two demand registers, First demand and Second demand source may be configured to provide an OR function so that one may be used for normal demands from wire sheet logic and the other could be used as an operator override input for test firing the burner. |
203 Second demand source | Category: Operating Control |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 0 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes No - RAM data No (not applicable) |
|
Description: | If enabled via the "Demand source" parameter, then this input may be set to a true value to create burner demand. The two demand registers, First demand and Second demand source may be configured to provide an OR function so that one may be used for normal demands from wire sheet logic and the other could be used as an operator override input for test firing the burner. |
204 Pilot turndown test hold | Category: Operating Control |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 0 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes No - RAM data No (not applicable) |
|
Description: | Used to support the pilot turndown test required by burner standards for Intermittent and Interrupted pilots. It is ignored if the pilot type s DBI . If the Pilot type is Interrupted or Intermittent and this parameter is enabled then the burner control sequence will hold (forever) at 1 second into the Ignition state. A flame-out timer always starts at zero when the Ignition state is entered, then counts up toward 15 seconds while flame is off and down toward zero when flame is on. This timer may run whenever the Ignition state is active, but it has a possible effect only during the Pilot test: if it ever reaches 15 seconds of accumulated flame out time then a lockout occurs. (The Pilot test hold should be enabled prior to entering Ignition, since changes to parameters may require some seconds to take effect. Similarly, when the hold is Disabled the burner control may remain in the hold condition for a short time.) |
205 Fan speed | Category: Operating Control |
Units; DataType: Max: Default Value: Min: |
revolutions per minute U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
104 2 Yes No - RAM data No (not applicable) |
|
Description: | Fan speed input reported to the Burner Control for RPM-based rate proving. |
206 Burner control state | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Ignition state of burner control |
1 | Unknown | State of burner control is unknown. |
2 | Initiate | Initializing control for burner interface |
3 | Standby | Waiting for burner demand or hold event to clear |
4 | Safe start | Checking whether it is safe to start |
5 | Prepurge drive to purge rate | Driving the burner to it's purge rate to prepurge before firing |
6 | Prepurge measured purge time | Prepurging the system for a specified period of time before firing the burner |
7 | Prepurge drive to lightoff rate | Driving the burner to it's lightoff rate |
8 | Ignition test | Testing the ignition procedure |
9 | Ignition time | Waiting for ignition to complete |
10 | Pilot flame establishing period | Waiting for pilot flame to be ready |
11 | Main flame establishing period | Waiting for main flame to be ready |
12 | Direct burner ignition | Igniting the burner using direct ignition. |
13 | Run | Main flame is present and burner is modulating |
14 | Hard Lockout | Lockout requiring manual intervention to resolve has occurred |
15 | Postpurge | Clearing burner system in preparation to go to idle |
16 | Standby Delay | Waiting a period of time before allowing another burner firing |
17 | Pilot Valve Hold Transition | Waiting for pilot valve to turn on for hold test |
18 | Pilot Valve Hold | Burner is holding due to the pilot valve is on |
19 | Soft Lockout | Lockout has occurred that does not require manual intervention to resolve |
20 | Pilot flame stabilization period | Waiting for pilot flame to be stable |
207 Burner control state time | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
second U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Running time for a timed state event |
208 Hold reason code | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Provides the reason the burner is holding and not firing. |
1 | Not holding | No hold condition exists. |
2 | No demand requested in either demand register | Configured for register demand, but both registers have no demand requested. |
3 | LCI/F1 demand is off | LCI/F1 (Limit Control Input / Fuel 1) is configured for demand and it is off. |
4 | LCI/F2 demand is off | LCI/F2 (Limit Control Input / Fuel 2) is configured for demand and it is off. |
5 | LCI/F1 recycle limit is off | Demand exists, but LCI/F1 (Limit Control Input / Fuel 1) is configured as a recycle limit and it is off. |
6 | LCI/F2 recycle limit is off | Demand exists, but LCI/F2 (Limit Control Input / Fuel 2) is configured as a recycle limit and it is off. |
7 | Waiting for post purge to finish | Blower and FA is finishing postpurge in standby |
8 | No fuel selected by LCI/F1 and LCI/F2 | Demand exists, dual fuel is enabled, and both LCI/F1 and LCI/F2 are off. |
9 | Waiting for flame to turn off | Flame is still on. Waiting for it to turn off before leaving Standby. |
10 | ILK is on during start check | Safe start check is configured for Interlock input (ILK) to be off, but it is on. |
11 | IAS is on during start check | IAS input is on. |
12 | Fuel Air is reporting invalid fuel selection | Fuel Air control is not able to provide the fuel (F1 or F2) selected by the BC. |
13 | Waiting for PPP switch | Waiting for Purge Position Proven switch to close during prepurge. |
14 | Waiting for Prepurge from Fuel Air | Waiting for prepurge position proven to be reported by the fuel air control. |
15 | Waiting for Prepurge rate | Waiting for prepurge rate to be reported by a tachometer. |
16 | Waiting for LPP switch | Waiting for Lightoff Position Proven switch to close during prepurge. |
17 | Waiting for Lightoff from Fuel Air | Waiting for lightoff position proven to be reported by the fuel air control. |
18 | Waiting for Lightoff rate | Waiting for lightoff rate to be reported by a tachometer. |
19 | PII is off | PreIgnition Interlock (PII) input is off. |
20 | ILK is off | Interlock (ILK) input is off. |
21 | PII is on | Preignition (PII) is on. |
22 | No demand | No demand is present. |
23 | Waiting for Prepurge time | Waiting for timed prepurge to finish. |
24 | Waiting for Prepurge speed to be reached | Waiting for tachometer feedback to prove purge. |
25 | Pilot test | Waiting due to pilot test switch is on. |
26 | Valve proving | Waiting for valve proving to finish. |
27 | Recycle delay | Waiting for the recycle delay timer to expire. |
28 | MOS is Off | Manual Open Switch is OFF |
29 | LPP was on at entry | Lightoff proving position input was ON at entry to driving purge to the lightoff state. |
30 | PPP was on at entry | Purge proving position input was ON at entry to driving to the purge state. |
31 | Service is disabled | Burner control service has been disabled. |
32 | Fuel air hold request | Fuel air module has requested a hold. |
33 | IAS is Off | IAS/LOI input is off. |
34 | No demand from first Demand register | No demand from first Demand register. |
35 | No demand from second Demand register | No demand from second Demand register. |
36 | No demand from either Demand register | No demand in either Demand register. |
37 | No demand from LCI input | No demand from LCI input(s). |
38 | Unconfigured | Configuration parameters cannot be read |
39 | No demand from either register or LCI | No demand fron either demand register or LCI |
40 | No demand from first Demand register nor LCI | No demand is present in the first Demand register nor in LCI |
41 | No demand from second Demand register nor LCI | No demand is present in the second Demand register nor in LCI |
42 | No demand source is configured | No demand source is configured |
43 | LCI/F1 and LCI/F2 are off | Demand exists, but both LCI/F1 and LCI/F2 are configured as recycle limits and both are off. |
44 | Reserved 44 | Available for future use. |
45 | Waiting for Lightoff proving | Waiting for Lightoff proving |
46 | Flame sensor communication | Communication error with flame sensor |
47 | Internal flame sensor | Internal flame sensor |
48 | Limit exceeded | Limit is exceeded |
49 | Limit module communication | Communication error with Limit module |
50 | Limit socket faulty | Limit socket is faulty |
51 | Safety relay faulty | Safety relay is faulty |
52 | Ignition relay is On | Ignition relay is On |
53 | Pilot Valve is On | Pilot Valve is On |
54 | Main Valve 1 is On | Main Valve 1 is On |
55 | Main Valve 2 is On | Main Valve 2 is On |
56 | Fuel air module communications faulty | Communication with Fuel air module is faulty |
57 | Fuel air position fault | Fuel air position fault |
58 | Reset switch is stuck | Reset switch is stuck |
59 | External reset switch is stuck | External reset switch is stuck |
60 | Flame is Off | Flame is Off |
61 | Pilot Valve is Off | Pilot Valve is Off |
62 | Main valve 1 is Off | Main valve 1 is Off |
63 | Main valve 2 is Off | Main valve 2 is Off |
64 | Ignition relay is Off | Ignition relay is Off |
65 | Opto strobe test failure | Opto strobe test has failed |
66 | Vref terminal is not powered | Vref terminal is not powered |
67 | Timing crosscheck failure | Timing crosscheck has failed |
68 | Soft lockout delay | Delay due to soft lockout. |
69 | Fuel Air Disabled | Recycle/Hold due to the fuel air module disabled. |
70 | Fuel Changed | The fuel choice acquired while leaving standby has changed during the ignition cycle. |
71 | LCI/F1 and LCI/F2 are both on as fuel selects | LCI/F1 and LC/F2 are both on but only one should be on to select a fuel. |
72 | Forced Recycle | Holding because a forced recycle was requested |
209 Hold source | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | System source that requested the burner to be held |
1 | Burner control | |
2 | Fuel air control | |
3 | Limit control |
211 Lockout source | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data No (not applicable) |
|
Description: | System source that requested the burner to lockout |
1 | Burner control | |
2 | Fuel air control | |
3 | Limit control |
212 Lockout burner state | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data No (not applicable) |
|
Description: | Burner control state at the time when the current (or last) lockout occurred |
1 | Unknown | State of burner control is unknown. |
2 | Initiate | Initializing control for burner interface |
3 | Standby | Waiting for burner demand or hold event to clear |
4 | Safe start | Checking whether it is safe to start |
5 | Prepurge drive to purge rate | Driving the burner to it's purge rate to prepurge before firing |
6 | Prepurge measured purge time | Prepurging the system for a specified period of time before firing the burner |
7 | Prepurge drive to lightoff rate | Driving the burner to it's lightoff rate |
8 | Ignition test | Testing the ignition procedure |
9 | Ignition time | Waiting for ignition to complete |
10 | Pilot flame establishing period | Waiting for pilot flame to be ready |
11 | Main flame establishing period | Waiting for main flame to be ready |
12 | Direct burner ignition | Igniting the burner using direct ignition. |
13 | Run | Main flame is present and burner is modulating |
14 | Hard Lockout | Lockout requiring manual intervention to resolve has occurred |
15 | Postpurge | Clearing burner system in preparation to go to idle |
16 | Standby Delay | Waiting a period of time before allowing another burner firing |
17 | Pilot Valve Hold Transition | Waiting for pilot valve to turn on for hold test |
18 | Pilot Valve Hold | Burner is holding due to the pilot valve is on |
19 | Soft Lockout | Lockout has occurred that does not require manual intervention to resolve |
20 | Pilot flame stabilization period | Waiting for pilot flame to be stable |
213 Lockout burner state time | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
second U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data No (not applicable) |
|
Description: | Burner control state event timer value at the time when the current (or last) lockout occurred |
214 Delay time | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
second U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | This output contains a non-zero countdown timer value measured in seconds, when the timer is active. It indicates that the burner is delayed for a period of time. |
215 Retry counter | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Counts of the number of retries so far. During the first attempt the value shown here is zero, the first retry is shown as 1, the second as 2, etc. Retry count is reset by loss of demand or achieving the Run state. |
216 Shutter command | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Command sent to control the shutter in the flame amplifier. |
1 | Closed | Flame module shutter is commanded to close. Ampli-check remains active and Normal. |
2 | Open | Flame module shutter is commanded to stay open. Shutter-check and Ampli-check are both inhibited. Used to detect flame as soon as possible, without interference from the check routines. |
3 | Operate | Flame module shutter is commanded to operate normally, i.e. to perform periodic amplifier checks and shutter checks. |
4 | Ignore | Flame module is commanded to maintain timers, filters, and output as if flame is off. This is commanded when the BC is configured to manage an "interfering" flame signal (where the spark is known to simulate flame) and the spark is on. |
217 Safety relay drive state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the state of the main safety microcomputer's output signal that turns on its safety relay drive transistor. |
219 Ignition relay state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when the ignitor relay is turned on to provide power to the IGN output |
220 Pilot valve relay state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when the pilot valve relay is turned on to provide power to the PV output. |
221 Main valve 1 relay state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when main valve 1 relay is turned on to provide power to the MV1 output. |
222 Main valve 2 relay state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when main valve 2 relay is turned on to provide power to the MV2 output. |
223 K1 relay state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when the K1 relay is turned on. |
224 LCI/F1 input state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when Limit control input for fuel 1 (LCI/F1) is energized. |
225 LCI/F2 input state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when Limit control input for fuel 2 (LCI/F2) is energized. |
226 PII input state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when the preignition interlock (PII) is energized |
227 ILK input state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when the ignition interlock (ILK) string is energized |
228 LPP input state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when the lightoff position proven (LPP) input is energized. |
229 PPP input state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when the purge position proven (PPP) input is energized |
230 VPS input state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when the valve proving switch (VPS) input is energized. |
231 Pilot valve hold input state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when the pilot valve hold (PVH) input is energized. |
232 MOS input state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when the manual open switch (MOS) input is energized |
233 IAS input state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | True when the interrupted airflow switch (IAS) input is energized |
234 Safety relay optocoupler state | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | This input reports the state of the optocoupler which monitors safety relay coil current. If the coil is powered then this input will be on. |
235 Safety relay feedback | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | Feedback from the point downstream of the safety relay's contacts. When the upstream side is powered, then this feedback will be on when the safety relay contacts are closed and off when they are open. |
236 IGN feedback input | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | Feedback status from driving the ignitor (IGN) output |
237 PV feedback input | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | Feedback status from driving pilot valve (PV) output |
238 MV1 feedback input | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | Feedback from driving main valve for fuel 1 (MV1) output |
239 MV2 feedback input | Category: Terminal Status |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte bool |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 1 No - Read Only No - RAM data No (not applicable) |
|
Description: | Feedback from driving main valve for fuel 2 (MV2) output |
240 LCI/F1 first out trigger | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | First out trigger that fires when the LCI/F1 string opens during the burner sequence. |
241 LCI/F2 first out trigger | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | First out trigger that fires when the LCI/F2 string opens during the burner sequence. |
242 PII first out trigger | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | First out trigger that fires when the PII string opens during the burner sequence. |
243 ILK first out trigger | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | First out trigger that fires when the ILK string opens during the burner sequence. |
244 IAS first out trigger | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | First out trigger that fires when the IAS (LOI) string opens during the burner sequence. |
245 System flame status | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Overall status of flame for this burner |
1 | Not configured | |
2 | Unknown | |
3 | Off | |
4 | Weak | |
5 | On | |
6 | Faulty |
248 Analog input | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Analog input (mA/V) value |
249 Module run time minutes | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
minute U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
72 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Run time minutes for module before next full run hour elapses (not writable). |
256 Run time minutes | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
minute U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
72 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Accumulated run time minutes before next full run hour elapses. |
257 Annunciator ILK trigger | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 6 No - Read Only No - RAM data No (not applicable) |
|
Description: | Provides first out and hold flags, and also terminal status for the input. This information is used by an Annunciator analyzer, if one is configured for this input. |
258 Annunciator IAS trigger | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 6 No - Read Only No - RAM data No (not applicable) |
|
Description: | Provides first out and hold flags, and also terminal status for the input. This information is used by an Annunciator analyzer, if one is configured for this input. |
259 Annunciator PII trigger | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 6 No - Read Only No - RAM data No (not applicable) |
|
Description: | Provides first out and hold flags, and also terminal status for the input. This information is used by an Annunciator analyzer, if one is configured for this input. |
260 Annunciator LCI/F1 trigger | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 6 No - Read Only No - RAM data No (not applicable) |
|
Description: | Provides first out and hold flags, and also terminal status for the input. This information is used by an Annunciator analyzer, if one is configured for this input. |
261 Annunciator LCI/F2 trigger | Category: Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 6 No - Read Only No - RAM data No (not applicable) |
|
Description: | Provides first out and hold flags, and also terminal status for the input. This information is used by an Annunciator analyzer, if one is configured for this input. |
600 Socket 1 limit module number | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Module number of the Limit module that is providing data for socket "N". No other Limit module will be examined for a safety package for this socket. |
601 Socket 1 limit name | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 12 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | String up to 12 characters (8 bit) that provide a unique name for the socket. All sockets in a burner control must have different names. When a safety packet is received from the module identified by the "Socket N limit module number" register, and when this packet is correct as defined by the SLATE "SafetyDataPackets" document, and when the name provided by this parameter matches the name provided in the packet, then the status data provided by the limit block is used as valid data. A safety packet having a name which does not match any of the sockets (and also the socket's module number) is ignored. |
602 Socket 1 limit response | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Response to valid (as defined by other socket configuration registers) limit block status values. The responses below are suppressed during those states when it is not desired, as specified by the value of the "Socket N limit respond when" parameter. If the response is set to "Recycle 1", "Recycle 2", or "Recycle 3" then, whenever the limit block status is not "Limit OK" then a recycle and hold occurs until the status reverts to "Limit OK" If the response is set to "Soft lockout" or "Hard lockout" then, whenever the limit block status is not "Limit OK" then the appropriate type of lockout occurs. If the response is set to "Auto-ignition active" then whenever the limit block status is "Auto ignition threshold exceeded" then the BC, when configured for auto-ignition detection, will act as defined by the "Auto ignition enable" parameter. For this response, the "Socket N response when" parameter value is ignored. If the "Auto ignition threshold exceeded" status is received but this parameter is not configured for "Auto-ignition active" then this status is ignored. |
1 | Unknown | It is not specified what should happen for an invalid limit event. |
2 | Recycle 1 | Invalid limit event should cause a type 1 recycle to occur. |
3 | Recycle 2 | Invalid limit event should cause a type 2 recycle to occur. |
4 | Recycle 3 | Invalid limit event should cause a type 3 recycle to occur. |
5 | Soft lockout | Invalid limit event should cause a soft lockout to occur. |
6 | Hard lockout | Invalid limit event should cause a hard lockout to occur. |
7 | Auto-ignition active | Operate according to auto-ignition conditions having been met. |
603 Socket 1 limit response trigger | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When the burner control responds to the limit. It also provides a master-disable for the socket. The values are: Disable - this limit socket is inactive Always - this limit socket is active without regard to BC state Prepurge and Ignition and Run - this limit socket is active during the named states (and their substates) Ignition and Run - this limit socket is active during the named states (and their substates) Flame is on - this limit socket is active whenever flame is required to be on Run - this limit socket is active during the BC's Run state (and its substates, if any). |
1 | Disabled - Ignore limit | Limit socket is inactive. |
2 | Always | Check limit in all states. |
3 | Prepurge, Ignition and Run | Only check limit when in prepurge, ignition, or Run states. |
4 | Ignition and Run | Only check limit when in ignition or Run states. |
5 | Flame is on | Only check limit when flame is present. |
6 | Run | Only check limit when in Run state. |
604 Socket 1 limit status | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the status provided by "Socket N" of the safety limit structures. See the configuration registers section for more details. A limit block can report any of the status values shown below: Limit OK - the limit is not exceeded Limit exceeded - the limit has been exceeded and a defined response should occur (if enabled) Limit recovery - the limit was exceeded but is now recovering. Even so, the defined response should still occur (if enabled) Auto ignition threshold exceeded - a limit block configured to detect an auto-ignition threshold is reporting this as having occurred. Additionally this status can also be reported, when the safety package mechanism has not received appropriate safety packages: Limit communication failure - the limit is not providing correct safety packages as specified by the socket configuration parameters and the SLATE SafetyDataPackets document. |
1 | Limit status unknown | |
2 | Limit OK | Limit has not been reached. |
3 | Limit exceeded | Limit has been exceeded for longer than the detection time. A limit event is currently in progress. |
4 | Limit recovery | Limit was exceeded in the recent past, but at the current time the sensor is now not beyond the limit. Recovery timer is running and when it elapses the limit condition will be reverted to OK again. |
5 | Auto ignition threshold exceeded | Reports that a block which is set up for auto-ignition detection has reached it's threshold. |
6 | Limit communication failure | Limit communication system has failed to detect a Limit that interacts correctly with the burner control. |
7 | Sensor fault | A sensor has been detected as out of range or disconnected. |
606 Socket 2 limit module number | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Module number of the Limit module that is providing data for socket "N". No other Limit module will be examined for a safety package for this socket. |
607 Socket 2 limit name | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 12 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | String up to 12 characters (8 bit) that provide a unique name for the socket. All sockets in a burner control must have different names. When a safety packet is received from the module identified by the "Socket N limit module number" register, and when this packet is correct as defined by the SLATE "SafetyDataPackets" document, and when the name provided by this parameter matches the name provided in the packet, then the status data provided by the limit block is used as valid data. A safety packet having a name which does not match any of the sockets (and also the socket's module number) is ignored. |
608 Socket 2 limit response | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Response to valid (as defined by other socket configuration registers) limit block status values. The responses below are suppressed during those states when it is not desired, as specified by the value of the "Socket N limit respond when" parameter. If the response is set to "Recycle 1", "Recycle 2", or "Recycle 3" then, whenever the limit block status is not "Limit OK" then a recycle and hold occurs until the status reverts to "Limit OK" If the response is set to "Soft lockout" or "Hard lockout" then, whenever the limit block status is not "Limit OK" then the appropriate type of lockout occurs. If the response is set to "Auto-ignition active" then whenever the limit block status is "Auto ignition threshold exceeded" then the BC, when configured for auto-ignition detection, will act as defined by the "Auto ignition enable" parameter. For this response, the "Socket N response when" parameter value is ignored. If the "Auto ignition threshold exceeded" status is received but this parameter is not configured for "Auto-ignition active" then this status is ignored. |
1 | Unknown | It is not specified what should happen for an invalid limit event. |
2 | Recycle 1 | Invalid limit event should cause a type 1 recycle to occur. |
3 | Recycle 2 | Invalid limit event should cause a type 2 recycle to occur. |
4 | Recycle 3 | Invalid limit event should cause a type 3 recycle to occur. |
5 | Soft lockout | Invalid limit event should cause a soft lockout to occur. |
6 | Hard lockout | Invalid limit event should cause a hard lockout to occur. |
7 | Auto-ignition active | Operate according to auto-ignition conditions having been met. |
609 Socket 2 limit response trigger | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When the burner control responds to the limit. It also provides a master-disable for the socket. The values are: Disable - this limit socket is inactive Always - this limit socket is active without regard to BC state Prepurge and Ignition and Run - this limit socket is active during the named states (and their substates) Ignition and Run - this limit socket is active during the named states (and their substates) Flame is on - this limit socket is active whenever flame is required to be on Run - this limit socket is active during the BC's Run state (and its substates, if any). |
1 | Disabled - Ignore limit | Limit socket is inactive. |
2 | Always | Check limit in all states. |
3 | Prepurge, Ignition and Run | Only check limit when in prepurge, ignition, or Run states. |
4 | Ignition and Run | Only check limit when in ignition or Run states. |
5 | Flame is on | Only check limit when flame is present. |
6 | Run | Only check limit when in Run state. |
610 Socket 2 limit status | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the status provided by "Socket N" of the safety limit structures. See the configuration registers section for more details. A limit block can report any of the status values shown below: Limit OK - the limit is not exceeded Limit exceeded - the limit has been exceeded and a defined response should occur (if enabled) Limit recovery - the limit was exceeded but is now recovering. Even so, the defined response should still occur (if enabled) Auto ignition threshold exceeded - a limit block configured to detect an auto-ignition threshold is reporting this as having occurred. Additionally this status can also be reported, when the safety package mechanism has not received appropriate safety packages: Limit communication failure - the limit is not providing correct safety packages as specified by the socket configuration parameters and the SLATE SafetyDataPackets document. |
1 | Limit status unknown | |
2 | Limit OK | Limit has not been reached. |
3 | Limit exceeded | Limit has been exceeded for longer than the detection time. A limit event is currently in progress. |
4 | Limit recovery | Limit was exceeded in the recent past, but at the current time the sensor is now not beyond the limit. Recovery timer is running and when it elapses the limit condition will be reverted to OK again. |
5 | Auto ignition threshold exceeded | Reports that a block which is set up for auto-ignition detection has reached it's threshold. |
6 | Limit communication failure | Limit communication system has failed to detect a Limit that interacts correctly with the burner control. |
7 | Sensor fault | A sensor has been detected as out of range or disconnected. |
612 Socket 3 limit module number | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Module number of the Limit module that is providing data for socket "N". No other Limit module will be examined for a safety package for this socket. |
613 Socket 3 limit name | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 12 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | String up to 12 characters (8 bit) that provide a unique name for the socket. All sockets in a burner control must have different names. When a safety packet is received from the module identified by the "Socket N limit module number" register, and when this packet is correct as defined by the SLATE "SafetyDataPackets" document, and when the name provided by this parameter matches the name provided in the packet, then the status data provided by the limit block is used as valid data. A safety packet having a name which does not match any of the sockets (and also the socket's module number) is ignored. |
614 Socket 3 limit response | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Response to valid (as defined by other socket configuration registers) limit block status values. The responses below are suppressed during those states when it is not desired, as specified by the value of the "Socket N limit respond when" parameter. If the response is set to "Recycle 1", "Recycle 2", or "Recycle 3" then, whenever the limit block status is not "Limit OK" then a recycle and hold occurs until the status reverts to "Limit OK" If the response is set to "Soft lockout" or "Hard lockout" then, whenever the limit block status is not "Limit OK" then the appropriate type of lockout occurs. If the response is set to "Auto-ignition active" then whenever the limit block status is "Auto ignition threshold exceeded" then the BC, when configured for auto-ignition detection, will act as defined by the "Auto ignition enable" parameter. For this response, the "Socket N response when" parameter value is ignored. If the "Auto ignition threshold exceeded" status is received but this parameter is not configured for "Auto-ignition active" then this status is ignored. |
1 | Unknown | It is not specified what should happen for an invalid limit event. |
2 | Recycle 1 | Invalid limit event should cause a type 1 recycle to occur. |
3 | Recycle 2 | Invalid limit event should cause a type 2 recycle to occur. |
4 | Recycle 3 | Invalid limit event should cause a type 3 recycle to occur. |
5 | Soft lockout | Invalid limit event should cause a soft lockout to occur. |
6 | Hard lockout | Invalid limit event should cause a hard lockout to occur. |
7 | Auto-ignition active | Operate according to auto-ignition conditions having been met. |
615 Socket 3 limit response trigger | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When the burner control responds to the limit. It also provides a master-disable for the socket. The values are: Disable - this limit socket is inactive Always - this limit socket is active without regard to BC state Prepurge and Ignition and Run - this limit socket is active during the named states (and their substates) Ignition and Run - this limit socket is active during the named states (and their substates) Flame is on - this limit socket is active whenever flame is required to be on Run - this limit socket is active during the BC's Run state (and its substates, if any). |
1 | Disabled - Ignore limit | Limit socket is inactive. |
2 | Always | Check limit in all states. |
3 | Prepurge, Ignition and Run | Only check limit when in prepurge, ignition, or Run states. |
4 | Ignition and Run | Only check limit when in ignition or Run states. |
5 | Flame is on | Only check limit when flame is present. |
6 | Run | Only check limit when in Run state. |
616 Socket 3 limit status | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the status provided by "Socket N" of the safety limit structures. See the configuration registers section for more details. A limit block can report any of the status values shown below: Limit OK - the limit is not exceeded Limit exceeded - the limit has been exceeded and a defined response should occur (if enabled) Limit recovery - the limit was exceeded but is now recovering. Even so, the defined response should still occur (if enabled) Auto ignition threshold exceeded - a limit block configured to detect an auto-ignition threshold is reporting this as having occurred. Additionally this status can also be reported, when the safety package mechanism has not received appropriate safety packages: Limit communication failure - the limit is not providing correct safety packages as specified by the socket configuration parameters and the SLATE SafetyDataPackets document. |
1 | Limit status unknown | |
2 | Limit OK | Limit has not been reached. |
3 | Limit exceeded | Limit has been exceeded for longer than the detection time. A limit event is currently in progress. |
4 | Limit recovery | Limit was exceeded in the recent past, but at the current time the sensor is now not beyond the limit. Recovery timer is running and when it elapses the limit condition will be reverted to OK again. |
5 | Auto ignition threshold exceeded | Reports that a block which is set up for auto-ignition detection has reached it's threshold. |
6 | Limit communication failure | Limit communication system has failed to detect a Limit that interacts correctly with the burner control. |
7 | Sensor fault | A sensor has been detected as out of range or disconnected. |
618 Socket 4 limit module number | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Module number of the Limit module that is providing data for socket "N". No other Limit module will be examined for a safety package for this socket. |
619 Socket 4 limit name | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 12 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | String up to 12 characters (8 bit) that provide a unique name for the socket. All sockets in a burner control must have different names. When a safety packet is received from the module identified by the "Socket N limit module number" register, and when this packet is correct as defined by the SLATE "SafetyDataPackets" document, and when the name provided by this parameter matches the name provided in the packet, then the status data provided by the limit block is used as valid data. A safety packet having a name which does not match any of the sockets (and also the socket's module number) is ignored. |
620 Socket 4 limit response | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Response to valid (as defined by other socket configuration registers) limit block status values. The responses below are suppressed during those states when it is not desired, as specified by the value of the "Socket N limit respond when" parameter. If the response is set to "Recycle 1", "Recycle 2", or "Recycle 3" then, whenever the limit block status is not "Limit OK" then a recycle and hold occurs until the status reverts to "Limit OK" If the response is set to "Soft lockout" or "Hard lockout" then, whenever the limit block status is not "Limit OK" then the appropriate type of lockout occurs. If the response is set to "Auto-ignition active" then whenever the limit block status is "Auto ignition threshold exceeded" then the BC, when configured for auto-ignition detection, will act as defined by the "Auto ignition enable" parameter. For this response, the "Socket N response when" parameter value is ignored. If the "Auto ignition threshold exceeded" status is received but this parameter is not configured for "Auto-ignition active" then this status is ignored. |
1 | Unknown | It is not specified what should happen for an invalid limit event. |
2 | Recycle 1 | Invalid limit event should cause a type 1 recycle to occur. |
3 | Recycle 2 | Invalid limit event should cause a type 2 recycle to occur. |
4 | Recycle 3 | Invalid limit event should cause a type 3 recycle to occur. |
5 | Soft lockout | Invalid limit event should cause a soft lockout to occur. |
6 | Hard lockout | Invalid limit event should cause a hard lockout to occur. |
7 | Auto-ignition active | Operate according to auto-ignition conditions having been met. |
621 Socket 4 limit response trigger | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When the burner control responds to the limit. It also provides a master-disable for the socket. The values are: Disable - this limit socket is inactive Always - this limit socket is active without regard to BC state Prepurge and Ignition and Run - this limit socket is active during the named states (and their substates) Ignition and Run - this limit socket is active during the named states (and their substates) Flame is on - this limit socket is active whenever flame is required to be on Run - this limit socket is active during the BC's Run state (and its substates, if any). |
1 | Disabled - Ignore limit | Limit socket is inactive. |
2 | Always | Check limit in all states. |
3 | Prepurge, Ignition and Run | Only check limit when in prepurge, ignition, or Run states. |
4 | Ignition and Run | Only check limit when in ignition or Run states. |
5 | Flame is on | Only check limit when flame is present. |
6 | Run | Only check limit when in Run state. |
622 Socket 4 limit status | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the status provided by "Socket N" of the safety limit structures. See the configuration registers section for more details. A limit block can report any of the status values shown below: Limit OK - the limit is not exceeded Limit exceeded - the limit has been exceeded and a defined response should occur (if enabled) Limit recovery - the limit was exceeded but is now recovering. Even so, the defined response should still occur (if enabled) Auto ignition threshold exceeded - a limit block configured to detect an auto-ignition threshold is reporting this as having occurred. Additionally this status can also be reported, when the safety package mechanism has not received appropriate safety packages: Limit communication failure - the limit is not providing correct safety packages as specified by the socket configuration parameters and the SLATE SafetyDataPackets document. |
1 | Limit status unknown | |
2 | Limit OK | Limit has not been reached. |
3 | Limit exceeded | Limit has been exceeded for longer than the detection time. A limit event is currently in progress. |
4 | Limit recovery | Limit was exceeded in the recent past, but at the current time the sensor is now not beyond the limit. Recovery timer is running and when it elapses the limit condition will be reverted to OK again. |
5 | Auto ignition threshold exceeded | Reports that a block which is set up for auto-ignition detection has reached it's threshold. |
6 | Limit communication failure | Limit communication system has failed to detect a Limit that interacts correctly with the burner control. |
7 | Sensor fault | A sensor has been detected as out of range or disconnected. |
624 Socket 5 limit module number | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Module number of the Limit module that is providing data for socket "N". No other Limit module will be examined for a safety package for this socket. |
625 Socket 5 limit name | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 12 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | String up to 12 characters (8 bit) that provide a unique name for the socket. All sockets in a burner control must have different names. When a safety packet is received from the module identified by the "Socket N limit module number" register, and when this packet is correct as defined by the SLATE "SafetyDataPackets" document, and when the name provided by this parameter matches the name provided in the packet, then the status data provided by the limit block is used as valid data. A safety packet having a name which does not match any of the sockets (and also the socket's module number) is ignored. |
626 Socket 5 limit response | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Response to valid (as defined by other socket configuration registers) limit block status values. The responses below are suppressed during those states when it is not desired, as specified by the value of the "Socket N limit respond when" parameter. If the response is set to "Recycle 1", "Recycle 2", or "Recycle 3" then, whenever the limit block status is not "Limit OK" then a recycle and hold occurs until the status reverts to "Limit OK" If the response is set to "Soft lockout" or "Hard lockout" then, whenever the limit block status is not "Limit OK" then the appropriate type of lockout occurs. If the response is set to "Auto-ignition active" then whenever the limit block status is "Auto ignition threshold exceeded" then the BC, when configured for auto-ignition detection, will act as defined by the "Auto ignition enable" parameter. For this response, the "Socket N response when" parameter value is ignored. If the "Auto ignition threshold exceeded" status is received but this parameter is not configured for "Auto-ignition active" then this status is ignored. |
1 | Unknown | It is not specified what should happen for an invalid limit event. |
2 | Recycle 1 | Invalid limit event should cause a type 1 recycle to occur. |
3 | Recycle 2 | Invalid limit event should cause a type 2 recycle to occur. |
4 | Recycle 3 | Invalid limit event should cause a type 3 recycle to occur. |
5 | Soft lockout | Invalid limit event should cause a soft lockout to occur. |
6 | Hard lockout | Invalid limit event should cause a hard lockout to occur. |
7 | Auto-ignition active | Operate according to auto-ignition conditions having been met. |
627 Socket 5 limit response trigger | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When the burner control responds to the limit. It also provides a master-disable for the socket. The values are: Disable - this limit socket is inactive Always - this limit socket is active without regard to BC state Prepurge and Ignition and Run - this limit socket is active during the named states (and their substates) Ignition and Run - this limit socket is active during the named states (and their substates) Flame is on - this limit socket is active whenever flame is required to be on Run - this limit socket is active during the BC's Run state (and its substates, if any). |
1 | Disabled - Ignore limit | Limit socket is inactive. |
2 | Always | Check limit in all states. |
3 | Prepurge, Ignition and Run | Only check limit when in prepurge, ignition, or Run states. |
4 | Ignition and Run | Only check limit when in ignition or Run states. |
5 | Flame is on | Only check limit when flame is present. |
6 | Run | Only check limit when in Run state. |
628 Socket 5 limit status | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the status provided by "Socket N" of the safety limit structures. See the configuration registers section for more details. A limit block can report any of the status values shown below: Limit OK - the limit is not exceeded Limit exceeded - the limit has been exceeded and a defined response should occur (if enabled) Limit recovery - the limit was exceeded but is now recovering. Even so, the defined response should still occur (if enabled) Auto ignition threshold exceeded - a limit block configured to detect an auto-ignition threshold is reporting this as having occurred. Additionally this status can also be reported, when the safety package mechanism has not received appropriate safety packages: Limit communication failure - the limit is not providing correct safety packages as specified by the socket configuration parameters and the SLATE SafetyDataPackets document. |
1 | Limit status unknown | |
2 | Limit OK | Limit has not been reached. |
3 | Limit exceeded | Limit has been exceeded for longer than the detection time. A limit event is currently in progress. |
4 | Limit recovery | Limit was exceeded in the recent past, but at the current time the sensor is now not beyond the limit. Recovery timer is running and when it elapses the limit condition will be reverted to OK again. |
5 | Auto ignition threshold exceeded | Reports that a block which is set up for auto-ignition detection has reached it's threshold. |
6 | Limit communication failure | Limit communication system has failed to detect a Limit that interacts correctly with the burner control. |
7 | Sensor fault | A sensor has been detected as out of range or disconnected. |
630 Socket 6 limit module number | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Module number of the Limit module that is providing data for socket "N". No other Limit module will be examined for a safety package for this socket. |
631 Socket 6 limit name | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 12 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | String up to 12 characters (8 bit) that provide a unique name for the socket. All sockets in a burner control must have different names. When a safety packet is received from the module identified by the "Socket N limit module number" register, and when this packet is correct as defined by the SLATE "SafetyDataPackets" document, and when the name provided by this parameter matches the name provided in the packet, then the status data provided by the limit block is used as valid data. A safety packet having a name which does not match any of the sockets (and also the socket's module number) is ignored. |
632 Socket 6 limit response | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Response to valid (as defined by other socket configuration registers) limit block status values. The responses below are suppressed during those states when it is not desired, as specified by the value of the "Socket N limit respond when" parameter. If the response is set to "Recycle 1", "Recycle 2", or "Recycle 3" then, whenever the limit block status is not "Limit OK" then a recycle and hold occurs until the status reverts to "Limit OK" If the response is set to "Soft lockout" or "Hard lockout" then, whenever the limit block status is not "Limit OK" then the appropriate type of lockout occurs. If the response is set to "Auto-ignition active" then whenever the limit block status is "Auto ignition threshold exceeded" then the BC, when configured for auto-ignition detection, will act as defined by the "Auto ignition enable" parameter. For this response, the "Socket N response when" parameter value is ignored. If the "Auto ignition threshold exceeded" status is received but this parameter is not configured for "Auto-ignition active" then this status is ignored. |
1 | Unknown | It is not specified what should happen for an invalid limit event. |
2 | Recycle 1 | Invalid limit event should cause a type 1 recycle to occur. |
3 | Recycle 2 | Invalid limit event should cause a type 2 recycle to occur. |
4 | Recycle 3 | Invalid limit event should cause a type 3 recycle to occur. |
5 | Soft lockout | Invalid limit event should cause a soft lockout to occur. |
6 | Hard lockout | Invalid limit event should cause a hard lockout to occur. |
7 | Auto-ignition active | Operate according to auto-ignition conditions having been met. |
633 Socket 6 limit response trigger | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When the burner control responds to the limit. It also provides a master-disable for the socket. The values are: Disable - this limit socket is inactive Always - this limit socket is active without regard to BC state Prepurge and Ignition and Run - this limit socket is active during the named states (and their substates) Ignition and Run - this limit socket is active during the named states (and their substates) Flame is on - this limit socket is active whenever flame is required to be on Run - this limit socket is active during the BC's Run state (and its substates, if any). |
1 | Disabled - Ignore limit | Limit socket is inactive. |
2 | Always | Check limit in all states. |
3 | Prepurge, Ignition and Run | Only check limit when in prepurge, ignition, or Run states. |
4 | Ignition and Run | Only check limit when in ignition or Run states. |
5 | Flame is on | Only check limit when flame is present. |
6 | Run | Only check limit when in Run state. |
634 Socket 6 limit status | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the status provided by "Socket N" of the safety limit structures. See the configuration registers section for more details. A limit block can report any of the status values shown below: Limit OK - the limit is not exceeded Limit exceeded - the limit has been exceeded and a defined response should occur (if enabled) Limit recovery - the limit was exceeded but is now recovering. Even so, the defined response should still occur (if enabled) Auto ignition threshold exceeded - a limit block configured to detect an auto-ignition threshold is reporting this as having occurred. Additionally this status can also be reported, when the safety package mechanism has not received appropriate safety packages: Limit communication failure - the limit is not providing correct safety packages as specified by the socket configuration parameters and the SLATE SafetyDataPackets document. |
1 | Limit status unknown | |
2 | Limit OK | Limit has not been reached. |
3 | Limit exceeded | Limit has been exceeded for longer than the detection time. A limit event is currently in progress. |
4 | Limit recovery | Limit was exceeded in the recent past, but at the current time the sensor is now not beyond the limit. Recovery timer is running and when it elapses the limit condition will be reverted to OK again. |
5 | Auto ignition threshold exceeded | Reports that a block which is set up for auto-ignition detection has reached it's threshold. |
6 | Limit communication failure | Limit communication system has failed to detect a Limit that interacts correctly with the burner control. |
7 | Sensor fault | A sensor has been detected as out of range or disconnected. |
636 Socket 7 limit module number | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Module number of the Limit module that is providing data for socket "N". No other Limit module will be examined for a safety package for this socket. |
637 Socket 7 limit name | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 12 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | String up to 12 characters (8 bit) that provide a unique name for the socket. All sockets in a burner control must have different names. When a safety packet is received from the module identified by the "Socket N limit module number" register, and when this packet is correct as defined by the SLATE "SafetyDataPackets" document, and when the name provided by this parameter matches the name provided in the packet, then the status data provided by the limit block is used as valid data. A safety packet having a name which does not match any of the sockets (and also the socket's module number) is ignored. |
638 Socket 7 limit response | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Response to valid (as defined by other socket configuration registers) limit block status values. The responses below are suppressed during those states when it is not desired, as specified by the value of the "Socket N limit respond when" parameter. If the response is set to "Recycle 1", "Recycle 2", or "Recycle 3" then, whenever the limit block status is not "Limit OK" then a recycle and hold occurs until the status reverts to "Limit OK" If the response is set to "Soft lockout" or "Hard lockout" then, whenever the limit block status is not "Limit OK" then the appropriate type of lockout occurs. If the response is set to "Auto-ignition active" then whenever the limit block status is "Auto ignition threshold exceeded" then the BC, when configured for auto-ignition detection, will act as defined by the "Auto ignition enable" parameter. For this response, the "Socket N response when" parameter value is ignored. If the "Auto ignition threshold exceeded" status is received but this parameter is not configured for "Auto-ignition active" then this status is ignored. |
1 | Unknown | It is not specified what should happen for an invalid limit event. |
2 | Recycle 1 | Invalid limit event should cause a type 1 recycle to occur. |
3 | Recycle 2 | Invalid limit event should cause a type 2 recycle to occur. |
4 | Recycle 3 | Invalid limit event should cause a type 3 recycle to occur. |
5 | Soft lockout | Invalid limit event should cause a soft lockout to occur. |
6 | Hard lockout | Invalid limit event should cause a hard lockout to occur. |
7 | Auto-ignition active | Operate according to auto-ignition conditions having been met. |
639 Socket 7 limit response trigger | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When the burner control responds to the limit. It also provides a master-disable for the socket. The values are: Disable - this limit socket is inactive Always - this limit socket is active without regard to BC state Prepurge and Ignition and Run - this limit socket is active during the named states (and their substates) Ignition and Run - this limit socket is active during the named states (and their substates) Flame is on - this limit socket is active whenever flame is required to be on Run - this limit socket is active during the BC's Run state (and its substates, if any). |
1 | Disabled - Ignore limit | Limit socket is inactive. |
2 | Always | Check limit in all states. |
3 | Prepurge, Ignition and Run | Only check limit when in prepurge, ignition, or Run states. |
4 | Ignition and Run | Only check limit when in ignition or Run states. |
5 | Flame is on | Only check limit when flame is present. |
6 | Run | Only check limit when in Run state. |
640 Socket 7 limit status | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the status provided by "Socket N" of the safety limit structures. See the configuration registers section for more details. A limit block can report any of the status values shown below: Limit OK - the limit is not exceeded Limit exceeded - the limit has been exceeded and a defined response should occur (if enabled) Limit recovery - the limit was exceeded but is now recovering. Even so, the defined response should still occur (if enabled) Auto ignition threshold exceeded - a limit block configured to detect an auto-ignition threshold is reporting this as having occurred. Additionally this status can also be reported, when the safety package mechanism has not received appropriate safety packages: Limit communication failure - the limit is not providing correct safety packages as specified by the socket configuration parameters and the SLATE SafetyDataPackets document. |
1 | Limit status unknown | |
2 | Limit OK | Limit has not been reached. |
3 | Limit exceeded | Limit has been exceeded for longer than the detection time. A limit event is currently in progress. |
4 | Limit recovery | Limit was exceeded in the recent past, but at the current time the sensor is now not beyond the limit. Recovery timer is running and when it elapses the limit condition will be reverted to OK again. |
5 | Auto ignition threshold exceeded | Reports that a block which is set up for auto-ignition detection has reached it's threshold. |
6 | Limit communication failure | Limit communication system has failed to detect a Limit that interacts correctly with the burner control. |
7 | Sensor fault | A sensor has been detected as out of range or disconnected. |
642 Socket 8 limit module number | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Module number of the Limit module that is providing data for socket "N". No other Limit module will be examined for a safety package for this socket. |
643 Socket 8 limit name | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 12 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | String up to 12 characters (8 bit) that provide a unique name for the socket. All sockets in a burner control must have different names. When a safety packet is received from the module identified by the "Socket N limit module number" register, and when this packet is correct as defined by the SLATE "SafetyDataPackets" document, and when the name provided by this parameter matches the name provided in the packet, then the status data provided by the limit block is used as valid data. A safety packet having a name which does not match any of the sockets (and also the socket's module number) is ignored. |
644 Socket 8 limit response | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Response to valid (as defined by other socket configuration registers) limit block status values. The responses below are suppressed during those states when it is not desired, as specified by the value of the "Socket N limit respond when" parameter. If the response is set to "Recycle 1", "Recycle 2", or "Recycle 3" then, whenever the limit block status is not "Limit OK" then a recycle and hold occurs until the status reverts to "Limit OK" If the response is set to "Soft lockout" or "Hard lockout" then, whenever the limit block status is not "Limit OK" then the appropriate type of lockout occurs. If the response is set to "Auto-ignition active" then whenever the limit block status is "Auto ignition threshold exceeded" then the BC, when configured for auto-ignition detection, will act as defined by the "Auto ignition enable" parameter. For this response, the "Socket N response when" parameter value is ignored. If the "Auto ignition threshold exceeded" status is received but this parameter is not configured for "Auto-ignition active" then this status is ignored. |
1 | Unknown | It is not specified what should happen for an invalid limit event. |
2 | Recycle 1 | Invalid limit event should cause a type 1 recycle to occur. |
3 | Recycle 2 | Invalid limit event should cause a type 2 recycle to occur. |
4 | Recycle 3 | Invalid limit event should cause a type 3 recycle to occur. |
5 | Soft lockout | Invalid limit event should cause a soft lockout to occur. |
6 | Hard lockout | Invalid limit event should cause a hard lockout to occur. |
7 | Auto-ignition active | Operate according to auto-ignition conditions having been met. |
645 Socket 8 limit response trigger | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | When the burner control responds to the limit. It also provides a master-disable for the socket. The values are: Disable - this limit socket is inactive Always - this limit socket is active without regard to BC state Prepurge and Ignition and Run - this limit socket is active during the named states (and their substates) Ignition and Run - this limit socket is active during the named states (and their substates) Flame is on - this limit socket is active whenever flame is required to be on Run - this limit socket is active during the BC's Run state (and its substates, if any). |
1 | Disabled - Ignore limit | Limit socket is inactive. |
2 | Always | Check limit in all states. |
3 | Prepurge, Ignition and Run | Only check limit when in prepurge, ignition, or Run states. |
4 | Ignition and Run | Only check limit when in ignition or Run states. |
5 | Flame is on | Only check limit when flame is present. |
6 | Run | Only check limit when in Run state. |
646 Socket 8 limit status | Category: Limit Socket |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the status provided by "Socket N" of the safety limit structures. See the configuration registers section for more details. A limit block can report any of the status values shown below: Limit OK - the limit is not exceeded Limit exceeded - the limit has been exceeded and a defined response should occur (if enabled) Limit recovery - the limit was exceeded but is now recovering. Even so, the defined response should still occur (if enabled) Auto ignition threshold exceeded - a limit block configured to detect an auto-ignition threshold is reporting this as having occurred. Additionally this status can also be reported, when the safety package mechanism has not received appropriate safety packages: Limit communication failure - the limit is not providing correct safety packages as specified by the socket configuration parameters and the SLATE SafetyDataPackets document. |
1 | Limit status unknown | |
2 | Limit OK | Limit has not been reached. |
3 | Limit exceeded | Limit has been exceeded for longer than the detection time. A limit event is currently in progress. |
4 | Limit recovery | Limit was exceeded in the recent past, but at the current time the sensor is now not beyond the limit. Recovery timer is running and when it elapses the limit condition will be reverted to OK again. |
5 | Auto ignition threshold exceeded | Reports that a block which is set up for auto-ignition detection has reached it's threshold. |
6 | Limit communication failure | Limit communication system has failed to detect a Limit that interacts correctly with the burner control. |
7 | Sensor fault | A sensor has been detected as out of range or disconnected. |
648 Flame amplifier 1 required type | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: |
1 | None | None means this is unused or setup is needed |
2 | UV Ampli-Check | Ultraviolet Minipeeper detector (C7027 / C7035) |
3 | UV Shutter-Check | Ultraviolet Purple Peeper detector (C7061) with shutter |
4 | IR Ampli-Check | Infrared (Lead sulfide) detector (C7915) |
5 | UV/Visible Ampli-Check | Ultraviolet (C7927) or Visible light (C7962) solid state detector |
6 | Rectification Ampli-Check | Flame rod (C7000x) or UV solid state Purple peeper (C7012 A/C) detector with shutter. |
649 Flame amplifier 1 flame threshold | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 0.8 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: |
650 Flame amplifier 1 weak flame threshold | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 1.2 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 Yes Yes - Configuration data No Yes - Can set up in AX |
|
Description: |
651 Flame amplifier 1 status | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | Not configured | |
2 | Unknown | |
3 | Off | |
4 | Weak | |
5 | On | |
6 | Faulty |
652 Flame amplifier 1 flame strength | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
653 Flame amplifier 1 fault code | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | None | |
2 | Shutter check failure | |
3 | Ampli-check failure |
654 Flame amplifier 1 key event | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Indicates that a button on flame amplifier 1 was pressed |
655 Flame amplifier 2 required type | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: |
1 | None | None means this is unused or setup is needed |
2 | UV Ampli-Check | Ultraviolet Minipeeper detector (C7027 / C7035) |
3 | UV Shutter-Check | Ultraviolet Purple Peeper detector (C7061) with shutter |
4 | IR Ampli-Check | Infrared (Lead sulfide) detector (C7915) |
5 | UV/Visible Ampli-Check | Ultraviolet (C7927) or Visible light (C7962) solid state detector |
6 | Rectification Ampli-Check | Flame rod (C7000x) or UV solid state Purple peeper (C7012 A/C) detector with shutter. |
656 Flame amplifier 2 flame threshold | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 0.8 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: |
657 Flame amplifier 2 weak flame threshold | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 1.2 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 Yes Yes - Configuration data No Yes - Can set up in AX |
|
Description: |
658 Flame amplifier 2 status | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | Not configured | |
2 | Unknown | |
3 | Off | |
4 | Weak | |
5 | On | |
6 | Faulty |
659 Flame amplifier 2 flame strength | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
660 Flame amplifier 2 fault code | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | None | |
2 | Shutter check failure | |
3 | Ampli-check failure |
661 Flame amplifier 2 key event | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Indicates that a button on flame amplifier 2 was pressed |
662 Flame amplifier 3 required type | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: |
1 | None | None means this is unused or setup is needed |
2 | UV Ampli-Check | Ultraviolet Minipeeper detector (C7027 / C7035) |
3 | UV Shutter-Check | Ultraviolet Purple Peeper detector (C7061) with shutter |
4 | IR Ampli-Check | Infrared (Lead sulfide) detector (C7915) |
5 | UV/Visible Ampli-Check | Ultraviolet (C7927) or Visible light (C7962) solid state detector |
6 | Rectification Ampli-Check | Flame rod (C7000x) or UV solid state Purple peeper (C7012 A/C) detector with shutter. |
663 Flame amplifier 3 flame threshold | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 0.8 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: |
664 Flame amplifier 3 weak flame threshold | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 1.2 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 Yes Yes - Configuration data No Yes - Can set up in AX |
|
Description: |
665 Flame amplifier 3 status | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | Not configured | |
2 | Unknown | |
3 | Off | |
4 | Weak | |
5 | On | |
6 | Faulty |
666 Flame amplifier 3 flame strength | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
667 Flame amplifier 3 fault code | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | None | |
2 | Shutter check failure | |
3 | Ampli-check failure |
668 Flame amplifier 3 key event | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Indicates that a button on flame amplifier 3 was pressed |
669 Flame amplifier 4 required type | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: |
1 | None | None means this is unused or setup is needed |
2 | UV Ampli-Check | Ultraviolet Minipeeper detector (C7027 / C7035) |
3 | UV Shutter-Check | Ultraviolet Purple Peeper detector (C7061) with shutter |
4 | IR Ampli-Check | Infrared (Lead sulfide) detector (C7915) |
5 | UV/Visible Ampli-Check | Ultraviolet (C7927) or Visible light (C7962) solid state detector |
6 | Rectification Ampli-Check | Flame rod (C7000x) or UV solid state Purple peeper (C7012 A/C) detector with shutter. |
670 Flame amplifier 4 flame threshold | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 0.8 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: |
671 Flame amplifier 4 weak flame threshold | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 1.2 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 Yes Yes - Configuration data No Yes - Can set up in AX |
|
Description: |
672 Flame amplifier 4 status | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | Not configured | |
2 | Unknown | |
3 | Off | |
4 | Weak | |
5 | On | |
6 | Faulty |
673 Flame amplifier 4 flame strength | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-float F32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
674 Flame amplifier 4 fault code | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | None | |
2 | Shutter check failure | |
3 | Ampli-check failure |
675 Flame amplifier 4 key event | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Indicates that a button on flame amplifier 4 was pressed |
676 Flame amplifier 1 address | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the number selected by the rotary switch |
677 Flame amplifier 1 operation state | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | Unknown | State of module is not known |
2 | Init | Module is initializing |
3 | Idle | Module is idle and not currently processing |
4 | Running | Module is functioning correctly with no faults |
5 | Standby | Module is standing by waiting for action to be requested |
6 | Prepurge | Module is in prepurge condition |
7 | Ignition | Module is igniting |
8 | Run | Module is operating in response to demand |
9 | Postpurge | Module is in postpurge condition |
10 | Hold | Module is waiting for a period of time or until a condition clears |
11 | Disabled | Module is currently disabled for operation |
12 | Unconfig | Module configuration is not complete |
13 | Fault | Module is in a fault condtion that can be cleared without human intervention |
14 | Lockout | Module is in a fault condition that requires human intervention to clear it |
15 | Lightoff | Module is in a lightoff condition |
16 | Modulating | Module is running and modulating |
17 | Normal | Module is operating in it's normal expected function |
18 | Limit event | Module has encountered a limit occurrence |
19 | Setup | Module is in setup mode |
20 | Curve edit | Curve editing is occurring in module |
21 | Configuration load | A configuration load is in-progress in the module. |
678 Flame amplifier 1 install date | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 Yes No - RAM data No (not applicable) |
|
Description: |
679 Flame amplifier 1 OS number | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
680 Flame amplifier 1 serial number | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
681 Flame amplifier 1 build code | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
682 Flame amplifier 1 module identifier | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
683 Flame amplifier 1 module type | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 10 No - Read Only No - RAM data No (not applicable) |
|
Description: |
684 Flame amplifier 1 module version | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
685 Flame amplifier 1 module revision | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
686 Flame amplifier 1 module short name | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 10 Yes No - RAM data No (not applicable) |
|
Description: | Short flame amplifier module name for Base display use |
687 Flame amplifier 1 module name | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 60 Yes No - RAM data No (not applicable) |
|
Description: | Full flame amplifier module name for display use |
688 Flame amplifier 1 Rx comm diagnostics | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
689 Flame amplifier 1 Tx comm diagnostics | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
690 Flame amplifier 1 hardware version | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
691 Flame amplifier 1 reset counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
692 Flame amplifier 1 watchdog counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
693 Flame amplifier 1 power-up counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
694 Flame amplifier 1 brownout counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
695 Flame amplifier 2 address | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the number selected by the rotary switch |
696 Flame amplifier 2 operation state | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | Unknown | State of module is not known |
2 | Init | Module is initializing |
3 | Idle | Module is idle and not currently processing |
4 | Running | Module is functioning correctly with no faults |
5 | Standby | Module is standing by waiting for action to be requested |
6 | Prepurge | Module is in prepurge condition |
7 | Ignition | Module is igniting |
8 | Run | Module is operating in response to demand |
9 | Postpurge | Module is in postpurge condition |
10 | Hold | Module is waiting for a period of time or until a condition clears |
11 | Disabled | Module is currently disabled for operation |
12 | Unconfig | Module configuration is not complete |
13 | Fault | Module is in a fault condtion that can be cleared without human intervention |
14 | Lockout | Module is in a fault condition that requires human intervention to clear it |
15 | Lightoff | Module is in a lightoff condition |
16 | Modulating | Module is running and modulating |
17 | Normal | Module is operating in it's normal expected function |
18 | Limit event | Module has encountered a limit occurrence |
19 | Setup | Module is in setup mode |
20 | Curve edit | Curve editing is occurring in module |
21 | Configuration load | A configuration load is in-progress in the module. |
697 Flame amplifier 2 install date | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 Yes No - RAM data No (not applicable) |
|
Description: |
698 Flame amplifier 2 OS number | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
699 Flame amplifier 2 serial number | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
700 Flame amplifier 2 build code | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
701 Flame amplifier 2 module identifier | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
702 Flame amplifier 2 module type | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 10 No - Read Only No - RAM data No (not applicable) |
|
Description: |
703 Flame amplifier 2 module version | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
704 Flame amplifier 2 module revision | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
705 Flame amplifier 2 module short name | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 10 Yes No - RAM data No (not applicable) |
|
Description: | Short flame amplifier module name for Base display use |
706 Flame amplifier 2 module name | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 60 Yes No - RAM data No (not applicable) |
|
Description: | Full flame amplifier module name for display use |
707 Flame amplifier 2 Rx comm diagnostics | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
708 Flame amplifier 2 Tx comm diagnostics | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
709 Flame amplifier 2 hardware version | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
710 Flame amplifier 2 reset counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
711 Flame amplifier 2 watchdog counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
712 Flame amplifier 2 power-up counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
713 Flame amplifier 2 brownout counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
714 Flame amplifier 3 address | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the number selected by the rotary switch |
715 Flame amplifier 3 operation state | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | Unknown | State of module is not known |
2 | Init | Module is initializing |
3 | Idle | Module is idle and not currently processing |
4 | Running | Module is functioning correctly with no faults |
5 | Standby | Module is standing by waiting for action to be requested |
6 | Prepurge | Module is in prepurge condition |
7 | Ignition | Module is igniting |
8 | Run | Module is operating in response to demand |
9 | Postpurge | Module is in postpurge condition |
10 | Hold | Module is waiting for a period of time or until a condition clears |
11 | Disabled | Module is currently disabled for operation |
12 | Unconfig | Module configuration is not complete |
13 | Fault | Module is in a fault condtion that can be cleared without human intervention |
14 | Lockout | Module is in a fault condition that requires human intervention to clear it |
15 | Lightoff | Module is in a lightoff condition |
16 | Modulating | Module is running and modulating |
17 | Normal | Module is operating in it's normal expected function |
18 | Limit event | Module has encountered a limit occurrence |
19 | Setup | Module is in setup mode |
20 | Curve edit | Curve editing is occurring in module |
21 | Configuration load | A configuration load is in-progress in the module. |
716 Flame amplifier 3 install date | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 Yes No - RAM data No (not applicable) |
|
Description: |
717 Flame amplifier 3 OS number | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
718 Flame amplifier 3 serial number | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
719 Flame amplifier 3 build code | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
720 Flame amplifier 3 module identifier | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
721 Flame amplifier 3 module type | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 10 No - Read Only No - RAM data No (not applicable) |
|
Description: |
722 Flame amplifier 3 module version | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
723 Flame amplifier 3 module revision | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
724 Flame amplifier 3 module short name | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 10 Yes No - RAM data No (not applicable) |
|
Description: | Short flame amplifier module name for Base display use |
725 Flame amplifier 3 module name | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 60 Yes No - RAM data No (not applicable) |
|
Description: | Full flame amplifier module name for display use |
726 Flame amplifier 3 Rx comm diagnostics | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
727 Flame amplifier 3 Tx comm diagnostics | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
728 Flame amplifier 3 hardware version | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
729 Flame amplifier 3 reset counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
730 Flame amplifier 3 watchdog counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
731 Flame amplifier 3 power-up counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
732 Flame amplifier 3 brownout counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
733 Flame amplifier 4 address | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: | Reports the number selected by the rotary switch |
734 Flame amplifier 4 operation state | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
1 | Unknown | State of module is not known |
2 | Init | Module is initializing |
3 | Idle | Module is idle and not currently processing |
4 | Running | Module is functioning correctly with no faults |
5 | Standby | Module is standing by waiting for action to be requested |
6 | Prepurge | Module is in prepurge condition |
7 | Ignition | Module is igniting |
8 | Run | Module is operating in response to demand |
9 | Postpurge | Module is in postpurge condition |
10 | Hold | Module is waiting for a period of time or until a condition clears |
11 | Disabled | Module is currently disabled for operation |
12 | Unconfig | Module configuration is not complete |
13 | Fault | Module is in a fault condtion that can be cleared without human intervention |
14 | Lockout | Module is in a fault condition that requires human intervention to clear it |
15 | Lightoff | Module is in a lightoff condition |
16 | Modulating | Module is running and modulating |
17 | Normal | Module is operating in it's normal expected function |
18 | Limit event | Module has encountered a limit occurrence |
19 | Setup | Module is in setup mode |
20 | Curve edit | Curve editing is occurring in module |
21 | Configuration load | A configuration load is in-progress in the module. |
735 Flame amplifier 4 install date | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 Yes No - RAM data No (not applicable) |
|
Description: |
736 Flame amplifier 4 OS number | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
737 Flame amplifier 4 serial number | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
738 Flame amplifier 4 build code | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
739 Flame amplifier 4 module identifier | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 20 No - Read Only No - RAM data No (not applicable) |
|
Description: |
740 Flame amplifier 4 module type | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 10 No - Read Only No - RAM data No (not applicable) |
|
Description: |
741 Flame amplifier 4 module version | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
742 Flame amplifier 4 module revision | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
743 Flame amplifier 4 module short name | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 10 Yes No - RAM data No (not applicable) |
|
Description: | Short flame amplifier module name for Base display use |
744 Flame amplifier 4 module name | Category: Flame Module Setup |
Units; DataType: Max: Default Value: Min: |
xAX string String |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 60 Yes No - RAM data No (not applicable) |
|
Description: | Full flame amplifier module name for display use |
745 Flame amplifier 4 Rx comm diagnostics | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
746 Flame amplifier 4 Tx comm diagnostics | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only No - RAM data No (not applicable) |
|
Description: |
747 Flame amplifier 4 hardware version | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
748 Flame amplifier 4 reset counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
749 Flame amplifier 4 watchdog counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
750 Flame amplifier 4 power-up counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
751 Flame amplifier 4 brownout counter | Category: Flame Module Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 No - Read Only No - RAM data No (not applicable) |
|
Description: |
5200 Reset counter | Category: System Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data No (not applicable) |
|
Description: | Counter of the number of times this module has been re-booted. |
5201 Watchdog counter | Category: System Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data No (not applicable) |
|
Description: | Counter of the number of times this module has reset due to a watchdog timeout (microprocessor hang). |
5202 Power-up counter | Category: System Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data No (not applicable) |
|
Description: | Counter of the number of times this module has started when powered up electrically. |
5203 Brownout counter | Category: System Status |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 U16 0 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data No (not applicable) |
|
Description: | Counter of the number of times this module has reset due to low power. |
5204 Module cycle count | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 No - Read Only Yes - Configuration data No (not applicable) |
|
Description: | Total cycle count for module (not writable) |
5205 Module run time hours | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
hour U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
71 4 No - Read Only Yes - Configuration data No (not applicable) |
|
Description: | Total run time hours for module (not writable) |
5206 Cycle count | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
xAX VAL-uint32 U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 4 Yes Yes - Configuration data No (not applicable) |
|
Description: | Accumulated cycle count since installation |
5207 Run time hours | Category: Status Outputs |
Units; DataType: Max: Default Value: Min: |
hour U32 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
71 4 Yes Yes - Configuration data No (not applicable) |
|
Description: | Accumulated run time hours since installation |