This article addresses the basic concepts of Tigo communication and the need for network functionality.
Tigo TS4 Systems are managed by data loggers that require access to the Internet. The internet connection is necessary for:
- Data transfer and visibility
- System Notifications and Alerts
- Remote updates and/or troubleshooting
There are three generations of data loggers available from Tigo. The version or model for your system may determine the specific steps you take, to reconnect to the network. Click on the image of your device below, to go to the unique troubleshooting article for that version.
Maximizer Management Unit (MMU) Ethernet connection, only (No WiFi) |
|
![]() |
(Ethernet or WiFi) |
![]() |
(Ethernet or WiFi) |
Your data is valuable!
Tigo does all that we can, to insure that you have full system functionality and data retention during network outages. A fully commissioned/discovered system that goes offline, will continue to :
- Produce Energy
- Optimize Modules
- Collect and store alerts and notifications
- Offer Rapid Shut Down (RSD) on modern TS4 systems
- Offer PV-Safe (operation is manually deployed from the Data Logger)
- Store production data for upload at a later time (storage not infinite)
Data Disclosure: Tigo Data Loggers are capable of storing production data (while offline) and automatically uploading the information to your cloud account, once the network is back. In cases of short network outages, the account should not lose any data. However, the amount of memory stored by the Data Logger, is dependent upon the size of the system (example: a system of 25 modules can store over 30 days of production data, while a larger system may store less).
If the duration of network outage is longer than the amount of memory on the Data Logger, the oldest data will be overwritten. Please know that this type of data loss cannot be retrieved.
Here are other instances where Data Loss is not retrievable:
- No AC power to the Data Logger (power supply failure)
- System not configured/discovered (blind deployment)
- Damage to Gateway or Data Logger (weather event, AC surge, etc)
- Communication loss between Gateway/TAP and Tigo MLPE's
- Communication loss between Data Logger and Gateway/TAP (wiring issue)
General Connectivity Issues
The first step in troubleshooting is to confirm if the Tigo Data Logger is still powered on, and functioning as expected. If it is, then there may be a general connectivity issue within your network. Here are some common network issues that you will want to check for:
- Router - Check Connection with the Internet
- Wired Network - Check Ethernet Connections
- Wireless Network - Check WiFi, MiFi, Hotspot Connections
- IT Administrator - Check Firewall Settings
- ISP - Check Data Allotment
Router - Check Connection with the Internet
A router can become disconnected with the internet, or even become sluggish and not recognize IP addresses. Try these steps to confirm the router is functioning as expected:
- Perform a Router re-start/power-cycle (allow up to 2 minutes for full reboot)
- Check the network speed with a computer or other internet connected device
- Check if the network router is configured for a static or dynamic IP address
If your settings are correct and you are still not passing data to the cloud, please contact your IT Administrator or Internet Service Provider (ISP). The service may not be allowing outbound access to the MMU (the network MAC ID of the MMU is the same as it's 12 digit Serial Number)
Wired Network - Check Ethernet Connections
All Tigo Data Loggers offer Ethernet (wired) connection. A wired network configuration is an extremely reliable option for connecting your Data Logger to the cloud. The setup is usually very simple, as it involves a direct Ethernet cable connection to a router/modem. However, networks can include extension devices that may require additional steps to connect. Here are some examples:
-
Active Hub or Switch
-
PLC (power-line communication) Adapter
-
Ethernet port on a WiFi extender or MiFi (mobile/cellular WiFi Hotspot)
-
Ethernet port on a Network Sharing device (Laptop, Inverter, Meter)
Most of the Ethernet extension devices are hard-wired to the router, but may require "Pairing" to initiate data transfer. If you are unsure about the connection, research the make and model of the product and see if there are Pairing directions available on the internet.
Wireless Network - Check WiFi, MiFi, Hotspot Connections
Most of Tigo's Data Loggers have a WiFi connection option (except the MMU). Wireless configuration is a great option for connecting your Data Logger to a network router, without additional wiring, and/or over a large distance. This connection usually requires connection to a network connection point (wireless transceiver), that is connected with a modem.
Here are some examples:
-
Router
-
WiFi Extender
-
Mesh/Relay Network
-
MiFi (mobile network or hotspot)
WiFi products can be a challenge to connect with, as they can be password protected, have bandwidth issues, or they can even be simply out of range (distance from transceiver). It's best to meet with the IT person who controls the network for the system, to get a better idea of possible issues.
IT Administrator - Check Firewall/Port Settings
If you have a Firewall for your network, please be aware of the required Internet Access Range and Port Numbers (below).
IP address | Subnet Mask | Protocol | Port | Service |
64.62.250.0 | '/24', upper bits (255.255.255.0) | TCP | 443 | HTTPS - AWS ECS servers |
64.62.250.0 | 24 | UDP | 123 | Network Time Protocol (NTP) |
34.193.254.249 | 24 | TCP | 443 | HTTPS - Tigo servers |
34.193.254.249 | 24 | UDP | 3256 | Tigo protocol port |
ISP - Check Data Allotment (CCA/Cloud Connect/MMU Data Usage)
The approximate amount of data issued from a Tigo System is 10 MB of data per panel / per month. This means that a 30-panel system generates approximately 300 MB of data per month.
If your service package requires less data activity, or you have limited bandwidth, you may contact our Support Team and request a Data-Reduction Package. Tigo will update the firmware on the CCA, to reduce the cycle of transfers to "one-per-day." For a small systems (less than 30 modules), this can reduce the amount to 1MB or less, per month. Please note that the reduced data option may require that you calculate the monthly usage, mathematically. For example:
How to calculate the reduced data usage required for a 300 module system:
300 modules / 30 ≈ 10 ➜ 10 * 1MB per month = 10 MB per month
For more information about data transfer and storage capabilities, go to:
Network Test:
Tigo's Data-Loggers offer a built-in Network Test, that will help you confirm whether there is a viable network signal or not. For the steps on each device, please click on the image of your Data Logger device (at the top of this page), to visit it's trouble-shooting article.
If all troubleshooting methods fail, please contact Tigo Energy’s Technical Support Team
Comments
1 comment
But what about communication with Mass CEC's PTS?
Please sign in to leave a comment.