Building Automation Knowledge Base

Issue The error "Security error: security logon rejected" is received when accessing schedules in webclient Environment webClient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause An "&" (ampersand) that is used in a logon name or password  or another object will cause problems with webClient Resolution Do not use the ampersand, change the object name or username to use a different character.

Issue Can the Continuum Software be downloaded from the web, or ordered on CD? Product Line Andover Continuum Environment Continuum Cyberstation software Cause Download of Continuum Cyberstation software Resolution The Continuum Cyberstation software is available for download from The Exchange Download Center. The link below will direct you to the Cyberstation software. CyberStation Software If specific older versions of software are required see Older CyberStation versions not found on the Extranet (Exchange Online). If a customer specifically requests the software on a CD, then these can be ordered through the regular Order Entry channel specifying the version required.

Issue Using a PE program to try and perform a readproperty on a 3rd party bacnet controller point Environment CX 9680 3rd party Bacnet controller Cause CX 9680 does not communicate with the Bacnet Protocol unless there is an Xdriver enabled and configured on the CX9680 Resolution There are 3 solutions to this issue. Either purchase an Xdriver for bacnet communications to communicate to the 3rd party IP Bacnet Device Install a BCX4040 on the site to handle the Bacnet communications. With this option you'll have much more flexibility to expand and add Bacnet capability in the future. Use a workstation program to handle the readproperty from the 3rd party bacnet device. This will work but if the workstation is shut down or the workstation has issues the communications to the 3rd party device will stop working.

Issue Need to show the name of a person triggering invalid attempt alarm at a door in the alarm's feedback message. Environment CyberStation CX9702 CX9900 CX9680 ACX5720 ACX5740 ACX701 ACX781 Cause Alarm engine does not provide functionality natively to display personnel name on invalid attempt at a door, Plain English program must be used. Resolution The basic idea is to set the door’s description to the value of the door’s LastInvalidEntry (or LastInvalidExit) attribute, and use the wild cards %N and %D to embed the Door’s name and LastInvalidEntry (or LastInvalidExit) into the alarm’s feedback messages. Since the controller is unable to resolve the path to the personnel object pointed to by lastInvalidEntry/LastInvalidExit a CyberStation program is needed. Also, because the InvalidAttempt flag of the door only persists for one scan it is necessary to latch its value into a numeric point. In the controller write a looping program to latch the value of the door’s InvalidAttempt flag. CONTROLLER PROGRAM 1:   If Vault_Door InvalidAttempt then     VaultDoorInvalid = 1         <---VaultDoorInvalid is a numeric point in the controller     Goto 2   Endif  2:   If VaultDoorInvalid = 0 then Goto 1 CYBERSTATION PROGRAM  Write a program in CyberStation to monitor VaultDoorInvalid and set the door’s description to LastInvalidEntry   WaitForInvalid:   If LocalNetwork\ACX2.13\VaultDoorInvalid then     Print LocalNetwork\ACX2.13\Vault_Door LastInvalidEntry to STR1     Goto SetDrDescription   Endif  SetDrDescription:   LocalNetwork\ACX2.13\Vault_Door Description = STR1  <--- STR1 is a String object in CyberStation   Goto ResetFlag  ResetFlag:     LocalNetwork\ACX2.13\VaultDoorInvalid = 0    If LocalNetwork\ACX2.13\VaultDoorInvalid = 0 then Goto WaitForInvalid  ALARM ENROLLMENT  Lastly, create an expression AlarmEnrollment , set it to             Description <> “” And attach it to the door.  When an invalid attempt is detected the alarm stays ON until the door object is edited (from the alarm view itself) and the description cleared.

Issue Which Continuum controllers support RAS via modem connection? Environment CyberStation CX9900 CX9940 CX9680 CX9640 CX9200 CX9924 Cause Not all Continuum controllers support modem connection. Resolution The access point for a remote site is the controller that is configured with a modem that is used to establish a communication link with the remote CyberStation. Only the following Continuum controllers can act as access points for remote sites. CX9900, CX9940, CX9680, CX9640, CX9200, CX9924. Note that other controllers communicating with the access point controller via ethernet can fully participate in RAS communications as the access point controller will route messages to/from its peers.

