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 Can the Robertshaw DMS T99 sensor be connected to an MNL controller using the Curve Fit object? Product Line TAC IA Series Environment Robertshaw DMS T99 MNL controller Cause The site requires the use of a Robertshaw DMS T99 sensor with an MNL controller, but the sensor’s characteristics differ from standard Balco sensors. Resolution The T99 sensor is a 2000 Ω silicon-based RTD with linearity similar to Balco. To integrate it with an MNL controller: Wiring: Connect the T99 sensor to the MNL controller’s UI input. Add a parallel 2000 Ω ±1% shunt resistor. AI Object Configuration: Select Balco type in the AI object. Curve Fit Adjustment: Use a Curve Fit object to correct temperature readings. Configure X and Y data points as follows: X (Balco temperatures): 52.5, 61.6, 70.0, 78.4, 86.6, 94.8 Y (Corrected T99 temperatures): 32.0, 50.0, 68.0, 86.0, 104.0, 122.0 Note: The A/D degree per count resolution is approximately 0.15°F per count, which is twice that of Balco.

Issue Connection to a DMS MicroPlex MSC-NC is successful; however, attempts to access a networked MicroSmart controller fail. Product Line TAC IA Series Environment DMS MicroPlex MSC-NC MicroSmart Controller Cause The Flash ROM in the MSC-NC requires reloading. Corrupted or incomplete flash memory can prevent proper communication with networked MicroSmart controllers. Resolution Reload the Flash ROM in the MSC-NC: Power down the MSC-NC. Install jumper J1 (located near the processor). Power up the MSC-NC. Connect using DCT. Remove J1 jumper. Perform Alt-L in DCT to start Flash ROM installation. Additional Benefits: Resets backdoor password issues. Removes “ghost” controllers. Corrects non-standard service alarm codes (e.g., 44+service alarm44144144/144).

Issue Can a Belimo damper actuator (e.g., NF-24SR) be powered from the same transformer as a DMS MSC-MPC Microsmart controller? Product Line TAC IA Series Environment Belimo damper actuator DMS MSC-MPC (Microsmart controller) Cause The MSC-MPC controller uses full-wave rectification, while Belimo actuators use half-wave rectification. Sharing the same transformer introduces electrical incompatibility, which can lead to component-level damage in the MSC-MPC controller. Resolution Do not share the same transformer between MSC-MPC controllers and Belimo actuators. Provide separate power supplies for each device to prevent electrical interference and potential damage.

Issue In a Niagara R2/DMS integration, the re-learn of the DMS database fails after some points were deleted in the DMS system. Product Line TAC IA Series Environment Niagara R2 (all versions) DMS (all versions) Cause The DMS driver uses the LOGPT index (1–250) to scan points during the learn process. When points are missing, the DMS panel returns “NOPOINT.” If multiple consecutive “NOPOINT” responses occur, the learn process terminates early. This happens when points have been deleted or re-created, causing gaps in LOGPT assignments. Resolution Adjust the learnNoPointAbortCount property in the DMS driver: Set learnNoPointAbortCount to 250 to ensure all possible points are scanned, even if gaps exist. Note: This will increase the time required for the learn process but guarantees a complete scan. Additional Notes: If the DMS database was reloaded from a saved backup, points will have consecutive LOGPT numbers, and gaps will not occur. Use this setting only when gaps are expected due to point deletion or creation.

Issue Is the MSC-LIM-1 compatible with any DMS revision 9 Microsmart controllers? Product Line TAC IA Series Environment Microsmart controllers revision 9, 10, and 11 MSC-LIM (Local Interface Module) Cause Need for a local controller connection and clarification on compatibility across different Microsmart controller revisions. Resolution MSC-LIM-1 is not compatible with revision 9 Microsmart controllers. It is only compatible with revision 10 and 11 Microsmart controllers. Earlier MSC-LIM versions (pre-08/96) could only access Level 10 controllers addressed below 99. To access controllers addressed higher than 99, the device required a factory upgrade to 11.0A. The latest MSC-LIM (formally MSC-LIM-1) supports Level 10 and 11 Microsmart controllers addressed up to 124.

Issue Two new batteries were installed in a DMS-350A panel, but neither charged to the point of indicating GOOD. The voltage measured at the battery clips with the battery installed reads approximately 4.5 VDC. Product Line TAC IA Series Environment DMS-350A Cause Poor physical connection between the battery and the battery holder contacts prevents proper charging. Resolution Inspect Battery Holder Contacts Check for dirt, corrosion, or misalignment on the contacts. Clean Contacts Use a suitable contact cleaner or a lint-free cloth to remove debris. Adjust Contact Position Gently bend the battery holder contacts to ensure a firm and secure connection with the battery terminals. Verify Voltage After adjustment, confirm that the battery voltage rises above 4.5 VDC and eventually indicates GOOD status.

