- More Assistance
|TAP (Tigo Access Point) is a wireless transceiver that sends and receives data within your array. 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 TAP is hard-wired to the CCA and transmits this data via an RS-485 cable. If the system loses communication with an array, it may be due to a wiring error. The Tigo EI App has the ability to run a test to confirm if it is still connected.
Note: Do you have an MMU or original Cloud Connect? For information on testing Tigo legacy equipment, please go to: Gateway Test (legacy)
Common symptoms of a poor TAP connection, can include:
- System Discovery failure
- A lack of data on the Tigo Portal (under View > System View)
- Reporting data, but a large section of the array is grey (not communicating)
To confirm that there is an issue, you will need to perform a TAP Test, using your Tigo EI App.
In order to initiate the TAP test, do the following:
1. Connect your device to the CCA:
How do I connect my phone to the CCA?
2. Once connected to your CCA, do the following to open the Settings:
- Choose CCA Configuration (menu will open)
- Select Settings from the menu options
3. Start the test as follows:
- Press TAP TEST (at bottom)
- Select START TAP TEST (at bottom)
- Allow test to complete to show the number of TAPs found
4. Select 'Click to view Details' to see the list of TAP serial numbers:
Within the resulting list of serial numbers, you can easily identify which TAPs are not responding, in a multi-TAP setup.
If the TAP Test shows No TAPs Detected (or less TAPs than expected), try these troubleshooting techniques:
Check Port Power
Measure for 24 VDC on the Gateway/TAP terminal connector (at the CCA). If the terminal port delivers less than 12 volts:
- Power off the CCA
- Remove Gateway/TAP 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 TAP (if multiple, they should all be the same).
- Check the entire length of RS-485 cable, from the Data Logger to the TAP(s). Make sure there are no tears, animal damage, bends, kinks or aggressive zip-ties.
- Make sure the last TAP (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 TAP Test again. If the result is still No TAPs Detected, remove the TAP(s) from the rooftop and bring them down near to the Data Logger. Connect the TAP directly to the CCA, using a brand new short piece of RS-485 cable (approx. 2 foot long) and run the TAP 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 TAPs). For more info, see: TAP and GATEWAY Communication Cable Installation
Questions, regarding wiring? Please review: TAP Communication Cable Guide
If you require additional assistance, please Contact Support while on site.