Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Label: "tac ia series"

View in: "Building Automation Knowledge Base" | Community

1684 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

Issue The Command Request / Command Response window is not available when using the Niagara G3 DMS driver. Product Line TAC IA Series Environment Niagara G3 Microsmart driver Cause This feature was present in the Niagara R2 driver but was not carried over to the Niagara G3 driver. Resolution The only available option is to tunnel to the Microsmart controllers using OPRIF for command requests and responses.

Issue UltiVist cannot communicate with the DMS panel over a serial connection due to incorrect port settings. Product Line TAC IA Series Environment UltiVist Software DMS Panel Cause The DMS panel’s serial COM port settings were reset to factory defaults, which do not match UltiVist’s required configuration. Resolution Configure the DMS panel’s serial COM port with the following settings to enable communication with UltiVist: Parameter Value Port PORT1 (typically) or PORT2 Baud Rate 9600 Stop Bits 1 Data Bits 7 Parity Even Mode Multi-drop Modem None Note: PORT1 is commonly used for UltiVist connections. Ensure these settings are applied after any factory reset.

Issue In a Niagara R2 and DMS integration, some points in the station are not updating after changes to the DMS database. Product Line TAC IA Series Environment Niagara R2 (all versions) DMS (all versions) Cause Controllers and associated DMS points were deleted as part of housekeeping. When points are deleted, added, or re-ordered in the DMS database, the Niagara R2 station does not automatically refresh its point list. Resolution Whenever DMS points are modified or the DMS database is downloaded via OPRIF, perform a re-learn of the DMS panel from the Niagara R2 station: In Niagara Workbench, right-click the DMS container. Select Go > PointListManager. Click GetPointListFromDevice to upload the current DMS database into the station. Important Notes: These steps will not affect existing objects under the specific DMS container. For detailed instructions, refer to the I/A Series Niagara DMS Serial Driver Engineering Guide (F-27071), section “Re-learning The DMS Panel.”

Issue Clarification is needed on whether the Ethernet NIM (Network Interface Module) settings are included when performing a DMS database backup. Product Line TAC IA Series Environment DMS-3500 with Ethernet NIM OPRIF 11.4 & 11.6 Cause Backup requirements can be confusing because the DMS database, controller databases, and NIM configuration are stored separately. Users may assume a single backup command covers all components, which is not the case. Resolution A complete DMS backup consists of three steps, all performed using OPRIF: Backup the DMS database Backup each individual MicroSmart controller database Backup Ethernet NIM configuration data separately Important Note: Echelon NIMs do NOT require backup. Ensure all three steps are completed during maintenance to guarantee full system recovery capability.

Issue On a DMS jobsite, the Operator Interface (OPRIF) does not display MicroSmart controllers on the screen. Although multiple controllers are confirmed to be communicating with the DMS, they do not appear in the controller list in OPRIF. Product Line TAC IA Series Environment OPRIF DMS MicroSmart Cause OPRIF displays controllers in groups of 32 per screen and reserves address slots even if they do not exist. If controller addresses start at 33 or higher, the first screen appears blank because it only shows addresses 1–32. Resolution Use the Page Down and Page Up buttons in OPRIF to navigate between controller lists: Page 1: Addresses 1–32 Page 2: Addresses 33–65

Issue A jobsite is visited periodically, and it appears that certain database elements have changed since the previous visit. These elements are not expected to change (unlike setpoints or schedules). The question is whether there is a built-in feature in a DMS panel or the OPRIF programming tool that provides database analysis. Product Line TAC IA Series Environment DMS OPRIF Cause The DMS product does not include built-in database analysis tools. Historically, supervisory computers provided this functionality using tools like UltiVist or SIGNAL, which could analyze databases and save information for future review. Resolution No built-in database analysis feature exists in DMS panels or OPRIF. When only OPRIF is available: Take screenshots of point configuration screens to store values for later comparison. DMS databases are not formatted for offline viewing, so direct comparison between copies is not supported. To compare two database states: Use a second DMS panel as a reference. For advanced analysis, consider using a supervisory computer with compatible tools (e.g., UltiVist, SIGNAL) if available.