Issue DMS OPRIF version 11.6 locks up when attempting to tunnel with Niagara R2 or Niagara G3. Product Line TAC IA Series Environment OPRIF 11.6 with a Windows OS. I/A Series Niagara R2 and G3 Cause The default installation path for OPRIF 11.6 is excessively long for Windows OS, causing the application to freeze during tunneling operations. Resolution During installation, avoid the default directory: x:\Documents and Settings\username\Local Settings\Temp Instead, install OPRIF into the root folder of the desired drive (e.g., x:\ ). The installation path can be specified in the extraction screen during setup.

Issue The desktop shortcut created during the installation of DMS OPRIF 11.6 for DCT does not work as expected. Product Line TAC IA Series Environment DMS OPRIF 11.6 running in a Windows OS. Cause The installed shortcut incorrectly calls c350dct instead of the required batch file dct.bat . This prevents the DCT tool from launching properly. Resolution Run DCT Manually Navigate to the DCT folder and run DCT.BAT directly. Modify Desktop Shortcut Edit the shortcut target line from: call c350dct to: call dct.bat Improve Performance Open DCT.BAT in the DCT folder and change: dctgl.exe %1 %2 to: start /low dctgl.exe %1 %2 This runs the process with lower priority, improving system responsiveness.

Issue Which USB-to-Serial adapter should be used with DMS Operator Interface (OPRIF) version 11.6? Product Line TAC IA Series Environment DMS OPRIF 11.6 DMS-350A DMS-3500 Cause Modern PCs often lack built-in RS-232 serial ports, requiring a reliable USB-to-Serial adapter for communication with DMS panels and related devices. Resolution Recommended Adapter: IOGEAR model GU232A This adapter is also suitable for MSC-LIM, MN-CIM, and CBL-002 (DB-9S > DB-9S). Special Note: When using the adapter with MSC-LIM, launch OPRIF from LINKERGL.EXE located in the DMS folder.

Issue How to share or broadcast analog values between multiple I/A Series UNC-520 controllers using a DMS-3500 panel. Product Line TAC IA Series Environment I/A series UNC-520 DMS-3500 Cause The system requires analog values to be broadcast globally across multiple panels. Direct linking of points does not work because the analog input needs conversion from floatStatus to floatPriority for proper handling. Resolution Create Dummy AP Point On each DMS panel receiving a global analog value, create a dummy AP point (UC AP). Assign a name and set AP type to 07 . Configure UNC Learn the new point at the UNC. Select PVALU:WRITE , then click Add and Create. Two objects will appear: AO and DmsGenericAO. Insert Math Object Add a Math object in the workspace. Link pOut of Math object to pIn of AO. This converts the AI from floatStatus to floatPriority . Broadcast Setup Link sinA of the Math object to the analog point in the DMS panel that will be broadcast globally. Edit the Broadcast Channel and assign the correct GLOBAL number. Address Book Configuration For each UNC station, add all peer IP addresses to the AddressBook under PEER setup. MicroSmart Integration For any MicroSmart controller, create an LP point and link it to the DMS AP point. The DMS AP acts as the input for the MicroSmart LP point.

Issue How to distinguish between the Enhanced and Non-Enhanced versions of the MSC-P1502 MicroSmart controller in a DMS system. Product Line TAC IA Series Environment DMS MicroSmart MSC-P1500 series Cause The MSC-P1502 controller was manufactured in two versions: Non-Enhanced: Standard functionality without configurable AI5 & AI6 inputs. Enhanced: Supports AI5 & AI6 configuration for Voltage/mA or resistance input via jumpers J1 & J2. Resolution Identify the version using these methods: Visual Inspection Non-Enhanced: Circuit board labeled MSCA-6160. Enhanced: Circuit board labeled MSCA-6161. If No Label Present Check above AI5 & AI6 inputs for a white box marked “ENHANCED AI” (Enhanced version only). Using OPRIF Both versions display PCB as Controller Type on the greeting screen, so rely on physical board markings for confirmation.

