Building Automation Knowledge Base

Issue Having difficulties binding (pairing) room controller with MPM Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) SE7000 Room Controller Cause Unable to make sense of LED blinks status Resolution The room controller cover needs to be removed to expose the LED located on the ZigBee communication module.   Here is a description of the LED status for Sigma Room Controllers (SE7000 Series): Blinks once: ZigBee Communication module is powered but might be defective or incompatible with the room controller base board. Blinks twice: ZigBee Communication module is compatible with room controller base board but cannot see any ZigBee network in its range that matches its own channel and PAN ID. Blinks 3 times: Room controller has joined the network successfully but it is not bound to MPM. Blinks continuously: Room Controller has joined the network and is placed in identify mode by MPM during the binding process. Blinks 4 short and 1 long: Thermostat is bound to the MPM and is communicating.

Issue What card readers and technology can be used with Continuum Access Control Systems Product Line Andover Continuum Environment Continuum Cause Need to know what card readers will work with Continuum Access Control Systems Resolution The card reader and card technology is not relevant to the Continuum Controller, as this is used between the card (tag, fob or other) and the reader. This allows the use of the standard technologies available today, including fingerprint and other biometric based access as well as cards, fobs and tags. The signal that comes from the reader must be serial data input type Wiegand or ABA (or Clock & Data) USB, Ethernet, RS485, RS232 inputs are not accepted. NOTES The exact input type and maximum data bits can only be determined by checking the hardware, firmware and Continuum version combination being used. Retina, fingerprint, facial recognition and other biometric based systems that are connected to Continuum Access Controllers will store the biometric information and still be connected via the serial data Wiegand or ABA to the Continuum Controller. The current Continuum access controllers also accept an 8 bit burst for PIN numbers from keypads See Where can I find datasheets, install guides and other information on HID Electronic Access Control products? ABA (or Clock & Data) this was often used with Magnetic Swipe technology which has mostly been phased out Standard Wiegand Formats within Continuum Infinity 37-Bit AC 4+4 32-Bit Wiegand 26-Bit CK 34-Bit G 32-Bit HIDCorp1000 35-Bit - Some restrictions Custom

Issue After upgrading a TAC Vista system on a site with high IT security you can end up with a wrong schema version in the SQL database causing issues such as failure to insert trend log data. Environment TAC Vista SQL Cause In some versions of TAC Vista, the SQL database upgrade carried out during the installation of TAC Vista doesn't upgrade the SQL database to the newest version. The first time you start TAC Vista Server, the server (TACOS) carries out the remaining upgrade steps. On a site with very high security standards, TAC Vista Server is however not able to apply the last SQL database upgrade scripts as those can only be carried out by the IT department directly on the SQL server, and as a result the SQL database is not fully upgraded. Resolution   1.      Note exactly what schema version the SQL database currently has This can be checked through SQL management studio with this query USE taclogdata; SELECT dbo.DSS_SchemaVersion() AS Db_SchemaVersion 2.      Note exactly what version of TAC Vista you have upgraded to 3.      Contact PSS to get a SQL upgrade script specific for the site and run that on the SQL database

Issue BACnet Broadcast Device Table (BDT) on a BACnet Broadcast Management Device (BBMD) becomes corrupted after a server version upgrade, only if the BACnet BDT was taught from another BBMD The following upgrades have this issue v1.5 to v1.6, v1.6 to v1.7, v1.7 to v1.8 Product Line EcoStruxure Building Operation Environment BACnet Broadcast Device Table BBDT BDT Management BBMD Cause When a BDT is manually built (or BBMD first created), BDTE00001 is always set to the Server IP address. In the example this is 192.168.1.15 When the BDT is taught from another BBMD, the BDT is changed and BDTE00001 is modified. When a Server (Enterprise or Automation) is upgraded (V1.5-1.6, 1.6-1.7, 1.7-1.8), then BDT entry BDTE00001 is changed to it's own IP address. Thus the Servers BBMD BDT can be corrupted with the Server IP address appearing twice in the BDT Resolution The taught BDT can either be set manually, before the upgrade, so it does not get corrupted by the upgrade process or be corrected following the upgrade. Option 1: Change the BDT before the upgrade The BDT Entry BDTE00001 should be set to the IP address the Server that contains it. The BDT Entry (BDTE00002 in the simple example above) that held the IP address of the Server should be set to the value that was in BDTE00001. Option 2: Correct the BDT after the upgrade For the first Server being upgraded Upgrade the Server Log into the Server and view the BDT from WorkStation Multi-select and delete all entries, Then manually reenter in all the BDT entries. For all remaining servers being upgraded Upgrade the Server Log into the Server and view the BDT from WorkStation Multi-select and delete all entries From the First Server BBMD do a teach Verify the BDT table is in the Server Below would be the first upgraded Server as option 2 or a corrected as option 1   NOTES Versions 1.8 and beyond include a fix so that the "BDT Teach" Mechanism does not allow the BDTE00001 to be changed. A hotfix will be available in V1.7 Upgrading to a fixed version will not correct the issue, one of the two resolutions above will still need to be completed.

