Issue
How to order controllers with XDriver support
How to upgrade a controller so it has XDriver support
All NC2 options are not available as standard
How to order node upgrade
XDriver X-Driver X Driver
Product Line
Andover Continuum
Environment
2nd Generation Controllers with X Driver Port enabled
NC2, NCII, Netcontroller 2 CX9680
bCX1, bCX9640 bCX4040 not bCX4000
ACX57xx ACX5720 ACX5740
CX9702 - No XDriver Support
X-Drivers
Cause
If the NC2 controller required has non standard XDriver requirement, then a standard unit must be ordered, then later upgraded
Resolution
- NC2 (NCII, NetController 2, CX9680)
This unit is only available with XDriver enabled on Comm1 (as an option). If other comms ports are required to have XDriver support then this can be ordered after the NC2 is received by ordering the upgrade (you need the serial number before the upgrade order can be processed) via your normal order entry facility.
Option tab - example NC2
Xdriver Comm1 : 00000009 (0000) (XDriver enable and but not loaded)
Xdriver Comm2 : 00000000 (0000) (XDriver not enabled)
Xdriver Comm3 : 00000000 (0000) (XDriver not enabled)
Xdriver Comm4 : 00000000 (0000) (XDriver not enabled)
Only the NC2-F (fitted with FTT10 Lon IO option) can support the Echelon XDriver, this is enabled via the Web interface and loaded on to Comm16 in the usual way. If this Comm Port is used for an XDriver, then no IO can be connected to the NC. (This is a no cost option and does not require an upgrade) - bCX bCX9640 bCX4040 - NOT bCX4000
The bCX has two comms ports, the XDriver functions can be enabled on none, either or both at the time of ordering (add X1, X2 or X12)
Option tab - example bCX
Xdrvr Comm1:00000009 (DF23) (XDriver enable and loaded)
Xdrvr Comm2:00000000 (0000) (XDriver not enabled) - ACX ACX5720 ACX5740
The ACX57x0 has a single comm port, the XDriver functions can be enabled at the time of ordering (see the
Option tab - example ACX57
Xdriver Comm1 : 00000009 (0000) (XDriver enable and but not loaded)
NOTES
- 00000000=XDriver not enabled, 00000001=CommPort only, 00000009=CommPort & Ethernet enable, 00000011=CommPort & Access API enable (Schlage, Assa Abloy etc)
- The four digit number in bracket shows which Xdriver is load and corresponds to "Xdriver valid" at the bottom of the xdriver.xdr file.
- If Ethernet support is required on the port then this should be requested at the time of ordering.
- XDrivers like Modbus TCP/IP and Bacnet IP are loaded on to a comms port but communicate via the Ethernet port, therefore the XDriver Ethernet support needs to be enabled for these XDrivers to operate.
- The XDrivers and hardware update forms are available for download: For orders submitted through Sweden | For orders submitted through the U.S.
- If an Xdriver requires removing, then go offline, select the comm port, change to Autoset, return online then reload the controller
- Other upgraded to controllers, eg. node count upgrade is dealt with in a similar way. (Order upgrade, apply upgrade file using "OS Update")
- 2018 Offer optimising see Product Announcements, means that controllers are no longer available with XDrivers enabled, therefore the controller must be purchased, then upgraded.
