Issue On rare occasions you will get an error during the installation of Echelon OpenLNS Server on Windows 8.1 64 bit saying that the installer can't create specific registry keys. Product Line EcoStruxure Building Operation, Other, TAC Vista Environment OpenLNS Windows 8.1 64 bit Cause The user does not have permission to access those registry keys. Resolution Add the registry keys manually. Alternatively, run OpenLNS on Windows 8.1 - Registry paths.zip reg file that will add the keys. Run the installer again.

Issue When a MPM is replaced on a BACnet IP network, a "Duplicate network identifier" alarm is generated Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment MPM Automation Server Cause If the BACnet name and instance number in the new controller is not exactly the same as the original MPM, the Automation Server will consider that an additional device has been installed and an alarm will be triggered stating that the new device has the same BACnet ID as an existing device. Resolution Steps to replacing a MPM to prevent the Duplicate ID alarm being triggered: When replacing the original MPM, note the BACnet name and Instance ID. Install the new MPM and enter the same BACnet name and Instance ID. Refer to BACnet device can't be discovered due to duplicate name for more information about duplicate BACnet names.

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.

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 Recommended method for replacing an MR-VAV-AX controller. Where to get ASC Parameters for the new device. Environment I/NET software all versions MR-VAV-AX controller Cause An MR-VAV-AX needs to be replaced on an existing VAV box. Resolution The ideal way to change an MR-VAV-AX or similar would be to use an airflow hood to calibrate when the device must be changed. However, if no airflow hood is available, see the options below: Obtain the ASC parameters of the existing MR before removing the device from service. Re-use the original settings. If these values cannot be recovered, then ask the customer for the original drawings or T&B reports on the device in an effort to properly establish correct duct diameter and total airflow. Rarely is this information readily available at the time of the change. Without such info, an estimation will have to be made. A rule of thumb is: 250 CFM per diffuser and an eyeball estimate of the duct diameter The pickup factor is left at factory default (3) or compared to other similar devices and an average of other pickup factors is used. For setting CHF, base it on the above estimate of 250 CFM per diffuser and make sure that the box just reaches 100% damper at the maximum airflow it is physically capable of at the AHU's normal static CLF is an estimate based on the use of the space and the temperature needs of the occupants. CLF is about 10% of the CHF.

Issue Many electrical power meters provide a high resolution Modbus or M-Bus output for cumulative parameters such as kWh, kVAh and kVARh.  This output can be displayed in Vista or on an Xenta Server web page, but the resolution can be degraded by inappropriate conversions in XBuilder and choice of display format.  This article shows how to maintain the full resolution of a meter reading from acquisition through to display on a Vista graphic or Xenta Server web page. Environment Xenta 511, 527, 555, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder PM710 Cause Applying scaling or connections in XBuilder, or processing in Menta, reduces the precision of a high resolution Modbus value to that of a Real or Float. Resolution The following comments refer to Modbus registers in the Schneider Electric PM710 energy meter, although many other meters deal with extended precision values in a similar manner.  Acquiring Data from the meter: 1. If you want to maintain the full precision of the meter 'Real Energy, Total' reading, use register 4000 which is a 32 bit signed integer, representing scaled kWh. The scale factor is stored in register 4108 as a 16 bit integer and the two registers should be used in conjunction for display purposes. The maximum full precision value that can be displayed this way is: 2147483647 - 10 decimal digits - before the scale factor is applied. 2. An alternative to register 4000 is provided in register 1000, which is of type 'Float'.  This equates to the REAL type in XBuilder, so it already has only 21 bit precision. However, there is no need to scale it as the exponent is built in to the Float type. Processing input in XBuilder: 3. For register 4000 in the device template, apply a gain of 1 and keep the converted value as INTEGER.  This will maintain the full 32 bit precision of the Modbus register.  If you apply any gain less than 1 or convert the value to a REAL, you will only end up with a 21 bit precision result.  This equates to a loss of 2 decimal digits approximately. 4. Avoid using Connection objects.  For example, a variable of type 'SNVT_elec_kwh_l' has theoretically the same precision as register 4000 in the PM710, so it would seem to be a direct conversion.  However, because you have to use a Connection object to link the two in XBuilder, the value is converted to a REAL internally and you end up with a 21 bit precision result. 5. Xenta Servers can provide full precision Modbus values for display in Vista. Create new Signal objects in the System pane in XBuilder and drag and drop the Modbus values from the Network pane onto the Signal objects.  The Signal objects will have the same precision as the original Modbus registers and are visible in Vista. Displaying values in Xenta Server and Vista: 6. Value pages in the Xenta Server and TGML graphics pages in Xenta Server and Vista can display a 10 digit integer. In the case of item 1 above, all 10 digits will be accurate. In the case of item 2 above, only the most significant 8 digits will be accurate. 7. A value page in the Xenta Server will display a real as 8 digits plus exponent. However, only the 7 most significant digits will be accurate. 8. The object view in Vista will display a real up to 8 significant digits, with only the most 7 significant digits being accurate.  Vista will attempt to show this as fixed point 6.2 and no exponent.  If the actual value is too big or small for this format it reverts to 3 significant digits plus 3 digit exponent.  