Issue Is there a way to stop the beginning zeros from being truncated off  in a card number? 00123  becoming 123 when saved and refreshed. Environment Continuum 1.93 PIM FIPs. Wiegand 26 Cause Exporting and Importing card data into 3rd. Party system. Resolution The beginning zeros automatically get truncated off in a card number They get removed in all the user fields in Continuum. This is by design and cannot be altered

Issue How do I add nodes to my controller? Environment Netcontroller CX99xx Netcontroller II ACX57xx BCX Series Cause Adding more nodes to a controller Resolution First you will need to contact upgrades department to obtain a node upgrade flash file for your controller.  Upgrades can be reached at upgrades.continuum@schneider-electric.com Once you have received your flash file you will being the process of updating your OS. 1.  Rick Click and Edit the controller 2.  Click update OS 3.  Path to file and select file 4.  Verify controller updated 5.  Reload Controller

Issue Wants to know the correct termination specification for each different I/O modules and different IOU networks. Environment NC1 - CX9900, CX9940 NC2 - CX9680 IOU modules Cause Different type of terminations are required for different type of I/O modules (ACC-LON and FTT-10A) and different topologies (Bus topology, Free topology and Doubly terminated Bus topology). Resolution ACC-LON  requires two 120 ohm resistors at both ends of the bus. One between pin 1&2 of the I/O module on the NetController side and the other one between pin 1&2 of the I/O module at the last node of the bus. FTT-10A Free topology requires one 52.3 ohm resistor between pin 1&2 at any place on the bus. FTT-10A Doubly terminated bus topology requires two 105 ohm resistors.  One between pin 1&2 of the I/O module on the NetController side and the other one between pin 1&2 of the I/O module at the last node of the bus.

Issue Creating a bacnet schedule to control a 3rd party device generates the error:  “Bacnet operation rejected generated in response to a confirmed request apdu in which the service choice field specifies an unknown or unsupported service”  Environment Continuum 3rd party bacnet device Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The bacnet error occurs when dynamic creating of schedules is not supported in the 3rd party device and the packet gets rejected. Resolution An ethereal capture from the Cyberstation will show the packet getting rejected. A work around for this is to use a BCX to create the schedule and communicate to the 3rd party device.

Issue Is there an Xdriver for the purpose of using comm1 as an BACnet over MSTP for this netcontroller BCX 9640 and still use comm2 as Infinet?   Environment BCX 4040 BCX 9640 Cause Supported feature to use Bacnet MSTP on a BCX 9640 on Comm1 via x-driver Resolution There is no x-driver to allow MSTP Bacnet communications on a BCX 9640 NOTE: Suggestion would be to use a BCX 4040 and Comm2 for MSTP Bacnet Communications.

Issue Does Modbus TCP/IP xDriver opens socket connection per each device or the gateway of the devices? Environment NetController - CX9900, CX9940, CX9680, bCX9640. BACnet Controller - bCX4040. Cause As some Modbus TCP/IP gateways have the limitation of maximum TCP/IP connections, if Modbus TCP/IP xDriver opens a socket per modbus device and keeps it open, the gateway might run into a problem due to the limited number of socket connections. Resolution The Modbus TCP/IP xDriver opens one(1) socket connection per server not device. So for a gateway that has a number of devices, the Modbus TCP/IP xDriver only uses one(1) socket connection.

Issue Reloading controller and receiving "Invalid Handle ID" error Environment Continuum Cyberstation BCX 4040 B3 controllers CX controllers i2 controllers Cause Most common cause is points already in the controller and/or bring controller from a different site/location and trying to reload while controller already has points in it. Resolution Reset controller Reload controller Backup controller flash memory

Issue CX9702:  appears to be powered up but showing offline in infinity programming Environment Continuum Cyberstation CX 9702 Cause Cannot communicate with 9702. Resolution Burn marks on then controller indicating overvoltage Send to repair.

Issue Receiving "Invalid Object context" error when saving a program Environment BCX 4040 B3 8xx -V Plain English Cause Receiving "Invalid Object context" error when saving a program Resolution Update B3 controllers with latest firmware version for Continuum Cyberstation version

