Issue Mapping a 3rd party bacnet point to a numeric gives 'object attribute not available' Environment Continuum BCX Viconics Stat Cause The path to the object couldn't be found Resolution Deleted the bacnet network Deleted the BCX Find new bacnet Able to map the 3rd party object to the numeric using ReadProperty with no error Note: Mapping a 2nd Viconic stat to the original BCX gave the same error, but mapping either stat to another BCX on the same subnet worked without error prior to the delete/Find.

Issue Trend chart report does not show Trend Chart data Environment CyberStation Cause Maximum number of values in the report not properly set Resolution Make sure to set the 'Maximum number of values' property to include all the data in the log being plotted.

Issue Can 2 comm ports be enabled when using the RTU Xdriver? Product Line Andover Continuum Environment Continuum 9680 99xx 9640 4040 Xdriver Modbus RTU Cause At times it is necessary to have multiple ports enabled for Xdrivers Resolution The ability to enable 2 comm ports using Xdrivers can be done, but is not recommended by the Xdriver developers or supported by PSS. The RTU Xdriver is poll on demand. This type of driver can request a lot of data and starve the CPU on the controller which then makes the polling irregular. If 2 ports are being used then there are typically more devices being added and therefore more points increasing the requests and demand on the controller's CPU. Use one program to control the polling on both ports. Two programs attempting to control the polling asynchronously will cause communication issues.

Issue What is the acceptable range of tolerance for resistance on a supervisory input. Environment i1 controllers i2 controllers b3 controllers I/O modules Cause Doors are being retrofitted, and the resistors that are installed are not 10K ohm and are inaccessible. Resolution The tolerance for the resistance on supervisory inputs is +/- 3%.

Issue Can the Anti-Passback rules be ignored for certain personnel cards? Environment Access Control: CX9702 CX9900 with AC1 modules CX9680 Netcontroller II with AC1 Modules ACX5720, ACX5740 Cause Often certain site personnel require free access around a site e.g. Security personnel or management. Resolution If Area Anti-Passback is being used then there is the “AllowEntEntEgr” attribute in the personnel object, it is named “Allow Passback Entry” in the Personnel Manager. This attribute is by default False, but can be set to True in any Personnel to ignore Area Anti-Passback rules. This attribute does not apply to Timed Anti-Passback.

Issue At times error logs are truncated from a controller Environment 9680 BCX 4040 BCX9640 ACX 57xx i2 b3 Cause There is a limited number of records that can be stored in controllers and if there have been a lot of error they will eventually get truncated. Resolution Flash memory for the controller error log is divided into 2 sections (A&B) When section A is filled with errors, section B begins to get filled Once both sections are filled, section A gets truncated and begins to fill with new records Once section A is filled, section B gets truncated and so on... There are approximately 8000-9000 records that can be stored in each section

Issue A requirement at some physical access control sites is that at the beginning of the day all access to an area/door is denied until a particular person shows up. Environment CyberStation CX9900 CX9702 CX9680 ACX5740 ACX5720 ACX781 Cause Requirements Resolution Write a PE program in the controller that disables the door at the end of the day and then uses the door's EntryLastSite and EntryLastCard to determine when the person that enables access has arrived in the morning at which point the door is enabled. Sample PE program 'Program is fallthru and triggered by the Second system variable 'Disable door at end of the day If Hour > 17 then   MainEntrance State = Disabled   Stop Endif 'Enable door when Elvis enters the building If MainEntrance State = Disabled then   If MainEntrance EntryLastSite = 123 and MainEntrance EntryLastCard = 456 then     MainEntrance State = Enabled   Endif Endif 'Keep program from getting disabled due to run time error E:   Stop   If door is a dual reader door the program can be modified to disable the door when the person leaves using door attributes ExitLastSite and ExitLastCard