Issue How many SC2300 could be connected to one SE7300 or 8300? Environment SC3000 SE7300 SE8300 Cause Inputs from the relay packs could not be connected in parallel. Resolution It is not possible to connect inputs in parallel, therefore you could only connect one relay pack to one device.

Issue Can the old Robertshaw T99 temperature sensors be integrated to SBO? Product Line EcoStruxure Building Operation, TAC IA Series Environment SBO all versions Cause Retrofit job installation Resolution According to the RTD-DI-16 specification sheet, the T99 sensor can be integrated to SBO as follows with some limitations. Configuration Use an RTD-DI-16 module with a 2 or 3 wire RTD resistive input. Select 1000 ohm for the Sensor class property of the RTD input object. Configure the Conversion Settings properties of the RTD input object near the endpoints of the temperature range to be measured using values from the T99 temperature/resistance table. Configure the remaining properties of the RTD input as needed. Limitations Input Range. An RTD-DI-16 input configured for 1000 ohm operation is limited to an input resistance range of 500 to 2200 ohms. This will limit the temperature range that can be measured with a T99 sensor to ~115 deg. F maximum. Linearity Error. Depending on the range of temperatures to be measured and the needs of the application, linearity error may be significant. This can be corrected by using a script or function block program to linearize the signal based on the T99 temperature/resistance table values.

Issue The default Unifact Pro stencil in VisiSat only includes items for the BB*3 range of controllers. It does not include the older BB*2 range, which may still be in use in legacy systems. Product Line Satchwell MicroNet Environment VisiSat Unifact Pro Cause VisiSat’s default stencil set excludes the obsolete BB*2 Unifact Pro controllers. These must be manually added to the drawing environment. Resolution To access and use the older BB*2 Unifact Pro controllers in VisiSat, follow the steps below based on your version of Microsoft Visio: For Visio 2003/2007: Open Visio. Go to the File menu. Select Stencil > Open Stencil. Navigate to: C:\Satchwell\Binary\VisiSat\EN\Visio Select the file: Obsolete.vss The stencil will now include the older BB*2 Unifact Pro controllers. For Visio 2010 and Later: Under Shapes, click More Shapes. Select Open Stencil. Navigate to: C:\Satchwell\Binary\VisiSat\EN\Visio Choose: Obsolete.vss Additional Notes These stencils are installed by default during the VisiSat installation process. If the Obsolete.vss file is missing, you can download it from the VisiSat 2.1 Build 196 (200, 201) Obsolete Stencil Archiv You may store the stencil anywhere on your system, but the default location is: C:\Satchwell\Binary\VisiSat\EN\Visio

Issue Site may be migrating from I/NET to another access control system and would like to import the data. Product Line TAC I/NET Environment I/NET Seven SQL Management Studio Cause The site is migrating from I/Net to Continuum or another access control system. Resolution Open SQL Management Studio and create a New Query by clicking on the "New Query" button Run the script below: SELECT * FROM InetDb.dbo.IdWorksView Note:  This view only shows the Primary Group associated with each individual.     Select File>Save Results As... Save the file as a .csv to a location of your choosing

Issue User unable to find means to add I/O points for an AS-B in workstation Environment Automation Server Basic Cause User not selecing the AS-B-XX onboard IO object Resolution In the system tree browse to the IO Bus/AS-B-XX onboard IO Right click on the object and select New/Input or Output Point Select the type of IO and continue creating the IO point.

Issue There are a number of object tabs that support the functionality of exporting to a CSV file. Can this CSV file then be used as a template and imported into another site? Product Line EcoStruxure Security Expert Environment Security Expert Cause Not sure how to import objects from CSV as a database creation tool. Resolution The export options are so you can export the required records to a file as part of site documentation, administration etc. There is no way to import anything other than users using a CSV file. A database backup that is already configured can be restored to a new system to be used as a site template. Another option for using the same configuration is the Copy Controller Feature. If you want to have multiple sites within a single Security Expert Server, take a bank for example where each branch is a separate site in the one server but configured pretty much the same, you could utilize the Copy Controller feature to copy all the programming from the template controller to a new one. Please note that although this feature currently exists within Security Expert it is currently being worked on by our engineers to improve its functionality.

