Trane Symbio 700 Wiring Diagram

Reading a Trane Symbio 700 Wiring Diagram Without Losing Your Mind

The Trane Symbio 700 is a variable air volume terminal unit, and like most modern VAV boxes, it runs on a control board that communicates with a DDC system while also handling a bunch of hardwired field connections. The wiring diagram isn't something you pull up and instantly understand. I spent about three hours with one last fall just trying to figure out why a reheat valve wasn't responding to the controller output. The problem turned out to be something most diagrams don't explicitly call out: the 24VAC transformer secondary shares a common with the controller ground, and if you're running isolated signals on a different circuit, you create a ground loop that makes everything act weird. The official diagram lives in the installation and operation manual for the Symbio 700 series. Trane publishes these through their official documentation portal at trane.com/commercial under the support section. You'll need the specific model suffix to pull the right one—the S700-E, S700-V, and S700-H all have slightly different terminal block layouts depending on whether you're working with electric reheat, hot water coil, or chilled water coil configurations. The diagram itself is usually labeled as Figure 4 or Figure 5 in the manual, and it covers the main control board (the LCP-200 or newer integrated controller depending on the production date), the transformer, the sensor inputs, the actuator outputs, and the communication terminals for BACnet or LonWorks. If you can't find the exact one for your unit, Trane's technical documentation team will email you a PDF within a day if you call their commercial HVAC support line. It's faster than navigating their website in my experience. The direct part number for the manual is typically something like S700-IO-001 or S700-MO-001 depending on whether it's the installation or operations manual. Both contain the wiring diagram you need.

What the Diagram Actually Shows

The Trane Symbio 700 Wiring Diagram breaks down into several main sections on the page. On the left side you'll see the line voltage input—usually 208-230VAC single phase—and the transformer that steps it down to 24VAC for the control circuit. The transformer is typically rated at 60VA for the basic unit, but if you're running a high-load electric reheat panel or multiple actuators, you may need an external transformer. The diagram will flag this with a note near terminal T1 and T2 on the control board. The middle section covers the control board terminal block. This is where most people get confused because the terminal designations change depending on the firmware version. Older boards use designations like +24, -24, C, O1, O2 while newer ones might label them as Term 1, Term 2, Comm+, Comm-. The diagram will have a small table on the side that maps the old designations to the new ones. Always check the date code on your control board before you assume the terminal labels match the diagram exactly. The right side of the diagram shows the field wiring connections: temperature sensor, duct pressure sensor, reheat actuator, damper actuator, and the communication bus. Each of these has its own section with wire gauge recommendations and polarity notes. The communication bus is the one that causes the most problems in the field. The Symbio 700 supports both BACnet MS/TP and LonWorks, and the diagram shows two separate terminal pairs for each. You only connect one or the other. I've seen technicians wire both because the diagram shows them on the same page, and then wonder why the controller throws a communication fault on startup.

Common Wiring Issues I've Run Into

Here's a specific problem that cost me half a day last spring. I was troubleshooting a Symbio 700 that kept cycling the reheat valve open and closed every thirty seconds. The diagram showed the actuator connected to O1, which is the standard reheat output. Everything measured correctly at the terminals. The problem was that the building's DDC system was also sending a modulating signal to the same VAV box through the BACnet network, and there was a conflict between the local control board's PID loop and the external setpoint being sent over the bus. The diagram doesn't show this interaction because it's a configuration issue, not a wiring issue. The workaround was to set the controller to "BACnet Master" mode instead of "BACnet Slave" mode, which disables the internal setpoint override and lets the external system take full control. Once I made that change, the cycling stopped immediately. Another issue that comes up regularly is the duct static pressure sensor wiring. The diagram shows a 2-10VDC input or a 4-20mA input depending on the model. The problem is that some installers run the sensor on 4-20mA but jumper the board for 2-10VDC, or vice versa. There's a physical jumper on the control board labeled SENSEL or SENSOR TYPE that you have to set correctly. If it's wrong, the controller reads garbage from the sensor and the damper goes full open or full close and stays there. I always verify the jumper position before I even connect the sensor wires.

Wire Gauge and Connection Best Practices

