Issue Which antivirus software is compatible with Niagara R2 and G3? Product Line TAC IA Series Environment Niagara R2 Workplace Pro (all versions) Niagara G3 Workbench (all versions) Cause Antivirus software can block essential ports, services, and files required for Niagara R2 and G3 operation, leading to communication failures or application issues. Resolution Niagara R2 and G3 software will work with any antivirus program that allows unblocked communication to the required ports, services, and files listed below: Niagara R2 Requirements Ports: Port 80 (Station communications & Web access) Port 3011 (Admin Tool) Services: Niagara Service (Control Panel > Administrative Tools > Services) Files: Files in C:\<niagara r2 release number>\nre\bin directory Niagara G3 Requirements Ports: Port 80 (Web access) Port 1911 (Station communications) Port 3011 (Platform access) Services: Niagara Service (Control Panel > Administrative Tools > Services) Files: Files in C:\<niagara g3 release number>\bin directory Important Notes: The specified Ethernet ports must be open bidirectionally for both TCP and UDP traffic. Configure antivirus software to allow or “unblock” these ports, services, and files.

Issue Upgrading Loytec L-IP to the latest firmware or checking current firmware version. Environment Loytec L-IP Vista Network Interface Cause UL 864 v.9 for Smoke Control requires at least version 5.04 firmware in all system L-IP's. Resolution Verifying L-IP Firmware Version via Console Connection To use the serial interface, the DB9 console connector of the L-IP can be connected to the RS-232 port of a PC. The L-IP-3ECTB and L-IP-33ECTB use a standard null-modem-cable must be used to connect the L-IP’s DB9console connector to the RS-232 port of the PC. The PC will communicate with the L-IP using a HyperTerminal program with the communication settings set to 38,400 bps / 8 data bits / no parity / 1 stop bit / no handshake. The L-IP displays the console menu shown in Figure 1 upon a successful HyperTerminal connection initiated by a “enter” keystroke or power cycle of the L-IP: LOYTEC electronics GmbH www.loytec.com L-IP Configuration Menu ======================= [1] Show device information [2] Serial firmware upgrade [3] System configuration [4] EIA-709 configuration [5] IP configuration [6] EIA-852 device configuration [7] EIA-852 server configuration [8] Reset configuration (factory defaults) [9] Device statistics [0] Reset device Please choose: Figure 1: L-IP main menu. Select Option 1 to Show device information  This menu item shows information about the L-IP and the current firmware version. The output should look like what is shown in Figure 2. Product information =================== Product code: L-IP-3ECT Firmware: L-IP Primary image Version: 5.0.5 Build date: Fri Mar 18 10:41:29 2005 Serial number: 002304-80000000E73C Free memory: 557K,57K System temp: 33.3C Supply volt: 12.0V Unique Node IDs =============== Port 1: 80 00 00 00 E7 3C EIA852: 80 00 00 00 F7 92 Figure 2: Device information. (For UL 864 v9: If the Firmware Version does not reflect a Version 5.0.4 or Version 5.0.5, you must update the firmware to an approved version in the next steps. If the L-IP contains an approved version, further action is not required.) L-IP Firmware Upgrade To download the firmware via the console connected the L-IP to the RS-232 port of a PC via its console interface as outlined above. Download the lswitch_lipxxx.zip located at www.loytec.com to the PC. Install the LOYTEC serial upgrade tool (LSU Tool) by double clicking LSU_2_0_1setup.exe. Double click on the lswitch_lip_xxx.dlc file. This will start the LSU Tool and load the firmware image referenced in the . lswitch_lip_xxx.dlc file. The start window of the LSU tool is shown in Figure 3. *note that the lswitch_lip_xxx.dlc file and the lswitch_lip_xxx.dl file must be stored in the same folder. Figure 3: LSU Serial Upgrade Tool in idle mode. If the L-IP is not connected to COM1 you can change the port to COM1, 2, 3, or 4. Press “Download” to start the download. A progress bar as shown in Figure 4 can be seen. Figure 4: Progress bar during firmware download. If the upgrade is successful the following window appears (Figure 5). Figure 5: Successful firmware upgrade. Exit the LSU Tool. Reconnect through HyperTerminal connection and  initiate the console by a “enter” keystroke or power cycle of the L-IP. At the console main menu, select option [1] Show device information, and press Enter. This will bring up the current device information as shown in Figure 2, for verification that the firmware version has updated successfully.

Issue What is included when the PIR option is ordered? Environment SE7300 series controllers Cause The SE7300 series controllers can be ordered both with and without the PIR option Resolution If the PIR sensor functionality is ordered as included from factory, code 55 (example: SE7600A5545E) should be used. If PIR functionality is not required, code 50 (example: SE7600A5045E) should be used. PIR functionality can be retrofit at any time. For details and part numbers, please see related documentation.