Issue Global point passing (broadcast) between MicroSmart controllers under a DMS system is not functioning as expected. Product Line TAC IA Series Environment DMS MicroSmart Controllers: MSC-L1000 MSC-MPC-001 MSC-P-751 to MSC-P-754 MSC-P-1501 to MSC-P-1504 MSC-V-510, MSC-V-511 MSC-V-521, MSC-V-522 MSC-V-751 to MSC-V-754 Cause Broadcast channel limits vary by controller type: MSC-L1000 / MSC-MPC: TXD and RXD on channels 1–122 MSC-P-75x / MSC-P-150x / MSC-V-51x / MSC-V-52x / MSC-V-75x: TXD on channels 1–122 RXD limited to channels 1–24 If RXD channels exceed these limits, global point passing will fail. Resolution Verify and adjust TXD/RXD channel assignments to stay within supported ranges: For MSC-L1000 and MSC-MPC: TXD and RXD can use channels 1–122 For MSC-P and MSC-V series: TXD: channels 1–122 RXD: channels 1–24 Ensure configuration aligns with these limits to restore global broadcast functionality.

Issue Communication between a DMS-3500 and a Niagara R2 UNC-520 is slow, causing point updates to occur very slowly. Users need guidance on settings that can be verified and optimized to improve performance. Product Line TAC IA Series Environment Niagara R2 UNC-5x0 DMS-35, DMS-350A, DMS-3500 Cause Several factors can contribute to slow communication: High count of polled objects Lower than optimal baud rate between UNC and DMS Non-optimal settings for the DMS Comm Service Resolution Follow best practices from the DMS Serial Driver Engineering Guide (F-27071). Key recommendations that do not require hardware changes include: Increase Baud Rate Use the maximum allowable baud rate for the DMS serial port (38.4 kbps for DMS-3500). Optimize DmsCommService Settings intermessageDelay = 1500 timeoutHostMsg = 215000 timeoutHostFragment = 110000 maxReadValues = 10 downDeviceRecoveryInterval = 1 maxMultipleMsgs = 3 autoCycleTimeOn = TRUE deltaCycleDifference = 10 deltaCycleChange = 25 globalCycleTime = 15000 Reduce Unnecessary Alarms Disable DMS point alarms that are no longer required from annunciating to the serial port. Optimize Polling Intervals Adjust minimumPollInterval for shadow objects. Example: Space temperature sensors can be set to 30,000–60,000 ms instead of the default 1,000 ms. Limit Poll-Always Points Keep below 600 points if polling at 1,000 ms.

Issue The last controller on a Microsmart trunk was removed and discarded without retrieving the End-of-Line (EOL) module. External resistors are needed to temporarily mimic the EOL module for communication stability. Product Line TAC IA Series Environment DMS (all models) Microsmart controller communication trunks Cause During site renovation, the last controller and its EOL module were removed and discarded, leaving the trunk without proper termination. Resolution Using external resistors is not recommended as a permanent solution. However, to stabilize communications until a proper EOL module (RBSC-16) is installed, replicate the following resistance values: Module Type: 8-pin Pin Connections: Pins 1–8: 3.3 kΩ resistor Pins 2–7: No connection Pins 3–6: 150 Ω resistor Pins 4–5: 3.3 kΩ resistor Resistor Specs: ¼ watt, 5% tolerance

Issue Understanding how unoccupied heating mode operates on a Type 2 Mode Control point in DMS Microsmart. Product Line TAC IA Series Environment DMS Microsmart Cause Perimeter radiation valves remain open or do not adjust correctly during unoccupied periods, causing the space temperature to be too warm when occupancy begins. Resolution The Heat/Cool Differential determines the occupied heating setpoint by subtracting its value from the occupied cooling setpoint. Example: Cooling Setpoint = 74°F Heat/Cool Differential = 4°F → Heating Setpoint = 70°F Night setup values: Cooling Night Setup = 80°F (must be higher than the occupied cooling setpoint) Heating Night Setback = 65°F (must be lower than the occupied heating setpoint) Both night setpoints require a Level 1 STOP command to engage.

Issue How to identify the point capacity of a DMS-3500 controller and verify the actual point count on an active system. Product Line TAC IA Series Environment DMS-3500 Cause When making additions to an existing DMS installation, it is necessary to confirm the remaining point capacity to ensure the system can accommodate additional programming. Resolution A DMS-3500 supports 250 points maximum. To check the current point count on a live system using OPRIF 11.x: From any screen, press F8 to enter command mode. Type CANCL and press Enter to view the first point in the database. Type PNTID and press Enter to display the first point's name. The three-digit number to the left of the point name should read 001 (first point). Press F5 to display the last point in the system. The three-digit number to the left of the point name indicates the total point count (between 001 and 250).

