Building Automation Knowledge Base

Issue WebClient login screen has the webClient background, but no login fields   Product Line Andover Continuum Environment webClient Cause This typically happens when webclient has been installed prior to IIS, so .Net framework does not get registered with IIS. Resolution The resolution is to run the regiis.exe command as follows: From a DOS Command Prompt (as an admin) For Windows 2000 Professional it is: "c:\WinNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i" "c:\WinNT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i" For Windows XP Professional, Windows Server 2003 it is: "c:\windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i" "c:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i"   For Webclient 1.94 and above, .Net Framework 4 is used "c:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i" Once this command is run the normal login prompt will be presented.

Issue Can a listview showing access events be filtered to only show access events for a specific door? Product Line Andover Continuum Environment Cyberstation WebClient Cause Need to monitor access events for one specific door using a listview. Resolution Create an Access Event Listview (1), add filter if required (2) and set path (3)  Add columns and include a column for DoorId Note the full path that shows up for the door under DoorId after running the listview Edit the listview and add a filter The syntax of the filter string should be:                          (DoorId is like DoorId Path String id)   Note: The filter string will not work unless  "id" is placed at the end of the qualifier.  Also the DoorId Path string must be exactly as it appears under the DoorId column for a door event of an unfiltered event listview.

Issue Webclient Pro and Personnel versions support different features and there is a need to understand the differences Product Line Andover Continuum Environment Webclient Cause It is helpful to understand the differences between Webclient Pro and Personnel Resolution Webclient Personnel features WebClient is an application that provides you with web-enabled access everywhere, all the time. By using Internet Explorer, your authorized personnel can access the Continuum facility management system in real-time across your site’s local area network (LAN) or across your wide-area network (WAN). WebClient is either added to a LAN Andover Continuum CyberStation system or installed with a standalone CyberStation on a single PC. With the basic WebClient Personnel Manager option, your users can:    -Create, search for, edit, and delete personnel records -Change employee access privileges -View a person’s access events -View and generate reports of all access events, including area access events, access events by persons, and    distribution-event transactions via the Access Distribution View -Edit and view schedules and calendars. -Change a password.   Webclient Pro features With the advanced WebClient Pro option, your users have all the features of the basic WebClient Personnel Manager option as well as the following additional features:    -Create, run, and view graphical reports (class object Report), including bar charts, pie charts, trend charts, text    reports, and so on.  -List and view graphics and groups -View live system alarms and live events -View live video, as well as search for and view recorded video, via the class object, VideoLayout. -Search for web.Client objects by exploring a folder tree hierarchy or a network/device tree hierarchy, or by using a   text search engine  -Edit and view Loops and TrendLogs.  

Issue Is 64-bit Internet Explorer supported for use with WebClient? Product Line Andover Continuum Environment WebClient Cause The Compatibility Matrix now mentions 64-bit Internet Explorer is NOT supported as the browser for the WebClient clients Resolution IE 64-bit Support Webclient does not support 64-bit Internet Explorer with WebClient See the Cyberstation and WebClient 2.03 Compatibility Matrix - Andover Continuum - PA-00664 R2  WebClient browser support section: Only the 32-bit version of Internet Explorer - Internet Explorer 10 and 11 Compatibility View for AlarmView Be sure to turn on the Compatibility View in the separate IE browser window that displays the Alarms view. Also turn off popup blockers in the browser window. For more information on the Alarms view, see the web.Client online help   Using IE 32-bit in 64-bit Environment</strong? In a 64-bit environment, both the 64-bit and the 32-bit versions of IE10 and IE11 are installed when you install IE. 64-bit version is under "C:\Program Files\Internet Explorer" 32-bit version is under "C:\Program Files (x86)\Internet Explorer" See the following article for using Webclient with Microsoft Edge: https://community.se.com/t5/Building-Automation-Knowledge/Internet-browser-alternatives-for-accessing-Continuum-WebClient/ta-p/363440

Issue Instructions are needed to configure the new SMTP configuration. Product Line Andover Continuum Environment Continuum Non-Microsoft Exchange/Outlook SMTP Email Cause Configuration for the SMTP Configuration for email alarming in Continuum 2.00 through 2.03 Resolution In Cyberstation 2.0 and above, you no longer need Microsoft Outlook and Exchange to send email alarm notifications. Other SMTP servers can be used on the network and other email clients can be used also to send email alarm notifications directly to an intended recipient. Note: Public SMTP servers such as Gmail SMTP and Yahoo SMTP do not currently work with this solution as they require SSL or certain unsupported port combinations. The connections these servers establish cause connection issues within the SMTP application. Private SMTP (In-house) servers can be set up and used.   Steps to Configure SMTP Email Alarming   Open and Event Notification Navigate to the Actions Tab Select which events to receive email alarms Select the Delivery Tab Click the Add Recipient button to open the recipient configuration Browse for the recipient Cyberstation by click the ellipsis Select the recipient Cyberstation Select the SMTP Configuration button in the Recipient Configuration window Fill in the Server Configuration fields in the SMTP Configuration window Specify the SMTP Server address, port and login information Fill in the Email Configuration Specify the sender's email address - this is the email address the email will be sent from and it is also the email address that failed emails will be sent to    Type in a Subject line if needed or the default Continuum email subject line will be used Alarm Option Settings - Fill in the RetryCount and Retry Time fields  Retry Count - once you pass this value the email is dropped. The maximum Retry Count is 10  Retry Time -  field is in minutes. The maximum is 1440 minutes (24 hours) Adding an email address to the recipient list Click the Display Master List to open the SMTP Master Email Configuration Dialog Place a check in the check box to add an email address from the existing Master List to the Event Notification's recipient list and then click OK Adding or deleting email addresses from the Master Email list Open the SMTPMasterEmail Event Notification in the templates folder In the opened SMTPMasterEmail Event Notification click the Display Master List button Click the Add Recipient or Delete Recipient button depending on what is needed After selecting Add Recipient supply the email address in the recipient field and click Add Recipient After selecting Delete Recipient, select the address to highlight it and then click the Delete Recipient button. Multiple Selection is supported To deliver email notifications to the added email address, select the check box next to it Testing to ensure email address recipients receive emails Select the address you wish to test and click the Test Selected button Successful email to SMTP Server test will display a pop-up Failed email to SMTP server test will display a pop-up to the Sender's email address Final address configuration Recipients Configuration Options Place a checkmark next to the option needed Ex. Primary or Backup  SMTP Email A checkmark next to Repeat. Repeat will function as if it were an Outlook email alarm and send until the alarm is acknowledged. Known issues: In order for BACnet controllers to use the new SMTP feature, the following hotfix from the following link is needed.  CyberStation v2.00 (Only) SMTP Emailing & BACnet Alarms - Hotfix 2.03 contains the hotfix listed above   For additional information, see the Cyberstation Help, search for SMTP.