Issue Enterprise Server and the B-OWS capability Environment SmartStruxure site Cause Enterprise Server and the B-OWS capability for viewing BACnet Operator Workstation Resolution The Enterprise Server is a native BACnet/IP protocol operator workstation and controller with a built-in web server. The Enterprise Server also serves as a BACnet/IP Broadcast Management Device (BBMD). The Protocol Implementation Conformance Statement (PICS) document details the BACnet Interoperability Building Blocks that are supported in StruxureWare Building Operation. The PICS are available from the BACnet International labs for BACnet Operator Workstation (B-OWS) Continuum 1.9x The below screenshot is of a StruxureWare Building Operation 1.3 Release and the desired connection using B-OWS to a Continuum 1.94 Release. Workaround is on the BACnet Interface of the ES, highlight the IP Network then Add New BACnet Device. 1. Suggested name would be the Cyberstation Name 2. Upload from BACnet device 3. Instance ID is the Device Node ID (Right-click/Edit on the Cyberstation) 4. Create Then perform an Upload from the newly created Cyberstation. Resulting View from the Enterprise Server: (Note that Cyberstation owned objects are not available in the Enterprise Server) There is an “official” document on Continuum and StruxureWare Building Operation BACnet communication that was produced specifically for this issue. It is a TVDA produced by the Buildings StruxureLab and it is Andover Continuum BACnet with StruxureWare TVDA 1.02

Issue How to completely uninstall and remove TAC Vista 5.X.X Product Line TAC Vista Environment TAC Vista 5.1 and later versions Windows OS (Windows XP, Windows 7 tested) Cause Occasionally it is beneficial to be able to remove a TAC Vista installation completely, removing any indication it was ever installed. Resolution When using the full SQL version not administered by TAC Vista: Backup SQL database named “taclogdata”. Use the backup function in SQL Server manager. Save the database outside of the Microsoft SQL folder Server and TAC root directory (usually C:\Program Files\Schneider Electric (note: TAC Vista 5.1.3 and prior will have path C:\Program Files\TAC instead) and C:\Program Files\Microsoft SQL Server). Backup TAC Vista database using backup function in TAC Vista. Stop SQL manager, Task manager/processes – stop sqlserv.exe and sqlagent.exe if running. Remove all TAC Vista hotfixes using the uninstall program in Control panel Add/Remove programs. Remove TAC Vista Server 5.x.x using the uninstall program in Control panel Add/Remove programs. If additional TAC programs like TAC toolpack, TAC Xbuilder etc. are installed remove them as mentioned before. Remove SQL (Microsoft SQL Server 2005) using the uninstall program in Control panel Add/Remove programs. Delete remaining uninstalled TAC folders (usually C:\Program Files\Schneider Electric, TAC Vista 5.1.3 and prior will have path C:\Program Files\TAC instead). Delete remaining files in C:\Program Files\Common Files\TAC Shared. Delete remaining uninstalled SQL (Microsoft SQL server) folders (usually C:\Program Files\Microsoft SQL Server). Check to see if TAC needs to be removed from the registry – Start, Run, REGEDIT. Find the registry key folder HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDll Remove all keys containing “TAC Shared”, e.g. C:\Program Files\Common Files\TAC Shared\TACADDON01_ENG.dll. If applicable - Remove SQL from registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft \Microsoft SQL server. Reboot. If SQL Server (TACVISTA) still listed under Services, please follow steps in SQL server service cannot be started during Vista 5.X.X installation to solve the issue. See How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 for steps to completely remove TAC Vista IV.

