Building Automation Knowledge Base

Issue Proper handling and preparation of existing .vsd files help eliminate the crashing and lockup of the Visio application. Product Line EcoStruxure Building Operation, TAC IA Series Environment Workplace Tech Editor EcoStruxure 1.9.x - 3.2.3 Workplace Tech 5.9.1 - 5.9.4 Visio 2013, Visio 2016 Note: This does not apply to Workplace Tech Editor EBO 2022 (and newer) and Workplace Tech 5.10.x Cause The product is affected by the version of Visio in use as well as the file size and unused objects in the drawing. Resolution When using Workplace Tech 5.9.x with Visio 2013 or 2016, the file has to be opened in "Compatibility Mode." DO NOT CONVERT. Illustration 1 While the .vsd file is open in Visio, not in Workplace Tech, use the "Reduce File Size" option and select the boxes in Illustrations 1&2. Illustration 2 In Visio 2016, after opening the "Inspect Diagram," (Illustration 3), select the first 3 boxes in the "Reduce File Size" option (Illustration 4). Illustration 3 Illustration 4 Save the file for use in the Workplace Tech Project or to be imported into your AS-P as a .vsd. Add the "cleaned" file to your project or import it to Workplace Tech Editor. Make sure the Visio 2013 or 2016 is at the most recent version and build. You can find this under the file/account/About Visio. If Version 1802 is available in your Microsoft Office update Channel, use it. Version 1801 was used in testing. For Visio 2013 Build 15.0.4971.1000 MSO 15.0.5007.1000 was tested (Illustration 5) Illustration 5

Issue Not able access a new MNB-1000 via its default IP address. It will not respond to when pinged. Product Line TAC IA Series Environment WorkPlace Tech all versions, WPT Version 1.50E and later Cause The ability to ping the MNB-1000 controller was removed starting in Firmware version 1.50E. All MNB-1000s are shipped with IP port disabled. Resolution Starting with firmware revision 1.50E, the ability to ping a MNB-1000 controller was removed; so any MNB-1000 controller at or above firmware Revision 1.50E will not respond to a ping. Reference Unable to ping the MNB-1000 (Plant Controller) using firmware Revision 1.50E or higher for further details. All new MNB-1000 controllers are shipped from the factory with their IP and MS/TP ports disabled. The Ethernet port is the only port enabled. The MNB-1000 controller must first be accessed via its Ethernet port. Once gaining access, its BACnet/IP port can then be enabled.  Note: Both BACnet/Ethernet and BACnet/IP ports should not be enabled at the same time. So if BACnet/IP is being used and once the BACnet/IP port is configured and enabled, then disable the Ethernet port. NOTE:  Firmware 1.537 made the MNB-1000 visible via the ping command again.

Issue Receive an error: "The user session is lost, no specific reason has been set." when logging into StruxureWare Building Operation WebReports from Internet Explorer (browser), while Reports from within Workstation work fine.  Receive an error: "The user session is lost, no specific reason has been set." when logging into StruxureWare Building Operation WebReports from Internet Explorer (browser), and get no Reports folder within Workstation. Login Screen appears as expected, but when attempting to log in with the user name/password; It times out and comes with the message 'Failed to establish connection with server.' Product Line EcoStruxure Building Operation Environment Building Operation WebReports 1.1 / 1.2 Cause The error is most likely due to ports been blocked and/or the incorrect port settings entered during the WebReports installation process. When installing (or upgrading) WebReports, you must enter this information on each occasion as this information is not retained from previous installations. If you need to change these settings, then you should follow the procedure detailed below. Resolution If installed on separate machines, then check the firewall settings and ensure the ports used for the Enterprise Server and the Report Server are not blocked.  If this does not resolve the issue or if you are running both the Enterprise Server and Report Server on the same PC, then the Enterprise Server port configuration during the WebReports installation may need to be changed.  This is achieved as follows: this, and follow these key steps: Run the WebReports Installation setup program, and at the Setup Type prompt, select Upgrade from... Proceed through the other options as normal. Once you reach the Reporting Agent setup, make sure you enter the correct URL (path and port number - this is unique for each installation) used during the Enterprise Server setup. Continue through the other settings as required - Ensure that any Path and URL ports are set correctly.  Once you complete these settings, the WebReports Installer package then goes through the following checks and installation: Checking Installation Requirements Pre-upgrade Configuration Installation of Reporting Agent, WebReports, and WebReports Service Post-Installation Configuration Installation PublishedReports After the above steps, the upgrade is completed. This will now allow login to the WebReports URL using your web browser. For additional assistance in installing/upgrading WebReports, refer to the online help website. 

