A System Discovery is the specific process by which the CCA makes contact with the network and receives the system information (or configuration) from the Tigo Cloud. The process typically occurs upon commissioning, and takes about 15 minutes. After the initial Discovery is complete, the CCA uses the new configuration to identify and validate the remaining components of a system (TAPs and MLPEs). The validation process can take from 30 mins, up to 24 hours (for a large system).
Once the validation portion is complete, the MLPEs will start to create data and transmit it to the TAP. The CCA sends this data to the EI Portal for processing. It takes approximately 20 mins for the most modern data to appear on the EI Portal and the EI App for viewing.
Here is an example of a successfully completed Discovery and system validation process. All TS4-A-O units show the yellow bar at the bottom of the module and various shades of green that indicate power production.
Before starting Discovery, ensure all equipment, Inverter, CCA, and optimizers are installed and powered on. Also, ensure you have completed the entry of all CCA and TS4 serial numbers.
Discovery takes time! For a typical-sized residential system with proper TAP placement, Discovery normally completes in less than 60 minutes. However, due to processing times, module icons can remain gray for at least 15 to 30 minutes after they are discovered. Please allow 60 minutes or longer before requesting technical support.
If Discovery can not find all TS4 devices in 60 minutes (or up to a few hours in larger systems), the Discovery process will continue even into the next day. Please allow at least 2 hours after sunrise before requesting support on undiscovered TS4s by contacting Tigo Support using the information below. This ensures the TS4s have enough voltage.
Undiscovered TS4s appear as blacked out or empty modules with no number results. In this example, notice the 3 black modules indicating those TS4-A-Os have not been discovered.
If the Discovery Fails to complete or the system never generates data, there may be an issue with the build on the system.
Number of Gateways/TAPS found is different than the amount indicated online.
Remember, the online build is the repository of all equipment for the system. If the number is inconsistent, there may be an issue with the build, or with the units on site. Review the online Equipment List to see if it is correct. Then, check cabling for improper connection or damage. Each Gateway/TAP should be wired correctly (with no exposed copper), to match the Gateway Port on the logger.
TAP(s) are too far away from MLPEs
The TAP will attempt to find and connect with all of the TS4 units, based upon their serial number. The system must find up to 75 percent of the serial numbers, in order for the system to be considered Discovered. This means that:
- The TAP must be wired, correctly and placed in the correct section of the array.
- The TS4 (or MLPE) units must be connected to their PV Modules and energized (sun).
- There can be no obstacles to the line-of-sight radio signal
Check to make sure that the system Map is correct (for the MLPE serial numbers) and make sure that the TAP is within at least 10 feet from the first 5 units.
For more information, see TAP Placement.
Incorrect serial numbers entered in Layout for a TS4.
Albeit rare, there are some conditions where the wrong serial numbers are updated to the Tigo Portal. This can happen if there is a team of installers who are working on multiple systems at a time. Make sure that the system has the correct serial numbers, so the TAP can be successful in it's search.
MLPEs are not receiving the minimum voltage (16 VDC) from the PV module.
Disconnect from string and measure the output of the unit. If there is no voltage, then disconnect the Tigo TS4 from the PV Module and measure the voltage coming from off the panel. If OK, reconnect and check connectors to make sure that each are fully latched. Remeasure the voltage on the string side connectors - if voltage is 0 then the unit is either in RSD (rapid shutdown) or there is something wrong with the MLPE.
In this case, there are only a couple possibilities:
- The unit(s) are in RSD, because they were Discovered, but the TAP is no longer transmitting the keep-alive signal (could indicate a wiring or power issue in the TAP or CCA).
- The unit(s) are in RSD, because they were previously Discovered on another system, and cannot receive signal from this new system (until re-assignment). This happens for installers who are re-installing salvaged units from another system.
- The unit(s) are damaged in some way. This can happen if the installation was assembled incorrectly. Always follow the directions
If you experience any issues with troubleshooting Discovery, please do not hesitate to Contact Tigo Support for assistance.