Issue Using I/NET Audible Alarms with Remote Clients No audible alarms with Remote Client configuration Product Line TAC INET Environment I/NET Seven Software 2.42 and newer I/NET Remote Client or Remote Client with I/O Server Cause The functionality was changed with the following TrackRecord 5940 fix in I/NET 2.42: Alarms in a Remote Client do not get an audible alarm Only clients configured as "Remote Client w/IO" are capable of routing alarms/events to the server. The masking on clients configured as "Remote Client" will not cause alarms/events to be routed to the server. On these clients, you can use the masking to get audible alarms with no danger of getting duplicate alarms.   Resolution To receive and activate audible alarms on a Remote Client, set the Distribution Group and Masking of the alarm point within AMT.   Note: This setting is only the case for I/NET 2.42 and above.  If this is setting is made in earlier versions of I/NET, it will cause alarms / events / trends to be routed to the server and possibly can cause duplicate events / trends to be sent to the server.  The following information is noted in TCON300: "Limitations to TAC I/NET Seven on Remote Clients   Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features:   Network functions                 Automatic DPU restore                 Archiving                 Dial after edit   Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed." "Limitations to TAC I/NET Seven on Remote Clients" Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features: Network function Automatic DPU restore Archiving Dial after edit Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed."  

Issue Changes to COV and ReadProperty in bCX from v4.500048 Product Line Andover Continuum Environment bCX b3 Controllers Cause New feature to allow user flexibility for using Forced Polling and not COV Resolution From bCX version v4.500048, all Controllers will have the option of forcing a poll of points from other Continuum and third party BACnet controllers. This new feature: allows programmers to decide which data exchange method to use by the syntax in which they write their data-sharing programs. provides a method for forcing point-to-point polling from a device that does not support COV and sends an invalid error message when the subscription is attempted. This previously caused Continuum to reject polling, resulting in a failure to share data. allows programmers to decide to poll a point only when needed, even if the device supports COV subscriptions. This ensures that data from a device is only sent when necessary instead of always being sent on a “change of value”. The following Plain English formats force polling: "Local point = Infinity Remote Point Value" "Local point = BACnet Remote point Value" "Local point = ReadProperty(BACnet Remote point Value)" The second argument, Value, ensures that polling is commanded – now for BACnet, as well as Continuum/Infinity. (The third example shows the use of Plain English’s ReadProperty system function.) If the Value argument, shown in these examples, is left out, Continuum BACnet will operate as it always has – always attempting a COV subscription and only falling back to the polling method if the target device sends the appropriate COV subscription failure message. Caution: If you have a device that does not support COV subscriptions or you have chosen to use the polling syntax, you must be careful how you write your Plain English programs. A program that runs every scan and polls a point from another controller will cause major problems. For instance, if your scan is running at 100 milliseconds and you try to poll any BACnet device at that rate, you will most likely knock the device offline. It will also cause the program to disable and seriously slow down the scan in your controller that is requesting the data (since the scanner waits for an answer to a poll before continuing). You should also use a line E in your programs, since any communication problem to the target device will cause the polling program to disable.

Issue Remote Client Configuration Issues I.Net 2.31 and prior Product Line TAC INET Environment I/Net Seven version 2.xx with need for Remote Client configuration. Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause Remote Client changes with I/Net Seven version 2.21 to 2.31 release. Resolution There are two different configurations for the Remote Client setup in I/Net Seven. Clicking the links below will open a PDF document which will show how the communication should be setup. This configuration is in the I/O Server under the current profile and can be found in the Workstation Options.   *IP Addresses are for demonstration purposes only.

Issue When attempting to run the WorkPlace Tech Tool, Application Menu missing or grayed out. All WorkPlace Tech Tool related entries in the Tools menu are grayed out or missing.   Project Toolbars are not displayed. "Unknown error occurred in an add-on to WorkPlace Tech" Environment WorkPlace Tech Tool 5.7.4 and later versions Microsoft  Visio 2003 or Visio 2007 Microsoft Windows XPsp2, XPsp3,  Vista or Windows 7 Cause Various causes beyond the scope of this article. Resolution There are several different reasons why these entries are grayed out or missing and therefore not selectable. The exact procedure for correcting the problem depends on the version of Visio and the version of Windows being used. WorkPlace Tech with Visio 2007 Open Visio 2007 Open the Tools Pull down. Select the Trust Center Select Add-ins. Verify that the box "Disable all Application Add-ins" is NOT checked. At the bottom of the screen, COM Add-ins is the default selection. Press GO. In the COM Add-ins box displayed, un-check the box for each third-party add-in. Click [OK] to apply. Close Visio 2007 Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username >\AppData\Local\Microsoft\Visio\content12.dat If running Windows XP, delete the file c:\Documents and Settings\< username >\Local Settings\Application Data\Microsoft\Visio\content12.dat Open Visio 2007 and wait for the "Getting Started with Microsoft Visio" window to be displayed. Close Visio 2007. Open WPT, all menu items should be there. Workplace Tech with Visio 2003 Open Visio 2003 Open the Tools menu. Select Options, then Security. Verify that the box for "Enable COM add-ins" is checked. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click [OK] to apply. Open the Tools menu and select Macros then select "COM Add-ins" Uncheck all third-party add-ins shown in the list. Click [OK] to apply. Close Visio 2003. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username >\AppData\Local\Microsoft\Visio\content.dat If running Windows XP, delete the file c:\Documents and Settings\< username >\Local Settings\Application Data\Microsoft\Visio\content.dat Open Visio 2003 and wait for the "Choose Drawing Type" window to be displayed. Close Visio 2003 Open WPT, all menu items should be there.