Issue Will the Bond Sensor Input Channel contribute to the Door Forced and Door Ajar alarms? If so, does it have to be in conjunction with the Door Switch Input Channel? Environment Continuum Access Control Products CX9900 CX9680 AC1, AC1A, AC1Plus ACX5720, ACX5740 CX9702 ACX781 Cause Not sure how the Bond Sensor works in relation to the Door Switch and the various Door Alarm states. Resolution BondFailure is an attribute of the Door object that represents a fault with the Bond Sensor. The way this works is if Valid Access = True and the Door Switch = Open and the Bond Sensor = Open, then BondFailure = False. If Valid Access = False or the system sees the Door Switch = Closed but the Bond Sensor = Open then you will get a BondFailure = True. This is another attribute (BondFailure) that can be monitored with an AlarmEnrollment in addition to the DoorForced and DoorAjar attributes. A Door Switch needs to be used for the Bond Sensor to operate correctly, otherwise BondFailure will always be False after a ValidAccess if there is no Door Switch value. Note: The actual value of the BondSensor attribute in the Door object may not seem to update properly if monitoring with a ListView. For this to show the correct BondSensor value make sure that the attribute Source is set to "Live" instead of the default "Database". Note2: A bond senor (usually an output from a maglock) should not be used as an alternative to a door switch, as it does not give indication of the door position.  

Issue What are the intervals for Trends when using StruxureWare Building Operations Product Line EcoStruxure Building Operation Environment Enterprise Server or Automation Server Cause Questions regarding what the interval in time is for trending Resolution Intervals can be in Days, Hours, Minutes, Seconds, and Milliseconds. . Trend logs can be of different types and used for different purposes. All logs in StruxureWare use circular storage. The interval trend log collects data at a specific time interval. Each logged value is stored as a record in the trend log. Use this trend log when the logging interval is less than 1 hour. You create interval trend logs using WorkStation or WebStation. In WorkStation, you configure the properties of the interval trend log to meet the specific needs of your site. The interval trend log does not record the values between the intervals. An interval log checks the monitored value at each interval and records the new value if it differs from the previously recorded value by more than the delta. Delta is the difference between the current variable value and the last log value. To log a variable according to the time interval, use a delta of zero. You use an extended trend log to transfer records from a trend log. An extended trend log can be connected to a trend log or connected in a series to another extended trend log. Only one extended trend log can be connected to a trend log. You create and configure extended trend logs using WorkStation. The extended trend log is often saved on a higher server level with more storage capacity than the server of an ordinary trend log. This extra storage capacity enables the server to store more records before it overwrites old ones. The extended trend log can be viewed in a trend log list or a trend chart. Trend log lists and records can be exported in two different formats: CSV (Comma separated values) is a standard file format for digital storage of data structured in a table of lists form. The CSV format can be used by Excel and in databases such as SQL. XML (Extensible Markup Language) is a standard file format for structured data and can be use with a lot of different tools. One last suggestion is the number of records, depending on how many records you want to store is important. For example: a single one minute interval Trend Log, and for 66 day, that would be 99,792 records. The maximum is 100,000 on an AS, so take this into account when configuring. This is why Extended Trend Logging is important. Check out Maximum number using StruxureWare Building Operation (Scalability and Capacity) for information on trends and extended trendlogs.

Issue What are the setup requirements for a L-switch on a classic network Environment Loytec L-Switch Cause What is the best way to setup a L-switch in a Vista classic network. Resolution The best option for a L-Switch on a classic network is in the Smart Switch Mode. In this mode the L-Switch decides based on the destination address of the message, which port(s) the message will be forwarded to. This functionality isolates network traffic. The dip switch settings for this setup are shown here.  Here is a link to the Loytec manual for the wiring configurations.

