Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

suntwins 5000TL #3

Closed
GoogleCodeExporter opened this issue May 3, 2015 · 6 comments
Closed

suntwins 5000TL #3

GoogleCodeExporter opened this issue May 3, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

Using solarmonj with a Suntwins 5000TL unit is giving me incorrect readings.

I've captured data to CSV as follows:

1396162955,35.7,18,25.76,384.7,242.2,0.7,4.78,0.8
1396163135,35.6,18,27.12,389.2,283.4,0.7,4.8,0.8
1396163218,35.5,18,26.77,368.5,288.1,0.6,4.81,0.7

According to main.cpp the column order is:

now  << "," <<   data.temperature << "," << data.energyCurrent << "," << 
data.energyToday << "," << data.energyTotal << "," << data.voltageDc << "," <<  
   data.voltageAc << "," << data.frequency << "," << data.current

The 4th column, 'data.energyToday' went backwards on the last reading (from 
27.12 to 26.77). I would expect that counter to always increase. Am I 
mis-reading this?

The other problem is that the values do not match the readout from the unit's 
LCD display. For example, the LCD says 'ETot 301' whereas the corresponding CSV 
values (data.energyTotal) are all higher than this!

Is anyone else using solarmonj with a Suntwins 5000TL?


Original issue reported on code.google.com by porj...@yahoo.com.au on 30 Mar 2014 at 7:22

@GoogleCodeExporter
Copy link
Author

After some tinkering, I discovered that the values I was getting were correct 
however in the wrong order. I've attached a patch to fix that.

As far as I can tell, my inverter does not provide a reading for the total 
energy generated. It does however provide a reading for 'PAC' (photovoltaic 
AC?). My patch removes field 'energyTotal' and adds field 'pvoltageAc'.

Original comment by porj...@yahoo.com.au on 2 Apr 2014 at 9:25

Attachments:

@GoogleCodeExporter
Copy link
Author

I have the same issue, will try your patch and compare.

Original comment by neal.cos...@gmail.com on 5 May 2014 at 7:34

@GoogleCodeExporter
Copy link
Author

FYI, the 'frequency' value needs to be divided by 100. I've updated the patch.

Original comment by porj...@yahoo.com.au on 5 May 2014 at 9:17

Attachments:

@benleov
Copy link
Contributor

benleov commented May 31, 2015

Hi GoogleCodeExporter,

Hope you don't mind but I have applied your patch to a branch of this repository.

@jcroucher
Copy link
Owner

Hello all.
Sorry I did not get notified as this was an exported project from Google Code.
Thanks benleov for fixing the issue. Are there any other issues here or can this be closed now?

@benleov
Copy link
Contributor

benleov commented Dec 16, 2015

No worries. I didn't fix the issue, just applied the patch that @GoogleCodeExporter created to my own branch then made a small modification to send the data out a socket which I'm reading into Elasticsearch via Logstash. You guys did all the hard work! As far as I know its working fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants