Building Automation Knowledge Base

Issue Where are release notes for Continuum Bacnet controllers located? Environment Continuum Bacnet BCX4040 B3-865-V B3-866-V Cause Bacnet firmware release notes location Resolution Release notes for Continuum Bacnet controllers are located on Exchange Online. Download Bacnet Firmware Release Notes

Issue System Diagnostics, Upload Files is always grayed out . Environment Sigma 4.05 all releases. Sigma 4.06 all releases. Cause Upload Files is always grayed out . Resolution Warning: The files that will be uploaded will overwrite the existing files in the database. It will be good practice to copy the existing files to another location before using Transfer File. Go to System Diagnostics. Go to Configuration > User Settings, tick the Advanced Menu box. Go to Options > Transfer File. Note: Upload Files is only available for IC LON controllers for uploading Network Variables (NVconfig.bin). 

Issue How to stop Controller Offline alarms from being generated if a controller is going to be offline for a significant period of time. This can be for planned maintenance or scheduled network outages on the site. Environment Cyberstation alarms, All versions. Cause Building maintainers or operators may want to disable controller offline alarms, but as the Offline alarm detection is built into the product there are no Alarm Enrollments to disable individual controllers. Resolution You can not disable the inbuilt Controller offline alarms from one controller or a network but still receive them from others. Use the Delivery tab to define which workstations you require the Controller offline alarms to go to and removing all recipients will mean no alarms are generated. If a controller is known to be offline and will remain offline for some time, then edit the controller and put the controller "Out of service" and clear out its IP address (0:0:0:0). This will stop alarms coming from this controller and any unwanted network traffic from being sent to it.  

Issue Cannot get a new B3-866-v controller to come online Environment Continuum BACNet MSTP device Cause Using a 250 Ohm terminator on the MSTP bus Resolution Replace 250 Ohm terminator with the correct 120 Ohm terminator on each end of the bus If the b3 will still not come online and other controllers are, disconnect the mstp bus and wait 10 seconds and reconnect.

Issue When trying to connect to a RAS Dialup the system gets to the Authentication Notify stage and then disconnects Environment Windows XP Remote dialup RAS CyberStation, modem Cause The baud rate of the modem in the PC does not match the baud rate of the controller's commport Resolution Hard set the baud rate on the modem on the CyberStation to match the controller's commport

Issue When trying to access PinPoint graphics across the LAN or on a network share you get a Pin file cannot be found error Environment CyberStation Windows XP Graphics PinPoint Cause Problem with the Windows DNS server.  Could not browse to the remote PIN file directory through Windows by computer name. Resolution Hardcode the IP address in the file path in the PinPoint Options Have the IT group determine what the problem is with the DNS server Edit the Hosts file in the Windows\System32\drivers\Etc directory and add the computer name and IP address to the file.

Issue Temperature inputs not reading the correct values Environment Cyberstation IOUs Controller Cause Bad input Bad controller Bad sensor Resolution Replace sensor with a 10k ohm resistor.  Temperature input should read roughly 77°F or 25°C.  If it does then the problem is with the sensor.  If it does not then the problem is either with the input board or that particular input itself.

Issue When a graphic is selected from the Xenta 555 menu structure,  the graphic opens, but only the close (X) button is shown. Environment Xenta 555 Micronet Cause The Java TM Runtime version is not correct. Resolution Update Java TM Runtime to the latest version. This can be downloaded from here.

Issue Cannot communicate to third party devices using the MODBus TCP XDriver or MODBus RTU XDriver. Environment CyberStation ACX5740 XDriver MODBus TCP Cause The MODBus TCP configuration point was not created Resolution Create the MODbus TCP configuration point following the guidelines in section 5.1.3 of the MODBus TCP guide

Issue Should the Touchscreen "Time Master" setting still be set, when the Touchscreen is connected to a Xenta 555? Environment Micronet Xenta 555 Cause The Touchscreen would normally be configured as a "Time Master" when not connected to a Xenta 555. Resolution The functionality remains the same, the Touchscreen is set as a "Time Master" and will broadcast the time every 10 minutes, by default.

