Issue Can ping the controller and access the controllers configuration webpage but cannot bring the controller online in Continuum. Environment BCX9640 Cause Windows Firewall is on Resolution Disable firewall.

Issue Some modbus device documentation indicate that there are 6 digits in a register to obtain certain information Environment Continuum Xdriver Modbus Cause The Modbus xdriver only allows for 5 digits  Resolution The modbus range is from 0-65535, so 6 digits is too large Some PLCs used the 40,000 and 30,000 notation which embeds the function code in the address. For example: 30,001= function code 4 start address 0 30,234= function code 4 start address 233 40,001= function code 3 start address 0

Issue Running a trend report on extended log data, only the first objects trend data is displayed. Environment Continuum CyberStation Trend Report Cause The default of the maximum number of values is 100 when a trend report is selected. . Resolution  Make the maximum number of values 10000 and it should bring in all the data when selecting trend.

Issue Need to connect xPModule away from the b3/i2 controllers. Need to know what is the maximum distance it can be installed using a ribbon cables. Environment Infinet II (i2) or BACnet (b3) families: i2/b3 920, i2/b3 810, i2/b3 814, i2/b3 850, i2/b3 851, or i2/b3 853. The bCX1 Controller/Router models. Cause There is a limitation of the length of the cable being used. Resolution Either the 3-foot or 10-foot ribbon cable can be used.  A total of 10 feet of cable may be used for all Expansion Modules.

Issue The PIN attribute of personnel objects has some limitations on visibility since it is considered sensitive information, this is the reason why Personnel PINs  do not show up in the personnel editor (it shows as ****) or List views. Environment CyberStation Cause Function as designed. Resolution One way to generate a report that shows all personnel objects PIN is to create a CyberStation program that prints the PIN to a file (or some other print destination) The following is a sample of a Looping CyberStation program that accomplishes the above. -------------------------------- Numeric CNT, OK File NEWDATA Object thePerson OPENINGFILE:   OK = OpenFile("C:\Temp\ALLPINS2.TXT", WriteOnly, NEWDATA)   If OK = Failure then Goto ENDING Else Goto PRINTTOFILE PRINTTOFILE:   OpenList("Personnel", thePerson, Root)   While GetObject(thePerson) is Success     Print thePerson PIN to NEWDATA   Endwhile CloseList(thePerson)   Goto CLOSINGFILE CLOSINGFILE:   OK = CloseFile(NEWDATA)   If OK = Failure then Print "CANNOT CLOSE TEXT FILE" else goto ENDING ENDING:   Stop --------------------------------

Issue What personnel attribute allows a card to only start working at a future time/ date? Is it ActivationDate or StartDate? Environment Access Controllers: ACX5720, ACX5740, NetcontrollerII, ACX780, ACX700, AC1, AC1-A, AC1-Plus, CX9900, ACX57xx, NCII Cyberstation, Access Control, Personnel StartDate, ActivationDate, ExpirationDate. Cause After setting the StartDate or Activation date on some systems, the card still operates even if the date is in the future. Resolution The ActivationDate attribute was added to Continuum V1.82 and above, it is only supported in the Netcontroller II & the ACX57xx controllers. So systems with Cyberstations older than V1.82 or that use CX9900 (Netcontroller 1) with AC1 series modules, ACX780 or ACX700 do not support an Activation date and will start to operate as soon as the personnel has been saved and distributed to the controller. The ExpirationDate is when a card will stop working and operates on all products / versions of Continuum. The StartDate is just a personnel information field to define when an individual started with the company.  

Issue When backing up the Continuum Database using SQL Server Management Studio the backup fails.  SQL indicates Status = 112  Environment Continuum SQL SQL Server Management Studio DB Backup Cause Insufficient disk space to hold backup file. Resolution Remove files from hard drive to free up a sufficient amount of storage space.

Issue What user account type does Continuum require to run correctly What could be causing Continuum or parts of Continuum to stop working or crash Environment Continuum, XP keywords: Account, user, Power User, Administrator Poweruser, Pinpoint, Graphic Cause User log in account may be blocking access to programs or files, can stop Pinpoint graphics from being edited. Resolution XP Once Continuum is installed using a Windows "Administrator" account, a Windows "PowerUser" account will give sufficient access to allow Continuum to run. If a Windows "User" account is used, some parts of Continuum will not operate correctly or may crash. We publish no information on what needs to be enabled/allowed/unlocked to allow a windows "User" or other such account to operate correctly. It is possible to set up an account correctly to run, but this would need to be set up by an IT expert on site, and updates/upgrades to Continuum may require the account setting to be changed.

