Building Automation Knowledge Base

Issue When reloading controllers, Continuum reports the following error: "An error occurred while installing the directory service." Product Line Andover Continuum Environment Continuum Alarm Points Cause A Continuum object is referencing a point in a controller that is offline or that requires a reload. Resolution Either reload the controller that owns the referenced point, or restore communication with that controller.

Issue After selecting a project and opening an application, WorkPlace Tech 5.7.7 successfully connects to a controller.  The monitor tags update.  After disconnecting and opening a second application (same project), WorkPlace Tech cannot connect to the controller. At the top of the window, it indicates that it's connected but the monitor tags remain gray.  The application downloads successfully but that does not help with the monitor tags. The only way to resolve the issue is to close and re-open WorkPlace Tech.  This action allows the first application to connect successfully to the controller but not any subsequent applications. Environment WorkPlace Tech 5.7.7 Cause Import of existing applications Resolution When a computer has been upgraded to WorkPlace Tech 5.7.7, the Projects folder is typically cut & pasted from a previous version. Any application that was from a previous version of Workplace Tech must be rebuilt within version 5.7.7. This step has corrected the gray monitor tag issue in several instances. This applies to both the MNL and MNB product lines. For more information, review Appendix B of the WorkPlace Tech Tool 5.7 Engineering Guide Supplement (F-27356).

Issue Clarification regarding Vista's OPC server and OPC client functionality. Incorrect configuration can cause unexpected results and crash the system. Product Line TAC Vista Environment Vista Server Vista OPC Server Cause There is some confusion as to the usage of the OPC server object in TAC Vista workstation. Resolution TAC Vista OPC Server TAC Vista OPC Server is an add-on module to TAC Vista Server, which enables third party OPC-compliant presentation systems to interface with TAC products. All objects and signals in the TAC Vista Server database can be read and changed via the OPC Data Access interface. Vista OPC Server is implemented as a Windows service and can be started from the Computer Management console.  A license is required, but no configuration is necessary in workstation TAC Vista OPC Client The TAC Vista database has to be programmed and configured as an OPC client, using the TAC Vista OPCTool. Simply browse the available OPC servers, select the objects to be added to TAC Vista and then from the tools menu select "Create/update TAC Vista objects...". When the dialogue opens up, browse to the appropriate location and select the OPC server object to be updated. If this is a new OPC client, right-click in the dialogue and select New->Device-OPC server. The object's properties will then be set by OPC tool after clicking on the select button. !!Do not create an OPC server object in Vista and set the program ID to TACOS.OPCServices.DA.1 and the Class ID to {7EA83597-0B54-4BAF-9EE5-D30AA9EB4D6D}. This will create a loop in the system and cause unexpected behaviour. There should be no OPC server objects in Workstation if TAC Vista is the OPC server!! read and changed via the OPC Data Access interface. to interface with TAC products.

Issue Controllers IP address needs to be changed but any attempt to do so results in the IP address reverting back to what it was previously configured for. Product Line Andover Continuum Environment Continuum CX9702 BCX controllers NC2 controllers ACX57xx controllers Cause The Controller has hit the Flash writes circuit breaker and is no longer able to save any changes to Flash. This includes updating Device settings such as IP address and ACC Node ID. The controller error log may also contain an error similar to below when attempting to make any such changes.   10/08/2014 19:00:22.00 0x00004406         0x03b76100        0x0004cb68         0x003e2000        0x000007d1                                         DEVICE_ERR_ERASE_LIMIT      (Flash circuit breaker tripped. CX97XX code base) Resolution One of the two methods to reset the Flash circuit breaker listed below should then allow the controller to write to Flash again.   1. accstatusbackup = accbackupenable   For more information see Caution when using PE programs to perform an automatic flash backup on a controller.     2. INFFlashDisabled.   Create a numeric in the controller with the following name and alias:   INFFlashDisabled   A value  greater than 0 usually indicates that the flash circuit breaker had tripped, though in some cases you may find these errors occurring when INFFlashDisabled = 0. In either case, once the value of this numeric is set to 0 and applied,  the flash circuit breaker errors should stop.