Issue What is the best way to completely clear an existing database from DMS3500 and DMS350A before reinstalling? Product Line TAC IA Series Environment DMS3500 DMS350A Cause When reinstalling a database, remnants of the previous database may cause conflicts or unexpected behavior. A full hardware-level clear is required to ensure the old database is completely removed. Resolution For DMS3500: Connect via OPRIF and enter Command Mode. Type the command: DBCLR After completion, log back into the DMS3500 and begin the new database installation. For DMS350A: Sign on using the keypad. Enter the command: DBCLR For each connected DCM: Set all 8 toggle switches to ON. Cycle power to the DCM. Wait 10 seconds, then re-address the DCM and cycle power again. Once complete, use OPRIF to start the database installation. Note: The DBCLR command combined with setting toggle switches to ON is considered a hardware-level database clear, ensuring no residual data remains.

Issue Customers need guidance on migrating DMS-3500 systems to the Building Operation platform. Product Line EcoStruxure Building Operation, TAC IA Series Environment DMS-3500 EcoStruxure Building Operation Cause The DMS-3500 system and its databases are not compatible with Building Operation. Schneider Electric does not provide a supported migration path for these legacy systems to Building Operation. Resolution Direct migration is unsupported. To integrate DMS-3500 data into Building Operation, use a Niagara device as a gateway between the two systems.

Issue A MicroSmart controller with revision 9 firmware needs to broadcast a point value to other MicroSmart controllers running revision 10 and 11 firmware under the same DMS. The broadcast is not working as expected. Product Line TAC IA Series Environment MicroSmart controllers connected to a DMS Cause Peer-to-peer data sharing was introduced starting with revision 10 MicroSmart firmware. Controllers running revision 9 do not support peer-to-peer communication, so they cannot broadcast or receive values directly. Resolution To enable value sharing: Link the sending point and receiving points to the DMS. Use the sending DMS point in conjunction with the receiving DMS point within the programming logic. The value will then propagate down to the MicroSmart controllers through the DMS.

Issue When opening (pulling up) the sunblind, it stops at the end of runtime and then rolls back down. Similarly, when closing (pulling down), it stops at the end of runtime and then rolls back up. Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Lonworks devices including REG-N MSE4 (SVEA 32237-346) Sunblind actuators Cause The actuator is preconfigured for venetian blinds, which include lamella angle adjustments. For simple sunblinds, these parameters cause unintended motor actions after reaching the end position. Resolution For non-venetian blinds: Set the following parameters to zero: UCPTdownPanelAngle UCPTupPanelAngle UCPTpanelTurnTime UCPTpanelTurnTimeBottom Ensure SNVTsetting commands have zero in the rotation part. This disables unnecessary panel angle adjustments and prevents rollback after full movement.

Issue A single folder on a jobsite computer contains multiple DMS backups performed over several years. Each backup consists of multiple files, but they are not grouped by name or date, making it difficult to identify and retrieve complete backups. Product Line TAC IA Series Environment DMS35, DMS350A, and DMS3500 (revisions 9, 10, and 11) Cause Multiple backups were saved in the same directory without a naming convention or date-based grouping, resulting in a disorganized collection of files. Resolution A complete DMS database backup consists of the following files: For DMS35 and DMS3500: filename.IOC – Stores DMS point IDs, records, and alarm parameters. filename.UC – Stores DMS point configuration elements. filename.PG – Stores DMS tables and schedules. filename.UDP – Stores UDPs in the DMS panel. For DMS350A: Includes the four files above plus: filename.Dxx – Stores DCM tables, schedules, and other elements (where xx = DCM address 01–32). filename.Uxx – Stores DCM UDPs (where xx = DCM address 01–32). Recommendation: To simplify future retrieval, create a folder for each backup and name it using a clear convention (e.g., Backup_YYYYMMDD_SiteName ). Move all related files into that folder immediately after performing the backup.

