Issue What is a suitable replacement for SHM-001 or SHM-002 short haul modems used with DMS control systems? Product Line TAC IA Series Environment DMS Systems using SHM-001 or SHM-002 short haul modems Cause Failure of SHM-001/002 short haul modems or inability to source discontinued models. Resolution   Recommended replacement: Model 1000SM from Patton Electronics Product details: Patton Electronics Model 1000SM Refer to original SHM-001/002 datasheet for wiring and installation guidance (Attachment: shorthaulmodem.pdf).

Issue Can the MF41-6043 actuator be wired to and controlled by a DMS MicroSmart MSC-V-511 controller when replacing a defective actuator? Product Line TAC IA Series, Field Devices Environment DMS MSC-V-511 MF41-6043 Cause The original actuator is defective and discontinued, making it impossible to replace with an identical unit. Resolution The MSC-V-511 controller can control the MF41-6043 actuator using its triac outputs. Terminals D1 to D4 on the MSC-V-511 provide 24 Vac, which matches the actuator’s voltage requirement. No external power source is needed because the MSC-V-511 supplies 24 Vac power. Wiring and programming details: Refer to MSC-V-511 Installation Guide (F-25710), page 18. Refer to MF41-6043 Installation Guide (F-26736), page 6 for wiring diagrams. Power considerations: Actuator requires 2.3 VA. MSC-V-511 digital outputs can supply up to 12 VA.

Issue How to identify controllers in a DMS system that do not support MicroSmart functionality. Product Line TAC IA Series Environment DMS Installations Cause Older DMS controllers manufactured prior to revision 9.X were not designed with MicroSmart capability. These units are not referenced in Niagara DMS/MicroSmart integration documentation. Resolution Controllers without MicroSmart capability are accessed exclusively through DMS programming. MicroSmart functionality cannot be added to these controllers. Common non-MicroSmart controller models include: Slave CO/CI Module: N604-002, N604-012 Slave AI Module: N604-003 Slave Pneumatic Motherboard: N604-004 Slave AO Module: N604-016, N604-017 General Purpose Slave Module: N604-021, N604-025 These controllers can coexist on the same trunk with MicroSmart controllers (revision 9.2, 10.X, or 11.X) if: Slave controllers have revision 9.0 firmware installed. The trunk uses a 2-wire design (not 4-wire). For additional details, refer to Tech Tip #350-95-03 (Attachment: TT350-95-03.pdf).

Issue How to configure an analog input on a DMS MicroSmart controller to function as a voltage input. Environment MSC-MPC (Revision 10) MSC-MPC-001 (Revision 11) Product Line TAC IA Series Cause The controller needs to accept voltage signals from sensors, but analog inputs must be configured correctly to interpret voltage rather than other signal types. Resolution To configure an analog input as a voltage input: Reference: MSC-MPC Install Instructions (F-24804-4)

Issue When integrating Microsmart controllers with Niagara G3 using the DMS driver, Mode Control points learned as Numeric Points cannot be modified directly. How can the stage setpoints (PVALU elements) be changed from the Niagara G3 station? Product Line TAC IA Series Environment Niagara G3 Microsmart driver Microsmart controllers Cause Mode Control points are learned into Niagara G3 as Numeric Points without writable options, preventing direct modification of stage setpoints (PVALU elements) from the station interface. Resolution Add PVALU Element to Database: Locate the Mode Control point and add the PVALU element for the specific stage to the Niagara G3 database. Update Command String and Index: Modify the Command String to include the PVALU element. Set the Index value to match the PVALU element (e.g., Index = 6 corresponds to PVALU,6 ). Enable Writable Action: After configuration, right-click on the Numeric Point in Niagara G3 to access an action item allowing modification of the PVALU element. Result: You can now adjust stage setpoints for Mode Control points directly from the Niagara G3 station interface.

Issue How to configure an analog input on a DMS MicroSmart controller to function as a contact input when no dedicated contact inputs are available. Product Line TAC IA Series Environment MSC-MPC (Revision 10) MSC-MPC-001 (Revision 11) Cause No contact inputs available on the MSC-MPC Resolution Below are illustrations and explanations on how to configure an analog input as a contact input.  

