Building Automation Knowledge Base

Issue Can I use a RS-232 converter to RS-485 Environment Modbus Cause Using a converter for RS-232 to RS-485 Resolution RS-232 converters to RS-485 have been reported to work in some cases, we do not support converting RS-232 to RS-485. There are a lot of different configurations that can be different from vendor to vendor that can cause communications issues. It is suggested to use a commport that can handle the particular protocol that is needed instead of using a converter to change the protocol. Another option is to use our own Infilink200 or B-Link as an RS-232 to RS-485 converter for use on Comm1 when loaded with an Modbus RTU Xdriver or similar RS-485 protocol.

Issue An ACX5740/CX9680 does not provide access events to Cyberstation 1.81. Environment Cyberstation 1.81 or earlier version SQL Server 2005  Cause The ACX 5740/CX9680 was running version 1.1xxxxx/2.1xxxxx firmware. This version of firmware is incompatible with Cyberstation versions 1.81 and earlier. Resolution The site was offered the option of upgrading the version of Cyberstation to 1.9x, or down-reving the ACX 5740/CX9680 to version 1.0xxxxx/2.0xxxxx. Flash down-reving the controller was chosen and did resolve the access event delivery issue.

Issue ACCTrace and Windows error log show multiple DBFaultDetection, SQLSTATE ERROR CODE:  S1000, ERROR MESSAGE:  [Microsoft][ODBC SQL Server Driver][SQL Server]Warning: Fatal error 823 occurred Environment CyberStation Cause Device (disk) error. Resolution Recommended course of action from Microsoft: Error 823 Severity Level 24 Message Text I/O error %ls detected during %S_MSG of %S_BUF. Explanation Microsoft SQL Server encountered an I/O error on a read or write request made to a device. This error usually indicates disk problems. The parameters in the error message refer to internal structures and don't often help determine which device is involved. However, additional kernel messages in the error log, recorded before error 823, should indicate which device is involved. Action Check the accessibility and condition of the device in question. After you have identified and corrected the problem, execute DBCC CHECKDB to ensure that no other damage was caused by the bad device. For information about using DBCC CHECKDB, see "DBCC CHECKDB" in Microsoft SQL Server Transact-SQL and Utilities Reference. Important If executing DBCC CHECKDB with one of the repair clauses does not correct the index problem or if you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider. In addition, run hardware diagnostics and correct any problems

Issue Cannot connect to video server when creating a VideoServer object in Continuum and Test Connection is selected. Product Line Andover Continuum, Pelco Environment Continuum DSConnex Digital Sentry Cause Patch not installed for DSConneX versions 4.3 and 7.x not working with Andover Continuum 1.91 or 1.92 or LAN connection problems Resolution Install v1.91 DSConneX Video Patch hotfix for issue with DSConneX versions 4.3 and 7.x not working with Andover Continuum 1.91. For 1.92 these files are included, so if the error is still occurring, then there are LAN connection issues.

Issue I have a site that has two workstations. The customer wants to use Video Monitor to display alarm video on one workstation. The customer wants to use Video Layouts to display alarm video on the other workstation. The customer does not want Video Layouts to display alarm video on the workstation that uses Video Monitor. Environment Continuum Cyberstation VideoMonitor VideoLayout Cause Each workstation has to display alarm video on one specific video display application.  On some workstations video must only be displayed by VideoLayout. On other workstations  video must only be displayed by VideoMonitor. Resolution VideoMonitor can be disabled on a per workstation basis by editing the workstation preferences in the device editor. VideoLayout display cannot be suppressed on a per workstation basis. The work around for this is to configure separate event notifications workstations that will display point alarm video using VideoLayout on its recipient workstations, and the other event notification that will not display video on its recipient workstation.

Issue Door unlock schedule configure for 8:00 AM to 4:00 PM active so doors unlock at 8AM and relock at 4PM. Occasionally, there is a need to additionally unlock the door from 6:00 PM to 7:00 PM. Created an exception event on the specific day for 6PM to 7PM but this causes the doors to lock in the morning (8AM to 4PM) Environment CyberStation All CXs, i2s and b3s Cause An exception event added to a day overwrites the whole day so on a regular day with event active 8:00 AM to 4:00 PM if an exception event active 6:00 PM to 7:00 PM is added the resultant effective event for the whole day is active at 6PM and inactive at 7PM. This will cause the door to remain locked until 6PM. Resolution The proper way to have the door unlock from 8AM to 4PM and then again from 6PM to 7PM on an exception basis is to add an exception event to the day configured for 8AM to 4PM and 6PM to 7PM. In other words, the exception has to include the events for the whole day as it overrides ALL normal events for the day.

