Building Automation Knowledge Base

Issue Get error "Local TAC Vista server not started . Cannot reserve graphic object" when trying to edit a OGC graphic from TAC Vista Workstation. Can not start OGC editor from within TAC Vista Workstation Product Line TAC Vista Environment Windows Server 2008 Windows Server 2008R2 Windows 7 TAC Vista Server running as a Service Cause When using Windows 2008/7 the following legacy tools can not be used when TAC Vista Server runs as a service: TA Draw, TA Main, Database Generator, LIST.EXE, IPCL Editor, Test Client and UPGRFILE.EXE. For more restrictions for Windows 2008 and Windows 2007 see the release TPA-VSTA-11-0002.01 for TAC Vista 5.1.5. Resolution Run TAC Vista Server as an application.  Refer to Registering/Unregistering TAC Vista Server as a Windows service for registering/unregistering Vista Server as a service.

Issue What are the product certifications? Product Line EcoStruxure Building Operation Environment SmartStruxure for Buildings AS ES Cause Standards documentation required. Resolution Click here for the CE Declaration of Conformity Click Here for the WSPCert For  BACnet BTL Testing see the PICs statements or the BTL Website: http://www.bacnetinternational.net/btl/ For UL and Country of Origin certification, please refer to PSS for this.

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 How can duplicate Handle errors be fixed? Product Line Andover Continuum Environment All versions of Continuum CX, i2 and infinet Controllers Cause An SQL database gives every object a unique handle that is used internally to reference that object. If Continuum requests a value from an Input point that has handle 1234, but that controller has handle 1234 for example as a TimeDate point, then problems will ensue. Every object in the DB has a unique handle. This includes all classes: points, programs, graphics, reports, schedules, etc. Duplicate handles can be caused on sites where engineers use multiple databases during commissioning on new panels (maybe a Single User on their laptop), It can also be caused by importing dump files with handles created from other databases, or just from database corruption on the server from failures etc. It can also be caused by the use of an Infinity LSX280 see Handle mismatch issues. Resolution Usually reloading the controller will re-sync the controller and all of its object handles back to the site database. If the DB has become corrupted, run the analyzer and try to fixup (Clean) any issues You may even have to manually delete the offending objects, running the Import Export Fixup utility (See How to run the Import/Export Fixup Utility) Follow this with a controller reload Worst case would be to revert to a backup DB if it is found to be corrupt. To avoid issues altogether, it is best to engineer a project all from a single DB and take care when importing dump files.

Issue When trying to add an automation server underneath an enterprise server the following error is given. Product Line EcoStruxure Building Operation Environment Workstation  Automation Server Cause Something has been left behind in the automation server that causes a conflict. Resolution Reformat the automation server by performing a New database download. Create a backup of the automation server. See Backup of StruxureWare/EcoStruxure Building Operation AS and ES. Launch Device Administrator and add the automation server. Select the automation server and click on the Upgrade Device button in the top left corner.  In the Upgrade device window, choose "New database" in the Type of upgrade field. Click OK. Once the download is complete, log into the automation server and restore the database. See How to restore a StruxureWare Building Operation server backup set. Now add the automation server underneath the enterprise server.

Issue Database maintenance has been keeping the event and extendedlog tables trim and someone decides they want to see data from a period of time that has been truncated from the Database. Environment Continuum Cyberstation SQL Server ActivityEvent AlarmEvent ErrorEvent ExtendedLog Cause Table truncation scripts have removed the events that a report is to be populated with. Resolution We can run reports on user activity and access event activity going back only as far as the information that is stored in the Continuum Database. This information is stored in specific tables that are normally truncated on a regular basis. The amount of time this information is saved for may be different for each installation.  (See articles Stand Alone Continuum using SQL Server 2005 Express is not purging the ExtendedLog table and How to setup automatic table truncation on Single-User SQL Express systems on how this is setup on a single-user system.) However, there is one possibility to being able to provide this information. If there has been a vigilant database maintenance schedule maintained and there have been periodic backups of the ContinuumDB, then the information stored in those backups can be retrieved and reports can be run. This would require a setup of a separate Continuum system (SQL Server and Cyberstation) that is able to have these backed up Databases restored to it. Restore each backed up copy of the ContinuumDB Run the required reports against this offline version of the Database. Do this one Database at a time until all the required data has been gathered.  

Issue How to integrate I/NET with Pelco Analog Matrix in order to implement some features, such as: Switch specific camera image to specific monitor. Switch specific camera to specific preset and display it on specific monitor. Product Line TAC INET Environment I/NET Pelco CCTV system Pelco Matrix Cause In some projects there is demand for access control system to integrate with analog CCTV system to do the alarm interaction. I/NET can integrate with Pelco CCTV system with ASCII code communication. Resolution I/NET communicates with Pelco analog CCTV system through ASCII code. There are two kinds of communication port for Pelco matrix, which are RS232 and RS485/422. For RS232 port for matrix, an RS232 to RS 232 cable is needed. If there are no COM ports for computer, an USB to RS232 converter is needed. For RS485/422 port for matrix, an RS232 to RS485/RS422 converter or USB to RS485/422 converter is needed. Connect the I/NET server to Pelco matrix through this converter, and the steps below should be followed: Open the I/O Configuration of I/NET, and choose the port for text output port and baud rate for the port communicating. In the AMT, choose Edit--->Text Library, and click Add. Choose a point for alarm interaction, and the status of the point to activate the interaction: alarm, acknowledge, return to normal (RTN) and acknowledged/return to normal (RTN). In the text area, enter the ASCII code for matrix. For the two applications of the alarm interaction, different ASCII code should used: 1Ma1#a, which means switching 1# camera image to 1# monitor 1Ma7#a1\\a, which means switching 7# camera to 1# preset and display it on 1# monitor. Here "\a" is an escape sequences for I/NET, so we need one more "\". Then the integration with I/NET and Pelco CCTV system is finished. When the specific point goes into alarm, then the specific camera can be switched to specific preset and displayed on specific monitor. For more applications of the integration with Pelco analog matrix, refer to the documentation for the Pelco ASCII Protocol Manual. And for more information about how to set text output in I/NET, refer to Text Output through RS-232 Port in I/NET.

Issue Controller regularly warmstarts or resets every 5 minutes. The site was upgraded from a BAS system Product Line Satchwell Sigma Environment Sigma Controller 1 warm start BAS Wireshark Cause In Sigma each device (server, controller and DNN) must be unique, in BAS this was not the case as terminal and outstations could share the same number. The resetting controller is receiving requests for files or alarm data that was previously routed to a BAS terminal, the Sigma controller does not handle the data and resets/warmstarts.  The previous BAS terminal number would have been the same as the controller number, typically T1 and OSN1.  When upgraded to Sigma the BAS terminal number would have been changed to a new designation but some of the system configuration has not been updated correctly. Resolution Alarm routing:  Check that all the alarm routing in the object files (R1, R2, R3, and R4) are set correctly.  Some systems use single destinations such as T1, if this is found and the destination number matches a controller number then this must be changed. (See Node reset messages are received at regular time intervals after a BAS 2800+ to Sigma upgrade) To search for possible incorrect routing destinations use the latest Sigview utility and search for any alarm routing that matches a controller number. Note: Typically device number 1 is the issue, but this may not be the case in all situations and another device number may have been duplicated. Operlist.txt Files: Check that all the operlist.txt files have been modified to the latest version and none contain the older BAS format. For example the wrong entries are; 1 C:\Bas\Data\OSN2\ROUTESET.REC    ROUTESET.REC 1 C:\Bas\Data\OSN2\LOOKOSN.REC     LOOKOSN.REC 1 C:\Bas\Data\OSN2\PNTFLE.REC      PNTFLE.REC With Sigma can be; ;This is a dummy OPERLIST.TXT   (Note: CRLF (Carriage Return & Line Feed) after the line) The dummy operlist.txt file will be created automatically by Sigma if the existing operlist.txt file is deleted from the server and then a download to the controller is performed. Default/Backup server number: Using the Diagnostics - View Comms Stats, check that all the controllers on the system do not have the default or backup server number configured the same as a controller number. Logging Servers: Using the Diagnostics - View Logging Servers, check that no logging data sets have been created with a server number matching an existing controller number. Wireshark Trace: If neither of the above help then it may be possible to look at the Ethernet data packets being received by the controller (obviously will not work if the controller is on an ARCnet LAN).    Set up a laptop with Wireshark (see Using WireShark to analyse communications on an Ethernet network) with an Ethernet hub at the controller. Run the trace until a reset/warmstart is observed at the controller Save the trace and email to Product Support or add and apply the following filter to show only those data packets being sent to the controller: ip.dst==192.168.2.1   (Change the IP Address to match that used by the controller) Look for packets that appear to come from another controller (source IP address).  For example below shows a request for the Lookosn.rec file on controller 1 (fault with operlist.txt file).

Issue DBCreate unable to run after installation. If installing I/NET on new PCs or upgrading to 2.42 and DBCreate does not start after selecting it from Programs > I/NET > DBCreate. Product Line TAC INET Environment SQL 2008 Server 2008 Windows 7 Windows XP Cause The SQL Browser needs to be enabled in the Services to get it to run. Resolution Run the SQL 2005 Backward Compatibility 64-bit option or 32-bit based on the OS. Restart I/NET Configuration Editor Modify the active profile and click on the Connections button. Verify that the database shown is the correct one that is being connected to and click on the okay button. Start I/NET again and verify that you can login and start the program again. See Initialization Error when starting I/NET for information that may also be helpful.

Issue In earlier releases of continuum Pre Windows 7, The Badge software would attach to the cameras and import a photo directly to the Badge without any additional cost. Canon's SDK for the Powershot cameras is not compatible with Windows 7 Canon's SDK for the EOS line of cameras is compatible with Windows 7 but requires  a license in order to import photos directly into the badge. Product Line Andover Continuum Environment Windows 7 Continuum 1.94 Cause There are a limited selection of cameras that are supported and qualified with Epi Canon's SDK for the Powershot cameras is not compatible with Windows 7 Canon's SDK for the EOS line of cameras is compatible with Windows 7 Resolution See related article, An Epibuilder Plugin is necessary for some badging devices to work. Camera (Face) Options: Canon EOS Camera (high end cost / higher functionality) Tested on Windows XP Pro SP 3 & Windows 7 Pro Models currently tested: EOS Rebel XS and EOS Rebel T3 Interfaces through the EPI Canon EOS capture plug-in license

Issue Vista reports fail to save to the server when they are being edited from a remote workstation. Product Line TAC Vista Environment Vista Microsoft Excel Cause When setting up remote workstations on a LAN or WAN, there are certain steps that must be taken. If the proper DCOM settings are not set up on every remote workstation as well as the computer that runs Vista server, there can be authority issues. Vista reports can be created but will not allow values or trends to be saved into the report. In some cases this has generated the error "The RPC Server is unavailable" as seen in Error: The RPC server is unavailable. Resolution On ALL remote workstations and the main server: Run DCOM Config 1.0.2.2.exe found in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. Either select Server-Workstation or Server-Workstation-Webstation. On the main server that will be used to run Vista Workstation: Run > dcomcnfg Expand Component Services Open Computers Right-click My Computer and choose properties Go to COM Security pane For Access Permissions and Launch and Activation Permissions choose to edit both Edit Limits... and Edit Default... Add users Anonymous and Everyone with Remote Access Go back to Component Services and open My Computer Open DCOM Config Browse for OPCEnum right-click and choose properties Go to Security pane Change the three options to Launch and Activation Permissions   -Use Default Access Permissions                        -Use Default Configuration Permissions                -Customize Choose Edit > add Anonymous and Everyone with Remote Access Go back to DCOM Config and browse for TACOS right-click and choose properties Go to Security pane Change the three options to Launch and Activation Permissions  -User Default Access Permissions                       -User Default Configuration Permissions               -Customize Choose Edit > add Anonymous and Everyone with Remote Access

Issue Host conflict window always pops up, and cleaning routing table doesn't help. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause Host conflict is a normal issue happening in I/NET. It is usually caused by the duplicated host ID setting on different servers, or an engineer laptop is inserted into the network with the same host ID setting with some server. And the routing table will be messed up since all the IP related information will be recorded in the routing table and it will be distributed to all the network devices, including all the servers and NPRs. The usual solution is to clear all the routing tables on all the network devices, . Refer to How to Remove the Routing Tables in a Device or PC about how to clear the routing tables. But if the routing table is cross referred, like Server 1 adding NPR 1 and NPR 2 as reference hosts, while NPR1 adding Server 1 and NPR 2 as reference host, the routing table will never be cleaned out since when you clean the routing table for Server 1, NPR1 and NPR 2 will still try to send their wrong routing table to Server 1. Unless all the network devices are disconnected and the routing tables are cleaned one by one, or disable the 50069 port for the whole network, which is used by the communication between network devices, there is no other way to clean them out. And these two method are not applicable sometimes. Resolution If the routing table can be managed well, such kind of issue will never happen. The best practice on adding reference host and creating routing table is: On the servers: Choose one server as the master reference host. All the other servers add this server as reference host. Don't add NPR as reference host. All the NPRs can be added into the master server by clicking on the NPR button in I/NET configuration and added one by one manually. By this way, the master server can build its own routing table without impacted by other devices. And this one is the only routing table in the whole network. On NPRs. If NPR doesn't need to talk to other NPRs, like transferring indirect points, there is no need to add reference host for NPR. If indirect points are needed, just add the master server as the reference host. Then this NPR will be able to see all the other NPRs based on the routing table on the master server. If the master server is not equipped with UPS, or not always promises to be online, another master NPR can be chosen as a secondary reference host. Add this NPR as a reference host to all the servers and other NPRs. Under this scenario. if the routing table needs to be cleaned, only the master server and the secondary reference host need to be cleaned. It will be more easier to clean all the routing table and get rid of the host conflict error.

Issue Unable to create a backup of an I/NET Seven Database using DBCreate, gets a backup failed error. Product Line TAC INET Environment Windows XP, Windows Vista OS, with SQL 2000, 2003 and 2005. Cause Functionality of the host pc and the database seems to be inconsistent. Resolution Option 1: Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy INetDb.mdf and INetDb_log.ldf to an alternate locations (located in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data) Restart all SQL Services. Launch DBCreate and remove the existing I/NET Seven Database. Create a new I/NET Seven Database. Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy the saved INetDb.mdf and INetDb_log.ldf over the newly created files. Restart all SQL Services. Launch DBCreate and attempt a backup. Option 2 (If Option 1 does not work) Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy INetDb.mdf and INetDb_log.ldf to an alternate locations (located in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data) Uninstall and Reinstall I/NET Seven. Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy the saved INetDb.mdf and INetDb_log.ldf over the newly created files. Restart all SQL Services. Launch DBCreate and attempt a backup. Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue When I/NET is running under Windows 7, there will be a display issue about alignment. The font size has been changed to smaller - 100%, but still no use.  Product Line EcoStruxure Building Operation, TAC INET Environment Windows 7 Cause Be sure to try I/NET Seven Windows fields not aligning correctly on workstation's display to change the font size first to see whether it can help. If not, continue to the next information. I/NET used the default MS Sans Serif font to display everything. But something has changed in Windows 7 about the font display.  Research showed that many users with high resolution monitors (particularly LCD flat screens) were running the monitors at lower resolutions than the native resolution of the screen. This was usually because at the native resolution, the fonts were becoming too small to read, so the users would decrease the resolution. Windows includes a facility to increase font and window sizes while keeping the screen at the native resolution.  This is a much better method of increasing the font size as it can produce much smoother images by using many more, smaller pixels. The really significant issue is, unlike CRT monitors, flat-panel LCD monitors have a fixed pixel size, or "resolution", and that when users change to a lower resolution (in order to increase text size) the system has to re-sample the lower-resolution display image into its fixed resolution causing a significant degradation in display quality: not just text looks worse, everything looks worse. A change was made for Windows 7, to set the screen resolution to the monitor's native resolution and if the screen is over a certain resolution to default the font size 120 DPI (dots per inch). This is approximately 125% of normal 96 DPI (100%). When the system defaults to 125% DPI it also adjusts the MS Sans Serif font to be bigger.  If the user then decides to set the DPI back to 100%, then TrueType fonts, which are scalable, adjust as expected. But the bitmap MS Sans Serif font does not: it remains at the larger size, hence this issue. This problem does not occur if Windows 7 keeps DPI at 100% when it is first installed. So anyway, when the default font size is Medium - 125% instead of smaller - 100%, probably the solution below is needed to solve it. Resolution Go to the Registry Editor, and find HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts. Find the entry MS Sans Serif 8,10,12,14,18,24. The original value is set to SSERIFF.FON on a system which started at 125% DPI. Set to SSERIFE.FON on a system which started at 100% DPI.  Notice that one character of the file name changes from F to E. Restart the computer, and make sure the font size is set to smaller - 100%. Refer to I/NET Seven Windows fields not aligning correctly on workstation's display about how to set font size. Then it should go back to work.

Issue Alarms generated from Sigma controllers are not received at the Sigma server. Product Line Satchwell Sigma Environment Sigma software - All versions Controller firmware - All versions Cause The controller generates the alarm correctly, but is unable to send the alarm to the Sigma server. This can be seen by using the "Comms Stats" request from the Sigma server. The screen shot below indicates that the "Alarm buffers" have 21 alarms waiting for transmission. Resolution To identify the cause of the problem, carry out the following steps. Perform a "Comms Stats" request of the controller from the Sigma server, to establish that an alarm has been generated. Confirm that the Client configuration has been correctly set up by referring to Alarms are not displayed in the Sigma local or remote client Alarm Manager window. Confirm that the Sigma server has been correctly configured in "System Setup / Networks and Devices". Confirm that the Sigma server IP Address matches the address set in "Network Connections" Upload an object with an alarm programmed from the controller, and check that the routing page has no references to "T" present. (T was used in the BAS2800+, but is not in Sigma). Confirm with the IT department that there are no network issues.

Issue Alarms being generated in I/Net are not showing up on the Enterprise Server. Product Line EcoStruxure Building Operation, TAC INET Environment SmartStruxure Integration with I/Net Alarms Cause Alarms generated in I/Net are not populating on the Alarms Window on the ES, all masking are set on both the AMT Configuration and Host Masks. When the point goes into Alarm, it populates the Alarm Window type, whether it is Priority or Critical with said point address. However, it does not show up on the Alarms page because the bin files on the controller needs to be updated to the latest version of software and all points need to be saved prior to integrating with SmartStruxure. Resolution When integrating with SmartStruxure, all controllers are supposed to be updated with the latest version of software as well as sav files, per Resetting a 7793 Controller and PCU (Applies to 7793, 7716, 7728, 7756). Once completed, recheck the points by putting them in Test mode so that they can generate the Alarm condition and it should show up in the ES Alarm now.

Issue No Messages Received in AMT from specific Link or Site Product Line TAC INET Environment I/NET Seven Xenta 527-NPR Xenta 527 Web Server NPR2000 Cause There are many causes outlined in AMT not receiving Data which show reason why AMT may not be receiving data. In some cases the issues is not due to programmatic issues but network Errors. I/NET uses UDP port 50069 to broadcast data from NPRs and Xenta 527s to any listening host device. While this does give the flexibility to have multiple hosts receive the same packet, it prevents the proof of delivery that a TCP packet provides. You can read more about UDP at this link. http://en.wikipedia.org/wiki/User_Datagram_Protocol Resolution  To prove a network error, use the following methods: Verify everything listed in AMT not receiving Data If feasible, repeat those steps above direct connected to the Xenta 527 via crossover cable. Ensure Window Firewall is disabled on the local PC when performing this task. Once you have a PC that will receive Messages while direct connected, re-connect the 527 to the network and use the same PC to connect to try to 527 over the network. If AMT works or fails based on being on or off of the network, then this is a networking issue. The PC, Domain Server, or Internet Service provider are all capable of blocking I/NET communication. This can be done by either blocking traffic going out of the PC(s) to the NPR/527(s), or it can block traffic from the NPR/527(s) to the PC. On a PC Windows Firewall these are referred to as outbound rule and inbound rule respectively. Please note the following conditions when certain parts of the network traffic are blocked. Traffic Blocked on traffic from NPR to PC Traffic Blocked on Traffic from PC to NPR Both Blocked You can connect to controllers in I/NET, values will update and you can control points You cannot connect to controllers in I/NET, values will not update and you cannot control points You cannot connect to controllers in I/NET, values will not update and you cannot control points AMT does not receive data from the blocked Link or Site AMT does not receive data AMT does not receive data   To Correct a PC Windows Firewall Issue: You will be able to prove a windows firewall issue by turning off the PC firewall for a few minutes and testing AMT. If traffic resumes, this is the cause. Open Windows Control Panel If needed, change "View By" from Category to Small Icons Click on Windows Firewall Select Advanced Settings Click on Inbound Rules Click on New Rule in the Actions Pane Select Program and click Next Browse to the InetIoSrv.exe application on your PC. Click Next Select the Action to Allow the connection and click Next   Set the Rule to apply to all locations. Click Next Name the Program and Click Finish. AMT Should begin to receive data. If not, repeat step 1 to verify this is a PC firewall issue and contact Product Support for additional assistance. If the data is being blocked by the network and not the PC Firewall: Contact your network administrator and explain that the Xenta 527 or NPR 2000 must be able to broadcast UDP data on UDP port 50069. This path must be open on every hop between the device and the PC. Verify that both the PC and device are on the same Windows Domain. Typically, UDP traffic will not travel outside of the Domain. If you are unable to get network blocked removed, you may be forced to put all I/NET devices and PC's on a single subnet.

Issue The TGML page is dynamic but looks static. Product Line EcoStruxure Building Operation, TAC Vista Environment Vista StruxureWare Interface Cause In the Release Note, page 30 says: It is possible to navigate to a TAC Vista Webstation TGML Graphic through a link in a SmartStruxure TGML Graphic. To achieve this connection a link object is created in the SmartStruxure TGML Graphic which is linked to a SmartStruxure hyperlink object that holds the TAC Vista Webstation TGML Graphic page address. Example of a hyperlink objects address in SmartStruxure that is linked to a TGML Graphic in TAC Vista: HTTP://ip_address/webstation/LoginPage.aspx?page=TgmlGraphicsPage.aspx?objectId=3074949137 Note: This will always require a login by a valid TAC Vista user, even if the TAC Vista Webstation auto login feature has been activated. Resolution The example link above is referring to a static page. For example, if the TGML page is dynamic, you will see the following in the copied link (see bold). HTTP://ip_address/webstation/LoginPage.aspx?page=TgmldynamicGraphicsPage.aspx?objectId=3074949137 You can also read the following in the release note: In order to determine the TAC Vista Webstation URL for a TAC Vista Webstation TGML Graphic the following TAC Vista Web Setting configuration must be in place: Optimized TGML Loading is deactivated Folders pane is set to Standard HTML With these settings it is possible to right-click a TGML object in the folders pane and select "Copy Shortcut." This will copy the TAC Vista Webstation URL to the clipboard and it can then be pasted into a SmartStruxure hyperlink object address field. After the shortcut has been pasted, it will have to be modified in order for the TAC Vista TGML Graphic to be displayed properly in SmartStruxure. The modification is marked with bold in the example below: Copied: HTTP://ip_address/webstation/TgmlGraphicsPage.aspx?objectId=3074949137 Modified: HTTP://ip_address/webstation/TgmlGraphicsPage.aspx?objectId=3074949137 If the link you copied was a dynamic TGML the link will look like: HTTP://ip_address/webstation/TgmldynamicGraphicsPage.aspx?objectId=3074949137 and should be modified as this HTTP://ip_address/webstation/LoginPage.aspx?page=TgmldynamicGraphicsPage.aspx?objectId=3074949137 Also reference the TAC Vista Webstation Graphics Links and SmartStruxure Integration tool on the Community.

Issue When Remote Alarm Manager attempts to initialise the GSM modem it fails during reset command. Modem will reset correctly if the same commands are sent from a terminal emulation program. Product Line Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Vista RAM Sigma Ram MicroNet RAM BAS RAM GSM Modem Cause The result codes from the modem are not returned in the format expected by Remote Alarm Manager Resolution The Mobile Equipment Errors setting (AT+CMEE) sets the format that error responses from the modem are returned in, the possible formats are: 0 disable result code and use ERROR instead 1 enable result code and use numeric values 2 enable result code and use verbose values The GSM driver in Remote Alarm Manager expects to see these results in numeric format. To Check and set the format do the following: Using a Terminal Emulation Program such as Hyperterminal connect to the modem Enter the command AT+CMEE? to show the current setting Enter AT+CMEE=1 Enter AT&W to store the current settings to non volatile memory. Disconnect Hyperterminal and test with Remote Alarm Manager.

Issue Both comm ports can be enabled for RTU, but is this a recommended configuration? Product Line Andover Continuum Environment Continuum 9900 9940 9680 9640 5740 5720 Xdriver Cause 2 port can be enabled for RTU Xdriver on a netcontroller, but is this a recommended configuration or will this be too much of a strain on the Controller? Resolution According to the Xdriver developers, it is NOT advisable to use 2 Modbus RTU Xdrivers on the same Controller  The Modbus RTU Xdriver is the only 'poll on demand' type xdriver and this dual configuration has the potential of holding the CPU for longer and could cause the polling to become irregular. It is recommended to add an additional Controller to handle the additional devices and points required. Also see BCX Controller can use Comm 1, Comm2, or both ports for Modbus RTU X-Driver Can two comm ports be enabled when using the RTU Xdriver?

Issue This is a guideline to do air balance settings (airflow calibration) on a VAV ASC using a I/STAT or M/STAT. Product Line TAC INET Environment MR-VAV-AX MR-VAV-X1 MR-VAV-X2 Cause The air balance company needs a procedure to properly set up the MR-VAV-AX products for the air balance settings. Resolution Understand the cooling setpoint is 75°F, and the heating setpoint is 70°F. This information is important in knowing which state the system is trying to control. While in the PP mode of the I/STAT, it is important to verify the setpoint is 75°F. This allows Test & Balance to set the temperature to: 77°F for maximum cooling 72°F for minimum cooling with no fan 68°F for heating mode - minimum primary airflow with fan To verify the current setpoint, use the Select key and scroll up to Set Temp. The I/STAT will display the current setpoint. For testing purposes as described in Step 1, if the temperature setpoint is not 75°F, press the + or - key to raise or lower the setpoint to 75°F. In order to enter the Service Mode, press the Service key. Enter the I/STAT password 183. Press the + or - key to see the left most digit change accordingly. Press the + key to scroll to 1 and press Enter. The cursor on the I/STAT will move to the center digit. Press the - key to 8 and press Enter. Now the cursor will move to the right most digit. Press the + key to 3 and press Enter. You are now in the Service Mode. While in the Service Mode, the Service key is the escape key and the Enter key will allow the controller to accept your desired changes. The first step in the calibration process is to make sure the controller is at the Factory Calibration Setting (FCS). Press the Select keys to scroll to Airflow Parameters (AP) and press Enter. CLF is displayed on the I/STAT. Press the Select keys to scroll to FCS, press Enter. The I/STAT will display NO. Press the + key to change the display to YES and press Enter. Press the Service key to back up one screen. To verify duct diameter (dd) press the Select key and scroll to Unit Parameters (UP). The I/STAT will display the current duct diameter as 10.0 (default of 10 inches) unless the value has already been changed. Press the + or - key to raise or lower the value, and the Select keys to move between the right most and center digit. Sample: 8 inch box is displayed as "08.0" Press the Enter key to allow the changes to take place. Press the Service key to back up one screen. To verify Cooling Low Flow (CLF) and Cooling High Flow (CHF) setpoints, press the Select keys to scroll to Airflow Parameters (AP) and press Enter. CLF is displayed on the I/STAT. Press Enter, the I/STAT will display the current value. Note that CFM is displayed as KCFM, for example 0.50 = 500 CFM. If the values are correct, press Enter. If the values need to be changed, use the + and - keys to change the values and the Select keys to move the cursor from the left most digit to the right most digit. Once you have the desired value displayed, press Enter. The I/STAT is now displaying CLF. Press the Select keys to scroll to CHF and press Enter. If the values are correct, press Enter. If the values need to be changed, use the +, -, and Select keys to change the CHF to the desired value then press Enter. CHF is displayed on the I/STAT. Press the Select keys to scroll down to Calibrate Primary Low (CPL), press Enter. The VAV controller will modulate the damper to maintain its design CLF. The I/STAT is currently displaying the CFM the controller is reading. Note that during this process, the CFM value may go to -0.1, 0.0, etc.; the controller is calibrating itself to the 100% actual closed position. Once the CFM comes within 10% of the CLF setpoint, the ON/OFF LED will turn on. While the LED is on, the controller is not modulating the damper and the controller has the damper in a fixed position for approximately 60 to 90 seconds. (Do not attempt to enter any values at this point. When the LED goes off, the controller takes back control of the damper and will modulate it to maintain CLF.) Once the airflow has stabilized and the I/STAT is displaying the CLF CFM, measure the airflow and input the actual value (do this as soon as possible because once the + or - key has been pressed, it freezes the damper into a fixed position to allow enough time to enter the actual value and to minimize chances of the actual CFM changing), into the I/STAT using the +, -, Select and finally the Enter key as described in Step 8. Important: Even if the current reading is correct, press Enter. The I/STAT will display Calibrate Primary High (CPH), press Enter. The VAV controller will modulate the damper to maintain its design CHF. Again, once the CFM comes within 10% of the CHF setpoint the controller's ON/OFF LED will come on and the controller will perform as described in Step 9. When the LED goes off, the controller takes back control of the damper and will modulate it to maintain CHF. Once the airflow has stabilized and the I/STAT is displaying the CHF CFM, measure the airflow and input the actual value (again, do this as soon as possible) into the I/STAT using the +, -, and Select and finally the Enter key as described in Step 8. Important: Even if the current reading is correct, press Enter. The I/STAT should be displaying CLF. Once the low and highs have been calibrated, press the Service key. Press the Select key to scroll to Operational Parameters (oP), press Enter. Press the Select key again to scroll to Prove Performance (PP). This mode will place the program's Room Temperature in a test state. The I/STAT display will toggle between the current CFM and the room temperature. This step will allow the balance engineer to verify proper operation of the VAV controller to maintain the design maximum and minimum airflow. Press the + and - keys to increase or decrease the room temperature in order to manipulate the system to control between cooling and heating as described in Step 1. Once the VAV has controlled the damper to design minimum CFM, the balance engineer can adjust the fan (if applicable) to design airflow. Important: If at any time during the calibration process, (not during Prove Performance (PP)) a mistake is made, make sure that the controller is reset back to the Factory Calibrated Settings (FCS), (see Step 4) and restart the calibration process. Also, if the VAV box does not control the CFM within the maximum allowable percentage, normally within 10%, go back to Step 4 and restart the calibration process. For further information see the following: TCON126 (Micro Regulator Controllers and I/STAT) TCON147 (ASC MR-VAV-AX) TCON155 (ASC MR-VAV-X1) TCON165 (ASC MR-VAV-X2) Go to TCON Number and Title Cross Reference (with links) and download the TCONS above.