Issue When wiring a TS-58011-774 Platinum RTD sensor to a DMS Microsmart MSC-MPC controller, what are the acceptable offset values for accurate temperature readings? Can the wire length exceed 200 feet? Product Line TAC IA Series Environment DMS Microsmart controllers TS-58011-774 Platinum RTD sensor Cause A significant offset (approximately 6°F) was required to match readings with a handheld calibration device, raising concerns about wiring length and sensor accuracy. Resolution Offset Values: There is no fixed maximum or minimum offset value. Proper wiring minimizes the need for large offsets. Wire Length: Do not exceed 200 feet. Recommended Cable: Belden #9501 (AWG24). Calibration Steps: Review the sensor installation guide (F-24874) for Software Setup (page 3). Use the temperature/resistance table (page 5) to verify sensor accuracy. Apply appropriate offset values to correct wire-induced error. If necessary, use SOCALC (page 4) to create custom SCALE and OFSET values. Reference: TS-58000 Series Platinum RTD Room Sensor Installation Guidelines (F-24874)

Issue An ENC licensed for DMS displays the error: Unlicensed: javax.baja.license.FeatureNotLicensedException: tac_llc:tacdms when attempting to access the DMS Network property sheet in Workbench. Product Line TAC IA Series Environment I/A Series G3, ENC-520 with TAC-LLC license installed Cause Although the TAC_LLC.license file is installed, the corresponding TAC_LLC.certificate is missing. The license will not be recognized without its certificate. Example of correct configuration: Licenses: TAC_LLC.license (never expires), Tridium.license Certificates: TAC_LLC.certificate, Tridium.certificate Resolution Two options to resolve the issue: If public Ethernet connectivity is available: Open Workbench and connect to the ENC. Navigate to Platform → License Manager. Select Import → Import licenses from license server. This will download and install all available licenses and certificates automatically. If public connectivity is not available: Download the attached TAC_LLC.certificate. Use Workbench to import the downloaded certificate file.

Issue In a DMS installation, a controller listed as SAI in OPRIF does not appear as a Microsmart controller, even though its points update correctly. Users are unsure how to save its database. Product Line TAC IA Series Environment DMS (all revisions) Cause The SAI controller is an early-generation device designed for the DMS product line. It is a Slave AI Module (part number N604-003) with six analog inputs and firmware revision 8.x. Unlike Microsmart controllers, the SAI is not a smart controller and does not store or require a database. Resolution The SAI controller does not support database storage; therefore, there is no need to back up its database. All analog input points for the SAI must be created and managed directly in the DMS system. Identification tips: Look for part number N604-003 on the controller sticker. Check the PCB for an IC labeled with firmware 8.x. Reference diagram: SAI Module Figure. 

