TAP communication protocol
looking for a documentation of the TAP communication protocol used over modbus. Is there anything, is TIGO TAP following Sunspec as others do?
My goal is to create a Software that does not require to have cloud connection over CCA, but instead does this locally not requiring CCA.
Thank you for your interesting question.
Unfortunately, Tigo does not offer any modbus/communication information for the TAPs at this time. The only way to pull data would be to set up an API connection through your account. If you'd like to do this, the information can be found in our article:
In the meantime, I will forward your request to our engineers for consideration on new Tigo product (in the future). Thanks for your interest!-1
I was thinking of something on similar lines myself. I have yet to have my system installed, it is part of a group purchase scheme, but is spec'd with panels and Tigo Optimizers, but the suppliers are yet to confirm if it will include a TAP, a CCA and the monitoring.
I have tried to find out how to keep the monitoring local and perhaps eventually incorporate it into an Emon Pi setup, but there doesn't appear to be any solid information available on any forums. My only thinking now seems to be first, confirm if the coms coming out of the TAP is indeed Modbus. If so, you could connect the TAP to a serial port on a PC (or serial to USB converter) and use something like the freeware CAS Modbus Scanner software to see if you can extract the panel data which is sitting in Modbus registers in the TAP. Then some code needs to be written to convert this data into feeds/inputs for a Emon Hub running on an Emon Pi.
Sounds like a lot of work which probably explains why nobody has bothered!
Does any of this make any sense to you as I am not too sure I understand it myself!
Thank you for participating in Tigo Community!
I do not know if what you are describing is possible, but it's worth going through the pros and cons:
- Data coming from the TAPs may not be in a modbus-friendly format
- Disconnecting TAP from CCA would cease the multi-level data interpretation that Tigo provides online
- Disconnecting TAP from CCA would cease any Rapid Shut Down (RSD) response (important for NEC regulations (U.S.A))
- Disconnecting a System from the cloud/network will affect Tigo's ability to properly diagnose system performance issues
- Blind Deployment may disqualify the system from Warranty Coverage
I have created a ticket for your question, and our Sales/Training engineers will reply more information regarding this unique question. In the meantime, we thank you for your patience.0
Hi Juergen and Alan. The communication protocol between the TAP and CCA is proprietary. The first response from Curtis says it all.
Gary Hethcoat, Sales Engineer, Tigo Energy0
Do you have the communication protocol already? I am interested as well.
Nope, the previous comments confirm the protocol is proprietary. I wasn't considering disconnecting TAP from CCA anyway, which would be considered ill-advised, but would try to run in parallel with the working setup. This would probably require a lot of time and knowledge, of which, I have not a great deal of either!
Have had the panels installed with optimisers and the TAP and CCA are up and running and performing well.
I have been overtaken by other projects so have not had the time to progress with enhancing panel monitoring.
Hello yongjiet & @Alan Harlow,
Thank you for your contributions to the Tigo Community.
Alan Harlow is correct, in saying that the data is both proprietary, and the TAP data cannot be read (or disconnected from the CCA). Disconnection of the TAP would cause the RSD (rapid shutdown) function to enact, and the MLPEs would no longer produce.
However, we appreciate the enthusiasm for the Tigo product and encourage you to contact our Sales Engineering team, if you have any additional questions about building and designing a Tigo System.0
I am also interested in being able to pull monitoring data locally. Some observations:
- the CCA responds to port 80, is there a way to retrieve data from the CCA?
- since the CCA pulls all the interesting data, it would be possible to attach a read-only device that simply monitors the modbus data returned by the TAP to the CCA in order to gather the data
- I find it disgusting that one has to pay to access one's own data via the Tigo Energy API when Tigo does not provide any alternative; I can rationalize opaying for additional services, but not for basic access to data that I am forced to send and cannot access in any other way
- the limited warranty still applies for 5 years in disconnected use, one 'only' looses the up-to-20-year warranty on the TS-4's as far as I can tell; there is also nothing that precludes manually reconnecting the TAP to the CCA when remote troubleshooting is desired
Tigo does not provide an option to collect the data locally, and as such, it must be derived from our secure data centers in the cloud. This data is not personal in nature and limited to solar system performance data only. We do not share or sell the data we collect to third parties. The data is used by Tigo only to make a better and more usable system for our customers.
Tigo values its customers deeply and protects all collected data utilizing robust security measures.0