Issue Continuum Reports Suite installation issues. Example error message could be: "Unrecoverable Error!" "Alias 'CURRENT3' is not found" "Method: ALARMEVENTS.RUN_REPORT_BTN.CLICK" Product Line Andover Continuum Environment Continuum Reports Suite Cause Problems with installing and running the Report Suite Resolution When editing the "Continuum_Reports.dmp" file using Notepad.exe, WordWrap must be unchecked!  Unfortunately, opening "Continuum_Reports.dmp" and unchecking WordWrap is not enough!  When WordWrap is checked, you must uncheck and Exit Notepad.  Then Open "Continuum_Reports.dmp", edit and SAVE AS.  When WordWrap is enabled and changes are made, after you Save and reopen the file, you will notice that is corrupt and all the PE Codes is scrunched into one enormous line, instead of 550+ lines. Alternatively use a different editor, eg. Metapad or Notepad++ If after editing and importing "Continuum_Reports.dmp", you discover there is no Plain English code or the Programs run, but are stuck on "Init", or other PE import / run issues, this is the result of incorrectly performing the Replacement of the workstation Folder Name.  When the Workstation Folder name and Workstation Name is correctly replaced, the PE programs will import and run properly. After installing Continuum Reports, you should confirm that the installation directory, "C:\Program Files\Continuum_Reports" has Modify privilege enabled for all "Workstation Users". After a Continuum Reports run-time error, run the Windows Task Manager and confirm that the "Reports.exe" Process does not exist.  If it exists, End the Process. If Continuum Reports does not exit normally, temp files will be orphaned in the C:\Program Files\Continuum_Reports\Data directory.  Although orphaned Temp Files do not affect Continuum Reports operation, they occupy disk space.  Temp files have an underscore ("_") as the first character.  To remove orphaned temp files, make sure Reports.exe is not running and CAREFULLY delete those files that have an underscore ("_") as the first character. Continuum Reports needs to be installed using the Setup Application. The Setup Application needs to be run on every workstation and configuration administered locally. Before you install Continuum Reports, the current version must be uninstalled.  Typically, uninstalling and reinstalling doesn't solve any problems.  But when this is done, make sure to delete the directory C:\Program Files\Continuum_Reports\DATA before reinstalling Continuum Reports. Continuum Reports remembers the Continuum Database access parameters, including Server Name, SQL Username and Password.  After installing Continuum Reports, you will need to run "Reset_Password.bat" if the Continuum Database name is not "ContinuumDB", or if appears that Continuum Reports is not accessing the correct database. If the Multi-Facility Report Data Partitioning has been used (17.2e onwards) the Revision Level in the upper right hand corner of the window is Red.  This indicates that Restrictions were enabled.  Therefore the whole database may not be queried. See "Continuum Reports Multi-Facility Report Data Partitioning Administration Guide" It is worth setting a default printer even if one does not exist. (use a PDF printer) If the default printer gets set to say a card printer, it can affect the output of the reports suite See the link below for all software and guides, always read, as required ReadMe.txt Upgradedoc.txt Continuum Reports Installation Guide Rev x.x.pdf @ Upgrade - Installation Instructions.pdf https://ecoxpert.se.com/search#keyword/Coe/tab/documents If you have other queries please contact COE.Support@Buildings.Schneider-Electric.com

Issue Can I use a 1.9 key on a 1.74 system? Product Line Andover Continuum Environment CyberStation Cause Key compatibility with Continuum versions Resolution A version 1.99 Andover Continuum key can be used on an older ( Ex. 1.74) system. Andover Continuum Keys are backward compatible. However, you cannot go in the other direction. For example, you cannot put a 1.8x key in a 1.9x system, this will require an upgrade.   All versions of a major revision are supported on the key. Ex. 1.90, 1.91,1.92,1.93, 1.94, and any future revisions of 1.9x are supported.   If you read the key with Excel or MMC, it will actually show as 1,79,1.89, 1.99.    Note: All upgrades are handled through the Licensing Team, requests should be directed to the following email address: BMS.Licensing@se.com