Issue After setting InfinityOutput to a pulse value the value prints as ON even when the relay is physically OFF Output print format is set to $### and output is NOT inverted or overridden. Environment All CXs All b3s All i2s Cause Function as designed Resolution When an output is commanded to a pulse value (i.e. 5) the relay energizes and then de-energize after 5 seconds, the value property retain the last value the output was commanded to, in this case 5. The display format $### displays values greater than zero as ON, zero values as OFF,  and values less than zero as -ON. The print format should be set without the '$' to display the pulse value (5) To make the system show the actual physical value of the output print the OverrideValue instead of the Value.

Issue Where is more information on Secure View? What is Secure View? Product Line Andover Continuum, Pelco Environment Continuum Secure View Pelco Cause What is SecureView Resolution The UK Buildings Business of Schneider Electric Limited has released Continuum SecureView, the add-on application offering seamless integration between Andover Continuum CyberStation and Pelco Endura CCTV system. This integrated solution provides the user with a powerful interface featuring live and recorded video streaming, PTZ (Pan / Tilt / Zoom) camera control from within the Continuum CyberStation Workstation itself, plus the ability to control external video monitors and layouts. For further details: Contact Technical Services paul.bates@schneider-electric.com PA-UK-11.00001 Continuum SecureView.pdf

Issue Digital Sentry Control Point  and Cyberstation have conflicts with both pieces of software on the same PC. Environment Cyberstation Digital Sentry Control Point Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The Cyberstation Video Integration and Digital Sentry Control Point use the same API to communicate and could cause issues. Resolution This configuration is not officially supported or tested, although we have reports that say people are doing it in the field. The reason it is not supported is because they both depend on the same DSConnex API. Installing both may introduce Windows registry issues. (causing issues with whichever application was first installed). From the field Without Control Point installed controllers were online. If only control point is installed they can view Video once Continuum is installed they can no longer view Video. Both program work independently of each other but not together, last one installed works. The configuration of having Digital Sentry Control Point and Cyberstation Video Integration installed on the same PC is not supported. The reason that it is not supported is because both products use the same API (Application Programming Interface) files in order to display video. There could also be Windows registry issues particularly if different versions of the API files are getting installed by each application.   An example from the field If only Control Point is installed the site could view video normally. Once Continuum was installed, video will no longer display in Control Point. Both programs work independently of each other, however, typically the last program that gets installed is the one that will work and the first program installed gets broken, so that video will not display.

Issue Need to obtain points InstanceIDs to provide to third party vendor for system integration. Environment bCX4040 b3s devices Cause Third party vendor system integration Resolution The instanceID of a BACnet object can be shown in a List View. In a list view configuration add a column to display InstanceId, the id will be shown as two numbers separated by a forward slash '/', the number after the '/' is the instance id. i.e. 73009/59 In the example above 59 is the instance id. Note that in BACnet the InstanceId of an object is a 32 bit number where the ten most significant bits contain the object class and the other 22 bits is the actual id. CyberStation strips the object class when showing an object's instance id. If the RoamIO BACnet service tool is used it can be configured to display the full instance id without stripping the object type from the value.

Issue At times it is necessary to get the Cyberstation product and database version without launching Cyberstation Environment Cyberstation Webclient Windows XP Windows Vista Windows 7 Window Server 2003 Windows Server 2008 Cause Need the ability to get the Cyberstation version without launching Cyberstation Resolution Using My Computer or Windows Explorer Navigate to c:\program files\Continuum Right Click on Continuum.exe Select Properties Select Version Select Product Version 1.74.0.20070914= 1.74 with No Service Pack Ex. 1.74.0.20070914 SP2 = 1.74 with Service Pack 2   To determine the database version in SQL: Use the SQL Server Studio Management Express and open the table "dbo.ACCDBVersion". This will show the database version as well as the Enhanced Alarm Logging and Enhanced Alarm Delivery status. 