Issue Customer wants to know if he gets any different functionality when updating from a MNL-20RS1 to a MNL-20RS3 in terms of the LonMark profile. Likewise, what is the difference between the MNL-10RS2 and MNL-10RS4 LonMark profiles. Environment MNL-xxRS1 / MNL-xxRS3 controllers MNL-xxRS2 / MNL-xxRS4 controllers Cause LonMark Profile update was required when the hardware was revised so that we could maintain our LonMark registration status on the controllers This same change applies to the RS2 and RS4 profiles Resolution The profiles for all the standard MNL-xx series controllers (MNL-50, MNL-100, MNL-110, MNL-130, MNL-150, MNL-200 and MNL-Vxx) are documented in Appendix B of the WorkPlace Tech Tool 4.0 Engineering Guide, F-27254. Specifically, the differences in the MNL-xxRS1 and MNL-xxRS3 profiles are as follows: NV Index # 23 MNL-xxRS1: Name: nvoSECAlarm Type:SNVT_str_asc MNL-xxRS3: Name: nvoDeviceAlarm Type:SNVT_str_asc NV Index # 58 MNL-xxRS1: Name: nciSECModelNum Type:SNVT_str_asc MNL-xxRS3: Name: nvoDeviceInfo Type:SNVT_str_asc Likewise, the differences in the RS2 and RS4 profiles are as follows: NV Index # 25 MNL-xxRS2: Name: nvoSECAlarm Type:SNVT_str_asc MNL-xxRS4: Name: nvoDeviceAlarm Type:SNVT_str_asc NV Index # 60 MNL-xxRS2: Name: nciSECModelNum Type:SNVT_str_asc MNL-xxRS4: Name: nvoDeviceInfo Type:SNVT_str_asc The corresponding differences exist in the Version 2 and Version 3 profiles for the MNL-xxRFp, MNL-xxRHp, MNL-xxRRp, MNL-V1RVp, MNL-V2RVp and MNL-V3RVp controllers where "p" corresponds to the Version number 2 or 3.

Issue How to bring an MPM-VA online over ZigBee to communicate with the ZigBee Coordinator (which is also the MPM you have your IP interface with). Environment MPM, MPM-VA, ZigBee Cause Cannot figure out how to get the MPM-VA to communicate over ZigBee to the Coordinator. Resolution Use web interface on the bench to set up ZigBee Pro Extended Configuration on the "remote MPM-VA" to match the Coordinator's Channel, PAN ID, Extended Network ID, Stack Profile, Security Profile and Trust Center Link. Save settings and save database to flash. You can now disconnect the IP connection to the remote MPM-VA. Re-discover controllers from the Coordinator MPM. It will appear as a "peer" below the coordinator, i.e., it will not be "under it" like a Room Controller (stat) or TE2.  

Issue taclogdata_log.ldf file is too big Environment SQL 2005   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 Services for assistance. Cause Fail to perform frequent SQL DB maintenance   Resolution To Shrink the LOG file (.ldf) follow the procedure. Connect to taclogdata.mdf using SQL server management studio. Run the following command: dbcc shrinkfile (taclogdata_log,100,truncateonly)   This will reduce the size (taclogdata_log.ldf) to 100 mb. Note : You can get the logical file name for the log by running the following select statement: (select * from sysfiles) The following are the query results: 1          1          6400    -1         6400    2          0          taclogdata         c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata.mdf   2          0          2624    268435456      1280    66        0          taclogdata_log  c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata_log.LDF   If the database has the truncate log checkpoint turned off, then the transaction log file will be shrink to the target size only when the transaction log is backed up. OR If the truncate log on checkpoint is turned on then go to Enterprise Manager - all tasks - and click "truncate log". This will shrink the file down to the target size and will release all the unused space to the Operating System.

Issue How to restore and view a Log backup without overwriting current database How to view backed-up events without overwriting current database How to restore a SQL database  without overwriting current database Environment TAC Vista 4.3 and higher running a typical (not custom) SQL. 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 Services for assistance. Cause The event and logs will be backed up as a SQL backup file. This means that restoring a backup on the same PC that it was made on replaces the SQL database.    Resolution To view old data, restore the log database backup file on a different PC that has the same TAC Vista database on it. Create a copy of the TAC Vista database (or make a backup) Copy / restore the database to a computer that is running the same version of TAC Vista Go to the Server application and log in Go to File > Restore Log Database Browse in the backup file, the path should be filled in automatically