Issue Having trouble communicating to an NPR or other I/NET hosts over a slow/busy ethernet. Product Line TAC INET Environment Any Version of Windows OS and Any Version of I/NET Seven Cause You can make I/NET more tolerant of communication delays over the IP network by making the following change. Resolution Open regedit. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\CSI - Control Systems International\I/Net 2000\Configurations. Select your active profile. On the right side, right click and modify the DWORD value "EthernetTimeout" and click "Decimal". The default value is 500mS or half of one second. Increasing this value will determine how long I/NET waits for a response over the ethernet before it gives up. Raise it to 1000, 2000, 2500, etc. and see if it helps. For additional information please see NPR's giving you "Host Lost - Host Restore" messages.

Issue Receiving error “Could not connect to server. Cause: System.Runtime.Remoting.RemotingException:Requested Service not found opening graphics in webclient Environment Windows XP Windows Server 2003 Windows Server 2008 Cause This issue usually happens after uninstalling and reinstalling IIS. The webclient and newgraphicsfiles virtual directories may have been added, but DNWACServerFactory was not. Since the DNWACServerFactory virtual folder is missing, it keeps trying to create itself, but it can't and it generates the error. Resolution Get all users out of webclient In IIS (Internet Information Services Manager) Right click on Default Web Site, select New> Virtual Directory Click Next In the Alias field type: DNWACServerFactory, Click Next Click Browse and navigate to C:\Progam Files\ Continuum\DNWACServerFactory Click Next For access permissions, keep read, run scripts and select browse Click Next, Click Finish Restart webclient and test out graphics

Issue After loading SigmaX on to a new laptop it does not run.  An error appears "The file SigInterfaceMfc.dll is not found." If accepted then another error message occurs, "The file SigShell.dll is not found." Product Line Satchwell Sigma Environment SigmaX Windows XP, 7, 10 Cause The Windows Environment Path "C:\sigma\bin" is not set when SigmaX was installed. Resolution Manually add the setting “c:\sigma\bin” to the Windows Environment Path. On Desk Top find the icon "My Computer". Using right hand mouse button select "Properties". Select the "Advanced" tab. Select the "Environment Variables" button. In the "System variables" window highlight the "Path" variable. Select the "Edit" button Scroll to the end of the "Variable value" text box and append the text string with “;C:\Sigma\bin\” Select "OK" buttons to close and save the changes (three times).   Also see similar KB article - SigmaX reports a missing DLL.

Issue Cannot get comms stats from the DNN or controllers below the DNN. Product Line Satchwell Sigma Environment Sigma Communication DNN RIP Listener Windows XP Persistent routes Cause The Sigma server 'learns' the network architecture by listening to RIP messages broadcast by the network DNN's.   This is performed by RIP Listener which by default is not enabled on Windows XP. Resolution Enable RIP Listener on the Sigma Windows XP server by; In Control Panel select 'Add or Remove Programs' From the left hand bar select 'Add/Remove Windows Components' Highlight 'Network services' and select 'Details' Enable 'RIP Listener'   Select 'Next' and then 'Finish' OR Add persistent routes as an addition to RIP Listener as a backup or if RIP v1 is not permitted on the system see Persistent routing on the Sigma server. Use the DOS Command ROUTE PRINT to list the dynamic and persistent routes, check that the gateway address and network addresses are correct.

Issue Do Xenta controllers support PT100/PT1000 sensors for measuring the temperature? Environment Xenta Controller TAC Menta PT100/PT1000 Temperature sensors Cause Requirement to measure the temperature using PT100/PT1000 Temperature sensors. Resolution PT100/PT1000 sensors are not supported within any of the Xenta controllers.  The following is a method to achieve this using Menta: When using PT100/PT1000 to connect to a thermistor input, Menta Logic is required to add a polynom using the expression block. It is also strongly recommended to implement some calibration software in Menta to allow for fluctuations in resistance for every input that PT100/PT1000 is connected to. If a sensor is replaced / changed, re-calibration will be required. Sample experiment results and Menta Logic's are available here.

Issue Does Continuum 2.0 SMTP alarm email support encryption? Product Line Andover Continuum Environment SMTP Cyberstation Cause There is a need for encryption on SMTP alarm delivery in Continuum. Resolution Continuum does NOT support encryption for alarm emails sent over SMTP from Cyberstation.

Issue What do the error codes mean on the SCX920 LCD display? Environment Infinet SCX920 SCX900 Cause What do the error codes mean on the SCX920 LCD display? Resolution See the attached 1995 INETGUID.pdf starting on page 4 for the LCD error code listing and troubleshooting tips. 