The diagram specifies 18-22 AWG wire for all low voltage control connections, and I'd stick to 18 AWG minimum. Thinner wire picks up noise on the communication lines, especially if you're running BACnet MS/TP over long distances. For the 24VAC power conductors, 18 AWG is fine for runs up to about 50 feet. Beyond that, you start seeing voltage drop that can cause the controller to reset intermittently. If your runs are longer than that, go to 16 AWG for the power conductors and keep the signal wires at 18 AWG shielded twisted pair. The communication bus wiring deserves special attention. BACnet MS/TP requires a shielded twisted pair cable, and the shield has to be grounded at only one end of the segment. If you ground it at both ends, you get ground loop currents that corrupt the differential signal. The diagram shows the shield terminal on the controller board, but it doesn't explicitly tell you not to ground it at the device end. I learned this the hard way on a project with twelve Symbio 700 units on a single MS/TP segment. We had constant communication drops until we traced it back to the shield being grounded at every device. Once we cut the shield connection at eleven of the twelve units and left it grounded only at the controller, the network stabilized completely. For LonWorks, the requirement is similar but the cable type is different. You need a shielded twisted pair rated for LonWorks, typically Belden 9941 or equivalent. The polarity matters on LonWorks too—terminals are usually labeled A and B, and while the protocol can tolerate reversed polarity in most cases, it's better to get it right the first time to avoid intermittent issues.

Reading the Diagram Step by Step

Start at the line voltage input terminals on the diagram, usually labeled L1, L2, and GND. Verify that you have the correct voltage at these terminals with a multimeter before proceeding. If you have 208-230VAC, the transformer should be receiving power. Check the secondary side for 24VAC between the R and C terminals. If you don't have 24VAC, the transformer is either bad or the primary fuse on the control board has blown. The diagram will show the fuse location—it's typically a small blade-type fuse near the transformer connections. Next, trace the 24VAC distribution. The R terminal is the hot 24VAC output from the transformer, and C is the common. All the low voltage components—sensors, actuators, the controller itself—get their power from these two points. The diagram will show jumpers or bus bars connecting multiple terminals. Don't add additional loads beyond the transformer's VA rating. A standard 60VA transformer can handle the controller, one damper actuator, one reheat actuator, and a couple of sensors. If you're adding anything beyond that, you need an external transformer, and the diagram will have a section showing how to wire it in. The sensor inputs come next. The Symbio 700 typically uses 2-kilohm thermistors for temperature sensing and a 0-10VDC or 4-20mA input for duct static pressure. The diagram shows the sensor wiring with polarity for the thermistor (it doesn't actually matter which way you connect a thermistor, but the diagram labels them anyway) and explicit polarity for the voltage and current inputs. Get the polarity wrong on the pressure sensor and the controller will read negative pressure, which makes the damper behave erratically.

Actuator wiring is straightforward but easy to mess up if you're not careful. The diagram shows two types of actuators: modulating and floating. Modulating actuators take a 2-10VDC or 4-20mA signal and position the valve or damper proportionally. Floating actuators are either fully open or fully closed and take a simple on/off signal. Make sure the actuator you're connecting matches the output type on the diagram. I once connected a modulating actuator to a floating output terminal and spent an hour wondering why the valve only opened or closed fully instead of modulating. The fix was moving the actuator to the correct output terminal and reconfiguring the controller setting.

Troubleshooting Using the Diagram

When something isn't working, the diagram is your roadmap for isolating the problem. Start by identifying which circuit the component is on. If the damper won't open, find the damper actuator on the diagram and trace its connections back to the control board terminal. Then check for voltage at that terminal with the controller powered on and calling for demand. If you have voltage at the terminal but the actuator isn't moving, the actuator or the wiring between the terminal and the actuator is bad. If you don't have voltage at the terminal, the problem is in the controller or the controller's configuration. For communication issues, the diagram shows the bus topology and termination requirements. BACnet MS/TP requires a 120-ohm termination resistor at each end of the segment. The Symbio 700 has a built-in termination resistor that you activate with a dip switch on the controller board. The diagram indicates which dip switch to use. Most people miss this and never terminate the line, which causes reflections and dropped packets on longer runs. I always check the termination resistors first when a BACnet network is acting unstable. If the controller itself is the problem, the diagram shows the power supply section and the communication port pinouts. You can use these to verify that the controller is receiving proper power and that the communication signals are within spec. A healthy BACnet MS/TP segment should show about 2-3VDC differential between the A and B lines when idle. If you're measuring significantly more or less than that, you have a wiring or termination problem somewhere on the segment.

The Trane Symbio 700 Wiring Diagram is a solid reference once you know how to read it, but it doesn't tell you everything. The real knowledge comes from understanding how the electrical sections interact with the control logic and the communication protocols. Without that context, you're just following lines on a page and guessing when something doesn't work the way you expected. The diagram gets you started, but experience tells you where the gotchas are.