Issue At times numbered errors pop up in Cyberstation or you may see a numbered error in the Error Listview Product Line Andover Continuum Environment Continuum Cyberstation Windows Cause Numbered errors appear in Cyberstation or in an Error Listview and an explanation is needed for troubleshooting Resolution With Continuum running and with the focus on the main Continuum screen or Continuum Explorer, press F1 to bring up the help menu Select index Type in ‘error’ Select Error Messages, Cyberstation This displays a list of some of the error messages that may come up in Cyberstation. This is not a comprehensive list and it doesn’t provide solutions, but gives an initial idea of what is happening for troubleshooting.   Below is the error list that you will find in the Help   OS Error Messages Error Hex Code Error text 1 0x0001 No message block available 2 0x0002 No message queue available 3 0x0003 Invalid message block 4 0x0004 Invalid message size 5 0x0005 Message is blocked 6 0x0006 Can't deallocate message, it is on a queue 7 0x0008 Invalid message queue 8 0x0008 Invalid message blocking order 9 0x0009 Invalid process ID 10 0x000A Duplicate queue ID 11 0x000B Timed out waiting for message CPL Error Messages Error Hex Code Error text 1024 0x0400 Name has more than 16 characters 1025 0x0401 Comment has more than 132 characters 1026 0x0402 Comment has more than 132 characters 1027 0x0403 Symbol(s) are not from the correct set 1028 0x0404 Field is too long to display 1029 0x0405 Statement or expression is not correct 1030 0x0406 Array is longer than 32,767 entries 1031 0x0407 FOR and NEXT use different index var names 1032 0x0408 GOTO is not allowed inside a loop 1033 0x0409 Fatal, not enough free memory 1034 0x040A Same line name given to more than one line 1035 0x040B No line has this line name 1036 0x040C Same name for more than one local variable 1037 0x040D No item with that name exists 1038 0x040E Cannot define any more local variables 1039 0x040F BREAK or CONTINUE is outside a loop or block 1040 0x0410 Same name or number for more than 1 argument 1041 0x0411 Operation is not available 1042 0x0412 Number is not valid 1043 0x0413 Number cannot be longer than 132 digits 1044 0x0414 Fatal, bad stack address 1045 0x0415 Fatal, illegal stack operation 1046 0x0416 No function with that name exists 1047 0x0417 Attributes do not apply to local variables 1048 0x0418 No quotation marks at end of string 1049 0x0419 Data type is not same as field type 1050 0x041A Data has more chars than field allows 1051 0x041B Record has too many or too few fields 1052 0x041C More records than RECORD statement allows 1053 0x041D Date or time is not valid 1054 0x041E Path name has too many names 1055 0x041F Attribute does not apply to the item type 1056 0x0420 Local variable name cannot be an argument 1057 0x0421 Incorrect array entry type 1058 0x0422 Alarm expression is too long 1059 0x0423 You cannot set that item value 1060 0x0424 You cannot change that attribute value 1061 0x0425 Name is not a program or function name 1062 0x0426 Cannot enable/disable all of one type 1063 0x0427 You must give a name of a local data file 1064 0x0428 Parser stack overflow 1065 0x0429 Cannot use that var as FOR...NEXT index var 1066 0x042A Data file is too long 1067 0x042B You cannot change value of system variable 1068 0x042C Statement is too long 1069 0x042D 0, C or E is a reserved line name 1070 0x042E Feature not available on this controller 1071 0x042F Number must be an integer 1072 0x0430 Passed too many arguments to a function 1073 0x0431 An argument index must be from 1 to 15 1074 0x0432 No chars allowed after continuation symbol 1075 0x0433 Cannot run or stop program from command line 1076 0x0434 Report files are not supported yet 1077 0x0435 Unknown command option 1078 0x0436 Name given is not a controller name 1079 0x0437 Command is valid only from the command line 1080 0x0438 Command is valid only in a program or function ITP Messages Error Hex Code Error text 2048 0x0800 Tried to set item you cannot set 2049 0x0801 Set point or var to value of wrong type 2050 0x0802 Tried to use local var that does not exist 2051 0x0803 An expression uses an operand incorrectly 2052 0x0804 Must set HOUR to value from 0 to 23 2053 0x0805 String is too long 2054 0x0806 Operation is not available 2055 0x0807 Scanner runtime stack overflow 2056 0x0808 Used an incorrect function argument 2057 0x0809 Tried to print to a non-string item 2058 0x080A Tried to rotate prog to nonexistent line 2059 0x080B Used an item type when it is not allowed 2060 0x080C Tried to divide a value by zero 2061 0x080D Gave an array entry that does not exist 2062 0x080E Gave non-numeric var as array index 2063 0x080F Gave more or less arguments than allowed 2064 0x0810 Date or time is not valid 2065 0x0811 Executed too many statements on one line 2066 0x0812 Function did not give the expected result 2067 0x0813 FOR...NEXT loop index variable not numeric 2069 0x0815 Invalid import point address 2070 0x0816 Used name that is not a data file name 2071 0x0817 Used rec or field data file does not have 2072 0x0818 Cannot read data file 2073 0x0819 Cannot write to data file 2074 0x081A Path name is not an actual path 2075 0x081B Attribute does not apply to the item type 2077 0x081D Tried to set attribute to an invalid value DCP Error Messages Error Hex Code Error text 3072 0x0C00 Operation is not available 3073 0x0C01 String is too long 3074 0x0C02 Fatal, not enough free memory 3075 0x0C03 Exceeded number of displayable lines 3076 0x0C04 Invalid import point address 3077 0x0C05 Statement is too long 3078 0x0C06 Controller cannot find an item 3079 0x0C07 Controller cannot open a file of this type 3080 0x0C08 Date or time is not valid OMS Error Messages Error Hex Code Error text 5121 0x01401 Cannot find the item 5122 0x01402 Reached end of the list 5123 0x01403 Attribute does not apply to the item 5124 0x01404 Name is too long 5125 0x01405 Attribute is inappropriate 5126 0x01406 Cannot access file on other controller 5127 0x01407 FatalErr__ Gave invalid hash table size 5128 0x01408 Not enough memory 5129 0x01409 SysErr__ Passed invalid info to database 5130 0x0140A Item is being used and not available now 5131 0x0140B Access to the item denied 5132 0x0140C Array index too large or too small 5133 0x0140D SysErr__ Invalid format for retrieving data 5134 0x0140E Cannot associate these items 5135 0x0140F No relationship of the type defined for item 5136 0x01410 SysErr__ Passed invalid setup to database 5137 0x01411 Reached end of the list of related items 5138 0x01412 Line is too long 5139 0x01413 Value does not apply to the attribute 5140 0x01414 File read error 5141 0x01415 Duplicate item name 5142 0x01416 SysErr__ Cannot set/get attribute 5143 0x01417 SysErr__ Terminal communication error 5144 0x01418 Lbus creation failed 5145 0x01419 String display failed 5146 0x0141A SysErr__ Cannot access the item in database 5147 0x0141B Incorrect path name 5148 0x0141C Incompatible value 5149 0x0141D SysErr__ Invalid message queue Id 5150 0x0141E SysErr__ Session not found 5151 0x0141F Attribute not defined yet 5152 0x01420 Invalid auto-conversion 5153 0x01421 Zero string size 5154 0x01422 Not allowed to delete a system variable 5155 0x01423 SysErr__ System hash tables locked 5156 0x01424 The class object list locked 5157 0x01425 Duplicate handle Id 5158 0x01426 Not enough memory - reset log array size 5159 0x01427 HardwareErr__ Bad RTC chip 5160 0x01428 Duplicate serial number 5161 0x01429 Duplicate Infinet Id number 5162 0x0142A Infinet learn mode is in process 5163 0x0142B Line name is undefined 5164 0x0142C SysErr__ Reserved line label 5165 0x0142D Unable to send the message 5166 0x0142E Dump process stopped 5167 0x0142F Controller not found 5168 0x01430 Invalid handle Id 5169 0x01431 Incorrect line or statement 5170 0x01432 Missing end of controller statement 5171 0x01433 Does not know the type 5172 0x01434 Not allowed to set the attribute 5173 0x01435 Not allowed to set the description 5174 0x01436 Not allowed to set the format 5175 0x01437 Not allowed to set the engineering unit 5176 0x01438 Item already exists 5177 0x01439 Not allowed to set the attribute 5178 0x0143A SysErr__ Invalid controller path 5179 0x0143B SysErr__ Invalid current controller message 5180 0x0143C Invalid response from other controller 5181 0x0143D Item is already being used 5182 0x0143E File is being saved by another operator 5183 0x0143F File is too long 5184 0x01440 Cannot access the item on other controller 5185 0x01441 SysErr__ Passed invalid indicator to database 5186 0x01442 Invalid Energynet ID 5187 0x01443 Invalid Infinet ID 5188 0x01444 Invalid Infinet port 5189 0x01445 Missing end of dictionary statement 5190 0x01446 Missing end of import/export statement 5191 0x01447 Unable to compile the file 5192 0x01448 Invalid dump file statement 5193 0x01449 Missing end of block statement 5194 0x0144A Missing end of code statement 5195 0x0144B Missing end of object statement 5196 0x0144C Unable to rename the controller 5197 0x0144D Unable to rename the comm port 5198 0x0144E Item has no type 5199 0x0144F Undefined alarm 5200 0x01450 Attribute can only be retrieved, not set 5201 0x01451 Conversion too long 5202 0x01452 Not allowed to retrieve the attribute value 5203 0x01453 No default format defined 5204 0x01454 SysErr__ Passed invalid indicator to database 5205 0x01455 Invalid schedule type 5206 0x01456 Missing colon in the statement 5207 0x01457 Incorrect name 5208 0x01458 Incorrect header for the code block 5209 0x01459 Incorrect header for a sub block 5210 0x0145A Incorrect header for the object block 5211 0x0145B Undefined system variable 5212 0x0145C Undefined comm port 5213 0x0145D Not allowed to create an alarm 5214 0x0145E Inappropriate request for the comm port 5215 0x0145F Invalid mode for the comm port 5216 0x01460 LBus is already set up 5217 0x01461 Invalid program file 5218 0x01462 Program is already in the firing order 5219 0x01463 Unable to access the item 5220 0x01464 No response to the Infinet token pass 5221 0x01465 NetworkErr__ Received incorrect CRC on Infinet 5222 0x01466 SysErr__ Invalid error value from Infinet 5223 0x01467 Attribute does not apply to the point type 5224 0x01468 Attribute does not apply to the port type 5225 0x01469 Item must be a program 5226 0x0146A File must be open 5227 0x0146B File took too long to open 5228 0x0146C Cannot alter the file 5229 0x0146D Cannot add or remove records 5230 0x0146E The relationship is already set up 5231 0x0146F CAnnot dump dictionary block of controller 5232 0x01470 Cannot dump the controller 5233 0x01471 Cannot dump associated items 5234 0x01472 Undefined IOU number 5235 0x01473 Invalid channel number 5236 0x01474 No free alarm links 5237 0x01475 Cannot access next Enet controller in list 5238 0x01476 Cannot access next Infinet controller in list 5239 0x01477 Incorrect header for the log array block 5240 0x01478 Invalid log array index 5241 0x01479 Cannot modify the file 5242 0x0147A Unable to create the Infinet controller 5243 0x0147B Zero is not a valid serial number 5244 0x0147C Invalid baud rate 5245 0x0147D Comm port is not set up for Infinet 5246 0x0147E Controller is not online 5247 0x0147F Not allowed to delete a comm port 5248 0x01480 Cannot define any more handle IDs 5249 0x01481 Invalid controller name 5250 0x01482 Invalid Infinet controller name 5251 0x01483 Invalid Energynet controller network ID 5252 0x01484 Controller doesn't know Infinet ID 5253 0x01485 Invalid electrical type 5254 0x01486 Invalid DateTime value 5255 0x01487 Invalid log type 5256 0x01488 Invalid floating point number 5257 0x01489 Attribute doesn't exist for the item 5258 0x0148A Access to the conversion denied 5259 0x0148B Number of array entries is too  arge 5260 0x0148C Invalid program status 5261 0x0148D Unable to access the comm port 5262 0x0148E Cannot overwrite the item 5263 0x0148F New default mode is current mode 5264 0x01490 Cannot set export flag for Enet controller 5265 0x01491 Operation is not supported 5266 0x01492 SysErr__ Unused sched events are inaccessible 5267 0x01493 Sched occup/unoccup variable not DateTime 5268 0x01494 Holiday schedule doesn't exist 5269 0x01495 Import/Export item must be a point 5270 0x01496 Point must export to controller/alarm 5271 0x01497 Sched occupancy flag not output/numeric point 5272 0x01498 Item is not a holiday schedule 5273 0x01499 Cannot dump the import/export block 5274 0x0149A Cannot set up the port 5275 0x0149B Index number for the alarm is too large 5276 0x0149C Invalid state 5277 0x0149D Comm port is busy 5278 0x0149E Reference array is full 5279 0x0149F Undefined alarm type 5280 0x014A0 Item is not local controller 5281 0x014A1 HardwreErr__ Bad EEPROM chip 5282 0x014A2 Cannot retrieve controller model number 5283 0x014A3 Cannot retrieve controller serial number 5284 0x014A4 Unspecified Enet ID 5285 0x014A5 Undefined controller model number 5286 0x014A6 Controller has no assigned Infinet port 5287 0x014A7 Cannot find controller in the Infinet list 5288 0x014A8 Invalid password 5289 0x014A9 Cannot retrieve controller version number 5290 0x014AA Handle ID is out of range 5291 0x014AB Not allowed to delete user ACC 5292 0x014AC Not allowed to use this many Infinet devices 5293 0x014AD Not allowed to change user ACC's security level 5294 0x014AE Full path is not set 5295 0x014AF Access denied 5296 0x014B0 User passwords are mismatched 5297 0x014B1 User doesn't exist on remote controller 5298 0x014B2 Invalid stop bits 5299 0x014B3 Invalid data length 5300 0x014B4 The user is logged in 5301 0x014B5 Not allowed to change user name 5302 0x014B6 Not allowed to delete this controller 5303 0x014B7 No TankProbe extension block installed 5304 0x014B8 No TankNet exists 5305 0x014B9 TankNet is already set up 5306 0x014BA Can't change a TankProbe to another electrical type 5307 0x014BB Duplicate PIN 5308 0x014BC There is no card information available for this person 5309 0x014BD Invalid card entry 5310 0x014BE Duplicate card 5311 0x014BF Invalid schedule 5312 0x014C0 Attribute does not apply to object type 5313 0x014C1 Undefined card type 5314 0x014C2 Invalid PIN value 5315 0x014C3 Same area on both sides of a door is not allowed 5316 0x014C4 The maximum number of doors allowed has been reached 5317 0x014C5 Personnel cleanup in progress.  Please try again. 5318 0x014C6 Unable to delete one or more personnel objects on rip 5319 0x014C7 Personnel distribution in process.  Please try again. 5320 0x014C8 Not allowed to set an area in a DefaultDoor 5321 0x014C9 Unable to set remote sync bit for one or more personnel objects 5322 0x014CA Could not synchronize CX and SX databases 5327 0x014CF Event log size has been automatically adjusted 5328 0x014D0 No XDriver code module installed 5329 0x014D1 XDriver code module installed 5330 0x014D2 XDriver code module incomplete 5331 0x014D3 Checksum error detected in S-record 5334 0x014D6 Duplicate XDriver parameter 5338 0x014DA Invalid IP parameter 5339 0x014DB Invalid Subnet Mask for the IP class 5340 0x014DC IP network number should not equal 0 5341 0x014DD IP host number should not be all 1s 5342 0x014DE Possible Infinet bus short detected 5345 0x014E1 Update operation still in progress 5348 0x014E4 Invalid NetWare frame type 5349 0x014E5 UTC Offset is out of range 5350 0x014E6 No personnel cache entries available 5351 0x014E7 Memory expansion board not installed 5352 0x014E8 Flash memory operation failure 5353 0x014E9 Too many IOUs 5354 0x014EA The maximum number of areas allowed has been reached 5355 0x014EB Attempt to lock door has failed 5356 0x014EC Attempt to unlock door has failed 5357 0x014ED OMS database has become corrupt 5358 0x014EE OMS internal error 5359 0x014EF Buffer too small for data requested 5360 0x014F0 OMS database not currently available (backing up) 5361 0x014F1 String size exceeds implementation limit 5362 0x014F2 Backup disabled due to excessive use (requires manual enable) 5363 0x014F3 Schedule events are out of order 5364 0x014F4 Invalid bookmark for error log 5365 0x014F5 Duplicate SmartSensor control point 5366 0x014F6 Inappropriate value for current restart mode 5367 0x014F7 Copy protection violation has occurred —  please contact your ACC dealer 5368 0x014F8 Error sending CustomABAFormat string to IOU module 5369 0x014F9 OBJ_ERR_BACnet_ERROR  - A BACnet error occurred. 5370 0x014FA OBJ_ERR_DABL_OVERFLOW - The controller has reached its BACnet device binding limit. LAN Error Messages Error Hex Code Error text 6144 0x1800 Comm user return 6145 0x1801 Comm invalid message length 6146 0x1802 Comm invalid destination address 6147 0x1803 Comm invalid source address 6148 0x1804 Comm invalid QID 6149 0x1805 The port is not an Infinet 6150 0x1806 The controller is not responding 6151 0x1807 Comm LAN reconfig in progress 6152 0x1808 The controller is offline 6153 0x1809 The EnergyNet is not configured 6154 0x180A Comm destination node paused 6155 0x180B Send request timeout 6156 0x180C Send error 6157 0x180D NULL message received 6158 0x180E Unable to send message 6159 0x180F Invalid EnergyNet node ID 6160 0x1810 Duplicate Ethernet ID 6161 0x1811 Duplicate EnergyNet ID 6162 0x1812 Out of memory 6163 0x1813 Ethernet RAM test faillure 6164 0x1814 Undefined EnergyNet ID 6165 0x1815 Undefined Ethernet ID GLB Error Messages Error Hex Code Error text 7169 0x1C01 Symbol name too long 7170 0x1C02 Invalid characters in symbol 7171 0x1C03 Symbol cannot be a system variable 7172 0x1C04 No items 7173 0x1C05 Too many items 7174 0x1C06 First character must be alpha 7175 0x1C07 System internal error 7176 0x1C08 System clock was changed IES Error Messages Error Hex Code Error text 8192 0x2000 Cannot build IE API request 8193 0x2001 Cannot send IE API request 8194 0x2002 IES has bad OMS pointer 8195 0x2003 IE handle points to wrong network address 8196 0x2004 IE handle is invalid 8197 0x2005 IE bad data in ObjKey 8198 0x2006 IE API response not received 8199 0x2007 IE no Infinet 8200 0x2008 Could not establish import 8201 0x2009 IE database locked LBS Error Messages Error Hex Code Error text 9217 0x2401 LBus not ready 9218 0x2402 wait_collect or wait_update timeout 9219 0x2403 Invalid IOU number 9220 0x2404 LBus database is locked 9221 0x2405 An active IOU exists 9222 0x2406 LBus error no memory 9223 0x2407 Comm channel specified is invalid 9224 0x2408 Sensor's channel is invalid 9225 0x2409 LBus does not exist 9226 0x240A The IOU number has not been defined yet 9227 0x240B Bad electrical type 9228 0x240C Value is too large or too small 9229 0x240D IOU communication status = online 9230 0x240E IOU communication status = offline 9231 0x240F IOU number is not between 1 and 16 IOS Error Messages Error Hex Code Error text 10240 0x2800 NULL 10241 0x2801 Type not valid for this IO channel 10242 0x2802 IO channel number out of range 10243 0x2803 IO channel already assigned 10244 0x2804 Vref out of tolerance 10245 0x2805 IO channel is unassigned 10246 0x2806 Tri-state partner is already assigned 10247 0x2807 AD converter trashed 10248 0x2808 AD converter timed out 10249 0x2809 Reference channels not initialized 10250 0x280A Adjacent channel is already in use 10251 0x280B Invalid channel for RTD use 10252 0x280C Cannot delete IOU module until all associated objects are moved to other IOU modules or deleted 10253 0x280D Duplicate module ID 10254 0x280E Insufficient memory for IO operation 10255 0x280F IO module is not commissioned 10256 0x2810 Incorrect channel type 10257 0x2811 Channel doesn't exist 10258 0x2812 Error installing IO system 10259 0x2813 Error in IO database 10260 0x2814 Module is not saved 10261 0x2815 Attribute does not exist 10262 0x2816 IO message queue does not exist 10263 0x2817 Illegal IO queue designator 10264 0x2818 IO module number is too large 10265 0x2819 IO queue is full 10266 0x281A No IO message buffers available 10267 0x281B Unknown IO message buffer size 10268 0x281C IO routing table section doesn't exist 10269 0x281D IO routing table entry not saved 10270 0x281E IO module response was lost 10271 0x281F IO MIP interface initialization error 10272 0x2820 No response from IO module 10273 0x2821 Illegal message received from IO module 10274 0x2822 IO module message data error 10275 0x2823 IO module message is not a service pin message 10276 0x2824 No IDs available for IO module commissioning 10277 0x2825 Too many IO modules for the controller 10278 0x2826 IO module domain update error 10279 0x2827 IO module read memory command failed 10280 0x2828 IO module update address command failed 10281 0x2829 IO module update NV cnfg table failed 10282 0x282A No message tags available for IO message 10283 0x282B Not a suitable replacement IO module 10284 0x282C Error in routing IO module response 10285 0x282D Incorrect response from IO module INF Error Messages Error Hex Code Error text 11264 0x2C00 NULL 11265 0x2C01 Comm port cannot connect an Infinet 11266 0x2C02 Comm port already set up for another purpose 11267 0x2C03 Comm port has not been assigned a purpose 11268 0x2C04 No Infinet controller with that serial number 11269 0x2C05 Infinet is not set up 11270 0x2C06 Infinet ID is already in use 11271 0x2C07 ID is not valid for Infinet 11272 0x2C08 Message received is not for an Infinet controller 11273 0x2C09 Controller received message from an unknown source 11274 0x2C0A Learn mode currently in use 11277 0x2C0D Learn already in process on this port 11280 0x2C10 Infinet controller is not responding 11281 0x2C11 NULL buffer passed to Infinet server 11282 0x2C12 Message type is not supported by Infinet server I2LD Error Messages Error Hex Code Error text 202752 0x31800 No model matching download header exists on this CX 202753 0x31801 Error found in I2 download header 202754 0x31802 Error found in I2 model information 202755 0x31803 Models in I2 download exceeds maximum 202756 0x31804 Received download message type out-of-service 202757 0x31805 Begin I2 download header not received 202758 0x31806 Comm Error - socket receive 202759 0x31807 Comm Error - socket send 202760 0x31808 No comm buffers available 202761 0x31809 Download state machine error 202762 0x3180A Illegal message type response from Infinet controller 202763 0x3180B Listen call failed 202764 0x3180C Bind call failed 202765 0x3180D Socket call failed 202766 0x3180E Received short packet - not enough data 202767 0x3180F Application type unknown by I2 202768 0x31810 Download model does not match I2 model 202769 0x31811 Unknown/unsupported message type 202770 0x31812 I2 download out-of-sync 202771 0x31813 I2 received unknown/unsupported packet type 202772 0x31814 I2 received segment that exceeds block storage 202773 0x31815 I2 received block address out-of-range for flash 202774 0x31816 I2 detected end of download CRC error 202775 0x31817 I2 does not support download revision 202776 0x31818 I2 is running in boot loader mode 202777 0x31819 I2 total received block count does not match 202778 0x381A I2 detected external RAM failure 202779 0x3181B I2 malloc failure during boot-up 202780 0x3181C I2 detected unknown flash device

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Access Event Viewer running in a CyberStation other than the primary access server works initially but after some period of time stops displaying access events. Product Line Andover Continuum Environment CyberStation MSMQ Cause Product support has identified several scenarios that can result in Cyberstations other than the primary not showing events in the Live Event Viewer. The commonality with all these cases is that the Primary Access Server(PAS) will always show the events, so before using any of the solutions specified below make sure that is ONLY workstations other than the PAS that are not displaying events in their Live Event Viewer   NOTE also, that we are referring strictly to the Live Event Viewer in this article so it is assumed events are showing in a list view including the Access Events tab that shows events in the door's editor.   CAUSE #1 (Primary failed over to Secondary then back to Primary) In systems configured with a Primary and secondary Access Server (SAS), it has been found that after a failover to the SAS due to the PAS going offline, event viewers in other workstations continue to show events UNTIL the PAS WS returns online and resumes its role of PAS at which point all workstations (other than the PAS) stop displaying events in their Live Event Viewers.   CAUSE #2 (MSMQ issue reported and fixed by Microsoft) Continuum running under MS Windows 7, Vista or MS Windows Server 2008 (including R2) Access event viewers at Cyberstations other than the PAS do not show events. Alarms acknowledged at one CyberStation would remain unacknowledged in the other CyberStations.  Please see MSMQ issue causes Alarms and Access Event delivery problems between CyberStations for more information.   ISSUE #3 MSMQ CleanupInterval setting is too short. Resolution SOLUTION #1 First, make sure the ControllerStatus notification object is configured to send the offline alarm to all the Workstations in question. Second, put a PE program in the SAS to serve as a monitor to let the Live Event Viewer know when the PAS has returned online, this is accomplished by referencing an object from the PAS  SAMPLE PE POGRAM SOLUTION #2  (MSMQ issue reported and fixed by Microsoft) Click MSMQ issue causes Alarms and Access Event delivery problems between CyberStations for more information.   SOLUTION #3 In the Windows registry add the key \SOFTWARE\Microsoft\MSMQ\Parameters\CleanupInterval The recommended setting is 3600000 which is the number of milliseconds in an hour   For additional information about the CleanupIntervalKey, see the following article from Microsoft: http://msdn.microsoft.com/en-us/library/ms703235(VS.85).aspx