Issue Downgrade SQL 2008 to SQL 2005 Restore from SQL 2008 to prior version. Product Line Andover Continuum, TAC INET, TAC Vista Environment SQL 2008 used by Building Management Software Cause Have database loaded on one machine using SQL 2008 and would like to move or change to SQL 2005 Resolution Golden Rule: A SQL 2008 database cannot be downgraded or restored to a SQL 2005 version. It is not possible to downgrade a database or a database backup. The SQL schema will not allow it.  For your current version of SQL: C:\Program Files\Microsoft SQL Server \80, \90, \100 Folders are the client tools. 80 = SQL Server 2000 90 = SQL Server 2005 100 = SQL Server 2008 How ever, it is not a rule. Since 2008 creates both 80, 90. The only way to find what versions are installed (besides regedit) is by the Sql Server Configuration manager.    For other SQL options related to I/NET, please visit SQL and version compatibility for Filemaster, Equalized Client, Remote Client, Limitations of SQL.

Issue For various reasons it maybe necessary to change a b3's device id, one way to accomplish this is using the RoamIO2 with the BACnet Service Tool. Product Line Andover Continuum, EcoStruxure Building Operation Environment B3 RoamIO2 BACnet Service Tool Cause The device ID of a b3 controller needs to be changed. Resolution Disconnect the b3 from the MSTP network and connect the RoamIO2 directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries   Click the green icon to make the RoamIO 2 join the MSTP network and discover the b3. (NOTE: If the b3 has not been previously assigned a valid MAC ID see How to change b3's mac ID using RoamIO service tool) Once you see the b3 in the object tree select it then switch to the grid view and double click on the device id value on the 'object-identifier'  field. In the 'Property View/Set' window enter the new device id to set and click on apply. You should get a feed back of 'Success!' if the device id was changed.

Issue A change is made to a public signal in TAC Vista Workstation, which was created in a Xenta Server XBuilder project, changed back to the initial value after performing a download to this Xenta Server. Environment Xenta Servers (Xenta 511, Xenta 515, Xenta 555, Xenta 527, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913) XBuilder Tested with Windows Server 2003, Window XP SP3 Cause If a path name is changed of a signal, for example, change the "the site name" folder name to another name, Vista consider this change as a major change, and Workstation will not be able to find the new path of the signal. Therefore, the signal will return to the initial value which is initialized in the Menta object. Resolution Suggestion is making all the infrastructure change at the beginning if you can. If there is a need to change the path, make sure all the initial values are reflect to the current values in Workstation. Then, make the download to the Xenta Server.

Issue When launching BAS2800+ V2.9 on a Windows XP system, the software fails to detect the dongle. A warning message appears: "No Dongle Driver Detected" Product Line Satchwell BAS & Sigma Environment   Windows XP BAS2800+ V2.9 Cause The issue occurs because modern PCs may operate too quickly for the dongle to be recognized during startup. Resolution To resolve this issue, follow these steps: Download the fast dongle driver Unzip the contents. Install the driver in the following directory: C:\bas\bin Run the executable: dk2wn32.exe Follow the on-screen instructions during installation. Restart your PC once installation is complete. After rebooting, the dongle should be successfully detected, allowing BAS2800+ to run normally.

Issue An error is received 'Error connecting to server' while testing a Digital Sentry DVR connection with Cyberstation 1.90 or 1.91. Product Line Andover Continuum Environment Continuum 1.90 Continuum 1.91 Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The DS Connex version of newer Digital Sentry DVRs are not compatible with Continuum 1.90 or 1.91 Resolution The DSConnex version of newer Digital Sentry DVRs are not compatible with Continuum 1.90 or 1.91 unless the following hotfix is applied. Click here to download the hotfix

Issue Difference found between 2 technical documents regarding the Universal Inputs of the b3810 and b3814 controllers. In the Controller Data Sheet the Universal Inputs are indicated 0-10VDC, 12 bit.  In the Family Controllers Brochure it's indicated Universal Inputs 0-5V, 10bit.  Which document is correct?   Environment BACnet b3810 and b3814 controllers Cause An older revision of the Family Controllers Brochure contains inaccurate / outdated information. Resolution The Universal Inputs for the b3810 and b3814 controllers are 12 bit,  0-10VDC.  The next revision of the BACnet Family of Controllers document will contain the correct voltage. Controllers available with 12 bit A/D Converters 0-10VDC are: i2/b3920 i2/b3810 i2/b3814 Other i2/b3 controller inputs have 10 bit A/D converters.