Issue What are the standard features of a Jace-6 and Jace-7? Environment Niagara G3 Cause Ordering them for a new job Resolution Each jace comes with Web Browser Support, Enterprise Connectivity Pack, and oBix Client/Server. For more details, review the License Form located on The Exchange Download Center.

Issue Performing a firmware upgrade on a reader expander module via the SP-C's web page will fail with the message: "Error - The module failed to restart in boot mode" Firmware update failure Product Line EcoStruxure Security Expert Environment SP-C, SP-RDM2, SP-MRDM2. Cause Cause 1 There was an intermittent communications fault hindering the update process. Cause 2 There are Smart Card Readers connected to the reader expander module, which are set to RS485 communication. This appears to be causing RS485 communication issues between the SP-C and the reader expander which is hindering the firmware upgrade process. Resolution For Cause 1 Run the module upgrade process again. For Cause 2 Physically remove all connected RS485 Smart Card Readers from the reader expander module being upgraded. Run the module upgrade process again. Once the reader expander firmware has been successfully upgraded, reconnect all Readers.

Issue Selecting/De-selecting Image Verification in AMT Environment I/NET site Cause How does one Select/Deselect Image Verification in AMT? Resolution With the inception of Image verification in AMT, the following steps should be used for the Selection and De-Selection process: For Selection, Open AMT, Select the Edit button in the Task Bar. Select Image Verification, in this editor the user can choose what they want to be displayed on the screen when the image appears. Select the Actions button, select Auto-Image Verification and select the doors that are being used for this application. Click OK, once a user who has access to these doors reads their card, their image will appear on the screen. Following these steps can do the De-Selection process: With the Image on the screen, select the Actions Button. A Check mark will be displayed at the Auto-Image Verification. Uncheck the mark and the Image will disappear. Note: An image needs to be associated with each individual.

Issue It is possible to browse and bind the public signals while working on MTA files on your hard drive, however this has repeatedly led to problems when downloaded due to differences in controller names between the MTA file and the controller name in the Vista database. Environment TAC Menta TAC Network Variables Xenta programmable controllers Cause Waiting until the application is imported into the network will allow the Vista database to automatically provide you with the correct controller name to the public signal you are wanting to use. You will have a database browse window rather then a file select window which is your indication that you are doing this the correct way. This method to reduces the chance of operator error. Resolution While generating your Menta application, do not set the Network Address while binding Inputs to the Network Variable option Complete the other parts of the application and import the .mta to the Vista Database using the System Plug In. Once the application has been incorporated in the Vista database you can then edit the application and browse the Network Address of the Input.

Issue Several doors need to be removed in an existing I/NET Seven System. What is the proper way to do this? Product Line TAC INET Environment I/NET Seven with Access Control Cause Steps to remove Doors in an existing I/NET Seven System Resolution It should be sufficient to just deselect the door from the tenant and then NETCON on one equalized client, the file master, or Standalone PC. If the door physically goes away, the next time an operator enters an individual or group that had that door it will display a * for the offline/deleted door. At that time just select "Unselected" option and that door will be removed from that list. If all trace of the door needs to be removed: Remove all access privileges from a door. Be sure to check System View to verify they are all removed. Remove the door from all tenants Connect to the Controller and select Edit>Controller>Doors Delete the Door Close of the Door editors and select Edit>Host Computer>Network Configuration Penetrate to the Door level and delete the door objects. Next, In the Resident I/O editor delete any points associated.

Issue Display the Text Value for a multistate point (e.g. enumerated SNVT) instead of the numerical value in a TAC Vista Graphic page. Product Line TAC Vista Environment Vista IV OGC Graphics Editor Cause A digital presentation will display the integer value of the enumerated SNVT by default (1, 2, 3...). Many structured SNVT types use default enumerations (e.g. HVAC_HEAT, HVAC_COOL, HVAC_OFF). Rather than setting up a customer dynamic text value each time, the standard enumerations can be displayed. Resolution Add a digital presentation to the Graphic page Browse in multistate point. Check the check box "Presentation format." Now the text will be displayed instead on the numerical value. To define custom texts for use with multiple points, see Creating custom Multi-state Text definitions.