Issue Which Continuum versions support an NC2(9680)? Procedure for replacing a CX99xx with a CX9680 Product Line Andover Continuum Environment CX9940 CX9900 NetController 2 NCII CX9680 Cause Netcontroller II (CX9680) is supported in Continuum versions 1.80 and higher Resolution Upgrade the site to Continuum 1.80 or higher for NC2 support   Procedure for converting an NetController1 (NC1/99xx) to a NetcontrollerII (NC2/9680) To convert a NetController to a NetController II, perform the following steps:   Back up your SQL Server database. See the Andover Continuum CyberStation Installation Guide, 30- 3001-720, and Microsoft® SQL server documentation. From the Continuum Explorer, use the right-click popup menu for this controller, and select Send to Text File. This drops the controller object’s data into a text file. For various ways to customize this operation, whereby you can save the controller’s child objects, please see the Send to Database Options in the CyberStation online help. Update your workstation with a version of CyberStation that supports the newer NetController models. These models are supported by CyberStation Version 1.8 and higher. Physically remove the old NetController, and mount/connect your NetController II. When you configure and commission the NetController II, use the same controller name, network IP address, and network ID. This is performed via the controller’s embedded web commissioning pages and via the General tab and the Network tab of the CyberStation’s Infinity Controller editor. Switch to CyberStation offline editing mode in the InfinityController editor. On the General tab, from the Controller Type dropdown menu, change the model number to 9680 or 9681, depending on which NetController II you are installing. Make sure you actually want to replace the NetController. When you attempt to change the controller model, Cyberstation displays a few warning messages: Cyberstation warns that a model change is irreversible. Cyberstation warns that, if an XDriver is used with this controller, not all XDrivers are supported by the new model. If you proceed, the XDriver links are left in place regardless of the availability of a replacement Xdriver. XDrivers on NetController II — In general, Xdrivers that are available on the bCX1 model 9640 are also supported on the NetController II. For example, supported NetController II XDrivers include, but are not limited to, the following: Filter XdTest Modbus TCP Modbus RTU XDrivers built for the previous-generation NetControllers will not run on the NetController II. What is an XDriver? An XDriver is special, customized software that your site purchases separately from TAC. The XDriver software allows your controller to connect to and communicate with a special piece of third-party equipment needed at your site. In the CyberStation CommPort editor, you must configure a controller comm port for this special device that the XDriver software enables. * When you leave the InfintyController editor, go back to online editing mode. If necessary, provide an updated XDriver file compatible with your NetController II. CyberStation prompts you to do this. Note: You can specify an XDriver on the General tab of the CommPort editor. Specify XDriver for the Default Mode, and use the browse button in the XDriver File Name field to search for and specify the path of the XDriver. Determine whether this NetController II has network security. If so, configure network security for this controller. Note: Network Security is supported only in NetController II model 9680, as well as ACX controllers 5720 and 5740. Restore (reload) data from your database into the new controller. From CyberStation’s Continuum Explorer, use the Object dropdown menu or right-click the object popup menu for this controller object, and select Send to Controller. Back up to flash. In Continuum Explorer, right-click over this controller, and from the container popup menu, select Backup to Flash. This saves the controller’s RAM configuration to its flash memory, in accordance with the attribute value that is set for the ACCRestartMode system variable.