Issue What are the PIN locations for right and left control? Environment MPT24DT Pan/Tilt functions, PT270-24P, PT280-24P, PT570-24P, PT680-24P Cause Loss of manual for PIN layout Resolution On either a 14-PIN or a 9-PIN the following applies:                                                                                                                      PIN 1 is P/T common PIN 3 is Left control PIN 5 is Down control PIN 6 is Up control PIN 7 is Right control PIN 8 is Safety Ground                                                                                          NOTE: MPT24DT can also be used to control 120 VAC pan/tilt  and scanners when used with RB115 relay box                                                                               

Issue Is there a way to get all my MTA from a files saved off to disk from a Vista db? Product Line TAC Vista Environment Vista Database Generator Menta Cause Archiving/extracting all Menta files from a Vista database at the same time. Backup all applications quickly. Resolution You can use the Database Generator    to do this. Vista Server must first be running before performing these steps: Start Database Generator (Start > Programs > Schneider Electric > TAC Tools X.X.X > Database Generator). May need to right-click and Run As Administrator. Go to the Database Menu and select Export Data from Database Click on the browse button for the object. Select device navigation, and browse to your Network object and click OK. In the Export from Database dialogue, keep the default settings and click OK. All MTA files in the selected Network will be saved to the $wrk directory in the Vista database.   MTA files will be updated with any changes made from Vista to PVR blocks, TSCH blocks, etc. If changes have been made while directly connected from Menta or an OP, right click on each controller and select "Upload Parameters" before exporting the MTA files. If more than one Network exists in one database, a separate export must be performed for each network.

Issue Use Modulus in Menta Expression Block. Environment Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause The Modulus operation in Menta is used to obtain the remainder of a division. If for example you want to perform 10 Modulus 7 the result would be 3. Resolution To perform this function in Menta, use an expression block with the contents of A%B. However, the built in Modulus function does not work with numbers larger than 65535. To perform the Modulus function with such large numbers, write out the Modulus calculation in the expression block instead of using the % symbol. This expression accomplishes the same thing: A-(B*INT(A/B))  

Issue How to find a dongle ID (PSU ID) if it has rubbed off of the dongle. Product Line TAC Vista Environment Vista IV TAC Dongle Utility Cause The dongle ID (PSU ID) can be found printed on the side of a Vista IV licensing dongle. However, on older dongles, this number can rub off. It is still possible to extract the dongle ID using the TAC Dongle Utility. Resolution Download the TAC Dongle Utility Install TAC Dongle Utility and run the program. Start > Programs > T A C > TAC Tools > TAC DongleUtil Plug in a valid Vista IV end user dongle. Hit Refresh on the Dongle Utility PSU ID is displayed. This is the ID required to add new licensing to an existing dongle. ReadFind a Vista 5 dongle ID for how to find a Vista 5 dongle ID.

Issue During a Sigma transition into EcoStruxure Building Operation (EBO), a duplicated set of Short Form Edit (SFE) graphics appears in a different language alongside the original graphics. Example: First Data Import: English Second Data Import: Danish This results in two sets of SFE graphics—one in English and one in Danish—linked to the same objects. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Satchwell Sigma Cause The language setting in EBO was different during each Data Import. When the Sigma Interface is imported with a different language setting, EBO creates a new set of SFE graphics in that language. Resolution To prevent duplicated graphics in multiple languages: Before starting the Sigma Data Import: Delete the existing Sigma Interface in EBO. Set the correct language in EBO that matches the desired import language. Restart the Sigma transition process. Important Note: Deleting the Sigma Interface will remove all existing SFE graphic links from the objects. A clean set of SFE graphics will be generated during the new import, ensuring consistency in language and structure. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue When connecting MP-C controllers in a daisy chain, do they act as a repeater and boost the signal thus allowing total network distances of greater than 90 meters. Product Line EcoStruxure Building Operation. Environment Building Operation Multi-purpose Controller. Cause Each MP-C acts as a switch and decodes and generates a new fresh packet. Resolution Maximum 100 meters between each device when using daisy chain when connecting MP-C.

Issue How can the instance number be changed in a Viconics BACnet thermostat? Environment Viconics BACnet thermostat Cause No visible button to enter configuration Resolution The ID or instance number is 7x000(x=series model)+ Mac address. The Mac address can be defined from the front of the unit. Press the white "config" button in the lower right hand corner of the circuit board once. Then keep hitting "no" until "Com Addr" is displayed and hit yes. Use up/down keys to set the address. For units with no white "config" button: VT7200 series press and hold the button (OVERRIDE) for 8 seconds VT7300 series press and hold the middle button (°C/F or OVERRIDE) for 8 seconds. VT7600 series press and hold the button (MENU) for 8 seconds Then press no until "com addr" displays, then press yes and use the up/down button to change it.