Issue Alarm values from LonWorks units in TAC Vista Product Line TAC Vista Environment Vista Workstation LON devices ASCs Xenta 102-AX, Xenta 104-A, Xenta 121 Cause Vista Workstation alarm objects can be used to monitor SNVT values from LON devices and alert the user when a value has gone outside of acceptable limits. For example, An alarm in TAC Vista if the nviSetpoint of a Xenta 104-A goes over 75ºF. This could also be used on programmable controllers -- any point in the database -- to avoid having to make Menta programming changes in order to alarm a point. The only issue with a Vista Server Change of state object is that the Vista Server will need to be running in order for the alarm to be received and actioned.  If multiple change of state objects are to be used consideration must be taken into the interface type as these points will be polled every second to check the state so actions can be taken on an alarm condition. This can easily overload a Lonworks interface if it is already managing lots of messages.  Resolution Create an object of the type "Change of state Dynamic SNVT" Right-click and go to properties. Click on the ALARM tab. Type in the alarm text for the Alarm. In this case, the alarm triggers if the temperature is over 75°F, so set the High limit to 75. Go to the Object tab and browse in the point that you want to monitor. In reference property select value. Click ok Go to the monitored point, right-click and select properties, change the watch setting to "watch"

Issue An error occurred while installing DSS: Cannot Start Service Product Line TAC Vista Environment DSS Vista Installation Cause This error can be found when installing Vista 4.3.x or higher after selecting Vista Administration of the SQL database. In the Application Event Log you will have an error stating the following: Cannot start service DSSWriterService on Computer '.'. --Stacktrace- at System.ServiceProcess.ServiceController.Start(String[[,args) at System.ServiceProcess.ServiceController.Start() at TAC.DSS.Install.ServiceInstallTask.Install() --End of stacktrace-- The reason this is happening is because when you selected to have Vista Administrate your SQL database it created local PC accounts (TACA_PCNAME and TACM_PCNAME). The TACA_PCNAME account is used to start the TAC DSS Writer Service and that account does not have access to the file to launch it. The access problems are typically caused by installing Vista on Windows Server 2003 and the "Authenticated Users" group has been removed from the User group on the PC. Resolution Click "Yes" at the install prompt and let the installation complete. Right Click on My Computer, and select "Manage". Navigate to Groups found in System Tools\Local Users and Groups. Double Click the "Users" group. Click the "Add" button. Click the "Locations" button and select your PC at the top of the list and then "OK". Type in TACA_PCNAME and click "OK". Note: This error should only occur if you have a non default security scheme on the network or PC. You should consult the IT department to make sure the TACA_PCNAME account will not be removed from the User group which will cause this problem to return.

Issue What should I set the Access Server System variable to on Continuum access controllers? Environment CX9200, CX99xx, ACX57xx or CX9702 controller with an ACX780 or ACX700 controller. Access Server, AccessServer Cause Below are the different configurations and what their different AccessServer system variable settings mean. Unlike Infinity when changing the setting in the controllers the controller does not reset. It is best if you set the AccessServer setting to the ACC Net ID of the Primary Access server workstation. This will keep the Access Control system operational should there be any distribution problems. Resolution CX9200, CX99xx,  or CX9702 controller with an ACX780 or ACX700 controller. The CX can stay at the default of it’s own ACC Net ID. In the above configuration the AccessServer variable in the CX is ignored. The AccessServer variable in the ACX controller can be one of the following: AccessServer value set to 0 in the ACX (Default setting).This means that access validation of personnel records will only be done locally in the ACX. If the person is not found in the ACX or the person is denied access locally in the ACX the person will not get in. AccessServer in the ACX controller set to the ACC Net ID of the Primary Access Server workstation (valid values are 191-253). This means that access validation of personnel records will be done locally in the ACX first. If the person is not found in the ACX or if the person is denied access the controller will double check at the workstation to verify whether or not the person is supposed to have access. If the person is also denied access at the workstation then the person will not get in. If the AccessServer value in the ACX controller is set to the ACC Net ID of the parent CX controller it has no effect and is ignored. CX99xxor CX9680 controller with AC1 modules  or ACX57xx. The CX can stay at the default of it’s own ACC Net ID.  AccessServer value set to the CX’s own ACC Net ID (Default). This means that access validation of personnel records will only be done locally in the CX. If the person is not found in the CX or the person is denied access locally in the CX the person will not get in. AccessServer value set to the ACC Net ID of the Primary Access Server workstation (valid values are 191-253). This means that access validation of personnel records will be done locally in the CX first. If the person is not found in the CX or if the person is denied access the controller will double check at the workstation to verify whether or not the person is supposed to have access. If the person is also denied access at the workstation then the person will not get in. AccessServer value set to 0. This is not a valid setting for a CX controller.