Issue Attempt to download license and see the below error. Failed to request license Error: Failed to store licence file Exception HRESULT:0x8007051B) (0x0000051B)   Failed to request license Error: Failed to store licence file Exception HRESULT:0x8007051B) (0x0000051B) Product Line EcoStruxure Security Expert Environment Security Expert Cause This error could be caused by a folder permissions issue. Usually occurring when Security Expert was installed without proper permissions to edit the folder or parent folder of where the license is stored. Alternatively it can be caused by a domain user account and local user account having identical names since Security Expert doesn’t know which user to check the permissions of when trying to save the license file. Resolution The possible solutions are shown in the order that they should be attempted: Right click the Security Expert license folder, (usually "C:\ProgramData\SchneiderElectric\SecurityExpert\License")and ensure that the Windows user has permissions to modify and view the contents of the folder. Ensure that the there is no local windows user with the exact same name as a domain windows user (e.g. LOCALHOST\admin, as well as ACME\admin). If this is the case change the name of one of the windows users so it doesn’t exactly match the other.  Perform a manual registration. Generate the .req file, go on the Licensing page, fill the form and download the license file. Then use the Browse button to import you license in Security Expert.

Issue Create smooth rotation for an object in a Vista TGML graphic Product Line TAC Vista, EcoStruxure Building Operation Environment TGML Graphics Editor Cause If the "CalcMode" is set to "Discrete" the object will rotate the full specified range instead of taking the duration time to slowly move around it.  Resolution Add a <rotate> tag to the object that will be rotating. Add an <animate> tag to the rotation. Set the properties for the animation: Animation = default state (Start/Stop), if a binding is ultimately used to control when the animation occurs, bind to this attribute. AutoReverse = should the animation continue in one direction or get to the end of the animation and then come back to the beginning? (True/False) CalcMode = determines whether the animation is smooth or jumps from end point to end point of the animation. For rotation, choose Linear. (Linear/Discrete) Duration = the amount of time in seconds that the animation should take. Higher numbers result in slower animation. Freeze = if true, the animation will pause at the last position when Animation is set to False. Otherwise it will revert back to the starting position. (True/False) Repeat = how many times should the animation occur. Default value is "Forever" but this value can also be set to any integer number (1, 2, 3, 4...) From, To = depend on the desired animation and target attribute. For rotation 0 to 360 is typical. Attribute = for rotation, the Angle property of the <rotate> tag is animated from 0 to 360 degrees. For more information on CalcMode see ‘Animation Overview’ in the Help.

Issue When the Sigma client attempts to connect to the Sigma server it fails and reports an error "No Seats Available".  What is the maximum number of clients that can be connected to a server? Product Line Satchwell Sigma Environment Sigma version 4.08 Client connections Cause Sigma server is not licensed for the attempted client connection Resolution For a customers system check: 1.  The Sigma dongle is licensed for the number of clients to be connected.  From a working client see Help - About and the number of clients supported is shown in the brackets ().  The maximum allowed depends on the operating system where the OS itself limits the number of consecutive connections; Windows 2003/Windows 2008 server:  Maximum client connections is 10 Windows XP/ Windows 7:  Maximum client connections is 5 2. Run the file C:\Sigma\bin\Setupsvr.exe and check that if a local client (on the same PC as the Sigma server) that "My Computer" is ticked or for a remote client (not the same as the server PC) that the "My Computer" is un-ticked and the correct Sigma server IP Address is entered. 3. Also in the Setupsvr.exe for a remote client check that the HTTP Server Port is set the same as the Sigma server (default = 8080) 4. Close down another client to free up a seat 5. Purchase more licensed clients (seats) using ZSO_CLIENT-x (where x is the number of additional clients - max 5 for Windows XP/7 server and max 10 for Windows 2003/2008 server).  Must add the Dongle number to order.    For an engineers laptop (Local connection) running SigmaX check: 1. SigmaX 7.0.9 does not require an unlocking code, if your using an older version of SigmaX you will need to uninstall SigmaX and install SigmaX version 7.0.9. SigmaX 7.09 no longer unlocks Sigma (or BAS2800+). To unlock Sigma you will need to install the SBO (Verision 1.5, 1.6, 1.7, 1.8 or 1.9) or EBO license administrator (Version 2.0 or later) and unlock Sigma using the current EcoStruxure Building Operation Evaluation License. The evaluation license is available to download form the Schnieder Echange Extranet web site. Latest version of SigmaX download provides some information on the changes in SigmaX version 7.0.9 and provided a link were the software can be downloaded. 2. If the Ethernet connections have been enabled or disabled (i.e. laptop has been with IT or wireless switched off/on) then a new SigmaX code will most likely be required. 3. Run the file C:\Sigma\bin\Setupsvr.exe and check that "My Computer" is ticked.

