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.

Sign up for GitHub

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

Jump to bottom

We've solved a few problems #4

Open
jaaphoenderdos opened this issue May 29, 2020 · 2 comments
Open

We've solved a few problems #4

jaaphoenderdos opened this issue May 29, 2020 · 2 comments

Comments

@jaaphoenderdos
Copy link

Hi,
With the help of Robmit68 we've solved two problems:

Unhandled Exception: int too large to convert to float
This is in solaredge models that uses the sunspec modbus. There is a difference in the modbus lines.

A splitfase setup. The current readings are across fase A and B. This is a different line in the modbus.

We've created two new files:
solaredge.py.txt
solaredge-splitfase.py (1).txt
@33Fraise33
Copy link

This introduces a new issue for me:

Starting up solaredge monitoring
Connecting to Solaredge inverter 172.16.33.100 on port 1502 using unitid 1
Writing data to influxDb 10.33.0.19 on port 8086 every     5 seconds
DEBUG:solaredge:Running eventloop
DEBUG:aioinflux:200: CREATE DATABASE "solaredge"
INFO:solaredge:Database opened and initialized
[101, 50, 1084, 1084, 65535, 65535, 65534, 2421, 65535, 65535, 65535, 65535, 65535, 65535, 26207, 65535, 49992, 65533, 26246, 65535, 14375, 65534, 9984, 65534, 52, 17229, 0, 6908, 65533, 3851, 65535, 26606, 65535, 32768, 4547, 32768, 32768, 65534]
ERROR:solaredge:Unhandled exception: unpack requires a buffer of 2 bytes

@jaaphoenderdos
Copy link
Author

I don't know this issue. You could better start a new issue

peplin added a commit to peplin/Solaredge-influxdb that referenced this issue Feb 21, 2022
@peplin
Fix register parsing for latest SolarEdge SunSpec ModBus implementation
c9b341a 
On a new SE5000H, I encountered issue salberin#4. I found that the register
parsing implementation doesn't match what's listed in the [SolarEdge
technical
spec](https://www.solaredge.com/sites/default/files/sunspec-implementation-technical-note.pdf)
for their SunSpec ModBus implementation.

The code was seeking too far forward, and from that point on it was
reading a mix of 2 registers and trying to interpret as scaling factors
or measurements. This caused seemingly random, extremely large values
that triggered the "int too large to convert to float". The issue, at
least for my unit, was not with the field that could not be parsed.

With these new values, all measurements supported by my unit are
reporting values that match the SolarEdge monitoring website.

I'm not positive if this is specific to only some units, but the
technical note does not indicate they use different registers for
different inverter models.
@peplin peplin mentioned this issue Feb 21, 2022
Merged
peplin added a commit that referenced this issue Jan 12, 2024
@peplin
Fix register parsing for latest SolarEdge SunSpec ModBus implementation
c55e27d 
On a new SE5000H, I encountered issue #4. I found that the register
parsing implementation doesn't match what's listed in the [SolarEdge
technical
spec](https://www.solaredge.com/sites/default/files/sunspec-implementation-technical-note.pdf)
for their SunSpec ModBus implementation.

The code was seeking too far forward, and from that point on it was
reading a mix of 2 registers and trying to interpret as scaling factors
or measurements. This caused seemingly random, extremely large values
that triggered the "int too large to convert to float". The issue, at
least for my unit, was not with the field that could not be parsed.

With these new values, all measurements supported by my unit are
reporting values that match the SolarEdge monitoring website.

I'm not positive if this is specific to only some units, but the
technical note does not indicate they use different registers for
different inverter models.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@33Fraise33 @jaaphoenderdos