Issue Using the RD and TD LEDs to help commission and Fault finding a Modbus RTU Continuum Xdriver Using the RX and TX LEDs to help commission and Fault finding a Modbus RTU AS, AS-P, AS-B Product Line Building Operation Automation Server Premium Continuum bCX4040 (BACnet) Environment Continuum Automation server Cause How to use the TD RD(TX RX) LEDs to help commission or check an installation Resolution Continuum The Comm Port LEDs on a net controller can be helpful when first setting up or fault finding an Xdriver (ModbusRTU) Every time the net controller transmits the TD LED will flash and every time another device on the bus transmits (such that the net controller can receive it) the RD LED will flash. Thus if Xdriver seems not to be working correctly this is often the first thing to check A simple check with Modbus RTU would be to stop any automatic polling on the network, then manually refresh a modbus point and watch for a single Transmit (TD) followed by a Receive (RD). SmartStruxure The Comm Port LEDs on an AS controller can be helpful when first setting up or fault finding ModbusRTU Every time the AS transmits the TX LED will flash and every time another device on the bus transmits (such that the AS can receive it) the RX LED will flash. A simple check with Modbus RTU is to create only a  single device (or inhibit polling to all but one device) and watch for a single Transmit (TX) followed by a Receive (RX). Modbus Simulation Another useful technique when commissioning or troubleshooting with Modbus is to simulation software on a PC (with RS232/485 convertor for RTU if required). A Slave device or the Master node can be simulated eg ModSim, ModScan, ModbusSlave, ModbusPoll, Mod_RSsim

Issue Continuum Database Initializer hits an error when an attempt is made to update the database. Environment Continuum Database Server Continuum Database Initialization Cause Technician is using the wrong Andover97 password. Resolution Use the current Andover97 password during the update database process.

Issue Can communicate (ping and open controller webpage) when plugged into the controller but cannot communicate from CyberStation over the site network. Environment CX, bCX, NC2, NetController, ACX2, ACX57xx  Cause Can communicate (ping and open controller webpage) when plugged into the controller but cannot communicate from CyberStation over the site network. Resolution In this case the problem was an issue with the end user's IT department. They missed one of the MAC entries in their router table causing the communication to stop at the router

Issue Need to determine which controllers have not had their battery tabs removed without going to each individual controller and removing its cover to perform a visual check. Environment Continuum Controllers bCX1 b3xxx i2xxx CX9680 CX9702 ACX57xx Cause During commissioning, battery tabs were not removed or batteries were not plugged into the PCB. There is no way to see the status of the backup battery by looking at the controller object in Continuum.  Resolution One method is to create a new object in the controller (numeric), do not save to Flash, then power cycle the controller. If the object is still in the controller after powering up (able to be opened without showing an error), then you can deduce that the battery tab has been removed and the battery is operational…if the point is not able to be viewed then the tab is still present or the battery is not holding a charge.

Issue How to implement a simple Man Trap using PE Environment CyberStation CX9900 CX9680 ACX5740/20 Cause A mantrap is an access methodology with an entry door and an exit door. One door of the mantrap can not be opened until the opposite door has been closed. Mantraps are most often used to keep non-secure areas separated from secure areas and prevent unauthorized access. Resolution 'This program implements a Man Trap that allows one person at a time in the man trap. 'Once a person is in the man trap no access is allowed until the occupant leaves the 'man trap via the REX. 'The occupant is allowed to exit at either door but once they have activated the REX 'at one door they are required to leave via that door. 'If occupant stays in the trap longer than TrapMaxOccTime and alarm can be sent via ManTrapStuck 'TrapMaxOccTime and ManTrapStuck are InfinityNumeric objects in the controller. 'Program is Looping and AutoStart TRAP_READY: ManTrap_A DisRdrKpAccess = False ManTrap_B DisRdrKpAccess = False ManTrap_A OpenOnExitReqst = True ManTrap_B OpenOnExitReqst = True If ManTrap_A ValidAccess or ManTrap_B ValidAccess then Goto TRAP_OCCUPIED TRAP_OCCUPIED: ManTrap_A DisRdrKpAccess = True ManTrap_B DisRdrKpAccess = True If ManTrap_B ExitRequest then ManTrap_A OpenOnExitReqst = False Goto WAIT_EXIT_B Endif If ManTrap_A ExitRequest then ManTrap_B OpenOnExitReqst = False Goto WAIT_EXIT_A Endif WAIT_EXIT_A: If ManTrap_A DoorSwitch = Opened then Goto TRAP_READY If TS > TrapMaxOccTime then ManTrapStuck = On WAIT_EXIT_B: If ManTrap_B DoorSwitch = Opened then Goto TRAP_READY If TS > TrapMaxOccTime then ManTrapStuck = On 'Keep program from disabling due to run time errors E: If TS > 30 then Goto TRAP_READY