Issue AccTrace shows error  "SQLSTATE ERROR CODE: 37000" and "ERROR MESSAGE: [Microsoft][ODBC SQL Server Driver][SQL Server]Failed to load msxmlsql.dll." every extendedlog interval.   The ExtendedLog does not work and no log data are found in the Database. Environment SQL Server Cyberstation NetController. Cause The "msxmlsql.dll" file has been deleted from SQL server by an anti-virus software or the security setting changes. Resolution Obtain the msxmlsql.dll and msxmlsql.rll files from the SQL Server installation kit.  

Issue When closing Continuum 1.9x SU (SQL 2005 Express engine on a stand alone workstation),  it shows MFC error message of ACCDataServices and the Windows Event Log shows AlmUtil.dll error message. Environment Continuum SU 1.82 and higher version. Cause There are 3 Windows Schedule Tasks which are created during the DBInitialization->Creation of the Continuum SU workstation. Some possible causes are: If these Schedule Tasks are missing The Windows Schedule Tasks cannot be executed due to that fact that the current login userID is different than the one setup for the Schedule Tasks The password is not correct Resolution Manually create these 3 Schedule Tasks in the SU Cyberstation Alternatively: Uninstall SQL engine, Continuum Reboot the Workstation Reinstall Continuum SU, create a new DB from DB Initialization. Verify these 3 Schedule Tasks are created as below: CS_Distn CS_hrly CS_Minute

Issue The department names were created using all caps. When viewing the attribute after changing and saving to mixed case, it is still all caps.  Environment CyberStation (all versions) Cause Trying to change Department attribute from all caps to mixed case. The change will not save. Resolution When changing just the case of an attribute (like Department) and saving it, it will revert to what you had before the change because CyberStation does not regard a case change as a change. If you want to change the department, for example, from pss to PSS you need to change to something with different characters like pss1 and save it. Then change it to PSS and save it. Now it will be PSS.  

Issue At time it is necessary when troubleshooting to check specific communication settings on a comm port Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Specific commands needed to check communication parameters with precision and to edit them if necessary Resolution Examples of command line parameters needed for Xdriver modbus communication. Command Result p comm2 defaultbaud 9600 comm2 defaultbaud=baud19200 (To set) p comm2 defaultbaud 19200 p comm2 parity None comm2 parity=Odd (To set) p comm2 parity Odd p comm2 stopbits stopbits1 comm2 stopbits=stopbits2 (To set) p comm2 stopbits stopbits2 p comm2 datalength databits8 comm2 databits=databits7 (To set) p comm2 datalength databits7

Issue ACX5740 controllers are found to have lost configuration and programming after power loss.  Environment ACX5740 ACX5720 NCII BCX B4920 Cause Controller cannot restore data from flash memory due to the presence of corrupt or a flash backup that was saved before the controller was redeployed at another location or that has been upgraded to a different firmware version. Resolution From the controller configuration page select Clear Database Backup and commit changes to controller.  Reload the controller. Backup controller to flash to ensure that current information is backed up.

Issue Opening a pinpoint graphic from Continuum Explorer takes long time or cannot open with the error Timeout error.  Environment Continuum LAN with WSs' pointing the shared folder of the pinpoint files. Continuum SU with additional WSs' pointing the shared folder of the pinpoint files Cause It takes longer time for workstation to get connection to the shared folder on the network when the pinpoint is configured to use the ServerName\SharedFolderName (or IP_Address\SharedFolderName) instead of Mapped drive. Resolution Map the shared folder of the server to each workstation as a network drive and use the mapped drive name in the Options setting of the pinpoint editor. Also, check if the issue is related to a Windows profile. Create a new Windows Admin user and see if the slowness persists. If it doesn't then the issue is a corrupted Windows profile.

Issue The Continuum database is created with SQL Compatibility Level 80 (SQL 2000) instead of 100 (SQL 2008). Can this be changed? Environment CyberStation SQL Server Cause The Continuum database is created with a Compatibility Level of 80. This is the default level of SQL 2000. SQL 2008 has a default setting of 100 but Continuum database is still created with a Compatibility Level of 80 even using SQL 2008. Can this setting be changed?  Resolution Continuum SQL installations have always used SQL2000 Version 80 compatibility and are only tested using this configuration, SQL2005 Version 90 or SQL2008 Version 100 configurations are untested in releases up to V1.93.  Compatibility level 100 has been tested in version 1.94, and is supported.