Issue Controller lost power or is new and needs to be reloaded Product Line Andover Continuum  Environment Continuum Cyberstation Cause How to reload a Continuum controller Resolution Steps to reload a Continuum controller Open Continuum Explorer Right-click and select Send to> Controller Open up the distribution window from the system icon tray(lower right-hand side) The distribution window will show controller reload progress and state when the reload is finished The attached documen provides additional information on the controller reload options that are available in the Continuum Explorer Options menu.  

Issue How to use the Continuum Report object Product Line Andover Continuum Environment CyberStation Cause Instructions are needed to use the Continuum report object Resolution CyberStation provides a graphical suite of features, called Reports, that allows you to gather, view, compare, and distribute point-object data values, locally or remotely, manually or automatically, from virtually anywhere in your Continuum system.  Using CyberStation Reports, you may collect and filter data from a multiple number of dynamic building-control data sources (including extended logs) then instantly display this data in graphical bar charts, pie charts, trend charts, or columned text charts. With reports, you can: • Display report data using one of several data formats • Display two or more reports simultaneously • Modify report configurations on the fly while viewing them • Schedule reports to run automatically at a specified time • Save a report to a file, manually and/or automatically • Email a report, manually and/or automatically • Print a report   Basic Report Example   1. Create a Report  In Continuum Explorer, right-click on a folder or device, and select New, then Report, from the popup menu.     Type in a Report name and Select the Create button   2. Source Page a. Select a Data Source from the drop-down (Tables from the database)  b. Select a Report Type - these change based on the data source c. Select a Chart Type   3. Configure Columns Click on the Configure Columns button in the middle of the Source Page   a. Select the Columns needed in the report b. Use the drop-down to select how the report will be sorted   4. Filter Tab From the Source Page, select the Filter Tab a. The Log Filter and Time Interval options allow for Time filtering b. Member Objects - Click Add to specify which Fileds/Attributes will be included on the report   5. Output Tab From the Source page select the Output Tab The settings on the Output Tab will reflect how the report appears and how it is to be viewed   For detailed instructions for standard(Not Add-On) Continuum reports, see Chapter 14 Reports in the Continuum Configuration Training Manual. This manual is not available online, it is distributed as part of the Continuum training courses.