Issue Need requirements for email notifications Environment Continuum Cyberstation Email Eventnotification Outlook 2007 (32bit Only) Outlook 2010 (32bit Only) Cause Requirements for sending email notifications with Continuum Resolution Here are some requirements for forwarding Continuum workstation alarm events via email and paging: The Continuum workstations that have been designated primary and backup email and/or page handlers must have a MAPI-compliant email client such as Microsoft Exchange or Outlook. The email client application must communicate with an existing email server application, such as MS Exchange Server. The primary or backup email/paging workstation must be running Continuum at the time an alarm is generated. Each EventNotification object associated with the alarms that you wish to email or page must have its own email distribution list in the personal address book of the client email application using a specified naming convention as outlined in the table below. This email distribution list must be stored in the first address book shown in the list of available address books in the email client application. For example, if you create an EventNotification distribution list in the Personal Address Book in Microsoft Outlook, then the Personal Address Book must be the first one showing in the address list dropdown box when you open the Address Book. How to Create an EventNotification Distribution List Note: The following steps are based on Microsoft Outlook(32bit). Other mail applications may have different menu names and choices but the general procedure is the same. Open the Address Book for the email account on the Continuum workstation that will be providing the email/paging services. Your toolbar may have a button for this. If not, use the Address Book option of the Tools menu. Select New Entry from the Address Book File menu. Select the entry type Personal Distribution List and put this entry in the Personal Address Book. In the Name field enter a name for the distribution list using the following format: For E-mail: ACC.name For Paging: ACC.page.name where name is the name of the EventNotification. Add members (the email addresses or pager and service numbers of those to whom the notification of the alarm will be sent) to your personal distribution lists. Set address book options so that the address book where your personal distribution lists are stored is the first one to be searched when sending emails or pages. ** Ensure that there are not 2 PCs using the same email account for Outlook.

Issue System was running fine with EBO version 3.2.3 and Active Directory (AD) integration. But after upgrading to EBO version 2022 no AD user could login to the ES. The Workstation Error when trying to login is: User_Not_Associated_With_A_Group And the error message seen in the ES trace log is: WinES\server\nsp_servers\csc\accountaccess\source\AccountAccess.cpp(486) Workstation Error: User_Not_Associated_With_A_Group (0xc002a) in module Account_Access(28).  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause The Windows AD integration performance in EBO was improved in version 2022 by storing and comparing the SID for the AD-groups. During the upgrade from version 3.2.3 to EBO 2022 all EBO groups should have been updated with an AD-connected group SID. This was not done as the AD server was offline when doing the upgrade of the ES. Resolution If turning on the below property in the properties the old way used in EBO version 3.2.3 of matching groups during logon will be used: In the "ES.properties" file usually placed in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\etc\config add and save: NspServer.Windows.Group.MatchByName = true   To utilize the AD performance improvement in EBO 2022 re-connect the AD group to their respective EBO group. This is done by changing the "Windows group name" property in the EBO group to anything else or an empty string and then change it back to its proper value, i.e. the AD group name. Doing so should correctly populate the hidden "External SID" property for the EBO groups that is missing as the upgrade was done with no connection to the AD server.  

Issue Getting DCOM errors when trying to access WebClient and need to determine which of the various permissions have not been set properly. Product Line Andover Continuum Environment WebClient IIS Cause DCOM permissions have not been set properly. Resolution Open EventViewer, go to System Events, and note the DistributedCOM error. Open the error and find the CLSID that it is referring to. In the DCOM Config, look through all of the DCOM objects and find the one with the matching CLSID. Make sure that it has the correct permissions according the WebClient installation document. If this does not resolve the problem, you can also consult WebClient most common installation problems for further troubleshooting steps.