Issue Cannot find third party bacnet gateway devices Environment BCX 3rd party bacnet gateway devices Cause Configuration issue will not allow proper communications on Bacnet protocol Resolution The third party Bacnet Gateway devices were setup as foreign device registration and not properly configured. Foreign Device registration is not needed on a single subnet bacnet setup. Disabled foreign device registration and Bacnet communications is now properly established. Also check that the correct subnet mask has been entered for the network

Issue I/O modules that cannot be successfully commissioned Is there a procedure to test these or any resets or checks to do before sending the IOU back for repairs?   Environment CX96xx I/O Module Cause Unable to commission I/O module. Resolution FLASHING STATUS LIGHT This indicates that the Neuron chip in the module has undergone a partial commissioning and that it has calculated an invalid checksum in its flash chip.  This could happen due to communications problems on the IOU bus, either during module commissioning or during a NetController reload (which also de-commissions and re-commissions the modules). If you are experiencing this problem, do not return the modules to the Repair department. We have added a routine in the NetController to automatically detect and correct this condition. You can download the new NetController flash file and upgrade your NetController in the field. This will automatically correct any IOU modules that have this condition. To avoid this issue, you should also verify that your controllers and IOU modules are installed per the installation instructions, paying careful attention to bus topology, bus terminations, network cable, and grounding. Please note when adding multiple IOU modules that exhibit the behavior described above, to add and commission the modules onto the system one at a time.  SOLID STATUS LIGHT This indicates that the IOU module application flash is not present in the module. This could happen either due to the conditions described above or by a failure during the flash upgrade process.  These modules can be corrected in the field using one of the manual procedures described below: If the module was already commissioned on the NetController If the NetController has the module information in its memory, you should be able to flash the IOU firmware by editing the IOU object and selecting the “Update IOU” button. Then select the correct flash file for that module. If the module will not upgrade Connect the faulty module to a CX9xxx. With CyberStation online, create an IOU module.  Specify IOU number but not module ID. Save and close  the editor disregarding the error message. Set CyberStation offline. Edit the IOU module object inserting the module ID. Save and close the editor. Set CyberStation back online. Open the IOU module object, re-insert the module ID, select the Uprev button, and select a .upd file. When the uprev completes, commission the module. TAC product development has made a correction to this issue Click Here  in firmware version 1.530023. You should also read Technical Bulletin #1041 to make sure that you are using the correct IOU file.  

Issue How to enable Xdriver on a CX9200 Environment Continuum Cyberstation CX9200 Cause When Infinity chips are installed on a CX9200 controller, it will not accept the XDriver upgrade cookie.  Attempting to change the commport configuration to Xdriver will return an error "Invalid Mode." Continuum chips are needed to properly apply the cookie. The controller can then be returned to Infinity by replacing the Continuum chip set. The Xdriver can then be used. Most commonly, the issue is due to the Infinity chip set not allowing the XDriver upgrade, but the chip set is not properly identified before the Xdriver upgrade is attempted. Resolution Enable an XDriver on an Infinity CX9200 must be accomplished from a dumb terminal connection: Log on to the controller via Hyperterminal Load -o -m with the XDriver cookie file provided by the repair department. Go to the Hyperterminal Transfer pull down menu and select "Send to Text File" and select the file as provided by Repair. Hit Enter to start the transfer. Send to database from the Continuum Explorer and only select the specific CX9200 controller. When the upgrade has completed, power down the controller, then repower the controller. Verify that the ACCSetEEVal string point in the CX9200 has been created. Check the Options tab of the Continuum controller editor and verify that the commport has been properly enabled for XDriver.

Issue Does Web Pinpoint user ActiveX Controls? Environment WebClient Cause On some projects the customer IT department will require that you let them know when Active X controls are being used over the internet. Resolution WebClient Pinpoint uses no ActiveX controls.

Issue Declaration of Conformity Environment Continuum hardware Declaration of Conformity Cause Location of Declaration of Conformity Resolution Regulatory Compliance on The Exchange

Issue Under certain unknown scenario reloading a b3 device may result in CyberStation hanging when setting the attributes of the first object to be reloaded. A buffer overrun error may also appear. Environment CyberStation bCX4040 b3 Cause Invalid BACnet device configuration in database. Resolution In CyberStation go to the BACnet Devices folder and delete the BACnet device for the b3. Perform a Find New BACnet Devices. Send the BACnet device for the b3 to the database The reload operation should now complete successfully.