Contents:
Introduction
| The Gateway is Tigo's original Legacy rooftop transceiver (predecessor to the modern TAP). It provides a wireless radio signal (2.4 GHZ ISM band), that communicates with the system's MLPEs (module level power electronics, or Maximizers/Optimizers) to gather their power reporting. |
The Gateway is hard-wired to the Data Logger (MMU / Cloud Connect / CCA) and may experience connectivity issues if that wire is damaged by force or weather.
Symptoms
Common symptoms of a poor Gateway connection, usually include a the lack of data on the Tigo Portal (account). The system may not be providing any modern data, or (in the case of multiple Gateways) the system may be sending data, but a large section of the array will be grey. To confirm, you will need to perform a Gateway Test.
Test
The Tigo MMU and the Cloud Connect are Legacy Data Loggers. Both offer a simple button selection on the front of the device, and a menu for running commands and troubleshooting.
To perform a Gateway Test at the Data Logger (MMU or CC):
- Press Menu (press enter)
- Arrow down to 2. Control (press enter)
- Arrow down to 2.5 Gateway Test (press enter)
- "Are you sure?" (press enter)
Note: The MMU does not offer Bluetooth connectivity. The only method of testing available, involves this method of using the keypad on the device. Whereas the Cloud Connect Data Logger does offer Bluetooth, and can be tested with the button method (above) or by connection to the Tigo EI App.
For information on testing Bluetooth enabled Data Loggers via the Tigo EI App: CCA - TAP Test.
Troubleshooting
If the Gateway Test shows No Gateways Detected (or less Gateways than expected), try these troubleshooting techniques:
Check Port Power
Measure for 24 VDC on the Gateway terminal (connector). If the terminal port delivers less than 12 volts:
- Power off the Data Logger
- Remove gateway cable connector
- Power on the logger (allow 2 minutes)
- Measure again
if still the result is still under 12 volts, the device may require replacement.
Check RS-485 Wiring for Errors
The most common reason for communication errors is a damaged or incorrectly wired RS-485 cable.
- Check both ends of the cable to insure that the wire colors are the same at both the Data Logger and the Gateway (if multiple, they should all be the same).
- 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 (in the string) includes a single 120-ohm resistor, installed between the B and A terminals.
Once you have checked the cable and corrected any wiring issues, run the Gateway Test again (at the Data Logger). If the result is still No Gateways Detected, remove the Gateway(s) from the rooftop and bring them down near to the Data Logger. Connect the Gateway directly to the Data Logger, using a brand new short piece of RS-485 cable (approx. 2 foot long) and run the Gateway Test again.
Note: Proper installation requires appropriately gauged cables, with twisted wire pairs (within the cable) for reinforcement. A high-quality shielded RS-485 cable is strongly suggested, but Ethernet (Cat-5/Cat-6) may work for short distances (with not more than 2 Gateways). For more info, see: TAP and GATEWAY Communication Cable Installation
Disclaimer
The Gateway, MMU and Cloud Connect are all Legacy devices (no longer eligible for coverage under Tigo's Limited Warranty). Any replacement of these devices would be at the discretion of the System Owner or Installer.
However, our Tigo Support Agents are sometimes able to assist in locating, or verifying the cause of the failure. If after trying the troubleshooting techniques (above) you have found no positive results, please feel free to Contact Tigo Support.
Note: Please be aware that troubleshooting this device requires that you are available on-site during the call.