Issue Communication failures with Microsmart controllers on the DMS bus network. Product Line TAC IA Series Environment Microsmart controllers (all models installed with revision 9.x, 10.x, or 11.x firmware) Cause Common causes include: Incorrect power supply wiring or insufficient voltage Shared power between controllers and field devices Exceeding maximum controller count per RS-485 segment Improper network topology or cable type Missing or incorrectly installed End-of-Line (EOL) modules Ground loops or shield continuity issues Duplicate or illegal point names in controller database Faulty line drivers or incorrect address switch settings Resolution The following checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. Do all controllers have a power supply? Each takes 24 VAC from a Class 2 transformer ACTION: Confirm with a voltmeter. If no voltage present, check on-board fuse and then the local circuit breaker. Note: Do NOT ground the transformer’s secondary when powering a MSC-MPC-001. With other controller types, the secondary is grounded. If voltage is present, must be within tolerances (20.4 to 30 VAC) Confirm power (VA) requirements. Varies per controller (see installation instructions) Do the affected controllers share a common power supply? The MSC-MPC-001 must have its own DEDICATED power supply Other controller types can share the same AC transformer provided the VA rating is adequate ACTION: Review power wiring (see installation instructions) Do the affected controllers share a common power supply with output field devices? Power for the controllers and power for the output devices MUST REMAIN SEPARATE ACTION: Review controller and field device power wiring (see installation instructions) In addition, avoid wiring any half-wave and fullwave powered devices to the same transformer. How many MicroSmart controllers exist? Firmware revision 9, 10, & 11 family controllers can communicate on the same RS-485 wire segment simultaneously Maximum per RS-485 segment = 30 (31 if no repeater is installed) ACTION: Determine controller count If there are more than 31, a repeater/router is required If there are more than 62, only firmware revision 11 family controllers can be physically addressed higher than 62 Connect the first 30 controllers (isolate any additional nodes) and attempt/stabilize communications. Any repeaters installed? Allows the connection of two or more RS-485 wire segments Extends the maximum controller count by 30 (maximum of 124 addressable nodes supported) ACTION: Identify model number Review settings using its installation instructions Replace line drivers with known, good ones (Part# E21-1144) How rapidly is the Watch Dog Timer (WDT) LED blinking? Once / second = proper network communication A controller’s logical address is always one higher than the number calculated by the switch settings. For example, if all switches are OFF (binary equivalent of 0), the controller’s logical address is 1. If switches 1 & 2 are ON (binary equivalent of 3), the controller address is 4. Network wire connections ARE polarity sensitive. ACTION: Review LED activity No blinking but illuminated Verify proper power requirements & wiring (see installation instructions) Perform a hardware clear (place all address switches in the ON position and power cycle the controller) No blinking & not illuminated Check the on-board fuse Blinking faster than once / second Check the address switch for proper position. Verify address is not duplicated on the network Check the network connector and ensure it is properly inserted Ensure the + wire and – wire are properly identified and the shield wire is also connected. What is the length and topology of the controller trunk? Bus Topology Daisy-chain (no tees) 4000ft/1219m maximum wire length Trunk wiring is polarity sensitive Recommended cable: 24 AWG twisted-pair, shielded General Purpose: Under 1000ft, Belden#9501 Over 1000ft, Alpha#9823C Plenum & Riser-Rated: Under 1000ft, Belden#89503 Over 1000ft, Belden#89182 ACTION: Review the following: Ensure two EOL modules are installed. Each module must be installed correctly (black dot on module in the same corner as the white dot on the circuit board) Remove each EOL and check for following resistances: Pins 1-8: 3.3 kohms Pins 3-6: 150 ohms Pins 4-5: 3.3 kohms Ensure there are no ground loops in the + and – wires. To do this, use a multi-meter & measure the + and – wires, separately to earth ground Ensure the shield wire is continuous throughout the entire length of the trunk and connected to a solid earth ground in only one location Replace line drivers on the controllers (Part# E21-661). Check trunk voltages: + to earth ground: 2.2 – 2.6 Vdc – to earth ground: 2.2 – 2.6 Vdc If 0 Vdc or 5 Vdc is detected, check other controllers for bad line drivers. Determine cable used. If it is shielded, connect it to earth ground in ONE location through a 470 kK, ¼ watt resistor. The shield must be continuous throughout the wire segment. What is the condition of the controller database? ACTION: Review the controller database Illegal point names must be corrected. Illegal characters are: / # * : ; $ = | &. Duplicate point names must be corrected Will Operator Interface (Part# PS-OPRIF) communicate to the controller? Direct connection to a controller can only be done with the Firmware Revision 10 & 11 Families Accessing a networked controller through a direct connection using a MSC-LIM is possible but very slow (300 baud maximum). It is only recommended for checking communication status and not for application programming. It will also require a master controller (DMS35/350A/3500) ACTION: Attempt an upload of the controller database Requires a Laptop Interface Module (Part# MSC-LIM) Operator Interface version 11.41 and 11.6 both support direct connection to a controller If communication fails to work, try another controller to eliminate the pc and interface cabling from the troubleshooting process

Issue A mothballed building is being recommissioned. It uses a DMS-35 with Microsmart controllers for building automation. The customer needs to know what the DMS-35 looks like, its dimensions, and the appearance of the power and communications connectors, which are missing. Product Line TAC IA Series Environment DMS-35 Cause Connectors for power and communications cables are missing, and the customer requires visual identification for installation. Resolution Digital photos of the DMS-35 unit are provided for reference. Scanned images of the obsolete installation guideline (portions thereof) are included to show connector details. Refer to the attached files: DMS35images.pdf dms35installguide.pdf

Issue A panel unit’s title (description) in a DMS database needs to be updated. How can this be done using OPRIF? Product Line TAC IA Series Environment DMS Operator Interface (OPRIF) All revisions of DMS 35, DMS 350A, and DMS 3500 Cause Equipment naming has changed, requiring updates to the DMS database to maintain consistency. Resolution   Access the Message Text Table in OPRIF. Locate the Panel Unit Descriptor Message that needs modification. Use the following steps: Cursor down to the descriptor requiring modification. Press the “=” key. Type the new text for the title. Press Enter to save changes. For detailed instructions, refer to Chapter 4 – “Setting Up Tables” in the DMS Operator Interface User’s Guide (F-25467).

Issue Where can Windows 10-compliant legacy tools be obtained for use with DMS and NETWORK 8000 products? Product Line TAC IA Series Environment DMS NETWORK 8000 Cause Legacy tools require updated versions to ensure compatibility with Windows 10 environments. Resolution Windows 10-compliant versions of the following tools are available for download: OPRIF 11.6 (for DMS products) PSI 4.1 (for NETWORK 8000 products) The PSIv4.1.zip package includes: XPSI PSI MF2 AirBalance MicroNet-CI MicroNet AirBalance Important Notes: Direct ASD connection is supported when using the recommended SerialComm USB to RS485 Adapter (Model USB-485B) for use with PSI.  MNet-CI and MNet-Air Balance require the use of an MN-CIM converter. This is an RS-232 to U-Link adapter that connects between the laptop and MicroNet 2000 U-Link sensor bus. The MN-CIM adaptor is obsolete and no longer manufactured. This will also require either a laptop with an RS-232 port or a USB to RS-232 serial adapter capable of working with the MN-CIM. The recommendation is to purchase a Keyspan USB to RS-232 serial adapter from Tripp-Lite. These tools are not compatible with 64-bit Windows natively, but can operate in XP Mode. Operating System Compatibility Table: Tool Win 10 32-bit Win 10 32-bit XP Mode Win 10 64-bit XP Mode Win 10 64-bit PSI/XPSI 4.1 Yes Yes Yes No MNCI 4.0 Yes Yes Yes No Microflo Balance 4.0 Yes Yes Yes No PSOPRIF 11.6 No Yes Yes No

Issue Are the Network 8000, DMS, and Signal product manuals available in an electronic format? Product Line TAC IA Series Environment Network 8000 DMS Signal Cause Customers and support teams need access to legacy product manuals in electronic format for reference and operational purposes. Resolution The attached Legacy.zip file includes Network 8000, I/A Series MicroNet 2000, DMS and SIGNAL product data, installation, user, and engineering documents.

Issue When connected serially to a DMS panel using Operator Interface (OPRIF), symbolic points cannot be added to the DMS, and Microsmart points fail to link. Product Line TAC IA Series Environment UltiVist server networked with multiple DMS panels via Ethernet DMS350A, DMS3500 (all firmware versions) Local serial connection to DMS panel using OPRIF software Cause The PSWRD element in the DMS database restricts point creation and linking when the panel is flagged as networked with an UltiVist server. If PSWRD contains an “N” flag (e.g., PSWRD = 159 03 2 N ), commands for creating, linking, or deleting points are blocked via serial OPRIF connection. Resolution Modify the PSWRD element to remove the “N” flag, allowing full database manipulation via serial connection: Example: PSWRD = 159 03 2 This enables point additions, deletions, and linking through OPRIF. Refer to Commands and Elements Reference (F-25469) for detailed instructions.

Issue USRobotics 5686 series modems fail to connect properly with DMS panels. Product Line TAC IA Series Environment USRobotics 5686 series DMS panel Cause The V.92 protocol is enabled by default on USRobotics 5686 modems, which prevents compatibility with older modems used in DMS panels. Resolution Disable the V.92 protocol on the USRobotics 5686 modem by entering the following setup string (without quotation marks) in addition to any required strings from the referenced bulletin, then save the settings: AT +PIG=1 +PMH=1 +PQC=3 Refer to Bulletin 00-19 for additional configuration details.

Issue Can existing communication wiring from a NETWORK 8000 (ASD) or DMS (MicroSmart) system be reused for a BACnet MS/TP trunk? Product Line TAC IA Series Environment NETWORK 8000 (ASD) cable DMS (MicroSmart) cable BACnet MS/TP Cause ASD and MicroSmart cables were designed for lower baud rates. BACnet MS/TP networks often require higher speeds, which these cables may not reliably support beyond 9600 or 19200 baud, especially over extended distances. Resolution Reuse Conditions: ASD and MicroSmart wiring can be reused for BACnet MS/TP only at 9600 baud, and possibly 19200 baud under limited conditions. For higher baud rates or longer cable runs, replace with BACnet-compliant cable. Recommended Cable Specifications for BACnet MS/TP: Type: Shielded twisted pair Gauge: 18 AWG or 22 AWG Impedance: 100–120 Ω Capacitance: ≤ 30 pF/ft (98 pF/m) Maximum Length: 9600 baud: up to 1200 m (4000 ft) 38400 baud: up to 1200 m (4000 ft) with proper cable Examples: Belden 3105A, 3106A or equivalent Ensure proper network biasing and termination when reusing existing wiring. If communication issues persist, migrate to recommended cabling standards for BACnet MS/TP. Cable Specification Comparison Parameter ASD / MicroSmart Typical Cable BACnet MS/TP Recommended Cable Type Unshielded or basic twisted pair Shielded twisted pair Gauge 22–24 AWG 18–22 AWG Impedance ~70–90 Ω 100–120 Ω Capacitance ~50 pF/ft (164 pF/m) ≤ 30 pF/ft (98 pF/m) Shielding Often none Foil or braided shield Max Segment Length Designed for ASD baud rates 1200 m (4000 ft) at 9600–38400 baud Examples Legacy ASD/DMS cable Belden 3105A, 3106A or equivalent

Issue How can the factory default settings for the Level 3 password and the two serial ports be restored on a DMS-3500? Product Line TAC IA Series Environment DMS-3500 Cause The Level 3 password and serial port settings were changed and need to be reset to factory defaults for system access. Resolution To restore factory defaults for the Level 3 password and serial ports: Power On the DMS-3500. Remove the cover to expose the circuit board. Locate the CONFIG 2-pin connector near the green LED labeled SYS. Move the jumper from one pin to short both pins. Cycle power to the DMS-3500. This clears NOVRAM and restores default password and port assignments without affecting the rest of the configuration or database. After reboot, return the jumper to its original position (one pin). If not returned, new settings will be lost on the next power cycle. Default Settings After Reset: Level 3 Password: 170 Serial Port 1: 9600 1 7 E P N Serial Port 2: 2400 1 7 E P M ⚠ Caution: Always return the jumper to its original position after the reset.

Issue How to delete all or specific parts of the E: Segment in an UltiVist/DMS database. Product Line TAC IA Series Environment UltiVist/DMS Cause The E: Segment database needs to be removed or cleaned up due to outdated or incorrect configuration data. Resolution Use the KILBRNCH tool to delete the required segment. Backup the database before proceeding. Open an OS/2 window and navigate to the FI directory. Disable communications by typing: SET NOFCS=TRUE (This ensures KILBRNCH only deletes offline elements.) At the x:\\FI prompt, run the KILBRNCH command: KILBRNCH FI Example: KILBRNCH \\FI\\FI E:001.12.01.023 E: = Segment 001 = Network ID 12 = Panel ID 01 = DCM ID 023 = Controller ID After completion, re-enable communications: SET NOFCS=FALSE Refresh the E: Segment in UltiVist.

Issue An override command was applied to a Network 8000/DMS standard point on a SIGNAL graphic. The graphic shows the point in override, but the actual point in the field panel is not overridden. Product Line TAC IA Series Environment Network 8000 SIGNAL Cause The override command in SIGNAL does not properly update the field panel point due to a corrupted or outdated override data file. Resolution Clear the override data file and reapply the commands: Shutdown SIGNAL. Open Windows Explorer and navigate to: C:\Windows\Override Delete the file: override.dat Restart SIGNAL. Apply the override commands again. (The override.dat file will be recreated automatically.)