Issue Replacing Satchwell Sensors with Schneider Electric part numbers Product Line Field Devices Environment Sensors Cause Cross referencing older 'T' type sensors to the current version. Resolution Outside Sensor DOT2301 , DOT0001, DOT0002 is now STO600 Immersion Pipe Sensor DWT1701 (125mm), DWT1702 (200mm), DWT0001 is now STP660 (note, if replacing sensor only then DWA0001 required). Strap On/Pipe Contact Sensor DST1601 , DST0001 is now STC600 Duct Sensor (mainly FCUs) DDU1803 , DDU0001 is now STD670 Duct Sensor DDT1701 (300mm) , DDT1702 (460mm) , DDT0001 is now STD660 Room Sensor DRT3453 (sensor only, no setpoint adjust) is now STR600 For other DR and DRT sensors see Replacements for Satchwell sensors Drayton Room Sensor A701 is now STR600D Drayton Outside Sensor A702 is now STO600D Drayton Immersion Sensor A703 is now STP600D Drayton Strap On / Contact Sensor A704 is now STC600D

Issue VSB valves have been substituted by the Schneider Electric V211T valve VSB..F valves have been substituted by the Schneider Electric V211 valve VMB valves have been substituted by the Schneider Electric V311T valve VMB..F valves have been substituted by the Schneider Electric V311 valve Product Line Field Device Environment VMB VSB Cause The existing actuator is not compatible with the replacement valve as it is a different type. Resolution Schneider Electric  are no longer supplying VSB and VMB valves. They are replaced by a Schneider Electric Venta valve. Note: VSB and VMB valves are still manufactured by Controlli. VSB 2 ports are replaced by the V211T, VSB..F is replaced by the V211. VMB 3 ports are replaced by the V311T, VMB..F is replaced by the V311. The existing actuator will no longer fit on the new valve and needs to be replaced as well. If the actuator was a Controlli MVB22, MVB26 or MVB28, then replace with MV15B-230 actuator. If the actuator was a Controlli MVB46, then replace with MV15B-24 actuator. If the actuator was a Controlli MVB36, MVB52 or MVB56 then replace with M800 actuator. For compatibility: V211, V211T, V311 and V311T Venta valves are directly compatible with the Forta range of actuators e.g. M310, M400, M800, M1500, M3000, M700, MG900 and the MV15B-24/230 and no linkage kits are required.

