| Scroll to: | About Browsers and Printing |
About Revision Codes |
General Differences Module Changes | How to Find a Module's ID |
Module Reference Documents
About Browsers and Printing
Back to topBrowser versions recommended
Tested browser versions for both viewing and printing:- Chrome - Version 63 or newer (to check, click the three-bar menu icon, choose Help, then About Google Chrome)
- Firefox - version 43 or newer (to check, click the three-bar menu icon, then the small question mark icon, then About Firefox)
- Internet Explorer - version 11 or newer (to check, click the sprocket icon and then About Internet Explorer
How to print
Landscape layout will typically be better than Portrait.- On a module information page, first click the "Open printable version" link.
- Check the page that appears to look for warnings and a button to "Allow" pop-ups or blocked content. Allow it.
- The print command is under the three-bar menu icon for Chrome and Firefox, and under the sprocket icon for IE.
Saving a reference locally
Each page of module information is complete as a stand-alone document. If you use your browser's save-as function to save the page as HTML on your PC, it will work without any need for other documents to support it. Links and buttons on a saved page that normally go to other pages will also work locally IF those other pages are in the same folder on your PC.About Revision Codes
Back to top
Slate module IDs have three parts separated by dots, for example
BCp.0102..01 How to find a Module's ID
But if a design is created for a BCp.0102.01, for example, that design (kit) cannot be used with the older BCp.0101.01 module. Why? Because the new design might have used 0102 features that do not exist in the 0101.
BCp = this identifies the module type: BC = Burner Control. ("p" is always
present in released modules, it indicates "product".
0102 = parameter/data compatibility and revision code, described below.
01 = version number. This is changed when software is updated without
affecting parameters or design compatibility. Examples are an improvement
in signal conditioning or fixing a bug.
The middle number is the important one for the design. It is advanced when the module definition is changed in a way that
affects module configuration or data reporting. Examples are:
- a new parameter is added
- a new choice is added to an existing parameter
- a new event and its event message is added
Backwards compatibility
Modules with newer revisions can be used with designs (kits) that were developed for older modules. A kit designed for a xx.0101.xx module can be used in a xx.0102.xx, or xx.0103.xx, or xx.0146.xxBut if a design is created for a BCp.0102.01, for example, that design (kit) cannot be used with the older BCp.0101.01 module. Why? Because the new design might have used 0102 features that do not exist in the 0101.
What module should I choose?
When designing a new SLATE application you use the AX tool's "Module selection" page to choose modules. In an up-to-date version of the tool all of the modules ever produced will be listed. Thus, for example, you might choose to design for a SBp.0101.01 Base module, or SBp.0102.01, or SBp.0103.01. All are available but Which one is the correct choice for your design ...- If you need one or more of the new features (as described on this page below) then you must choose the newer module that has those features.
- If the older module is good enough, selecting it for your design will ensure that it works whether old or new modules are used on the DIN rail. This may be a factor for field repair: a new replacement module will be compatible with a design that assumed only old features, but if the design (the kit) requires a newer module revision then an older module won't work as a replacement: the device will report an error when the installer reloads the old kit.
- As of January 2018, Honeywell recommends the latest modules (3.10 SW) as the baseline for new designs. Choose only the older modules if you know that your design might be used with some of the older modules that will not be updated. See the General Differences section for a description of the changes between revisions.
Can I mix module revisions?
Yes. When a kit is loaded (or reloaded from the internal SD card for a field repair) the modules chosen by the kit designer are compared with the actual modules on the DIN rail. This is done on a module-by-module basis. As an example, a kit designed for 0102 modules will work with any mixture of 0102, 0103, and 0104 modules.If I have mixed modules will I see any unusual behavior?
- The modules will run and behave appropriately, backwards compatibility is provided.
- In a few cases a commissioning feature may not be supported: For example the Golden Kit feature will work with a mixture of modules, but a 0101 module pre-dates the feature and will not be included. Similarly the Seasonal Curves feature requires both a 0102 Base and a 0102 Fuel Air control (or newer) since these two modules cooperate to implement that feature. (Both the Golden Kit and Seasonal Curves features are described in the General Differences section.)
- Also see the next section immediately below ...
If my kit design is older than the modules that are actually used, will I see any unusual behavior?
No, and maybe.- The design will run and behave appropriately, backwards compatibility is provided.
- However the new module may generate Event and Alert reports that are newer than the kit. In this case there will be no detailed text for them in the kit (which is the source for the text messages) and so instead of a descriptive phrase after an event code in the Event Log, you will see only a generic number (e.g. "Event 123"). The event is still reported and the code is valid; you could determine what it means by looking it up in the reference for the new module (as provided by these web pages).
Future: Revision codes 01xx vs. 02xx
If Honeywell ever chooses to break the backwards compatibility chain, for example to provide a module with entirely new features, then the revision code will jump to a new century; that is 02xx instead of 01xx. Then the same rules apply for the 02xx series as for the 01xx series: design for older 02xx modules will work in newer 02xx modules, but a 01xx design will not work with a 02xx module, and vice versas. The compatibility checking rules are: When the design (kit) is compared vs. the actual modules:- If the century values differ, then there is no compatibility.
- Otherwise the kit (the design) is compatible if the kit's revision number for each module is less than or equal to the revision number of the actual module on the DIN rail.
General Differences
Back to top
The modules with parameter/data revision codes of 0101 were the originals. All SLATE modules were upgraded to 0102 as of late 2015, and more recently the Slate Base module and Burner Control were released again as revision 0103. Several other updates have occurrd over the life of the product which have individually updated affected modules further. It is important to know that not all releases update all module revisions. (For more about these Revision codes, see the About Revision Codes section.)
The 3.20 update is generally classified as an incremental update to the SLATE system with some improvements that are clearly visible to the user, but many more enhancements "behind the scenes". The revisions codes includes are;
The major features added to this sytem release are:
The 3.10 update is a major update with significant improvements that are both visible to the user and enhancements "behind the scenes". The revisions codes includes are;
The major features added to this sytem release are:
https://<SLATEdevice_IP_Number>/generic
this simpler form also works:
<SLATEdevice_IP_Number>/generic (for example: 192.168.91.10/generic).
As with the last update, these updated screens come with a Base Module of revision 0104 and can be installed in an older Base via a service pack.
A verified kit is useful for cloning identical SLATE devices. When a verified kit is installed in a SLATE device that exactly matches the kit's requirements, that device will be ready-to-run without requiring the safety data verification step.
A verified kit is created by first creating a normal kit, then installing it in a SLATE device, and then performing safety verification as usual. The verification information can then be extracted from the SLATE device and saved with the kit. This then becomes a "verified kit": one which has already been verified in a SLATE device and which then can be installed in a SLATE device with identical modules (such as on a production line) without the need to again perform verification.
A verified kit is recognized only by 0102 (or newer) modules. If it is used with 0101 modules this causes no problems, but the safety data for the 0101 modules will still have to be verified in the normal way; that is, the "verified" aspect is not recognized by them.
This feature allows a SLATE Fuel/Air control to have multiple additional stored curve sets that are available for manual changeover. The feature is called "Seasonal" because a typical reason to load a different curve set is because of a change in the winter/summer season, however the actual reason for changing might be anything: for example different batches being processed in an industrial furnace, where oxidation vs. reduction is varied based on the batch type.
Curve sets are saved in the Base module, which can contain as many saved curve sets as are needed. This feature requires a 0102 (or newer) revision for both the Base module and the Fuel Air Control; other modules are not involved with this feature and may be of any revision.
A saved or stored curve set is created by commissioning a Fuel Air control in the usual way, and then (typically, but optionally) verifying it in the usual way by "walking the curve"; that is, by operating the burner throughout its throttling range. If this is completed for a curve set before it is saved, then when this curve set is manually loaded into the Fuel Air Control to be active, it is immediately ready to run without requiring the "walking the curve" verification step because that has already been done.
A curve set's verified status is preserved only when loaded back into the specific Fuel Air Control that created it. If loaded anywhere else its verified status is always cleared.
https://<SLATEdevice_IP_Number>/generic
this simpler form also works:
<SLATEdevice_IP_Number>/generic (for example: 192.168.91.10/generic).
The 0101 revision of the Base (SBp.0101.01) contains the initial versions of these screens. All of them were revised and improved for the 0102 version (SBp.0102.01). Changes were made to improve their usability and to ensure that all data items are represented.
To obtain these updated screens the Base module must be revision 0102 or newer - they also can be installed in a 0101 Base via a service pack.
New registers in the Base module also allow wire sheet logic to generate events that are stored in the Event log.
Software 3.20
This revision is noted as the software version in the header above, because each module has started to diverge in terms of revision code. The revision code changes when necessary do to enhancements made to the register set. As the SLATE system has evolved, releases have occurred that only enhanced specific modules (and they saw new revision codes), while other modules remain with features they had from a past release (i.e. the Annunciator or Digital IO module).The 3.20 update is generally classified as an incremental update to the SLATE system with some improvements that are clearly visible to the user, but many more enhancements "behind the scenes". The revisions codes includes are;
- Annunciator - 0102
- Burner Control - 0105
- Fuel Air Ratio - 0104
- Analog I/O - 0104
- Digital I/O - 0102
- Limit - 0104
- Base Module - 0105
The major features added to this sytem release are:
General System Enhancements and Fixes
Numerous "behind the scenes" enhancements have taken place to improve system stability, security and usability.Annunciator Dual Path Fixed
Dual Path Annunciator configurations have been improved to properly determine the first out cause.Base Module Updates
The Base Module has had a notable amount of changes to provide additional resources for user wiresheet programming.- Improved ModBus TCP reliability
- General system performance improvements to speed web responsiveness
- Increased BACnet binding registers from 20 to 40
- Increased wiresheet data registers from 5 to 10
- Added 10 non-volatile wiresheet data registers
- Minor built-in web page enhancements
Expanded Analog Cell Functions
All modules that include Analog Cell functionality (Analog I/O, Limit, Fuel Air Ratio) have a few enhanced features:- Added type R and S thermocouples
- Expanded range of PT-100 sensor to measure up to 850C
Burner Control Updates
Additional configuration options have been added to the Burner Control to cover additional Legacy EC78xx sequences.- Ability for LCI to cause lockout in Standby
- Option for Dynamic Check on LPP and PPP inputs
Software 3.10
This revision is noted as the software version in the header above, because each module has started to diverge in terms of revision code. The revision code changes when necessary do to enhancements made to the register set. As the SLATE system has evolved, releases have occurred that only enhanced specific modules (and they saw new revision codes), while other modules remain with features they had from a past release (i.e. the Annunciator or Digital IO module).The 3.10 update is a major update with significant improvements that are both visible to the user and enhancements "behind the scenes". The revisions codes includes are;
- Annunciator - 0102
- Burner Control - 0104
- Fuel Air Ratio - 0103
- Analog I/O - 0103
- Digital I/O - 0102
- Limit - 0103
- Base Module - 0104
The major features added to this sytem release are:
Multi-Language Support
Primarily a SLATE Base Module feature, the SLATE system now offers support for multiple languages and user selection of the language shown via the web interface.Combination Flame Sensor Support
A new feature to support configuration and use of up to two flame amplifiers for a single Burner Control. A few examples of usage may be additional redundancy in a system or using separate detectors for a Pilot Flame versus a Main Flame.Further Improved Built-in Pages
As improved in the last major system update, many of the built-in display screens that are part of the Base module have been updated again. They are accessed from the "Generic" main page, which may be displayed in any SLATE device by using the URL:https://<SLATEdevice_IP_Number>/generic
this simpler form also works:
<SLATEdevice_IP_Number>/generic (for example: 192.168.91.10/generic).
As with the last update, these updated screens come with a Base Module of revision 0104 and can be installed in an older Base via a service pack.
General System Enhancements and Fixes
Numerous "behind the scenes" enhancements have taken place to improve system stability and usability.Burner Control 0102 vs. 0103
This revision to the Burner Control was a minor update to fix several small bugs and add one minor featue (Run Stabilization). See module differences for more details.Base Module 0102 vs. 0103
This revision currently (Jan 2015) affects only the Base module (SBp.0103.01) It provides the Base with improved handling of its internal and external SD cards and also USB memory sticks (also called flash drives or thumb drives) and better diagnostics when these have faults. It also added a few other events (see the Base module differences section).0101 vs. 0102
The 0102 version provides some significant enhancements and some smaller improvements:Verified Kits
(A "kit" is the set of all files and data that is installed in a SLATE device to transform it from generic modules from Honeywell, into a control for a specific application. When a kit is installed safety data must be verified via a manual review process before the device will operate.)A verified kit is useful for cloning identical SLATE devices. When a verified kit is installed in a SLATE device that exactly matches the kit's requirements, that device will be ready-to-run without requiring the safety data verification step.
A verified kit is created by first creating a normal kit, then installing it in a SLATE device, and then performing safety verification as usual. The verification information can then be extracted from the SLATE device and saved with the kit. This then becomes a "verified kit": one which has already been verified in a SLATE device and which then can be installed in a SLATE device with identical modules (such as on a production line) without the need to again perform verification.
A verified kit is recognized only by 0102 (or newer) modules. If it is used with 0101 modules this causes no problems, but the safety data for the 0101 modules will still have to be verified in the normal way; that is, the "verified" aspect is not recognized by them.
Seasonal Curve Sets
(A "Curve Set" is a set of curves - one for each actuator - that define the actuator positions for a range of throttle positions. For a dual fuel system, two curve sets can be active and loaded into the Fuel Air control at the same time: one set for Fuel1, and another for Fuel2.)This feature allows a SLATE Fuel/Air control to have multiple additional stored curve sets that are available for manual changeover. The feature is called "Seasonal" because a typical reason to load a different curve set is because of a change in the winter/summer season, however the actual reason for changing might be anything: for example different batches being processed in an industrial furnace, where oxidation vs. reduction is varied based on the batch type.
Curve sets are saved in the Base module, which can contain as many saved curve sets as are needed. This feature requires a 0102 (or newer) revision for both the Base module and the Fuel Air Control; other modules are not involved with this feature and may be of any revision.
A saved or stored curve set is created by commissioning a Fuel Air control in the usual way, and then (typically, but optionally) verifying it in the usual way by "walking the curve"; that is, by operating the burner throughout its throttling range. If this is completed for a curve set before it is saved, then when this curve set is manually loaded into the Fuel Air Control to be active, it is immediately ready to run without requiring the "walking the curve" verification step because that has already been done.
A curve set's verified status is preserved only when loaded back into the specific Fuel Air Control that created it. If loaded anywhere else its verified status is always cleared.
A curve set does not have to be verified before it is saved - it is simply stored in whatever condition it had when it was in the Fuel Air Control, that is: not verified at all, partly verified, or fully verified. Then, whenever a saved curve set is reloaded into the Fuel Air Control that created it, it comes back in the same state as when it was saved: not verified at all, partly verified, or fully verified. However the two latter conditions occur only for the Fuel Air Control in which the curve set was verified. That is, a saved curve set (in any condition) also can be loaded into a different Fuel Air Control if the SLATE device has more than one, or it can moved to a Fuel Air Control in a differnt SLATE device and installed there. This is a way to get a quick start in setting up another Fuel Air Control, but when a curve set is loaded into any Fuel Air Control that did not create it, that curve set will be in a completely unverified condition and will have to be verified by walking the curve before it is used.
Improved Built-in Pages
A SLATE device comes with many built-in display screens that are part of the Base module. They are accessed from the "Generic" main page, which may be displayed in any SLATE device by using the URL:https://<SLATEdevice_IP_Number>/generic
this simpler form also works:
<SLATEdevice_IP_Number>/generic (for example: 192.168.91.10/generic).
The 0101 revision of the Base (SBp.0101.01) contains the initial versions of these screens. All of them were revised and improved for the 0102 version (SBp.0102.01). Changes were made to improve their usability and to ensure that all data items are represented.
To obtain these updated screens the Base module must be revision 0102 or newer - they also can be installed in a 0101 Base via a service pack.
BACnet Improvements
The SLATE Base module was improved by adding a BACnet router between its ethernet and the RS-485 busses. This allows BACnet devices on one bus to be "seen" by devices on the other bus. New parameters to support this were added to the Base.Event Logging Improvements
If you view the changes for each module you will see that all of them have new registers for events. Register 28 permits a user to log a personal event manually, to identify when a significant action affecting the system has occurred and should be noted. (Register 27 is also new, but it supports additional text for internal operations and is not otherwise useful.) Most of the modules also have new event messages that support improved detection of problems and changed messages that provide better diagnostic information.New registers in the Base module also allow wire sheet logic to generate events that are stored in the Event log.
Default and Range Values
Missing default values and range limit values were added for some modules.Module Changes
Back to topANNp.0101.01 vs. ANNp.0102.01
A few new events and event handling registers were added.New Registers
r27 - Event text r28 - User event text
Changed Events
9 - User: %s (Was: Autogen reserved 9)
10 - Module number changed %s (Was: Autogen reserved 10)
Back to top
BCp.0101.01 vs. BCp.0102.01
Additions and changes:- New events and event handling registers
- Valve proving status registers
- Configuration registers for the Energy Saving Prepurge feature and Flame tolerance time were added
- A Pilot stabilization state is now available (required in Europe)
- Range limits were added for many registers
- Time data types were enlarged to extend time measurement capability
- Golden kit support was added (see the General Differences section)
New Registers
r27 - Event text r28 - User event text r191 - Valve proving state r192 - Valve proving state time r193 - Energy saving prepurge r194 - Flame tolerance time r195 - Pilot stabilization time
Changed Register Values
r142 Fuel selection setup
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 4 (Was: <empty>)
r143 LCI/F1 enable
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 3 (Was: <empty>)
r144 LCI/F2 enable
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 3 (Was: <empty>)
r178 Recycle 1 retry limit count
ValueMax changed to: 65534 (Was: 65535)
r181 Recycle 2 retry limit count
ValueMax changed to: 65534 (Was: 65535)
r184 Recycle 3 retry limit count
ValueMax changed to: 65534 (Was: 65535)
r186 Valve proving enable
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 4 (Was: <empty>)
r207 Burner control state time
DataType changed to: U32 (Was: U16)
r213 Lockout burner state time
DataType changed to: U32 (Was: U16)
New Events
120 - Interrupted ignition with zero MFEP
Changed Events
9 - User: %s (Was: Autogen reserved 9)
10 - Module number changed %s (Was: Autogen reserved 10)
61 - UV/VIS flame amplifier NV storage not initialized (Was: SSUV flame amplifier NV storage not initialized)
62 - False flame in UV/VIS flame amplifier (Was: False flame in SSUV flame amplifier)
63 - UV/VIS flame amp invalid flame signal (Was: SSUV flame amplifier invalid flame signal)
64 - UV/VIS flame amplifier low duty (Was: SSUV flame amplifier low duty)
73 - Burner was in %s state (Was: Burner lockout in %s state)
74 - Burner state time: %d seconds (Was: Burner lockout state time: %d)
75 - Burner cycle count: %d (Was: Burner lockout cycles: %d)
76 - Burner run time: %d hours (Was: Burner lockout run time: %d)
77 - Burner state: %s (Was: Burner lockout: %s)
91 - Safety relay key feedback failure (Was: Safety relay MFO signal failure)
100 - UV/VIS flame amplifier HW error (Was: SSUV flame amplifier HW error)
101 - UV/VIS flame amplifier Low 18V (Was: SSUV flame amplifier Low 18V)
110 - UV/VIS flame amp flame on threshold out of range (Was: SSUV flame amp flame on threshold out of range)
111 - UV/VIS flame amp weak flame threshold out of range (Was: SSUV flame amp weak flame threshold out of range)
BCp.0102.01 vs. BCp.0103.01
Additions and changes:- New Run Stabilization feature
- Pilot Valve Hold feature fixed to better transition between modulation, PVH and lightoff
- Postpurge fix
New Registers
r262 - Run stabilization enable r263 - Run stabilization time r264 - Run stabilization threshold
Changed Register Values
r132 Pilot valve hold transition time
ValueMin changed to: 10 (Was: 5)
ValueMax changed to: 255 (Was: 60)
BCp.0103.01 vs. BCp.0104.01
Additions and changes:- Range limits were added for many registers
- Descriptions updated for many registers
- Combination rate proving options added (i.e. Fuel Air AND PPP)
- Combination flame sensing support added (Dual Flame Amplifier)
- New Events for new features
- New Alerts added
New Registers
r265 - Combination flame sensing r266 - Run flame sensing changeover delay time r267 - 1400DegreeFlameOverrideStatus
Changed Register Values
r116 K1 relay usage
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 3 (Was: <empty>)
r120 Prepurge rate (RPM)
ValueMin changed to: 0 (Was: <empty>)
ValueMax changed to: 20000 (Was: <empty>)
r122 Lightoff rate (RPM)
ValueMin changed to: 0 (Was: <empty>)
ValueMax changed to: 20000 (Was: <empty>)
r126 Ignitor duration
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 3 (Was: <empty>)
r131 Pilot valve hold enable
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 2 (Was: <empty>)
r133 Manual open switch enable
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 3 (Was: <empty>)
r134 Auto ignition enable
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 2 (Was: <empty>)
r146 Pre ignition interlock enable
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 3 (Was: <empty>)
r148 IAS start check enable
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 2 (Was: <empty>)
r149 IAS/LOI monitoring
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 4 (Was: <empty>)
r154 Purge rate proving failure response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 6 (Was: <empty>)
r155 Lightoff rate proving failure response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 6 (Was: <empty>)
r160 LCI open response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 6 (Was: <empty>)
r162 PII open response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 6 (Was: <empty>)
r164 IAS / LOI open response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 6 (Was: <empty>)
r165 ILK/IAS start check failure response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 6 (Was: <empty>)
r166 PII dynamic check failure response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 6 (Was: <empty>)
r174 Fuel air communication fault response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 6 (Was: <empty>)
r602 Socket 1 limit response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 7 (Was: <empty>)
r603 Socket 1 limit response trigger
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 6 (Was: <empty>)
r608 Socket 2 limit response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 7 (Was: <empty>)
r614 Socket 3 limit response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 7 (Was: <empty>)
r620 Socket 4 limit response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 7 (Was: <empty>)
r626 Socket 5 limit response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 7 (Was: <empty>)
r632 Socket 6 limit response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 7 (Was: <empty>)
r638 Socket 7 limit response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 7 (Was: <empty>)
r644 Socket 8 limit response
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 7 (Was: <empty>)
New Events
121 - Flame amplifier %d packet response %s 122 - Flame amplifier %d packet shutter error %s 123 - Flame amplifier %d packet timeout %s 124 - Flame amplifier %d packet challenge error %s 125 - Flame amplifier %d reported unknown fault %s 126 - Flame amplifier configuration fault 127 - Flame amplifier %d packet threshold %s 128 - Lightoff unproven - neither LPP nor Fuel Air 129 - Lightoff unproven - neither LPP nor Fan RPM 130 - Lightoff unproven - neither Fuel Air nor Fan RPM 131 - Lightoff unproven - neither LPP nor FA nor Fan RPM 132 - Prepurge unproven - neither PPP nor Fuel Air 133 - Prepurge unproven - neither PPP nor Fan RPM 134 - Prepurge unproven - neither Fuel Air nor Fan RPM 135 - Prepurge unproven - neither PPP nor FA nor Fan RPM
Changed Events
21 - Prepurge unproven by PPP (Was: Purge position is NOT proven by PPP)
22 - Prepurge unproven by Fan RPM (Was: Purge position is NOT proven by fan)
23 - Lightoff unproven by LPP (Was: Lightoff position is NOT proven by LPP)
24 - Lightoff unproven by Fuel Air control (Was: Lightoff position NOT proven by Fuel Air control)
44 - PII dynamic check failure (Was: PII start check failure)
49 - Lightoff unproven by Fan RPM (Was: Lightoff unproven by TACH)
New Alerts
11 - Demand has been detected
12 - No demand present
13 - Burner recycling (code=%d)
14 - Burner is holding (code=%d)
15 - Burner is not holding
Changed Alerts
9 - Auto ignition in Run established (Was: Auto flame in Run established)
10 - Auto ignition in Run lost (Was: Auto flame in Run lost)
BCp.0104.01 vs. BCp.0105.01
Additions and changes:- New dynamic check configuration options for both LPP and PPP
- New LCI option to Lockout if open in Standby
- Enhanced flame status troubleshooting with combination flame sensing systems
New Registers
r246 - FlameAmp1StatusHistory r247 - FlameAmp2StatusHistory r268 - LPP dynamic check enable r269 - PPP dynamic check enable
Changed Register Values
r143 LCI/F1 enable
ValueMax changed to: 4 (Was: 3)
r144 LCI/F2 enable
ValueMax changed to: 4 (Was: 3)
New Events
136 - LPP dynamic check failure 137 - PPP dynamic check failure 138 - IR flame amplifier Low 18V 139 - Flame amplifier 1 fault status is %s 140 - Flame amplifier 2 fault status is %s
Back to top
FAp.0101.01 vs. FAp.0102.01
Additions and changes:- New events and event handling registers
- Support for the new and more accurate temperature-compensated thermocouple
- Golden kit support was added (see the General Differences section)
- Seasonal Curve feature was added (see the General Differences section)
New Features
t2,t3: Thermocouple with External NTC input cell:A t6,t7: Thermocouple with External NTC input cell:B
New Registers
r27 - Event text r28 - User event text
Changed Register Values
r111 InactiveCurveBitmap
Name changed to: Inactive curve bitmap (Was: InactiveCurveBitmap)
r329 Actuator 1 diagnostics d3
Name changed to: Actuator 1 diagnostics transmit count (Was: Actuator 1 diagnostics d3)
r330 Actuator 1 diagnostics d4
Name changed to: Actuator 1 diagnostics receive count (Was: Actuator 1 diagnostics d4)
r338 Actuator 2 diagnostics d3
Name changed to: Actuator 2 diagnostics transmit count (Was: Actuator 2 diagnostics d3)
r339 Actuator 2 diagnostics d4
Name changed to: Actuator 2 diagnostics receive count (Was: Actuator 2 diagnostics d4)
r347 Actuator 3 diagnostics d3
Name changed to: Actuator 3 diagnostics transmit count (Was: Actuator 3 diagnostics d3)
r348 Actuator 3 diagnostics d4
Name changed to: Actuator 3 diagnostics receive count (Was: Actuator 3 diagnostics d4)
r356 Actuator 4 diagnostics d3
Name changed to: Actuator 4 diagnostics transmit count (Was: Actuator 4 diagnostics d3)
r357 Actuator 4 diagnostics d4
Name changed to: Actuator 4 diagnostics receive count (Was: Actuator 4 diagnostics d4)
New Events
42 - Curve verification needed: data mismatch
43 - Curve verification retained
44 - Analog cell %s low and high limits reversed
Changed Events
9 - User: %s (Was: Autogen reserved 9)
10 - Module number changed %s (Was: Autogen reserved 10)
21 - Actuator %d fault. %s (Was: Actuator %d fault)
FAp.0102.01 vs. FAp.0103.01
Additions and changes:- Added support to transition between Normal Operation and Commissioning without locking out Burner
- Improved ability to use the Trim feature on VFDs
- Added Totalizer option when Analog Cell is used for General Application Use (non-VFD)
- Updated supported fault code identification from Low Torque Actuatrs
- Updated many descriptions
New Features
t2,t3: Thermocouple Sense Block input cell:A t2,t3: Thermocouple with External NTC input cell:A t2: Totalizer input (t4) cell:A t6,t7: Thermocouple Sense Block input cell:B t6,t7: Thermocouple with External NTC input cell:B t6: Totalizer input (t8) cell:B
New Registers
r362 - VFD1 Minimum Command Percent r363 - VFD1 Maximum Command Percent r364 - VFD2 Minimum Command Percent r365 - VFD2 Maximum Command Percent r526 - Totalizer preset request, cell:A r527 - Totalizer preset value, cell:A r528 - Totalizer preset request, cell:B r529 - Totalizer preset value, cell:B
New Events
45 - Actuator %d EEPROM fault
46 - Actuator %d reported unknown fault
FAp.0103.01 vs. FAp.0104.01
Additions and changes:- Improved behavior when using a VFD for Trim
- Added R and S type thermocouples (when using general purpose Analog I/O)
- Improved PT-100 range to 850C (when using general purpose Analog I/O)
Changed Register Values
r103 Position confirm
Name changed to: Reserved 103 (Was: Position confirm)
DataType changed to: U16 (Was: EnumSingle)
r117 Confirmation enable
Name changed to: Reserved 117 (Was: Confirmation enable)
DataType changed to: U16 (Was: EnumSingle)
Back to top
IOA1p.0101.01 vs. IOA1p.0102.01
Additions and changes:- New events and event handling registers
- Support for the new and more accurate temperature-compensated thermocouple
New Features
t10,t11: Thermocouple with External NTC input cell:C t14,t15: Thermocouple with External NTC input cell:D t2,t3: Thermocouple with External NTC input cell:A t6,t7: Thermocouple with External NTC input cell:B
New Registers
r27 - Event text r28 - User event text
New Events
11 - Cell A Internal Failure
12 - Cell B Internal Failure
13 - Cell C Internal Failure
14 - Cell D Internal Failure
15 - Analog cell %s low and high limits reversed
Changed Events
9 - User: %s (Was: Autogen reserved 9)
10 - Module number changed %s (Was: Autogen reserved 10)
IOA1p.0102.01 vs. IOA1p.0103.01
Additions and changes:- Added Totalizer option for Analog Cell
New Features
t10,t11: Thermocouple Sense Block input cell:C t10,t11: Thermocouple with External NTC input cell:C t10: Totalizer input (t12) cell:C t14,t15: Thermocouple Sense Block input cell:D t14,t15: Thermocouple with External NTC input cell:D t14: Totalizer input (t16) cell:D t2,t3: Thermocouple Sense Block input cell:A t2,t3: Thermocouple with External NTC input cell:A t2: Totalizer input (t4) cell:A t6,t7: Thermocouple Sense Block input cell:B t6,t7: Thermocouple with External NTC input cell:B t6: Totalizer input (t8) cell:B
New Registers
r352 - Totalizer preset request, cell:A r353 - Totalizer preset value, cell:A r354 - Totalizer preset request, cell:B r355 - Totalizer preset value, cell:B r356 - Totalizer preset request, cell:C r357 - Totalizer preset value, cell:C r358 - Totalizer preset request, cell:D r359 - Totalizer preset value, cell:D
IOA1p.0103.01 vs. IOA1p.0104.01
Additions and changes:- Added R and S type thermocouples
- Improved PT-100 range to 850C
No differences.
Back to top
IOD1p.0101.01 vs. IOD1p.0102.01
New events and event handling registers were added.New Registers
r27 - Event text r28 - User event text
Changed Events
9 - User: %s (Was: Autogen reserved 9)
10 - Module number changed %s (Was: Autogen reserved 10)
Back to top
LMp.0101.01 vs. LMp.0102.01
Additions and changes:- New events and event handling registers
- Support for the new and more accurate temperature-compensated thermocouple
- Low limits were added for many registers
- Golden kit support was added (see the General Differences section}
New Features
t10,t11: Thermocouple with External NTC input cell:C t14,t15: Thermocouple with External NTC input cell:D t2,t3: Thermocouple with External NTC input cell:A t6,t7: Thermocouple with External NTC input cell:B
New Registers
r27 - Event text r28 - User event text
Changed Register Values
r205 Limit block 1 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r206 Limit block 1 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r207 Limit block 1 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
r217 Limit block 2 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r218 Limit block 2 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r219 Limit block 2 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
r229 Limit block 3 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r230 Limit block 3 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r231 Limit block 3 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
r241 Limit block 4 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r242 Limit block 4 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r243 Limit block 4 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
r253 Limit block 5 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r254 Limit block 5 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r255 Limit block 5 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
r265 Limit block 6 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r266 Limit block 6 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r267 Limit block 6 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
r277 Limit block 7 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r278 Limit block 7 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r279 Limit block 7 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
r289 Limit block 8 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r290 Limit block 8 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r291 Limit block 8 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
r301 Limit block 9 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r302 Limit block 9 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r303 Limit block 9 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
r313 Limit block 10 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r314 Limit block 10 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r315 Limit block 10 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
r325 Limit block 11 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r326 Limit block 11 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r327 Limit block 11 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
r337 Limit block 12 hysteresis offset
ValueMin changed to: 0.0 (Was: <empty>)
r338 Limit block 12 detection time
ValueMin changed to: 0.0 (Was: <empty>)
r339 Limit block 12 recovery time
ValueMin changed to: 0.0 (Was: <empty>)
New Events
38 - Invalid limit block %d hysteresis
39 - Invalid limit block %d detection time
40 - Invalid limit block %d recovery time
41 - Analog cell %s low and high limits reversed
42 - Safety Relay K2 ON
Changed Events
9 - User: %s (Was: Autogen reserved 9)
10 - Module number changed %s (Was: Autogen reserved 10)
15 - Safety relay key feedback failure (Was: Safety relay MFO error)
LMp.0102.01 vs. LMp.0103.01
Additions and changes:- Added Totalizer option when Analog Cell is used for General Application Use (non-Limit)
New Features
t10,t11: Thermocouple Sense Block input cell:C t10,t11: Thermocouple with External NTC input cell:C t10: Totalizer input (t12) cell:C t14,t15: Thermocouple Sense Block input cell:D t14,t15: Thermocouple with External NTC input cell:D t14: Totalizer input (t16) cell:D t2,t3: Thermocouple Sense Block input cell:A t2,t3: Thermocouple with External NTC input cell:A t2: Totalizer input (t4) cell:A t6,t7: Thermocouple Sense Block input cell:B t6,t7: Thermocouple with External NTC input cell:B t6: Totalizer input (t8) cell:B
New Registers
r700 - Totalizer preset request, cell:A r701 - Totalizer preset value, cell:A r702 - Totalizer preset request, cell:B r703 - Totalizer preset value, cell:B r704 - Totalizer preset request, cell:C r705 - Totalizer preset value, cell:C r706 - Totalizer preset request, cell:D r707 - Totalizer preset value, cell:D
LMp.0103.01 vs. LMp.0104.01
Additions and changes:- Added R and S type thermocouples
- Improved PT-100 range to 850C
No differences.
Back to top
SBp.0101.01 vs. SBp.0102.01
Additions and changes:- New events and event handling registers
- New BACnet router configuration registers
- Seasonal Curve support was added (see the General Differences section)
- General purpose wire sheet data registers added (future use)
- Range limits were added for many registers
- Golden kit support was added (see the General Differences section)
New Registers
r27 - Event text r28 - User event text r77 - FBE Event text r78 - FBE User event text r140 - BACnet Ethernet/IP Network number r141 - BACnet MS/TP Network number r142 - BACnet configuration status r143 - Curve set login required r144 - System up time r456 - Wiresheet data 1 r457 - Wiresheet data 2 r458 - Wiresheet data 3 r459 - Wiresheet data 4 r460 - Wiresheet data 5
Changed Register Values
r104 Modbus/TCP configuration
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 2 (Was: <empty>)
r108 BACnet Ethernet configuration
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 4 (Was: <empty>)
r118 Ethernet IP address source
ValueMin changed to: 1 (Was: <empty>)
ValueMax changed to: 2 (Was: <empty>)
New Events
32 - Failed to get safety verification file from m%d
33 - Golden safety verification file %s created
34 - Safety verification file loaded into m%d
35 - Failed to load safety verification file into m%d
36 - Curve set %s created
37 - Curve set %s loaded into m%d
38 - Verified kit %s successfully installed
Changed Events
9 - User: %s (Was: Autogen reserved 9)
9(F) - User: %s (Was: Autogen reserved 9)
10 - Module number changed %s (Was: Autogen reserved 10)
10(F) - Module number changed %s (Was: Autogen reserved 10)
11 - Module %d serial number mismatch (%s) (Was: Module %d serial number mismatch)
13 - Module %d not ready for startup (%s) (Was: Module %d not ready for startup)
14 - Module %d type mismatch (%s) (Was: Module %d type mismatch)
15(F) - Battery is present (Was: Battery inserted)
15 - Module %d configuration signature mismatch (%s) (Was: Module %d configuration signature mismatch)
16(F) - Battery is not detected (Was: Battery removed)
16 - Duplicate module number %d (%s) (Was: Duplicate module number %d)
17 - Module number %d missing (%s) (Was: Module number %d missing)
25 - Kit %s successfully installed (Was: Kit successfully loaded)
26 - Kit %s install failure (Was: Kit load failure)
SBp.0102.01 vs. SBp.0103.01
Additions and changes:- A few new events were added.
- Better handling of SD card and USB memory problems is implemented with new diagnostics status registers (these are used by the Base module's small display).
New Registers
r145 - Internal SD card status r146 - External SD card status r147 - USB status
Changed Register Values
r132 Display sleep delay time
ValueMax changed to: 1092 (Was: 1440)
New Events
39 - Internal SD card missing
40 - Invalid format internal SD card installed
41 - Read only internal SD card installed
42 - Invalid format SD card installed
43 - Read only SD card installed
44 - Invalid format USB installed
45 - Read only USB installed
Changed Events
23(F) - High temperature in Base module (Was: High temperature) 29(F) - Aux supply Over current protection is enabled (Was: AuxSupplyOvercurrentProtectionEnabled)
SBp.0103.01 vs. SBp.0104.01
Additions and changes:- Added multi-language support
- Improved overall look and feel of web pages for consistency
- Added ability to configure Lead Lag Method and Number of Stages in the field
- A few new events were added
New Registers
r148 - Enable Web interface r149 - Kit name r150 - Kit install time r461 - Stage driver lead lag - Needs restart - see desc. r5300 - Common language 1 r5301 - Common language 2 r5302 - Common language 3 r5303 - Common language 4 r5304 - Common language 5 r5305 - Common language 6 r5306 - Common language 7 r5307 - Common language 8 r5308 - Common language 9 r5309 - Common language 10
Changed Register Values
r455 Stage driver maximum stages
Name changed to: Stage driver stages - Needs restart - see desc. (Was: Stage driver maximum stages)
New Events
46 - Web page(s) installed in Base module
47 - Platform bus access degraded
48 - Event log cleared
49 - Alert log cleared
50 - Service pack %s installed
51 - Web interface enabled
52 - Web interface disabled
Changed Events
20 - Configuration set %s invalid (Was: Configuration set invalid)
21 - Configuration set %s not compatible with kit (Was: Configuration set not compatible with kit)
22 - Configuration set %s modules mismatch (Was: Configuration set modules mismatch)
23 - Configuration set %s was loaded (Was: Configuration set was loaded)
24 - Configuration set %s was not loaded (Was: Configuration set was not loaded)
New Alerts
12 - Internal SD card is almost full
SBp.0104.01 vs. SBp.0105.01
Additions and changes:- Improved Modbus TCP reliability
- Updated web certificate to address Chrome security warning
- Optimizations to improve responsiveness and performance
- Added calendar registers for Month, Day and Year
- Doubled BACnet binding registers from 20 to 40
- Doubled wiresheet register data registers from 5 to 10
- Added 10 new registers for non-volatile wiresheet data
New Registers
r151 - Date month r152 - Date day r153 - Date year r462 - Wiresheet data 6 r463 - Wiresheet data 7 r464 - Wiresheet data 8 r465 - Wiresheet data 9 r466 - Wiresheet data 10 r467 - NV wiresheet data 1 r468 - NV wiresheet data 2 r469 - NV wiresheet data 3 r470 - NV wiresheet data 4 r471 - NV wiresheet data 5 r472 - NV wiresheet data 6 r473 - NV wiresheet data 7 r474 - NV wiresheet data 8 r475 - NV wiresheet data 9 r476 - NV wiresheet data 10 r700 - BACnet bind 21 setup r701 - BACnet bind 21 status r702 - BACnet bind 21 data r703 - BACnet bind 22 setup r704 - BACnet bind 22 status r705 - BACnet bind 22 data r706 - BACnet bind 23 setup r707 - BACnet bind 23 status r708 - BACnet bind 23 data r709 - BACnet bind 24 setup r710 - BACnet bind 24 status r711 - BACnet bind 24 data r712 - BACnet bind 25 setup r713 - BACnet bind 25 status r714 - BACnet bind 25 data r715 - BACnet bind 26 setup r716 - BACnet bind 26 status r717 - BACnet bind 26 data r718 - BACnet bind 27 setup r719 - BACnet bind 27 status r720 - BACnet bind 27 data r721 - BACnet bind 28 setup r722 - BACnet bind 28 status r723 - BACnet bind 28 data r724 - BACnet bind 29 setup r725 - BACnet bind 29 status r726 - BACnet bind 29 data r727 - BACnet bind 30 setup r728 - BACnet bind 30 status r729 - BACnet bind 30 data r730 - BACnet bind 31 setup r731 - BACnet bind 31 status r732 - BACnet bind 31 data r733 - BACnet bind 32 setup r734 - BACnet bind 32 status r735 - BACnet bind 32 data r736 - BACnet bind 33 setup r737 - BACnet bind 33 status r738 - BACnet bind 33 data r739 - BACnet bind 34 setup r740 - BACnet bind 34 status r741 - BACnet bind 34 data r742 - BACnet bind 35 setup r743 - BACnet bind 35 status r744 - BACnet bind 35 data r745 - BACnet bind 36 setup r746 - BACnet bind 36 status r747 - BACnet bind 36 data r748 - BACnet bind 37 setup r749 - BACnet bind 37 status r750 - BACnet bind 37 data r751 - BACnet bind 38 setup r752 - BACnet bind 38 status r753 - BACnet bind 38 data r754 - BACnet bind 39 setup r755 - BACnet bind 39 status r756 - BACnet bind 39 data r757 - BACnet bind 40 setup r758 - BACnet bind 40 status r759 - BACnet bind 40 data
New Events
53 - Curve set %s NOT loaded into m%d
How to Find a SLATE Module's ID
Back to topThe best way to see a SLATE module identifier is to power up a SLATE system and use the Base Module's display.
If you want to identify a set of modules you can include one of each of the modules types that you intend to use (e.g. one Burner Control, one Limit, one Fuel/Air control, etc.). More than one of each type is also OK.
You can omit (or include) flame amplifiers because they are not configured in the same way as other modules: They are "child" modules of a Burner Control and are configured via settings in the Burner Control. Thus their module IDs are not needed.
You don't have to load a kit into the device (although it's OK if you've done that). Everything can be factory-fresh. All that is necessary is to mount them normally and then power up the Base module.
After you have the desired modules in place and have turned on the Base, the Base module screen should light up.Then follow these steps:
| 1. Push the Menu button on the Base. That will show a screen similar to this: |  |
|
2. Use the Down-arrow button to select the "Device information" item as
shown here: 3. Then press the OK or the Right-arrow button (they both do the same thing on this screen). |
 |
|
The screen that appears will be similar to this: It will list the Base itself and all of the modules that were found by the Base. |
 |
|
Note: The example screens above and below show module numbers
on the left margin. But if you are viewing factory-fresh modules that have
never been assigned a number (a kit has never been loaded) then you will
see "m?" instead, as shown here: |
 |
|
4. Next use the Down-arrow (and Up-arrow) buttons to select the module you
want to identify. As you use the arrow buttons the screen will scroll
if necessary to show all of the modules. In this example the Burner
module is selected: 5. When you have selected a module then press the OK or the Right-arrow button. |
 |
|
You will then see information about the selected module. The Module ID
will be the fourth item: 6. To identify more modules first use the Left-arrow button to go back to the previous screen, then repeat steps 4 and 5. |
 |
Back to top