This article is a guide to help you troubleshoot Gateway communication issues and how to fix them.
|The Gateway is a wired rooftop transceiver that handles all communication for the Tigo MLPEs (module level power electronics). It is attached to the Data Logger, via RS-485 cable.|
The Tigo Legacy Data Loggers are the MMU and the Cloud Connect. Both offer a button selection on the front of the device, and a menu for running commands and troubleshooting:
- MMU gateway test does not display expected gateway(s)
- Discovery does not detect gateway(s)
- Not all gateways report on the Tigo website status page
- Poor or no wireless signal strength in a section of PV array known to have a gateway installed
Step 1: Perform a Gateway Test at the Data Logger
- Press Menu (press enter)
- Arrow down to 2.Control (press enter)
- Arrow down to 2.5Gateway Test (press enter)
- "Are you sure?" (press enter)
The MMU's gateway test results will determine how many gateways are able to communicate with the MMU, along with the serial numbers of the gateways.
Step 2: Check Gateway Status LED
All Gateways have a Status LED (located near the bottom of the chassis). The LED should be blinking Blue (for power) and Yellow (for communication).
• If the LED is solid Blue - There is power, but no communication
• If the LED is not on - There is no power and no communication
A lack of connection to the Data Logger can exist, due to a wiring error, damaged or weathered RS-485 cable, or even an issue with the Data Logger or Gateway (rare).
Step 3: Check RS-485 Wiring for Errors
The most common reason for communication errors is a damaged or incorrectly installed RS-485 cable. Since the cable is manually wired to both the Gateway and the MMU, it is important to check both connection points to make sure the wiring for the + - | A B terminals are correct on both ends and the wires have a clean installation.
Use the information from the gateway test to determine which gateway is not communicating, and then apply the process of elimination to find and isolate the issue:
- Check to see if terminal blocks on both the Data Logger and Gateway(s) are installed properly, the screw downs are tight and the the wire is inserted properly (no exposed copper).
- Check the entire length of RS-485 cable, from the Data Logger to the Gateway(s). Make sure there are no tears, animal damage, bends, kinks or aggressive zip-ties.
- Make sure the last gateway has a 120-ohm resistor installed between the B and A terminals.
The easiest way to verify if an RS-485 connection has been damaged, is to simply remove the Gateway(s) from the rooftop and re-connect them directly to the Data Logger with a short length of brand new (un-used) cable. Then, run the Gateway Test again to see if the Data Logger finds all of the Gateways.
You will know the issue has been corrected once the gateway test passes with all expected gateways communicating
Step 4: Contact Tigo Customer Care for Further Support
Please contact Tigo Support if you are unable to resolve the issue after going through the above steps. Provide all relevant information and results from your diagnostics.
Disclaimer: Due to the age of Tigo Legacy products, they are no longer considered eligible for Warranty coverage.