Issue  The error LED on a CX9900 Controller is flashing.  What does this mean. What do the various NetController Error LED blink rates indicate. Environment NCI CX9900 CX9000 Cause An controller error has occurred. Resolution The ERROR indicator remains OFF until an error occurs. If the NetController fails an internal system test, the ERROR indicator blinks a preset number of times, then pauses, and repeats the blinking and pausing sequence. This blinking pattern will persist until you reset the controller. The number of blinks between pauses identifies the specific problem (as shown in the table below). ERROR Indicator Blink Rates (before a pause) # Blinks                Type of Failure                                                               17                           CX Firmware is corrupt (Bad Flash/ROM or bad update) 18                           LAN Card's memory is faulty - Try replacing the LAN Card. 19                           Problem creating certain System Tasks - Maybe due to lack of memory. 20                           Problem with the NIC - Try replacing the LAN Card 22                           RTC Failed - Possible Hardware issue 24                           Problem with the PIT chip - H/W related 25                           Problem creating Timer Tasks - Maybe due to lack of memory 28                           The RAM memory is faulty or bad. Try replacing the RAM module(s). 29 to 62                                 Problem creating certain System Tasks - Maybe due to lack of memory. 63                           Copy protection - Flash Upgrade file is invalid for this Controller (UPD file is Serial # protected) 64                           Problem creating the Uprev task - Maybe due to lack of memory. Note: If a Plain English program disables due to an error, the ERROR indicator illuminates and stays ON (without blinking)—if this occurs, you can turn the indicator off by setting the ERRORS system variable to zero.

Issue The operation was not performed error pops up when accessing logs or extended log via a group with Continuum 1.9 Environment Continuum Webclient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The installation was accomplished according to the instructions in the readme file to rename the original logviewer.exe Resolution Shutdown Cyberstation Install 1.90 SP1 first Copy in the AccSQLSP.dat from the hotfix and upgrade the database Delete all the original logviewer.exe files then copy in the new logviewer.exe from the hotfix. Just renaming the file will not work. Reboot the PC and restart Continuum and the error should no longer appear.

Issue The Alarms system variable in a controller contains a value other than zero but Active Alarm list view in CyberStation does not show any active alarms from that controller, How can I find out which alarms are active in the controller? Environment CyberStation All CXs All I2 devices Cause Active alarm can be determined by creating a column in the default list view to store alarm information from 'Live' source. Resolution Right click on InfinityNumeric and select 'View' to launch the default list view for the class. Edit the list view and add a column for the 'AlarmValue' attribute and set the column source to 'Live' Run the list view and inspect the AlarmValue: Blank = No active alarm on point Alm1 = the first alarm is active on point. Alm2 = the second alarm is active on point ... Alm8 = the 8th alarm is active on the point

Issue What ElecType can be used with the current range of controllers Environment Continuum NC2 NC11 CX9900 CX9940 bCX bCX4040 bCX9640 ACX57 b3 i2 Cause What ElecType can be used with the current range of controllers Resolution The current range of Continuum controllers can't use most of the options available in Continuum (ElecType) as many of these are for older controllers. See Continuum help (in Cyberstation) for the best descriptions of use. Current range of controllers mostly use (see specific spec. for full details):- Voltage, Digital, Counter, ACCTemp(DegF), ACCTemp(DegC), Supervised To use any other analog sensors, within the current range of controllers, including thermocouples and RTDs, they need to be converted to a 0-10Vdc (or preferably 0-5Vdc) or 4-20mA and use "Voltage" ElecType   Other ElectTypes below. For CX9400 controller:- RTDTemp(DegF), RTDTemp(DegC), RTD1000TempF, RTD1000TempC, ThermCoupJTempF, ThermCoupJTempC, ThermCoupKTempF, ThermCoupKTempC, ThermCoupTTempF, ThermCoupTTempC, ThermCoupETempF, ThermCoupETempC, ThermCoupRTempF, ThermCoupRTempC, ThermCoupSTempF, ThermCoupSTempC, ThermCoupBTempF, ThermCoupBTempC, RTDTempF2W, RTDTempC2W, RTD1000TempF2W, RTD1000TempC2W Not Used:- ACC_InputCurrent, ACC_Keypad, ACC_Pressure, ACC_Airflow Older Controllers:- TankProbe