Issue MSMQ error starting Continuum. "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ." Environment Continuum loaded on a Microsoft Operating System computer Cause MSMQ has become corrupt on this PC. Resolution Continuum cannot be installed on XP HOME(XP Professional only) Verify that the msmq service is started Go to Add/Remove programs > Add/Remove Windows Components does not give the option of installing Message Queuing. Go to a DOS Prompt and change your directory to C:\Program Files\Continuum\Install (cd \Program Files\Continuum\Install) Run the batch file Runafterreboot.bat (This will reinstall the Continuum version of MSMQ. NOTE: Most recent versions of CyberStation RunAfterReboot.bat has been renamed InstallMSMQ.bat Run the batch file and re-boot the machine then run Continuum ** In some cases Windows Add/Remove programs may not completely remove MSMQ and a utility like Revo Uninstaller may be helpful in getting a clean uninstall, so that a reinstall is successful.

Issue BACnet b3 or Infinet i2 controller shows version 0.000000 Product Line Andover Continuum Environment BACnet b3 Controller Infinet i2 Controller Cause The Controller is likely to be in bootloader mode, this can be confirmed by looking at the CPU flash speed. If you can count the flashes it is likely to be in bootloader mode see CPU LED flashing rate  Resolution Reflash the controller OS with the firmware compatible with the Continuum installation on site, using "Update b3 OS" or ""Update Infinet2 OS" NOTE - An ACX57 with Comm1 set to Infinet is unlikely to be able to communicate with an i2 device in bootloader mode, in this case an NC2 or other NetController may be required

Issue TAC Vista Server fails to start or "hangs" during startup. "Ensure TAC Vista Server is started" error, after having just started Vista Server and attempting to open Workstation. Product Line TAC Vista Environment Vista Server Cause Corrupt Vista database Bad installation of TAC Vista Resolution Troubleshooting technique to determine if you have corruption of the TAC Vista Database or TAC Vista Software. Determine if the TAC Vista Server is starting by observing the Tacos.exe process in Windows Task Manager. Server is crashing if Tacos.exe is not present or disappears after starting the Server. From the Start Menu, navigate to TAC Vista Server Setup and browse the Vista Server database location to a test location, i.e. :\DBTest. This will create a new "blank" database at that location. Attempt to start TAC Vista Server and observe results in Windows Task Manager. You should get one of two results: If TACOS.exe process is running and the Server seems to start correctly, you may have a corrupted Vista Database. You may further investigate by copying the site Vista Database folder structure and placing it on another computer (with the same Vista Software version) to see if the Server will start. In some cases, it may be successful, a backup can be made and restored to site machine. In most cases, it will also fail. Restoring to a known good backup is the only recourse.   If TACOS.exe process is not running and the Server seems to start incorrectly, you may have corrupted Vista Software. It is recommended to follow the uninstall/ reinstallation procedure for your version of Vista. You may further investigate by copying the site Vista Database folder structure and placing it on another computer (with the same Vista Software version) to see if the Server will start. In this case, it should be successful.

Issue Programming a 7798C controller with a Virtual HHC Console Environment 7789C HHC Hand Held Console Cause The 7798C controller can only be programmed with the Emulated HHC Console (The TacHHC.exe is located in the support folder of the INET install CD) using CBL 082 connected to the PC and RS 232 port on the controller. Resolution Before following these steps, make sure you have closed down I/NET, AMT and the InetIOServer applications.    Locate the HHC file on the I/Net CD, Support Folder and copy it to the Root of I/NET. Once copied, double click on the file to launch it, I/NET should not be running at this time. Connect the CBL 082 (Grey shroud connects to the PC)  The virtual HHC is displayed at this time. Right Click and Select the Com Port and Baud Rate. To Set the Controller Type: On the HHC, select Code 90, Enter to set the Controller Type. To Set the Controller Address Select "DCU Address" Enter he desired Address To Set the Baud Rate Code 06 for C-LAN Code 91 for Sub-LAN baud rate. To Direct Connect Once completed, disconnect the CBL 082 from the PC and replace it with CBL 072 for a direct connect to the controller. Start I/NET and open the configuration editor, create a new profile for a direct connect, if it has not been created already. Make this configuration active, close the configuration editor down as well as I/Net, and then restart it again. At this time communications should be established with the controller and the user can start programming the controller. 

Issue How to calculate the required disk space that will be used by WebReports? How to know if SQL 2008 R2 Express (with Advanced Services) will have adequate storage space for the sites Reporting requirements? Product Line EcoStruxure Building Operation Environment WebReports 1.9 / 2.0 Cause Require the ability to forecast how much space will be required to store and retain data within the Building Operation WebReports database. Resolution The attached Excel Spreadsheets can be used to forecast how much space is needed to store and retain the Building Operation WebReports database. WebReports_DB Usage Calculator.zip WebReports_DB Growth Estimator 2.0.zip Note that SQL 2008 R2 Express only allows a database size of 10 GB, so if your configuration is more extensive than that you should probably consider using the full SQL Server 2008 R2 editions. As a quick indicator here are the record sizes for each object type stored in the report server database: Object Type Size per record (bytes)   WebReports versions <1.8 >1.9   Ext. Trend 140 165   Meter 170 140   Alarm 900 500   Event 400 520  

Issue Unexplained network and communication errors IT department may have set up IP blocking or set up IP switches incorrectly or there may be an issue with the Continuum setup Product Line Andover Continuum Environment IP network Cause Problems in the IP network, port blocking or incorrectly setup in IP switches IT departments may say their system is set up correctly, but this may need to be tested. Resolution See Router required open port numbers to run a Continuum system for IP port requirements See Continuum Controllers and IP Managed switches for other IP switch settings Get all the problematic equipment connect to a simple non managed IP switch (this will probably involve temporarily moving PCs and/or controllers) Disconnect from the site IP switches if possible (this may not be possible, depending on the site setup, eg. SQL server may be in a server room) PC and Controller settings (IP address, subnet mask, default router) may also need to be temporarily modified depending on the original site set up. Test the system with this temporary setup, if all is ok then the problem lies with the site IP network, if the problem persist then  look at the Continuum setup (Cyberstation install, database, operating systems, hardware issues)