Issue Enhanced and Standard Alarm Delivery Explained Product Line Andover Continuum Environment Cyberstation Cause Information on the difference between Enhanced Alarm Delivery and Standard Alarm Delivery feature. Resolution Standard Alarm Delivery:   Prior to Continuum 1.7, alarms were delivered from the controller to each workstation on the network as long as a  Cyberstation is online (from the controller's perspective) AND if the Cyberstation is a recipient of the alarm or not.   The first workstation which receives the alarm logs it to the SQL database. The alarm is broadcast and if for some reason it doesn't get logged there is no guarantee it will be delivered to any Cyberstastion. It gets broadcast once.   Enhanced Alarm Delivery: The alarm engine was changed so that alarms could be delivered to Workstations that were temporarily offline. To accomplish this Continuum implemented Microsoft Message Queuing (MSMQ).   The controllers generate alarms based on criteria set up in alarm enrollments. These are logged in the database by the first workstation that receives the alarm which then hands it off to MSMQ for delivery to all workstations in the recipient list. The controller still sends the alarms to all online workstations. If a workstation is offline, alarms are stored in an outgoing MSMQ queue that will be delivered once the Cyberstation is back online.   Acc.App.AlarmServer.exe (Alarm Delivery Server) is the process that handles alarms and hands them off to MSMQ which is handled by the Windows Message Queuing service.   To view MSMQ queues, go to [Windows Control Panel>Security Settings]> Administrative Tools> Computer Management> Services and Applications> Message Queuing   Enabling Enhanced Alarm Delivery when upgrading or with a new install This is accomplished by leaving the default checkbox for Enhanced Alarm Delivery selected in the database initialization step on a new install or when upgrading to a version greater than 1.7x. MSMQ will then be installed as part of the Cyberstation installation or upgrade.   Note: If the Enhanced Alarm Logging checkbox is not checked initially, the Enhanced Alarm Delivery checkbox may become unselectable. See Installing Continuum Database for the First Time on a Multi-User LAN System in the Installation Guide   Enabling enhanced alarm delivery in a system that doesn’t have the checkbox selectable 1. Manually Install MSMQ Start> Run> type cmd then click OK (to open a command prompt) At the DOS prompt type cd\ then enter (places the cursor at the root) cd \program files\continuum\install then enter Type cscript MSMQInstall.js then enter (Windows component wizard Installs MSMQ) When the script is finished, one of the lines will indicate that MSMQ started successfully Type exit 2. Updating the database Note: Ensure you have a recent database backup before the next step Run Database Initialization Select Server if LAN or Stand Alone accordingly Select Enhanced Alarm Delivery checkbox Select update existing database and then click continue Restart all Cyberstations (If ALL aren't restarted, the system can still be in mixed mode)   3. LAN installation  Manually install MSMQ on each Cyberstation according to the instructions above (step 1). MSMQ will now be used for guaranteed alarm delivery.     Caution: Make sure that all Cyberststations in the database are restarted after Enhanced Alarm Delivery was selected and the DB Update performed!    Not restarting a Cyberstation puts the system at risk of using workstations with both types of alarm delivery (PSS may refer to this as MIXED MODE).   If all but one of the Cyberstations gets restarted and a Continuum User changes the alarm delivery mode and then a Cyberstation gets restarted later, the system  will be in mixed mode.   Uninstalling MSMQ Uninstalling MSMQ on a workstation (if needed at some point) Go to Control Panel> Add/Remove Windows Components> Deselect Message Queuing Say Yes to the warning message Reboot Also, check the following: Add a column to the alarm list view check the loggingWSId and see if the alarms are being delivered to another workstation that is no longer used. If it is no longer needed delete that Workstation which should correct this issue.

Issue Can the damper feedback function be calculated using Plain English based on the drive time of the damper? Product Line Andover Continuum Environment Continuum i2866-V Controller Continuum b3866-V Controller Cause For this controller application, information about the vav damper position is required.   Resolution Only the i2866-v and the b3866-v provide integrated damper feedback.    When using other controller models such as the i2865 or the b3865, an approximation of the damper position can be calculated by adding the damper pulse value to the drive time.   Whenever the damper output is driven to the closed position, a pulse equal to the full damper drive time should be sent to the output and the damper position is reset to 0%.   Whenever the damper output is driven to the fully open position, a pulse equal to the full damper drive time is sent to the output and the damper position is reset to 100%.   Because this method of calculating the position of the damper is only an approximation, it should not be used for critical applications. 

Issue Continuum Graphics (Pinpoint): How do point updates take place and how can I change the update interval and polling speed? Is it different for BACnet points? Product Line Andover Continuum Environment Pinpoint Graphics Bacnet Cause How do point updates take place and how can I change the update interval and polling speed? Resolution In Cyberstation V1.71 and greater, the graphics polling engine was significantly changed. Prior to this change, the Pinpoint application would poll the points within its graphic file directly. If several graphics were open, each graphic would perform its own polling, This engine also applied to Web.client. Each control on the graphic had a separate selection where you could set the polling rate on a per-point basis on the miscellaneous tab of each control. This was the only method to adjust the point polling interval. The main reason for the graphic engine change was for Web.Client graphics. Slow networks, multiple browsers accessing the same graphics, and slow browser machines could make Web.Client graphics unacceptably slow.   The current method to get data into graphics involves a separate graphics polling engine per workstation. When one or more graphics are opened on a workstation or a Web.Client IIS server, the graphics register the points into the polling engine on that workstation. The polling engine then begins updating the values and sends the data to the Pinpoint/web.pinpoint clients. After initially sending all the data values to the graphic, it then only sends the data that has changed since the last update in an XML document format. If several graphics are requesting the same point values, the data is only polled once for all the Pinpoint clients on that workstation or Web.Client. Efficiency was also achieved by registering the points in the polling engine which allowed the polling engine to decrease the number of data requests by 50% to retrieve the same data.   There are now additional settings to adjust the polling rates in a graphic. #11 General preferences "Time interval between requests" This is a global setting and affects all workstations. By default, all polled points which are in the polling queue are sequentially updated at a continuous rate with a default delay between requests of 30 milliseconds. It is often recommended to set this to 100ms (Additional considerations below  under Multiple Cyberstation graphics performance)   General Preferences are accessed by Right Clicking on the Continuum icon in the Windows system tray and selecting General Preferences     There are also a pair of settings in the workstation preferences: #24 Pinpoint active polling rate #25 Pinpoint inactive polling rate These settings are for each workstation individually and do not affect the polling rates of the polling engine, but merely determine how often the graphic requests data updates from the polling engine based on whether a panel is or is not the active window. Typically these settings can be left at their defaults R&D has indicated that #24 is not used as Pinpoint always uses the inactive polling rate whether the window is active or not. Therefore, adjust #25 "Pinpoint inactive polling rate".  It is recommended to set this to keep this at the default of 250ms.   Cyberstation Preferences are accessed by Right Clicking on one of the Cyberstations while logged into Continuum and selecting Edit   Multiple Cyberstation graphics performance Several workstations may be configured to display graphics that are pointing to the same controllers and the controllers being polled may be on a large Infinet or MSTP network. In this case, the controllers could be overwhelmed by simultaneous data requests from the different workstations, slowing down controller scans, the whole field bus and overall system performance. R&D indicates that when multiple Cyberstation Graphics are used there is some randomness as to how the polling requests are accomplished. If graphic or system performance is an issue, it is suggested that another 30 Milliseconds is added to the general preferences "Time interval between requests" (#11) and then measure system performance and add additional time if needed up to 500ms.   When using this setting it is necessary to consider how many Cybersations would be running simultaneous graphics. For example:4 workstations polling graphics simultaneously with "x" number of points in it for 1 Netcontroller could have about 20 requests per second (determined via Wireshark capture at the NC NIC) 30 ms per X 4 Cyber =120ms added In this case, the recommendation was to set the "Time interval between requests" value to 250ms for performance   Note: Individual millisecond settings in each point do not effect polling for the point. They are not used.   BACnet points Bacnet points can be managed differently. Continuum BACnet points can either be polled the same way that Standard continuum points are polled or by using a COV. Standard polling is done by using the point objects from the "Infinity" side of the object tree. If you want to use COV for the point updates which is much more efficient, you should use the "BACnet Points" in the graphic, from the BACnet side of the object tree. The polling engine will then subscribe for COV updates to the respective controllers. When the graphic is closed the polling engine will unsubscribe the COVs. Third-Party BACnet controllers have an additional method to adjust the poll frequency. If the third-party BACnet controller supports COV subscriptions, Cyberstation will subscribe to these points as COV's like the Continuum BACnet controllers however, if the devices do not support COV's their points will be polled. Since many third-party BACnet controllers cannot withstand frequent data requests, there are two additional settings on the BACnet device object editor. The settings are on the Details tab on third-party BACnet controllers only. 1. Max # of Async requests The max # Async requests specify how many requests we should send before we get a reply to the data request, or how many requests can I queue. Typically this should be set to 1. 2. Request interval in ms  The request interval setting will depend on the device. Does it use Ethernet or MSTP network architecture? Are you running "Enhanced MSTP"? How many third-party devices are on the mstp network that cannot run enhanced MSTP? Typically it would be safe to set this in the 1000 to 5000 ms range based on desired data update rates and the controller's capability to handle the polling.

Issue There is a need to know which card formats are supported by Continuum Product Line Andover Continuum Environment Access Control Continuum Cyberstation Cause There are many different card formats available from HID, so there is a need to know which formats that Continuum allows. Resolution Here are the formats that HID offers: 26-Bit Format: H10301 HID Proprietary 37-Bit Format: H10302 **** HID Proprietary 37-Bit Format with facility code: H10304 Corporate 1000 Formats HID Long Format Card Programming OEM Proprietary Formats (i.e. Continuum 37) 35-Bit Card Format Formats 1, 4, and 6 above are supported natively We support all the other formats (as custom cards) so long as the format does not exceed 64-bits and the format can be supplied or understood. (i.e. start/end bit of the site code, card number, etc.)   ****IMPORTANT Continuum supports a maximum of 32 bits for the Card Number field, any format above, such as the H10302, that defines more than 32 bits for Card Number field will only work if the card number range used at the site is between 1 and 4,294,967,295, any card number above 4,294,967,295 will NOT be read correctly by the controller. A possible solution for this limitation is to use the Extended Custom Cards feature supported ONLY in the ACX5720 and ACX5740 controllers.   More information about Extended Custom Cards https://community.se.com/t5/Building-Automation-Knowledge/Extended-Custom-Wiegand-features-available-for-ACX57xx/ta-p/1215 

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Introducing a previously commissioned Continuum IOU module such as an AC-1 to an Access Expert or Security Expert site can cause communication issues in the LON bus due to duplicated node id. Product Line Andover Continuum, EcoStruxure Security Expert, EcoStruxure Access Expert Environment Continuum AC-1 Continuum Net Controller Continuum Net Controller II Access Expert Controller Security Expert Controller Cause When IOU modules are commissioned in a Continuum system, the Net Controller assigns each module a Node ID, this is in addition to the LON Module ID that is unique to each module hardware, the purpose of the Node ID, is to decouple the identifier used by Continuum for communication from the specific piece of hardware, this in order to facilitate the replacement of a failed module without the need to change its Continuum identifier. The module stores the Node ID in nonvolatile memory so that it persists across power loss. If a Continuum IOU module is introduced to a LON network (Security Expert SP-AC1 or Access Expert AX-SSC) without clearing its Node ID, there is a risk of creating a duplicate Node ID condition that will prevent the LON network from operating properly. IMPORTANT This should not be an issue during the normal transition of Continuum site to Security Expert or Access Expert, as all the modules on the running LON bus should have unique Node IDs, this is only a problem when adding a module, or replacing a module with one that has been used before. Resolution In order to signal its presence on the LON network, each module will transmit on resetting its status network variable. If upon receiving this message, the Net Controller determines that the module is NOT in its local database, the controller will decommission the module by setting its Node ID to zero. Before introducing a Continuum IOU module that has been previously commissioned to the LON network of an SP-AC1 or SX-SSC controller, decommission the IOU module using the steps below: Attach the module to an empty Net Controller that is powered down with its battery removed. For a Net Controller II, in order to be absolutely sure that the Net Controller has an empty database, you may need to clear its backup in flash from a browser or by the use of the reset IP switch. See LL on how to use the controller's reset IP switch to clear its flash backup https://community.se.com/t5/Building-Automation-Knowledge/How-to-clear-the-controller-flash-backup-from-the-hardware-using/ta-p/5877 Power up the Net Controller Once the CPU led on the Net Controller starts blinking, press the 'Reset' button on the IOU module. Wait 30 seconds to make sure the decommissioning process has completed. Power down the Net Controller Remove the IOU module

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue There is a limit of around 200 user-created objects in b3/i2 devices, once that limit is reached, an attempt to create a new object of any type in the device will result in  "Invalid Handle" error. See https://community.se.com/t5/Building-Automation-Knowledge/Creating-an-object-in-a-BACnet-B3-or-Infinet-controller-results/ta-p/9490 for more info.   Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum b3920 Controller Continuum i2920 Controller Cause Each Continuum object is represented in the system by a "Handle Id", in b3/i2 devices, the handle ID is stored in the controller as a byte value which allows for a maximum of 255 handles, the system objects (System Variables etc.) use around 55 of the handles leaving around 200 for user-created objects.  CX controllers store handle IDs using a 2 bytes value, which allows for 65535 handles, CX controllers rarely run out of handle IDs. Resolution One way to deal with this limitation in the Continuum field devices is to combine InfinityNumeric, InfinityDateTime objects (when possible) into one object configured as an array (manual log).   EXAMPLE: The screen capture below shows 10 InfinityNumeric objects in an i2920 device that are used in the control application of a room named "MainLab"     Let's say for the purpose of this illustration that the following is the control program for MainLab     Since InfinityNumeric objects MainLab.a thru MainLab.j are used exclusivity to store values *** (i.e Setpoint etc), we can configure one of the objects as an array and have it hold all 10 values, thus allowing us to delete 9 InfinityNumeric objects and free 9 handle ids       Before deleting MainLab.b thru MainLab.j we need to modify ALL references to those objects, instead of referencing MainLab.b - MainLab.j we need to reference MainLab.a[1] - MainLab.a[9], note that MainLab.a holds its value (70) normally (not as part of the array), so in this case, we are only using 9 of the 10 array elements.     ***IMPORTANT Only InfinityNumeric and InfinityDateTime objects that are used exclusively to hold a value should be combined, if the object is being used for any of the following operations then it should be left as its own object.   Object triggers one or more programs Object is configured as a log Object is Occupancy flag of a schedule Object has alarms associated with it or is alarm point Object is a setpoint

Issue Out of range alarm attached to i2 device does not work when point's value is out of the range. The 'Alarms' system variable in the controller shows 0 Product Line Andover Continuum Environment CyberStation All i2 devices All InfinityControllers Cause Out of Range alarm is a BACnet alarm and can not be used with Infinity points Resolution Use Expression or Infinity Low/High Limit alarm type.

Issue MSTP controllers go offline when changing the MaxMaster value in the Automation Server from it's default of 127 Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server MSTP Master Controllers Cause The MaxMaster value is being set lower than some or all of the MSTP controllers on the network Resolution EcoStruxure Building Operation supports MSTP Master controllers in the address range 0-127 (often refered to as the node id). The MSTP network is a token passing network where the token is passed around the network, until a controller has the token it cannot 'talk' to other devices.   The MaxMaster value is defaulted to 127 to allow all devices on the network to receive the token and reply to online status requests, send values etc. If the MaxMaster value is less than any of the MSTP Master controller addresses then those controllers never receive the token and cannot respond to online status requests.   The value for the MaxMaster needs to be equal to or greater than the highest addressed MSTP controller node id.  For example, if the highest node id=54 then the MaxMaster will need to be set to 54 or higher. For maximum efficiency the MaxMaster should be set 1 or 2 greater than the highest controller address, this allows for adding future devices without needlessly polling for many non-existent devices.    Please refer to BACnet MS/TP Network Properties – Basic Tab or Configuring the MS/TP Network for b3 Communication