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 |
6 Alert display level | Category: Module Setup |
Units; DataType: Max: Default Value: Min: |
VAL-ubyte U8 127 |
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 |
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 |
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 1 3 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Specifies how the K1 relay will be used. If "Wiresheet" 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), whichever 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 remains closed up through the end of Postpurge. If the usage is set for Hot surface ignitor (HSI), the "Ignitor duration" parameter must also be set for HSI, otherwise a communication parameter fault occurs. |
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. A setting of 0 indicates that no Fuel Air control interacts with this burner control. When a Fuel Air control is specified either the Prepurge rate proving or Lightoff rate proving features must be enabled for this Fuel Air control otherwise a configuration parameter fault will occur. |
120 Prepurge rate (RPM) | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
revolutions per minute U16 0 0 20000 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
104 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | 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. This parameter must be set when prepurge rate proving is via RPM 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. If prepurge is to be proven, the Rate proving delay and Purge rate proving failure response parameters must be specified. If prepurge is proven by fan RPM, the Prepurge rate RPM parameter must also be specified. If prepurge is proven by a fuel air control, the module number of the fuel air control must be specified. If none of these conditions are met, a configuration parameter fault will occur. |
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). |
5 | PPP switch and Fuel Air | Prepurge is proven by input switch and Fuel Air control data |
6 | PPP switch and Fan RPM | Prepurge is proven by input switch and RPM feedback (e.g. a tachometer input) |
7 | Fuel Air control and Fan RPM | Prepurge is proven by Fuel Air data and RPM feedback (e.g. a tachometer input) |
8 | PPP switch and Fuel Air and Fan RPM | Prepurge is proven by input switch and RPM feedback and Fuel air data |
122 Lightoff rate (RPM) | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
revolutions per minute U16 0 0 20000 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
104 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | 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. This parameter must be set when lightoff rate proving is via RPM 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. If lightoff is to be proven, the Rate proving delay and Lightoff rate proving failure response parameters must be specified. If lightoff is proven by fan RPM, the Lightoff rate RPM parameter must also be specified. If lightoff is proven by a fuel air control, the module number of the fuel air control must be specified. If none of these conditions are met, a configuration parameter fault will occur. |
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). |
5 | LPP switch and Fuel Air | Lightoff is proven by input switch and Fuel Air control data |
6 | LPP switch and Fan RPM | Lightoff is proven by input switch and RPM feedback (e.g. a tachometer input) |
7 | Fuel Air control and Fan RPM | LIghtoff is proven by Fuel Air data and RPM feedback (e.g. a tachometer input) |
8 | LPP switch and Fuel Air and Fan RPM | Prepurge is proven by input switch and RPM feedback and Fuel air data |
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. The maximum is 300 seconds (5 minutes). If prepurge rate is to be proven by external means, then this time must be specified (not zero). |
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 1 3 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Specifies how long a spark ignitor (IGN output) should be turned on during ignition. If a Hot Surface Ignitor (HSI) is enabled, then IGN must be disabled and "K1 relay user" parameter must be set to "Hot surface ignitor". 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. If ignition type is interrupted pilot, then PFEP and MFEP times must also be specified (not zero). |
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 used to determine whether a flame is present. |
1 | Single flame sensor | Flame is detected using a single flame sensor only. |
2 | Ignition:S1 Run:S2 | Flame is detected using two flame sensors. Sensor 1 is used during ignition and Sensor 2 is used during Run. |
3 | Ignition:S1 Run:Combined S1 S2 | Flame is detected using two flame sensors. Sensor 1 is used during ignition. During Run a combination of sensor 1 and sensor 2 is used, according to a parameter that defines Combination flame sensing. |
4 | Combined S1 S2 | Flame is detected using two flame sensors combined in the same way during both Ignition and Run. Sensor 1 and Sensor 2 are combined according to the parameter that defines Combination flame sensing. |
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: | 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 1 2 |
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. This feature is only allowed for intermittent and interrupted pilot burners ("Ignition type" parameter) s. Lightoff rate proving must also be enabled for this feature to be used. If these conditions are not met, a configuration parameter fault occurs. |
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 10 10 255 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
73 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Specifies the timing that occurs to establish the Pilot valve hold condition. |
133 Manual open switch enable | Category: Ignition Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 1 3 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Specifies if a manual open switch is to be used. It is a configuration fault if this input is enabled and Direct burner ignition (DBI) is also enabled since this feature must be used with a pilot system. This feature can also only be used with UV or IR flame amplifier types. 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 1 2 |
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 (or a lockout will occur), 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. If ignition type is interrupted pilot, then this time must be specified (not zero). |
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.) If ignition type is interrupted pilot, then this time must be specified (not zero). |
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 1 4 |
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 AND 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 1 4 |
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 ("LCI open response" parameter must be specified). |
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. |
4 | Use as limit in all states including standby | The input acts as a run-permissive input in all states including standby. A use as limit selection is required for dual fuel. |
144 LCI/F2 enable | Category: Interlocks Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 1 4 |
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 ("LCI open response" parameter must be specified). |
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. |
4 | Use as limit in all states including standby | The input acts as a run-permissive input in all states including standby. A use as limit 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 1 3 |
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" 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 one 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. If 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 ("PII open response" and "PII dynamic check failure response" parameters must be specified). |
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 1 2 |
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 ("ILK/IAS start check failure response" parameter must be specified). |
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 1 4 |
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 applications). 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 ("IAS/LOI open response" parameter must be specified). |
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 applications). 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: | 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 1 6 |
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 "Prepurge 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 1 6 |
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 "Lightoff 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 1 6 |
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 1 6 |
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. Must be set to a known response when PII is enabled for checking (either dynamic or not). |
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 1 6 |
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. This parameter should be specified when "IAS/LOI monitoring" parameter 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. |
165 ILK/IAS start check failure response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 1 6 |
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. This parameter must be specified when either the "IAS start check enable" or "ILK start check enable" parameters are 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. |
166 PII dynamic check failure response | Category: Failure Response Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 1 6 |
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. This parameter must be specified when PII dynamic check 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. |
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 1 6 |
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 it's 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 65534 |
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 65534 |
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 65534 |
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 1 4 |
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 as 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. A configuration parameter fault also occurs when no valve proving open time is specified and this feature is enabled. |
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.) If ignition type is interrupted pilot, then this time must be specified (not zero). |
193 Energy saving prepurge | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 1 2 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | Delay blower relay turn-on until the prepurge rate is proven as long as certain conditions are met: K1 is configured as the Blower, prepurge time is non-zero, and prepurge proving is PPP switch or Fuel Air control. |
1 | Disable | Feature is not enabled. |
2 | Enable | Feature is enabled. |
194 Flame tolerance time | Category: Timings Setup |
Units; DataType: Max: Default Value: Min: |
second U16 0 40 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 allowed for flame to be present while in the Initiate and Standby states before faulting. |
195 Pilot stabilization 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 allowed for pilot flame to stabilize. |
262 Run stabilization enable | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 1 4 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data No Yes - Can set up in AX |
|
Description: | When enabled the commanded firing rate will remain in the Lightoff condition upon entry to the Run state until either a time period expires or a stabilization threshold is achieved, or both conditions must be satisfied together. When the enabled conditions are met or this feature is disabled, the firing rate will be commanded to the Modulate condition. |
1 | Disable | Run stabilization is not enabled. |
2 | Modulate after stabilization time | Run stabilization is enabled to go to modulation after stabilization time has expired. |
3 | Modulate after stabilization threshold | Run stabilization is enabled to go to modulation after stabilization threshold has been met. |
4 | Modulate after stabilization time and threshold | Run stabilization is enabled to go to modulation after stabilization time has expired and threshold has been met. |
263 Run stabilization 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 No Yes - Can set up in AX |
|
Description: | When run stabilization is enabled the commanded firing rate will remain in the Lightoff condition upon entry to the Run state until this time expires. When this time expires, the firing rate will be commanded to the Modulate condition. |
265 Combination flame sensing | Category: Ignition Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 1 4 |
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 Flame sensing system type parameter is configured for combined usage of two sensors (such as during ignition or during Run or both), the flames of the two sensors are viewed according to this setting. If combined usage is not defined, then this parameter must be set to Not Combined. |
1 | Not Combined | Flame is proven based on flame sensing system type parameter |
2 | S1 OR S2 - both required | Flame is proven if either sensor sees flame. Both sensors must be working normally or else the configured Flame amplifier fault response will occur. |
3 | S1 OR S2 - one required | Flame is proven if either sensor sees flame. If one sensor is offline or not connected or malfunctioning this does not cause a fault response as long as the other sensor is OK. This allows a broken sensor to be repaired without shutting the burner down. |
4 | S1 AND S2 | Flame is proven only if both sensors see flame. Both must be working normally or else the configured Flame amplifier fault response will occur. |
266 Run flame sensing changeover delay 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: | When the Flame sensing system type chooses different flame sensing during Ignition vs. Run, then this setting delays the changeover if it is non-zero. Until the delay time expires the Ignition sensing continues to be used. If the Flame sensing system type uses same sensing during Ignition and Run, then this parameter is ignored. |
268 LPP dynamic check enable | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 1 2 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | configure the testing of the LPP input as the Lightoff proving state is entered and when enabled fault if the LPP input is already on |
1 | Disable | Feature is not enabled. |
2 | Enable | Feature is enabled. |
269 PPP dynamic check enable | Category: Rate Setup |
Units; DataType: Max: Default Value: Min: |
VAL-uint16 EnumSingle 1 1 2 |
Units Code: Size: Writable: Permanent: Verified: DesignSetup: |
256 2 Yes Yes - Configuration data Yes - Safety data Yes - Can set up in AX |
|
Description: | configure the testing of the PPP input as the purge proving state is entered and when enabled fault if the PPP input is already on |
1 | Disable | Feature is not enabled. |
2 | Enable | Feature is enabled. |
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 provides 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 1 1 7 |
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", 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", a Limit module is used in the ignition process. The "Auto ignition enable" parameter must be enabled also to for this response to be used. This response acts whenever the limit block status is "Auto ignition threshold exceeded", then the BC will check for flame presence after 5 seconds has elapsed. 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 1 6 |
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. |
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 provides 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 1 1 7 |
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", 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", a Limit module is used in the ignition process. The "Auto ignition enable" parameter must be enabled also to for this response to be used. This response acts whenever the limit block status is "Auto ignition threshold exceeded", then the BC will check for flame presence after 5 seconds has elapsed. 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. |
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 provides 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 1 1 7 |
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", 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", a Limit module is used in the ignition process. The "Auto ignition enable" parameter must be enabled also to for this response to be used. This response acts whenever the limit block status is "Auto ignition threshold exceeded", then the BC will check for flame presence after 5 seconds has elapsed. 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. |
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 provides 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 1 1 7 |
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", 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", a Limit module is used in the ignition process. The "Auto ignition enable" parameter must be enabled also to for this response to be used. This response acts whenever the limit block status is "Auto ignition threshold exceeded", then the BC will check for flame presence after 5 seconds has elapsed. 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. |
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 provides 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 1 1 7 |
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", 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", a Limit module is used in the ignition process. The "Auto ignition enable" parameter must be enabled also to for this response to be used. This response acts whenever the limit block status is "Auto ignition threshold exceeded", then the BC will check for flame presence after 5 seconds has elapsed. 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. |
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 provides 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 1 1 7 |
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", 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", a Limit module is used in the ignition process. The "Auto ignition enable" parameter must be enabled also to for this response to be used. This response acts whenever the limit block status is "Auto ignition threshold exceeded", then the BC will check for flame presence after 5 seconds has elapsed. 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. |
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 provides 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 1 1 7 |
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", 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", a Limit module is used in the ignition process. The "Auto ignition enable" parameter must be enabled also to for this response to be used. This response acts whenever the limit block status is "Auto ignition threshold exceeded", then the BC will check for flame presence after 5 seconds has elapsed. 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. |
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 provides 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 1 1 7 |
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", 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", a Limit module is used in the ignition process. The "Auto ignition enable" parameter must be enabled also to for this response to be used. This response acts whenever the limit block status is "Auto ignition threshold exceeded", then the BC will check for flame presence after 5 seconds has elapsed. 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. |
648 Flame amplifier 1 required type | 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: | Type of flame amplifier required to be installed for the first flame amplifier. If selection is "None", then no flame amplifier is expected to be installed. |
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: | Flame strength threshold in the first flame amplifier that indicates whether a flame is detected or not. Flame strength below this threshold indicates that no flame is present. |
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: | Flame strength threshold in the first flame amplifier that indicates a weak flame is detected. |
655 Flame amplifier 2 required type | 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: | Type of flame amplifier required to be installed for the second flame amplifier. If selection is "None", then no flame amplifier is expected to be installed. |
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: | Flame strength threshold in the second flame amplifier that indicates whether a flame is detected or not. Flame strength below this threshold indicates that no flame is present. |
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: | Flame strength threshold in the second flame amplifier that indicates a weak flame is detected. |
662 Flame amplifier 3 required type | 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: | Type of flame amplifier required to be installed for the third flame amplifier. If selection is "None", then no flame amplifier is expected to be installed. |
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: | Flame strength threshold in the third flame amplifier that indicates whether a flame is detected or not. Flame strength below this threshold indicates that no flame is present. |
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: | Flame strength threshold in the third flame amplifier that indicates a weak flame is detected. |
669 Flame amplifier 4 required type | 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: | Type of flame amplifier required to be installed for the fourth flame amplifier. If selection is "None", then no flame amplifier is expected to be installed. |
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: | Flame strength threshold in the fourth flame amplifier that indicates whether a flame is detected or not. Flame strength below this threshold indicates that no flame is present. |
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: | Flame strength threshold in the fourth flame amplifier that indicates a weak flame is detected. |