Issue An attempt to assign an IO channel results is Infinity Controller Error - Invalid Channel Number. Environment CyberStation All CXs, I2s and B3s Cause The OMS database in the controller does not match the sql database seen from CyberStation. This can occur if the controller has re-started with a stale oms database in flash. Resolution Perform a Send to Controller from CyberStation to sync up the database in the controller, once all is working and the configuration is as desired perform a backup to flash of the controller.

Issue Although all the cameras connected to Pelco Endura SM5000 system manager can be found by the video server, when using "Video Administrator" to try to assign alarm points to cameras, sometimes cameras cannot display properly,  such as "1-192.168.5.10"(SM5000 IP Address),  or return "not found' and get an error message such as "Camera or Video server maybe offline....". Environment Windows XP SP3 Cyberstation 1.92, Cyberstation 1.93 Pelco Endura SM5000 system manager Cause It is an Endura configuration problem. A camera should be added into a group. In and Endura system, there is a default group, if no additional group is created. Normally, cameras should be added into this default group. However, in some situation, some cameras will not be automatically added into that default group. In this situation, those cameras do not belong to any group; therefore, those cameras will not display properly in the camera's field drop down menu and cannot be selected. Resolution Create one or more groups in Endura system. Add the desired cameras into the groups created in step 1. Learn cameras again from the video server. Reopen the video administrator and add points to cameras.

Issue xP expansion module is not being recognized. Environment BCX 9640 ACX 57xx xp DI8 Cause Controller that the module was added to needs to be cold started before it will recognize the module Resolution Adding xP expansion modules to either an ACX57xx or a BCX9640 states in the module reference guide that the modules can be added to controllers while the power is applied EXCEPT for the ACX57xx or the BCX96xx models. Power down the ACX57xx or the BCX96xx Add module to the ACX57xx or the BCX96xx Re-apply power to the controller Green CPU light on module should blink, if not follow next step. Re-load of controller.

Issue Door value set to UNLOCKED from the editor but the door relocks when a card (valid or invalid) is presented at the door reader. Environment CyberStation CX9680 ACX5740/20 CX9702 CX9900 ACX701 ACX781 Cause Door value is reset by the access engine every time the door processes a validation attempt. Resolution To keep a door unlocked use one of the following door unlock strategies: 1. PermanentUnlock attribute 2. TimedUnlock attribute 3. Door unlock schedule

Issue Following a loss of power the CX9640 Controller shows no activity on comm2  even though Infinet devices are connected to the field bus. The CX9640 itself shows online but opening the comport shows the mode as Autoset. Environment bCX9640 Other controllers that support Infinet field bus. CX9900 CX9680 ACX5740/20 Cause The controller has lost its OMS database and the comport has default to Autoset. Resolution Reload the controller from CyberStation,

Issue Miscellaneous points that are controlled via Plain English programs are not following the program's command. Environment Cyberstation, All Versions. All BACnet type controllers with Plain English Code Cause Default BACnet Command Priorities must be modified based on the Continuum system configuration and integration with other 3rd Party BACnet devices. Example: By default, Graphics have a Command Priority of "Manual Operator" (8) and Plain English has a default Command Priority of (10). If the system is left with these defaults, then an operator who modifies, adjusts or toggles a point value via a graphic will in turn set that value with a command priority of 8. Since PE has a command priority of 10, the operator command remain in effect until either it is relinquished or a similar or higher command priority is sent. In this example, an operator set a point that is controlled via Plain English was toggled (not overridden) from On to Off. The Program wanted it ON. The point will stay in the Off position until either the operator(s) relinquish the command or another command of the same command priority sends a value. Resolution Open the BACnet preferences at the Workstation. Set all the Command priorities to 10. This will allow Plain English programs, etc to retake control of point affected but changes made via graphics or other editing methods. If the points however are actually override, you must release the override and relinquish the command. See BACnet Documentation: BACnet For Continuum Users (loaded on all Cyberstations) Continuum BACnet Engineering

Issue Workstation does not delete from database correctly Object does not delete from database correctly Environment Continuum 1.81 only seen in this version on XP Cause When deleting the workstation using Continuum explorer only the objects within the workstation get deleted, the workstation does not. Resolution Run Continuum Analyzer when you see a failed item, run the "clean". (Always backup the database before using the "clean" command)

Issue Some X Drivers on the Third Party Interface datasheet are classed as 1st Generation and others are 2nd Generation, which drivers should I use? Product Line Andover Continuum Environment All X Drivers Any controller with XDrivers enabled on a Comm port. Cause Sometimes the incorrect file is being used on a controller and this will stop the X Driver from working correctly. Resolution You can only use a 1st Generation X Driver on a 1st Generation controller and a 2nd Generation X Driver on a 2nd generation controller. - 1st Generation controllers are: CX9200, CX9400, CX9900, CX9940, CMX9924 - 2nd Generation controllers are: Netcontroller II (CX9680), bCX1 (4040 or 9640), ACX II (5740, 5720)   Download the Third Party Interface datasheet Note: Not all X Drivers are available for both generations of controllers, consult the above datasheet for availability.