Issue Need to Export a Trend log file without using Reports Server Product Line EcoStruxure Building Operation Environment SmartStruxure Workstation Cause Customer needs a log file, but does not have Report Server Resolution In Workstation, right click on a Trend and create a new Trend Log List View Once the List populates, click on the Icon showing a green arrow labeled .csv Save the file to an appropriate location. If this is a frequent action, save the Trend Log List View Please Note that this feature is not available in WebStation  At v2.0 WebStation introduced the option to export to Excel, creating an XLSX file, this can be opened in Excel and saved as a CSV if required (this option is not available if WebStation is directly logged on to the AS/P/B)

Issue How to connect a 4 wire PT100 or PT1000 sensor to a 3-wire RTD input. Product Line EcoStruxure Building Operation Environment Building Operation I/O Module 16 Ch RTD Cause Some PT100/PT1000 sensors have only 3 terminals to connect to. Resolution The wires to the sensor are often color marked in pair, like two red cables and two white cables. As we only have 3 terminals to connect to, the solution is to only connect 3 of the cables, and not connect the 4th cable.   As the RTD device also measure the resistance of the cables, to make a correct temperature reading, it is important that all three wires used do have the same length and resistance. Therefore, the fourth wire should NOT be connected in parallel, it has to be un-connected.

Issue MNL-800 LON SNVT Programming Standards Environment Workplace Tech Tool software (any version) MNL-800 controller application Cause Problems occasionally arise as a result of improper LON SNVT programming and configuration in the MN-800 device application.  These issues include problems with the re-commissioning of the updated controller and potential network variable mismatch situations. Resolution  The following standards will prevent these problems from occurring. Network variables MUST be manually indexed. This prevents issues with the network variables becoming renumbered when application programming changes are made. (See NOTE 1) Change the application "Program ID" any time network variables are added or removed from an application.  To change the "Program ID" use the WPT Hardware Wizard,  (See NOTE 2) Select Hardware Wizard from Application Menu Click [Next] in MicroNet Setup Wizard screen Change the displayed program ID by entering a different program ID or adding a suffix letter/number. Maximum length is 8 characters. Click [Finish] to save the changed program ID and exit the MicroNet Setup Wizard.  In addition, one method of minimizing the need to repeatedly change the "Program ID" as the application is developed and debugged is to add a few extra common SNVT input and output definitions when first creating the application, leaving them unconnected to the application program.  If one of these SVNTs is needed, it is available in the LON network image (XIF file) and it is not necessary to change the "Program ID". If the MNL-800 controller has firmware version 2.0 (or later) installed, the standard nci network variables do not have to be indexed as the highest numbered SNVTs in the application.  It is perfectly acceptable to number them as the first 17 indexed SNVTs. Note that there are 17 standard network variables (12 nci, 2 nvo & 1 nvi), not just ten nci SNVTs. SNVT variable names should be limited to 16 characters or less.  Longer names are accepted by the WorkPlace Tech programming tool but the names will automatically be truncated by the LON Network Management tool when commissioning the controller. In addition, when programming the MNL-800 applications with the WorkPlace Tech Tool version 5.0, or later, it is not necessary to put each MNL-800 application in a separate project. NOTE 1: If using the WorkPlace Tech Tool version 5.8 or above, you can use the "Object Indexer" to automatically number all the network variables for you.  This tool also includes functions for detecting duplicate SNVT index numbers and for detecting gaps in the assigned index numbers. NOTE 2: If using the WorkPlace Tech Tool version 5.8 or above, you can set an option in the Hardware Wizard to automatically generate a new ProgramID and reindex the network variables when compiling the application.  Please be aware that this automatic generation of the ProgramID will require the Echelon network image for this device to be updated in any Echelon compatible network management tool.  Please refer to the documentation for the network management tool to determine what actions will be required. For example, if Niagara was used to manage the LON network, then the old shadow will need to be deleted, a new one added, and the device points rediscovered and the device re-commissioned.  

Issue Troubleshooting guide for ASD bus communications. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Legacy Controllers ( GCM, MicroZone II, MicroFlo II, LIM, PEM, MN-ASDI) I/A Series R2 UNC I/A Series G3 ENC Building Operation Automation Server Premium ( Pre EBO 2022 ) I/A Series N4 Jace 8000 Cause Troubleshooting guide for ASD bus communications. Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. NOTE:  The ASD protocol is not supported in EBO 2022 or subsequent versions

Issue What are CZT, CXT, CXR Controllers? Why are CZT, CXT, CXR Controllers used? What is Proportional, Integral Action and Derivative control. Why does a controller deliver different pulse lengths to the valve and not drive it fully open or closed? What is Pb, IA, PID? Environment CZT CXT CXR DC1100 DC1400 Proportional, Integral Action, Derivative, Pb, IA, PID Cause What do these controllers do and what are their applications? What is Proportional, Integral Action and Derivative control. Why does a controller deliver different pulse lengths to the valve and not drive it fully open or closed? What is Pb, IA, PID? Why is a 0-10V Signal used? Why is a 3 point control / Open Closed actuator used? Resolution Proportional Controllers are used in applications where there are long time lags e.g. room control, return air control, storage calorifier (HWS). Where the controlling sensor is a medium to long distance from the heat/cooling source. An example of a proportional controller is the Satchwell CZT. Integral action controllers are used in applications where there are short time lags e.g. supply air control, frost coil control, non-storage calorifiers. Where the controlling sensor is a short distance from the heat/cooling source. An example of a integral controller is the Satchwell CXT or the CXR. The CXR is a controller where the supply air is controlled, but the setpoint is reset by the return air or space temperature, therefore the time lag is short. Other controllers that fall into this category are the DC1100, DC1400 again the controlling sensor (mixed flow temp) is located a short distance from the heat source.  The term proportional band (Pb) is where the valve is moved to a position proportional to the deviation from setpoint. 0-10V modulating actuators are generally used on these controllers. The term integral action (Ia) is where the valve is moved at a rate according to the deviation from setpoint i.e. the valve is given longer pulses the further away from setpoint, shorter pulses as it gets closer. 3 point control/pulsed pair/open-close actuators are generally used on these controllers. Further to proportional controllers, inherent offset (the setpoint is never quite reached) can be an issue. Integral action can be applied to remove this offset. These controllers are primarily proportional, but integral action can be found on them and is applied. Hence the term PI or PI controller. Derivative control is generally only found on BMS controllers and is used occasionally with PI control, hence the term PID. Here the derivative action moves the valve proportionally to the change from setpoint. It is complex and is rarely used. Further detail about CSC controllers can be found here. Further detail about CXT controllers can be found here. Further detail about CXR controllers can be found here. Further detail about CZT controllers can be found here. Further detail about DC1100 and DC1400 controllers can be found here.

Issue Should the Modbus master (eg Xenta 913) also be terminated if it is in the middle of the Modbus bus? Environment Xenta Server with Modbus capabilities Xenta 511, 527, 701, 711, 721, 731, 913 Cause There are a number of installation possibilities/restrictions that may mean that the Modbus master does not always end up at one of the ends of the communication field bus. Resolution Only the ends of the bus should be terminated (see below).   More information is available for Modbus.org at the following link: Modbus over serial line specification and implementation guide V1.02.

Issue Satchwell VZF 2-Port Flanged Valve Body requires replacement. Environment Satchwell 2-Port Plug and Seat Flanged Valve Body VZF1727                                VZF 1727 VZF1777                                VZF 1777 VZF1852                                VZF 1852 VZF1902                                VZF 1902 VZF1954                                VZF 1954 Cause Obsolescence of Satchwell VZF 2-Port Flanged Valve Body Resolution A number of alternative S-E 2-Port Flanged Valve Bodies are available to replace existing Satchwell VZF 2-Port Flanged Valve Bodies. Suggestion 1 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E VG221F 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body.  In such instances a S-E L9TVG Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the VG221F 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. Suggestion 2 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E V222 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body.  In such instances a S-E L8TV Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the V222 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2-port Flanged Valve Body  Similarly, the centre line to bottom of third port dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2port Flanged Valve Body  As a result alterations to the pipework connected to the VZF 2-port Flanged Valve Body will be required. Details of the Satchwell VZF 2-port Flanged Valve Body may be viewed here. Details of the S-E VG221F 2 port Flanged Valve Body may be viewed here. Details of the S-E V222 2-port Flanged Valve Body may be viewed here. Details of the S-E L9TVG Linkage Kit may be viewed here. Details of the S-E L8TV Linkage Kit may be viewed here.

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 Receive alarm messages as "Server does not exist or access denied", "08001: [FreeTDS][SQL Server]Unable to connect to data source" or "08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" when using SQL Server Express for External Log Storage even though login credentials are correct. 08001: [FreeTDS][SQL Server]Unable to connect to data source 08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" Product Line EcoStruxure Building Operation Environment Enterprise Server Workstation External Log Storage SQL Server Cause SQL Server Express is using Windows Authentication and/or the TCP/IP network protocol is disabled. Resolution To use external log storage with SQL Server Express the User must be able to login with SQL Server Authentication (e.g. a username and password) and the TCP/IP Network protocol must be enabled.  Consult Setup External Log Storage using MSSQL for additional details.   Check SQL external log storage host address: In the host address type the IP address or DNS name of your external log storage, without the SQL instance name. Having the SQL instance name in the host address can cause communication failure if EBO server is connecting to remote SQL server, refer to: Microsoft SQL Server - Basic Tab. To check the User login credentials: Open SQL Server Management Studio and enter the details from EcoStruxure Building Operation into the SQL Server connection window.  Choose SQL Server Authentication (A), enter the server details (1), user name and password (2) and attempt to login. If an error message appears indicating cannot connect and the credentials are correct it is possibly SQL Server Authentication is not enabled. Login to the SQL Server using Windows Authentication and follow the Microsoft article Change server authentication mode to set to 'SQL Server and Windows Authentication mode'. Attempt to login to SQL Server and the specific database should be visible. To enable the TCP/IP Network protocol:  Open SQL Server Configuration Manager (1) In the SQL Server Network Configuration menu, select Protocols for SQLExpress (2) Right-click TCP/IP (3) and select Properties (4) In the window that opens, click the IP Addresses tab (5) Either set a different port number for each one of the IP addresses or simply set one for all (6).  The default is 1433 but will need to be a port that is free.   Click OK. Back in the SQL Server Management Studio ensure the SQLExpress service is restarted. For additional information please consult Default SQL Server Network Protocol Configuration and Enable or disable a server network protocol            

Issue java.io.EOFException    at javax.baja.xml.XParser.read(XParser.java:753)    at javax.baja.xml.XParser.parseString(XParser.java:555)    at javax.baja.xml.XParser.parseAttr(XParser.java:492)    at javax.baja.xml.XParser.parseElemStart(XParser.java:421)    at javax.baja.xml.XParser.next(XParser.java:262)    at javax.baja.xml.XParser.parseCurrent(XParser.java:146)    at javax.baja.xml.XParser.parse(XParser.java:119)    at javax.baja.xml.XParser.parse(XParser.java:102)    at javax.baja.ui.px.PxDecoder.decodeDocument(PxDecoder.java:77)    at javax.baja.ui.px.PxDecoder.decodeDocument(PxDecoder.java:64)    at javax.baja.workbench.px.BWbPxView.loadPx(BWbPxView.java:176)    at javax.baja.workbench.px.BWbPxView.doLoadValue(BWbPxView.java:90)    at javax.baja.workbench.BWbEditor.loadValue(BWbEditor.java:233)    at com.tridium.workbench.shell.NHyperlinkInfo.loadView(NHyperlinkInfo.java:563)    at com.tridium.workbench.shell.NHyperlinkInfo.hyperlink(NHyperlinkInfo.java:100)    at com.tridium.workbench.shell.BNiagaraWbShell.doHyperlink(BNiagaraWbShell.java:350)    at com.tridium.workbench.shell.BNiagaraWbShell.hyperlink(BNiagaraWbShell.java:316)    at com.tridium.workbench.shell.WbCommands$BackCommand.doInvoke(WbCommands.java:718)    at javax.baja.ui.Command.doInvoke(Command.java:303)   Environment G3 (Niagara) station with px files, any revision level. Cause The px file did not copy correctly. Resolution There are three possible approaches to recover from this situation, as follows: Try copying the file again.   Open the px file with a text editor. It might be possible to determine what was either not copied at all, or what might have been corrupted during the copying process. The example shown below is part of the BoilerRoom.px file from niagara-3.6.47 \ stations \ demo \ px \ plant. Lines 489 through 495 contain 'closing tags' for the Canvas Pane, Scroll Pane, Border Pane, content, and px statements that were opened at an earlier point in the px file. If one or more of these 'closing tags' were not copied, or were somehow corrupted during the copying process, the error would result .  If necessary, restore the px file from a backup.