Issue Will we be able to use our Schneider Electric Workbench (Tech Laptop) to connect to the Honeywell Supervisor? Product Line TAC IA Series Environment I/A Series AX (all versions) I/A Series N4 (all versions) Cause The NiCS statement within the license controls the sharing of data and usage of Workbench on a G3 (AX) platform. Resolution The answer depends upon the NiCS statement within the Honeywell Supervisor license. If the Honeywell license accept.wb.in statement is open, the SE brand Workbench would be able to connect and engineer. Based on past experience, the accept.wb.in statement is typically set to webs and can only be accessed by a Honeywell licensed Workbench. The NiCS statement for the Jace is setup to prevent connection by a non-SE brand Workbench. The statements that control sharing of data (accept.station.in and accept.station.out) have always been open. Unfortunately prior to AX version 3.6, the Niagara driver point discovery process utilized some Workbench functionality to perform the connection and use basically defeating the main purpose of the NiCS statement. This meant that the points needed to be added manually. The software was corrected in 3.6 to allow discovering of points regardless of the NiCS accept.wb.in statement. The points will be able to be discovered with the Honeywell Supervisor as long as AX version 3.6 or higher is being used.

Issue Not all features are seen when a BMS platform is viewed using remote control software e.g. RealVNC Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Remote Tools: RealVNC, TeamViewer, LogMeIn, UltraVNC, etc. Cause Remote control software may not fully render graphical elements or interactive UI components of BMS applications. This is often due to: Graphics acceleration limitations UI rendering differences between local and remote sessions Security or permission restrictions in remote sessions Example: When using RealVNC to access the SmartStruxure License Administrator, the dropdown menu for adding license details may not appear, even though it functions correctly in a local session. Resolution Local Verification: Run the BMS application directly on the host machine to confirm full functionality. Remote Software Settings: Enable full desktop rendering or mirror driver (if available). Disable any performance optimizations that reduce UI fidelity. Alternative Access Methods: Use Remote Desktop Protocol (RDP) instead of third-party remote tools. Consider web-based access if supported by the BMS platform. Additional Notes These issues are not specific to one remote control tool; they may occur across various platforms.

Issue Building Management System (BMS) equipment may malfunction due to electromagnetic interference (EMI) from nearby electrical devices. Diagnosing and resolving such issues can be complex and costly, making preventive installation practices essential. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Improper installation can lead to the generation or exposure to high- and low-frequency EMI, which may disrupt system performance or cause equipment failure. Resolution To ensure reliable operation and minimize EMI-related issues, follow these key EMC installation practices: Key EMC Practices Follow Manufacturer Recommendations Always adhere to the installation guidelines provided by equipment manufacturers, as they are tailored to the specific EMC requirements of each product. Proper Cable Routing Separate power and signal cables. Avoid parallel runs near high-interference sources (e.g., motors, transformers). Shielding Use shielded cables for sensitive signals. Ground shields correctly—typically at one end to prevent ground loops. Grounding and Bonding Establish a low-impedance ground path. Bond all equipment to a common ground reference. Surge Protection Install surge protection on power and communication lines. Protect against lightning and switching transients. Filtering Use EMI filters on power inputs. Apply ferrite beads or chokes on signal lines where needed. Physical Separation Maintain spacing between high-voltage and low-voltage components. Isolate noisy equipment from sensitive electronics. Enclosure Design Use metal enclosures for shielding. Ensure proper sealing and grounding of enclosure panels. Installation Environment Avoid placing equipment near strong EMI sources (e.g., radio transmitters, welding equipment). Maintain clean, dry conditions to prevent corrosion and poor connections. Compliance Testing Verify installations against relevant EMC standards (e.g., IEC, EN). Conduct site surveys if persistent issues arise. Reference Document: Practical Installation Guidelines for Electromagnetic Compatibility