Issue What output does a DMS Loop Point provide when the setpoint and process variable are equal, and only a proportional constant is used? Product Line TAC IA Series Environment DMS control applications using proportional-only loop points Cause When using proportional-only control, the behavior of the loop output at equilibrium (setpoint = process variable) can be unclear, leading to confusion during configuration or troubleshooting. Resolution A proportional-only Loop Point assumes a midrange output when the setpoint and process variable are equal. Midrange means halfway between the loop output high range and low range (typically 100 and 0 respectively). For detailed configuration guidance, refer to DMS Operator Interface User's Guide (F-25467), Chapter 13.

Issue What speed and duplex settings do the DMS and GCM Ethernet Network Interface Modules (NIMs) operate at? Product Line TAC IA Series Environment DMS-ETH-001 GCM-ETH-001 Cause Uncertainty about the Ethernet configuration (speed and duplex) can lead to misconfigured switches or network devices, causing communication failures or degraded performance. Resolution Both DMS and GCM Ethernet NIMs comply with the IEEE 802.3 standard as defined in the early 1990s. Port Speed: 10 Mbps Duplex Mode: Half-duplex Ensure that connected network equipment (switches, hubs) is configured to support 10 Mbps half-duplex to maintain reliable communication.

Issue When Microsmart AP7 (Application Type 7)/Chain Calculation points are learned into Niagara G3 using the DMS driver, they appear as Numeric Points but are not writable. This prevents operators from sending setpoint values to LOOP points in Microsmart controllers. Product Line TAC IA Series Environment Niagara G3 DMS Microsmart Cause AP7 points are learned into the Niagara G3 station as Numeric Points without write capability. These points are not linked to the DMS database, limiting control functionality. Resolution To enable write capability for AP7 points: Locate the AP7 point in Niagara G3. Learn the PVALU element of the AP7 point into the database. Open the Property Sheet of the object and add a Command String. After adding the Command String, an Action option will appear on the Wire Sheet, which can also be transferred to a graphic for operator use.

Issue Customer needs to replace a failed DMS-35 controller and wants to know if a DMS-350A can be used as a substitute. Product Line TAC IA Series Environment DMS-35 Controller DMS-350A Controller Cause The original DMS-35 controller has failed. Customer has a spare DMS-350A from a previous retrofit project. Resolution Yes, a DMS-350A can replace a DMS-35 controller, provided the following conditions are met: Include at least one DCM MicroSmart controllers connect to the DCM, and the DCM connects to the DMS-350A. Firmware Compatibility Ensure the firmware level in the DMS-350A and DCM matches or exceeds the MicroSmart controllers. Example: If MicroSmart controllers are revision 10.x, then DMS-350A and DCM must be revision 10.x or 11.x. Database Considerations The DMS-35 database cannot be installed directly into a DMS-350A due to DCM requirements. Points in MicroSmart controllers must be re-linked, creating a new database.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Robertshaw DMS T99 Sensor Integration with MNL Controller Using Curve Fit Object

DMS MSC-NC Connects but Fails to Access Networked MicroSmart Controllers

Can Belimo NF-24SR Actuator Share Transformer with DMS MSC-MPC Controller?

Niagara R2/DMS Integration – Re-learn Fails After Point Deletion

MSC-LIM-1 Compatibility with DMS Microsmart Controllers

DMS-350A Battery Does Not Charge After Replacement

DMS OPRIF 11.6 Freezes When Tunneling with Niagara R2 or G3

DMS OPRIF 11.6 Desktop Shortcut for DCT Does Not Function

Recommended USB-to-Serial Adapter for DMS Operator Interface (OPRIF) v11.6

Passing Analog Data Between Multiple I/A Series UNC-520s and DMS Panels

Identify Enhanced vs Non-Enhanced MSC-P1502 MicroSmart Controllers in DMS

DMS MicroSmart Global Point Broadcast Not Working

Slow Communication Between DMS-3500 and Niagara R2 UNC-520 – Optimization Tips

Resistance Values for EOL Module (RBSC-16) on DMS Microsmart Controller Trunks

Unoccupied Heating Mode Behavior on Type 2 Mode Control in DMS Microsmart

Determine Point Capacity of DMS-3500 on a Live System

DMS Loop Point Output When Setpoint Equals Process Variable (Proportional-Only Control)

Ethernet NIM Speed and Duplex Settings for DMS and GCM Modules

How to modify a Microsmart point, learned as a Numeric Point, using the Niagara G3 DMS driver.

Can a DMS-350A Controller Replace a DMS-35 Controller?

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!