Issue How to convert a B4-920 to a BCX4040 Environment BACnet B4-920 BCX4040 CyberStation Cause How to convert a B4-920 to a BCX4040 Resolution ASCII export the B4-920 then modify the dump file to change from the B4-920 to the BCX4040.  Delete the B4920 from both the Continuum view and the BACnet view in Continuum Explorer. Import the converted dump file into the system.   Reload the new BCX and all it's child objects.  Execute a Find New BACnet Device to pull all the devices back into the BACnet view.  Execute a Send to DB on the BACnet side to pull all the objects in. NOTE:   Another option if you are running version 1.90 CyberStation or greater is to change the model number through the controller editor in Continuum Explorer.

Issue What does error 1808 mean in a controller error log Environment Controller Continuum Cause The controller tried talking to another controller but could not because the other controller was offline. Resolution Determine why the controller is offline and the error will go away

Issue Continuum Add-On Software products and support contacts Environment Continuum Continuum Reports Suite Continuum Archiver/Archivers Continuum Elevator Control Continuum Bioscrypt Integration Video Monitor For Third Party Video Systems Continuum Guard Tour Center of Excellence (COE) Cause Continuum Add-On Software products and support contacts information. Resolution Please forward Continuum Add-on Software support requests to COE.Support@buildings.schneider-electric.com The Reports Suite software can be downloaded here: https://ecobuilding.schneider-electric.com/search?documentUUID=e040ce9b-7114-4cbc-b9cc-bcde73a6d64e&title=Continuum%20Reports%20for%20CyberStation%20v1.81%20and%20v1.82%20Add-on%20Software Internal note: In bFO the Care Team to which PSS will De-Escalate case is the NAM_BLD_COE_ADV Care Team.

Issue Will a Power Supply PS 120/240 AC 85 work with a Netcontroller 1? Environment CX 9900 CX 9901 CX 9940 Cause Verifying power supply compatibility Resolution The PS120/240 AC 85 model power supply will work with CX 99xx model controllers.

Issue Is IPv6 supported with Continuum Netcontrollers? Environment BCX 4040 BCX 9640 9680 ACX57xx Cause IPv6 compatibility with Continuum Netcontrollers Resolution As of today, 3/21/2013, Continuum controllers do not support IPv6. There are no plans at this time to implement IPv6 into Continuum controllers.

Issue The Network Service account doesn't show when searching by using the Find button in webclient dcom configuration. dcomcnfg is used to set permissions for the network service for components in webclient and by default the wrong context may be selected. Environment Webclient 1.8x Webclient 1.9x Windows Server 2003 Windows Server 2008 Cause When using dcomcnfg (DCOM configuration) the context of the search for the user account is not correct, so the account isn't found when using the Find button. Resolution   Start> Run>dcomcnfg Select one of the 4 components to configure Select the security tab Select the Customize radio button and select Edit In the Launch Permissions dialog select the ‘Add’ button In the Select Users, Computer or Groups dialog select LOCATION Select the PC name of the webclient PC and click OK Click on Advanced and select Network Service and add Local Launch and local activation Repeat this for the other 3 components.

Issue When executing a Find New BACnet Device a third party controller (Alerton) would not come into the system. Product Line Andover Continuum Environment CyberStation BACnet Alerton Cause The third party device did not have a name assigned to it. Duplicate device id on the network. Resolution Check with third party vendor to determine how to assign a name to the device When devices from different vendors are used it is possible to have device id duplication which will prevent one or more of the devices to be found. If device id duplication is detected, Continuum will indicate the condition in the error log. To solve the problem you must change the device id of one of the devices so that they all have unique device ids. You can determine which devices are duplicating by running acctrace and a wireshark while doing a Find New Bacnet and then looking in the database for these objects. If you cannot interpret what is found in those traces, send them to PSS for analysis.

Issue What does the error 01/30/2011 01:01:57.00 0x00004418       0x00002100       0x021046e2       0x00080003       0x00000030          DEVICE_ERR_NODATA_I2C      mean in a controller error log? Environment CyberStation Controller Expansion module Cause The error code means that the 9640 can’t communicate with the expansion I/O modules or with the RealTimeClock. Resolution Check communications to expansion modules Verify correct operation of the system time in the controller. Replace controller if needed

Issue Where to send broken/mal-function I/net hardware RMA Environment I/NET  Hardware Cause Can't find where to return a broken I/Net product Resolution Västerhaninge handles repairs, advance replacement and repurchase. Repair and advance replacements shall be added into their warranty claim system. http://warranty.tac.com   NOTE: The warranty starts from the day of purchase

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 2 nd 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.