Issue Customers may need a copy of their License Entitlement certificate Product Line EcoStruxure Building Operation Environment Building Operation Licensing Cause Missing Entitlement certificate  Resolution Customers have access to the following link, where they can use the Entitlement ID or Activation ID to login to the Licensing page: License Page information After logging in, select the “List Entitlements” under “Activation & Entitlements” on the top. Tick the checkbox in front of one Activation ID (ACT), select View/View certificate Now, a new page pops up which contains the Entitlement Certificate information. This can be saved or printed.

Issue In WorkPlace Commissioning Tool, the following error message appears when browsing a BACnet/IP network: "A critical error occurred in the communication server rtmonitor.exe. Please shutdown this application and the communication server then try again." Product Line TAC IA Series Environment Windows 7 computer WorkPlace Tech Tool software version 5.7 or later Cause The WinPcap driver, used in WorkPlace Tech BACnet communications was configured to start on demand and the WPT module that is attempting to start WinPcap does not have the necessary Windows security rights.  Resolution NOTE 1:  Before using this procedure, please verify that the issue noted in WorkPlace Commissioning Tool UDP Port: "A critical error occurred in the communication server rtmonitor.exe" has been corrected, if present, and did not solve the problem. NOTE 2: If the computer is running Windows 7-64 bit, replace the following references to "Program Files" with "Program Files (x86)". To correct this issue, perform the following steps. Open Windows Explorer, i.e., "My Computer" or "Computer" from the Windows Start menu or computer desktop. Open the folder "C:\Program Files\WorkPlace Tech" For each of the following program files listed here, in turn: RTMonitor.exe, WPCT.exe, WPFB.exe and WPTech.exe Right click on the program name, Select Properties from the pop-up menu, Select the "Compatibility" tab. In the Compatibility display, click the button [Change settings for all users]. Locate "Privilege Level" section of the displayed window and check the box "Run this program as an administrator". (See snapshot below) Click the [OK] button to save the settings for all users. The window will close. You will see that the Privilege Level option is no longer selectable. Click the [OK] button to save the compatibility settings.   After setting the privilege option for each of the four programs in the Workplace Tech folder, repeat the same setting change for the Microsoft Visio program itself, VISIO.EXE. Depending on the version you are using, it will be located in the C:\Program Files\Microsoft Office\OfficeXX folder where xx is 14, i.e., Office14, for Visio 2010, 12, i.e., Office12, for Visio 2007 or 11, i.e., Office11, for Visio 2003. After setting these options, the computer should be shut down and restarted before using the WorkPlace Tech Tool software.  

Issue 7790A LAN Interface Unit and Information. Why is the 7790A not shown in my Network Configuration Product Line TAC I/NET Environment I/NET Seven Software v2.45 7790A LAN Interface Unit (LIU) 7791A Door Processing Interface (DPI) 7792A Micro Regulator Interface (MRI) 7793A Micro Control Interface (MCI) Cause Information about the 7790A LAN Interface Unit or LIU Confusion is usually with the Hardware Model when purchasing. Once installed and configured for one of the three common options above, firmware (software) is downloaded to the hardware device (7790A) to become one of the three indicated interfaces, DPI, MRI, and MCI. In the later release of I/NET Seven Software only supports the 7793 MCI.  Resolution Refer to TCON109 attached for further information.    The 7793 has two channels and will handle 32 devices on each channel if addressed correctly. This gives a total of 64 SCU units on a single 7793. The 7790A can be addressed using the HHC to a 7790, 7791, 7792, 7793, 7797.  The 7790A replaces the 7797A-C as of January 1, 2013. The original 7791 was primarily for Access Control. The original 7792 was primarily for HVAC. The 7793 is a combination for both and the most popular of the 7790 series. To clarify, when purchasing a 7790A, you would address as a 7793, then put up to 32 SCUs on each of the channels giving you a total capacity of 64 SCUs.     For access control, the model 7798C has more memory but only one Channel, which means it can handle up to a maximum of 32 SCU controllers and the recommended interface for larger access control sites.  

Issue Calculation for converting static air pressure to cfm Product Line TAC INET Environment INET HVAC Site Cause What are the calculations for converting static air pressure to cfm? Resolution SRVP ("water column") * 4005 = FPM (feet per minute). The second calculation is FPM * AreaFtSQ (size of box) = CFM You will need an airflow monitoring device and duct static pressure sensor to measure SRV P (v of Vs of P).