Issue What TTS-SD-LED and TTS-SD-LCD Smart Sensors are available? Environment TTS-SD-LED Series • TTS-SD-LED-1 • TTS-SD-LED-B-1 TTS-SD-LCD-Series • TTS-SD-LCD-1 • TTS-SD-LCD-4-2 • TTS-SD-LCD-B-1 • TTS-SD-LCD-C-1-10P • TTS-SD-INFBUF Cause Some products in this range have become obsolete due to the discontinuation of some key components. Resolution Full details are on the attached Product Announcement PA-00171 TTS-SD-LED-1 Discontinued TTS-SD-LED-B-1 Discontinued TTS-SD-LCD-1 Modified TTS-SD-LCD-4-2 Modified TTS-SD-LCD-B-1 Replaced by TTS-SD-LCD-1 TTS-SD-LCD-C-1-10P Discontinued TTS-SD-INFBUF Discontinued

Issue DVR incorporated with I/NET Seven and Pelco Integral or Digital Sentry Product Line Pelco, TAC INET Environment I/Net Seven Pelco Integral or Digital Sentry DVR CCTV Cause Send back a Integral DVR and it comes back as a Digital Sentry or confusion revisions of I/NET Seven and Pelco Integral of Digital Sentry Resolution This chart to clarifies which versions of I/NET Seven are compatible with which Pelco DVRs: For the latest products (after 2.31 revision) please visit Software and Firmware compatibility matrix for older versions of the traditional product lines which has the most recent Pelco compatibility.

Issue When deploying Automation Server or Enterprise Server from Workstation for Projects under PCS, it will fail. The error shown in the Progress view window is "The live server is not empty." Product Line EcoStruxure Building Operation Environment SmartStruxure Project Configuration Server Workstation for Projects Enterprise Server (ES) Automation Server (AS) Cause A project can only be deployed to a server when the server has an empty database and not has been part of a multi-server system. A server is considered empty when it does not contain any user-created objects, such as programs and graphics. Resolution The server database can be emptied in different ways depending on if it is an Automation Server or an Enterprise Server: Reinstall the Enterprise Server. Upgrade the Automation Server with a new database. For more detail about how to deploy AS or ES, refer to Offline Engineering with Project Configuration Server (PCS).

Issue Customers wanting to use a Barcode Reader for door access Environment Access Control site wanting to use Barcode Readers Cause Barcode Readers often are a higher  Resolution I/NET The SCU is the best you could have so that makes it easier with memory requirements and so forth. Since you have the SCU, set it up for 26-bit Wiegand (2 parity bits and 24 data bits). It would look like this: e eeeeeeee eeeeooooooooooooo o That is a 1-bit starting bit, even parity, 8-bit facility code, site number, card number, 16-bit segment, and the 1-bit ending parity (26 bits all together). That is how many data bits the reader normally takes. 26-bit Wiegand is typical and most common. The true bits are the facility code, site and card number. The beginning and end is the parity. For more information, see TCON300, beginning on page 9-59. This is the key card translations section, and may be valuable in figuring out the solution to the bar code reader. Lastly, one idea is to contact a company called RFIDeas.com. They make a bar code reader that may be a solution. If the bar code reader is outputting a card number larger than 16 digits, convert it to 26-bits of Wiegand data (it can handle up to 64-bitWiegand). If it goes over 64-bit, they have a special firmware which allows up to 254 bits of wiegand data. With the SCU, the 26-bit is the standard. Code 128 is used to barcode INET products. The Cypressworld CVX-1300 is an alternate solution for connection between the I/NET SCU and the Barcode Reader. Continuum Code 39 is used to barcode the serial number on Continuum and Pelco boards.  Most readers can auto switch between these and other code types.