English (US) Deutsch Español (México) עברית Italiano 日本語 简体中文
Call now
Resource Center

Articles in this section

See more

Network 101 - Providing Internet access for data loggers: Cloud Connect Advanced (CCA), Cloud Connect (CC), and Maximizer Management Unit (MMU).

See also these other articles about home networking, and setting Wi-Fi passwords:

  1. "Locating and Identifying Communications Equipment."
  2. "Changed WiFi or need to Reconnect your CCA?"
  3. "Configuring Wi-Fi using Cloud Connect menu buttons"

Identify your Tigo Data Logger

There are three data loggers available from Tigo. The type of data logger in use on your system may determine some troubleshooting steps. For example, the MMU does not have Wi-Fi support, only Ethernet.

Cloud Connect Advanced (CCA)

 Cloud Connect

Management Unit (MMU)

Legacy Product
Tigo_12-15_202W-revised.jpg

 

Procedure:

Step 1: Identify Type of Network Equipment in Use

Before proceeding further, it is necessary to identify the hardware components of the Tigo Cloud Connect Advanced (CCA), Cloud Connect or Management Unit’s (MMU) network connection.

The wired network configuration involves a direct, hard-wired Ethernet cable to router connection:

  1. Network router
  2. Ethernet cable connected from router to CCA/Cloud Connect/MMU
  3. CCA/Cloud Connect/MMU

Non-standard network setups will sometimes include a third-party device known generically as a Wi-Fi Extender which is used to relay a Wi-Fi signal that is from a Wi-Fi Access Point/Router to a CCA.

Some networks may use a Power Line Communication Adapter in place of a home-run of Ethernet cable:

  1. Wi-Fi router
  2. Wireless Adapter (e.g. Netgear or Linksys)
  3. Ethernet cable connected from Adapter to CCA/Cloud Connect/MMU
  4. CCA/Cloud Connect/MMU

Step 2: Verify/Test Internet connectivity by running a Network Test:

For a CCA:

  1.  Install Tigo Smart App 3.1
  2. Look in Create and Edit System (Configure Communication)   to learn how how to connect to the CCA from your mobile device, to configure the CCA to use the network  and then run a Network Test.

For a Cloud Connect or Maximizer Management Unit:

  1. Press MENU, then ENTER
  2. Use arrow keys to go to menu number 3. NETWORK; then press ENTER.
  3. Use arrow keys again to go to 3.2. TEST;  then press ENTER to start the test.

This table explains any messages shown:

Message

Description

Corrective Action

"Connecting..."

Trying to access Tigo Energy's server.

N/A

"Success"

Cloud Connect/MMU has successfully accessed the server.

N/A

"Error: Checking"

Cloud Connect/MMU could not connect to the server, and is diagnosing cause of problem.

N/A

"Cable unplugged"

No physical cable detected.

Check cable connection and re-initiate network test

"No IP address"

Cloud Connect/MMU is not receiving an IP address from the router.

Check cable connection and verify that the Ethernet cable is plugged into the router. If there are power line adapters, make sure they have a connection with its sibling unit.

Restart the management unit's network by either 2.4 "Restart" (full restart that takes a few minutes) or 3.5 "Renew" (management unit looks for new IP address)

"No association with AP"

Cloud Connect/MMU sees the network but cannot gain access to it.

Check to make sure password is correct or if network security settings allow extra devices.

"Check proxy svr"

Cloud Connect/MMU is configured to access the web via HTTPS proxy server, and it is either inaccessible or the site does not have a proxy server.

Verify proxy settings on Cloud Connect/MMU. If site does have proxy, verify it allows access to *.tigoenergy.com. Re-initiate network test. If site has no proxy (default is off for Cloud Connect/MMU and for most networks), turn proxy off by going to: 3.4 "Set Proxy" on Cloud Connect/MMU menu > "Are you sure?" press ENTER for Yes > "Proxy Server?" press MENU for no.

"No Default GW"

Missing default gateway. Either DHCP server is not replying (i.e. the router), or static IP configuration entry is not present (only applies to networks requiring static IP setup)