Issue What are the NEMA or IP ratings for a specific product? Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment All devices Cause Users often need to know whether a product is protected against: Water ingress Intrusion by foreign objects (e.g., dust, fingers) Resolution To determine a product’s protection level, refer to the Degrees of Protection document, which includes: IP Rating Chart NEMA Enclosure Rating Chart 🔹 Understanding IP Ratings An IP rating consists of two digits: First digit: Protection against solid foreign objects Second digit: Protection against water Examples: IP20: Protected against fingers (≥12.5 mm), no water protection IP10: Protected against objects up to 50 mm, no water protection If a product datasheet does not specify water ingress protection, the second digit defaults to 0. 🔹 Typical Building Products Many building automation products: Prevent insertion of fingers (≥12.5 mm) Do not offer water protection → Common rating: IP20 📎 Attachment Degrees of Protection.pdf (Includes full IP and NEMA charts)

Issue When using a Windows PC with Microsoft Visual Studio installed, an unexpected error message appears referencing Just-In-Time (JIT) Debugging. This can interrupt normal operations and confuse users unfamiliar with debugging tools. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating System Cause Visual Studio includes a feature called Just-In-Time Debugging, which attempts to launch the debugger when a program crashes or encounters a critical error. If enabled, this feature can interfere with other applications or workflows by prompting unexpected debug dialogs. Resolution To disable Just-In-Time Debugging, follow these steps: Open Visual Studio. Go to the Tools menu and select Options. In the Options dialog box: Expand the Debugging section. Select the Just-In-Time page. In the Enable Just-In-Time debugging of these types of code box, uncheck the relevant options: Managed Native Script Click OK to apply changes. Note: Disabling JIT debugging modifies a registry key. You must have Administrator privileges to make this change.