Issue Personnel objects named VisitorX. When the card is issued the name is changed from visitorX to the name of the person the card is issued to. Once the card is returned the name is changed back to visitorX until ready to be reissued. When a list of Access Events is shown the events only show the current name associated with the person and all previous names are lost from the system Environment CyberStation Cause Function as designed. Resolution Create a Custom Attribute for personnel objects (i.e. CardHolderName) and use it to store the actual name of the person holding the Visitor card.

Issue In a Graphic panel configured with a background image and several controls including a combo box control when the list is exposed (pulled down) it snaps back closed before a selection can be made. Environment CyberStation Cause Interaction between combo box control and other graphic object components such as back ground image can cause the combo box control to behave inappropriately. For example, an overlap of the combo box control with other controls and/or images in the canvas may cause the issue. Resolution Switch graphic to design mode and re-arrange controls and images until combo box works as expected.

Issue I2867 inputs all read 1000 Degrees. Change out of controller does not remedy the issue. Environment All Infinet/MSTP controllers Cause Field controllers have an electrical range that they will properly operate. Typically this is +10% and -15% of the required power as described in the installation manual. If the power supplied to the unit is below this threshold, the CPU and power LEDs may appear normal, however the inputs and outputs will not function properly or at all. They are out of range. This situation must be remedied or damage can also occur. One way this can occur is if a properly grounded secondary transformer is not supplied. Supplying power from a piece of equipment that uses a step down 220/208-24 etc power supply can cause electrical issues should that equipment experience electrical problems. Resolution Supply proper, grounded 24Vac power to the controllers. Always check the power with a multi-meter and verify grounding.

Issue How does CyberStation determine which printer to send alarms to when EventNotification is configured to print the alarm. Environment CyberStation Cause Question on Alarm printing configuration. Resolution When an alarm is configured to be sent to a printer, if no printer has been specified in the preferences of the Workstation receiving the alarm then the default printer configured at the PC is used. To use a different printer open the CyberStation object from the Continuum Explorer at the workstation receiving the alarm and enter the full path to the printer in the “Path to the Alarm Printer” field using the format  \\Server-Name\Printer-Name Example: \\ServerBoston-001\PR-HP3800N When CyberStation receives an alarm, if the EventNotification specifies that the alarm is to be printed, CyberStation will use the named printer instead of the default printer. In the EventNotification, make sure the "Print Alarm" option is ticked in the Actions tab. On the Delivery tab, check that the WS is configured as "Primary Print". Test your alarm against the Microsoft XPS printer by selecting this as your default (right-click on the printer and select "set as default printer")and then triggering an alarm.

Issue How to modify or add an area or areas to selected personnel How to modify personnel (or other) attributes Environment Cyberstation Personnel Listview Attributes Editlock lock locked Cause Need to add or delete areas from multiple personnel Need to change attributes Resolution Create a listview of personnel, with a filter (for example, by department) to show only the personnel to be modified. Select the personnel to be modified. Right click on the selected Personnel objects and select "Add Areas" or "Remove Area" from the context menu. In the ‘Area’ window you can select one or more areas to assign. Other attributes can be modified in the same manner EG. if many objects get edit locked, select all in the listview, then right click, set attribute, Edit lock to false.

Issue The Modbus IP X Driver can operate in 2 modes Client & Server, can it poll multiple servers in "Client mode", or serve to multiple clients in "Server mode"? Environment Modbus TCP/IP X Driver XDriver IP X-Driver, X Driver, Client Server Cause Clarification required on the functionality of Modbus IP interfaces. Resolution A Continuum controller can only support 1 IP level X Driver. The Modbus IP X Driver can be configured in Client or Server mode but not both (that would require 2 Controllers)  In Server mode the Modbus IP X Driver can serve data out to multiple clients on the same network. In Client mode the Continuum Modbus IP X Driver can co-exist with another IP Modbus client on the same network/ device. It can also poll multiple servers. When polling a 3rd party Modbus IP Server that can also be polled from a second Modbus IP Client, you will need to determine from the supplier if it supports multiple simultaneous sessions. In both Client and Server configurations the number of different sockets (different IP addresses it can talk to) is dependent on the controller used. A bCX1 has a total of 128 IP sockets, but a number of these are used by the regular workstation comms, others can be used for add on options like SNMP alarming, so I would not recommend on communicating with more than around 80 different devices from 1 controller. Currently the NCII only has around 30 available sockets (although this is planned to be increased in a future firmware revision).