Verify physical connection of cabling at router. Verify configuration of router allows Cloud Connect/MMU to access network. Re-initiate network test.

“Cannot ping GW”

Default gateway did not respond to ping. May not be a problem depending on router configuration.

Verify physical connection of cabling at router. Re-initiate network test.

“Cannot ping DNS”

Global public DNS server (8.8.8.8) is not responding. Indicates possible inability to connect to internet. May not be a problem depending on router configuration.

Verify physical connection of cabling from router to modem. If other devices in house are not connected to internet, call your service provider for assistance. May be a problem with modem or router.

“Cannot ping Tigo”

Cannot exchange ICMP packets with Tigo Data Center. May not be a problem depending on router configuration.

Contact Tigo Energy’s Technical Support team by phone at +1.844.805.8550, or by email at support@tigoenergy.com.

Step 3: Troubleshooting Cloud Connect/MMU

If your Cloud Connect/MMU only shows you the message “Error” or you are not sure how to perform some of the fixes described above, try the following steps to reconnect the Cloud Connect/MMU to the Internet:

  1. Verify that the Ethernet cable is good by unplugging the end that is in the Cloud Connect/MMU, and plug it into a laptop or desktop computer. Make sure that the wireless Internet receiver is turned OFF on the computer to ensure that you are only connecting to the network via the cable. Try browsing a website that you do not frequent often (e.g. news.google.com). If you are able to browse new websites, then this confirms that the Ethernet cable is viable.
  2. Unplug the Ethernet cable from the Cloud Connect/MMU and wait 10 seconds before plugging it back in. Renew the IP address on the Cloud Connect/MMU by following these steps:
    1. Press MENU, then ENTER
    2. Use arrow keys to find 3. NETWORK, press ENTER
    3. Use arrow keys to find 3.5. RENEW, press ENTER
    4. A new IP address should display if the request was successful.
    5. Perform network test again, and see if you get SUCCESS as the result. If not, then proceed to the next step.
  3. Unplug power supply of the Cloud Connect/MMU, wait 10 seconds, then plug back in. This will reboot the unit completely. Perform network test again. If you get ERROR, then proceed to next step.

Step 4: Rebooting All Network equipment

In some cases, a full reboot of all devices inside of the CCA/Cloud Connect/MMU’s network needs to be done. This is accomplished by the following steps:

  1. Reboot the router by unplugging its power supply, waiting 10 seconds, then plug it back in. Wait for the lights on the unit to stabilize before proceeding to the next step.
  2. If you have a third party device (e.g. wireless network bridge, or wireless adapter) that is allowing Internet to pass to the Cloud Connect Advanced/Cloud Connect/MMU, please reboot this unit next after the router lights stabilize. If you do not have one of these devices, proceed to the next step.
  3. Reboot the Cloud Connect/MMU (i.e. unplug, wait a few seconds, then plug back in) and wait for text to appear on the display. Try doing a network test again and record the messages that you see. If it goes immediately to "Success", this indicates that your Cloud Connect Advanced/Cloud Connect/MMU is reconnected to the Internet.

If all troubleshooting methods fail, please contact Tigo Energy’s Technical Support team by email with system ID and street address: support@tigoenergy.com.

Firewall Settings:

Required server and TCP port access:

When the network providing Internet service is using a Firewall to block incoming server connections, it must be allow the Tigo data logger to access the following servers and ports.
  • 64.62.250.0/24 on TCP 443.  HTTPS - to AWS ECS server.
  • 64.62.250.0/24 on UDP 123.  123 is Network Time Protocol (NTP), used for time synchronization.

  • 34.193.254.249 on TCP 443.  HTTPS to Tigo server.
  • 34.193.254.249 on UDP 3256.  3256 is Tigo protocol port.
CCA/Cloud Connect/MMU Data Usage
As of February 2015 the amount of data sent over the Internet is approximately 10 MB of data per panel per month. So a 30 panel system transfers approximately 300 MB per month. More information about data transfer and storage capabilities is available here.See also: MMU Internet Connection

Related articles

Comments

0 comments

Please sign in to leave a comment.