Issue When attempting to run LonMaker, the following errors may occur in succession: Could not listen on poet/tcp: The address specified is already in use (Error -2532) Database error: (Subsystem: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) Additional errors that may be caused by the same underlying issue: Problem connecting with the database server process: (Subsystem: LNS, #36) [DB#-2523] Error opening LCA Global database Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma, TAC IA Series, TAC Vista Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause The issue is typically caused by a conflict between the Sentinel Protection Server and the POET Server, as both attempt to use the same port(s). Sentinel Protection Installer 7.6.1 installs the Sentinel Protection Server, which manages Sentinel SuperPro and UltraPro keys used with Satchwell Sigma and other products This service is not required for the dongle driver to function and can interfere with LonMaker’s operation. Refer to: Error: LNS #25 lcaErrDatabase for more technical details. Resolution To resolve the issue: Stop the Sentinel Protection Server: Open the Windows Services console: Press Windows + R , type services.msc , and press Enter. Locate Sentinel Protection Server. Right-click and select Stop. (Optional): Disable the service if not needed: Right-click > Properties > Set Startup type to Disabled. ✅ This will allow POET Server to operate without port conflicts.

Issue How to estimate the thermal load (in BTU/hr or Watts) that your controllers and equipment will produce. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Applicable to all electrical equipment used in building automation systems. Cause Understanding the thermal load is essential for: Sizing air conditioning systems Ensuring proper ventilation Avoiding overheating in enclosures Not all equipment datasheets provide thermal dissipation values, so manual calculation may be necessary. Resolution You can estimate the thermal load using the power consumption of each device. Formula To convert power (in Watts) to thermal load: BTU/hr = Power (W) × 3.412141633 Watts = Power (W) (already known) Note: 1 Watt = 3.412141633 BTU/hr Example Calculation Using the Continuum AC-1 I/O module: Power consumption: 2.6 W (without attached reader) Thermal load: BTU/hr = 2.6 × 3.412141633 = 8.87 BTU/hr Watts = 2.6 W If the reader is powered by the AC-1, include its power consumption in the total. International Units Reference Unit Conversion 1 Watt 3.412 BTU/hr 1 BTU/hr 0.293 Watts Additional Notes Use this method for any device where power consumption is known. For grouped equipment, sum the total wattage before converting. Consider using an online calculator for quick conversions.

Issue Continuum 1.9x and above may fail to install correctly on domain-joined machines. A common error during installation is: "You must have local NT administrative privileges to run this application." Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows 7, 8, 10, 11, Server 2016 and later SQL 2005, 2008, 2012 and later Cause Microsoft SQL installations require elevated local administrator privileges. Domain accounts often lack these rights due to group policies or security restrictions. A local administrator account is required to complete the installation successfully. Resolution Resolution: Create a Local Administrator Account 🔹 Windows 7 / 8 / 10 (Classic Method) Open Control Panel → Administrative Tools → Computer Management Navigate to Local Users and Groups → Users Right-click in the right pane → New User Enter a username and password Uncheck User must change password at next logon Check Password never expires Click Create → Close Right-click the new user → Properties → Member Of tab Click Add → Type Administrators → Check Names → OK 🔹 Windows 10 / 11 (Modern Method) Open Settings → Accounts → Family & other users Under Other users, click Add someone else to this PC Select I don’t have this person’s sign-in information → Add a user without a Microsoft account Enter a username and password After creation, click the account → Change account type Set to Administrator → OK 🔹 Windows Server 2016+ Open Server Manager → Tools → Computer Management Go to Local Users and Groups → Users Right-click → New User Fill in the details and assign to the Administrators group as above 🔹 Command Line (All Versions) Run the following commands in Command Prompt (Admin): net user LocalAdmin P@ssw0rd123 /add net localgroup Administrators LocalAdmin /add Replace LocalAdmin and P@ssw0rd123 with your preferred username and password. 🔐 Additional Notes Ensure the account is local, not domain-based. You may need to disable UAC temporarily for installation, but re-enable it afterward. For Server OS, PowerShell can be used for automation if needed.

Issue What is the accuracy of the I/A Series MN-Sx S-Link wall sensors? This information is required for project submittal documentation. Product Line Field Devices, Satchwell MicroNet, TAC IA Series Environment MN-SX MN-S1 MN-S2 MN-S3 MN-S4 MN-S4-FCS MN-S5 S-Link Cause Sensor accuracy specifications are needed to meet submittal requirements for building automation projects. Resolution Refer to document TPA-RKFD-09-0021.00 for factory-calibrated accuracy and stability specifications. Sensor Specifications: Element Type: Precision Thermistor Operating Temperature Range: 0 – 50 °C (32 – 122 °F) Stability: < 0.02 °C (< 0.04 °F) per year (typical) Accuracy: Temperature °C Accuracy Temperature °F Accuracy 24 °C ± 0.6 °C 75 °F ± 1.0 °F 0 to 50 °C ± 1.7 °C 32 to 122 °F ± 3.0 °F

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Command Request/Response Window Missing in Niagara G3 DMS Driver

DMS Panel Serial Port Settings for UltiVist Communication

Niagara R2/DMS Integration – Points Not Updating After Database Changes

DMS Ethernet NIM Settings Backup Procedure

MicroSmart Controllers Not Displayed in OPRIF on DMS Jobsite

Database Analysis Options for DMS Panels Using OPRIF

Clear Existing Database from DMS3500 and DMS350A

Migration Path for DMS-3500 to Building Operation

How to broadcast a value from one MicroSmart controller to other MicroSmart controllers under the same DMS.

LonWorks Sunblind Actuator Rolls Back After Full Movement

Identifying Files in a Complete DMS Database Backup

Using Schneider Electric (SE) licensed Niagara Workbench to connect to the Honeywell Supervisor

Remote Control Software

Installation Guidelines for Electromagnetic Compatibility (EMC)

IP Protection and NEMA Ratings for Products

Microsoft Visual Studio Triggers Just-In-Time Debugging

Errors Encountered When Trying to Run LonMaker

Estimating Thermal Load (BTU/hr or Watts) for Controllers and Equipment

How to Create a Local Administrator Logon in Windows

Accuracy of I/A Series MN-Sx S-Link Wall Sensors

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!