Issue When changes are made to the BACnet schedule in a third party device, the object editor crashes when the changes are applied. ACCTrace file shows the following error: The datatype of a BACnet property value specified in a service parameter does not match the datatype of the property referenced by the specified Property_Identifier. Environment CyberStation Continuum BACnet Trane SC Schedule Object Cause The object type is not fully support by the third party controller.   Consult the devices PICS statement. Resolution In some cases third party vendors will implement BACnet object types for internal use while not allowing other vendors to write to these object.  Occasionally it may be possible to write values to some of the objects properties.  However, when Continuum tries to write to a value to the unsupported property the object error will crash.

Issue When trying to save a simple InfinityProgram to map a third party BAcnet point, the error "Cannot find the item" is generated by the PE editor. Environment CyberStation ver. 1.81 bcx4040 Cause When trying to save the simple looping InfinityProgram below the error "cannot find the item" (on the ReadProperty statement) is generated. The LeavingChWTemp is updating fine on the BACnet side. It's just not mapping to the Infinity side.  Line 1 ReadProperty(BacnetDevices\BNet_3021\YKVSDIMK5005\LeavingChwTemp) Goto Line 2 Line 2 If (TS > 1) Then Goto Line 1 Resolution ContinuumExplorer had two BACnet icons on the tree - one with all the BACnet controllers and points and one with no controllers and points. The "empty" one was renamed BacNet_1. CyberStation was restarted. The program saved correctly. It appears that CyberStation was not referencing the correct BACnet instance and therefore Plain English could not resolve the path in the ReadProperty statement. Once the duplication was removed all worked fine. Note: There should never be more than one BACnet icon in ContinuumExplorer. In the case it was not determined how this situation occurred.   

Issue Using the SendMail function in the NC2 and ACX2 to know if CyberStation is shut down would be a nice feature. Environment CyberStation NC2, CX9680, bCX4040, bCX9640, ACX5720, ACX5740 Cause When a standalone CyberStation is not monitored 24x7 and it is emailing critical alarms or pulling extended logs, it is important that it remains up and running as much as possible. How can the newer controllers' email capability be used to add this functionality. Resolution The SendEmail function can be used for this purpose. Set up the bCX via the "Email setup" controller webpage. This will require at least one Outgoing SMTP Server be accessible to your controller. The workstation commstatus is not a supported function within Plain English (although it may appear to compile in a program), so the workaround is to write a workstation program that sets a numeric in the controller on fixed timeframe. An InfinityProgram in the controller can monitor that numeric value and send the email if the value is not updated. Here are two sample programs for your use that provide a starting point for this application: ======= 'Fallthru program in CX triggered by minute which sends an email every 30 minutes while the workstation is offline 'Note: Set (Minute-Heartbeat) long enough for a CyberStation reboot/restart to avoid false alarms on an intentional shutdown.  Checking: If Minute = 10 and (Minute - WSHeartbeat) > 4 then goto Sending If Minute = 25 and (Minute - WSHeartbeat) > 4 then goto Sending If Minute = 40 and (Minute - WSHeartbeat) > 4 then goto Sending If Minute = 55 and (Minute - WSHeartbeat) > 4 then goto Sending Stop Sending: SendEmail('theemailaddresshere', Date, 'CyberStation is offline') Goto Wait30m   Wait30m: If TM < 29 then goto Wait30m E: If TS > 60 then Goto Checking ========== ========== 'Looping, autostart program in workstation Wait30s: If TS > 29 then goto SetRemoteFlag   SetRemoteFlag: MyNetwork\My_bCX\WSHeartbeat = Minute Goto Wait30s   E: If TS > 2 then goto Wait30s ======  Note: For LAN Systems a workstation can monitor the other workstations using the CommStatus attribute.

Issue Webpinpoint requires mime types and if a selected option is missing, the object doesn't show in IIS Environment Windows 7 Windows Vista Windows Server 2003 Windows Server 2008 Cause If all the IIS options in IIS that are specified in the webclient installation guide are not selected then objects for webclient installation will not be available. Resolution In Windows Control Panel> Programs and Features> Turn Windows Features On/Off  Make sure that Common HTTP Features> Static Content    is checked If not, check this options and restart the PC