Rich Solar LV6548 clone: QPIRI reports correctly, QPGS does not. #372
Replies: 14 comments 5 replies
-
|
So QDI is easy - its the default settings, not the current settings |
Beta Was this translation helpful? Give feedback.
-
|
Yes I have two Rich Solar 6548 inverters working in split phase 180. Still working out mppsolar appropriate use, just started a few days ago, and this is the only solution I thought was best for logging into prometheus out of everything I found. I thought more appropriate to work with your project and make a more formal solution while I develop some Python Foo. 😀 |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
can you try |
Beta Was this translation helpful? Give feedback.
-
|
Currently I only have one serial cable hooked up to the first inverter.
|
Beta Was this translation helpful? Give feedback.
-
|
Can you try with protocol pi30 the qpgs0 and qpgs1 commands to see if they
Gove correct responses
…On Sat, 22 Jul 2023, 6:55 pm Cordel, ***@***.***> wrote:
Currently I only have one serial cable hooked up to the first inverter.
Here is what returns:
`
mpp-solar -P pi30max -c QFLAG Command: QFLAG - Flag Status inquiry
Parameter Value Unit
buzzer enabled
lcd_reset_to_default enabled
over_temperature_restart enabled
primary_source_interrupt_alarm enabled
record_fault_code enabled
overload_bypass disabled
unknown_j disabled
overload_restart disabled
lcd_backlight disabled
`
`# mpp-solar -P pi30max -c QPGS0
Command: QPGS0 - Parallel Information inquiry
Parameter Value Unit
parallel_instance_number valid
serial_number 96342112100901 {'icon': 'mdi:identifier'}
work_mode Line Mode
fault_code No fault
grid_voltage 120.4 V {'icon': 'mdi:power-plug', 'device-class': 'voltage'}
grid_frequency 59.96 Hz {'icon': 'mdi:current-ac', 'device-class':
'frequency'}
ac_output_voltage 120.4 V {'icon': 'mdi:power-plug', 'device-class':
'voltage'}
ac_output_frequency 59.96 Hz {'icon': 'mdi:current-ac', 'device-class':
'frequency'}
ac_output_apparent_power 1095 VA {'icon': 'mdi:power-plug',
'device-class': 'apparent_power'}
ac_output_active_power 1067 W {'icon': 'mdi:power-plug', 'device-class':
'power', 'state_class': 'measurement'}
load_percentage 16 % {'icon': 'mdi:brightness-percent'}
battery_voltage 53.1 V {'icon': 'mdi:battery-outline', 'device-class':
'voltage'}
battery_charging_current 20 A {'icon': 'mdi:current-dc', 'device-class':
'current'}
battery_capacity 69 % {'device-class': 'battery'}
pv1_input_voltage 0.0 V {'icon': 'mdi:solar-power', 'device-class':
'voltage'}
total_charging_current 40 A {'icon': 'mdi:brightness-percent',
'device-class': 'current'}
total_ac_output_apparent_power 1577 VA {'icon': 'mdi:power-plug',
'device-class': 'apparent_power'}
total_output_active_power 1543 W {'icon': 'mdi:power-plug',
'device-class': 'power', 'state_class': 'measurement'}
total_ac_output_percentage 11 % {'icon': 'mdi:brightness-percent'}
is_scc_ok 0 bool
is_ac_charging 1 bool
is_scc_charging 0 bool
is_battery_over_voltage 0 bool
is_battery_under_voltage 0 bool
is_line_lost 0 bool
is_load_on 1 bool
is_configuration_changed 0 bool
output_mode Phase 1 of 2 phase output
charger_source_priority Utility first
max_charger_current 50 A {'device-class': 'current'}
max_charger_range 120 A {'device-class': 'current'}
max_ac_charger_current 20 A {'device-class': 'current'}
pv1_input_current 0 A {'icon': 'mdi:solar-power', 'device-class': 'power'}
battery_discharge_current 0 A {'icon': 'mdi:battery-negative',
'device-class': 'current'}
pv2_input_voltage 0.0 V {'icon': 'mdi:solar-power', 'device-class':
'voltage'}
pv2_input_current 0 A {'icon': 'mdi:solar-power', 'device-class':
'current'}`
`mpp-solar -P pi30max -c QPGS0 -o raw
Command: QPGS0 - Parallel Information inquiry
raw_response '(1 96342112100901 L 00 120.6 59.97 120.6 59.97 1037 1001 015
53.1 020 069 000.0 040 01506 01476 011 01000010 5 0 050 120 020 00 000
000.0 00\x99\xe7\r'`
—
Reply to this email directly, view it on GitHub
<#372 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJVKNX53HJP6NL7KENZ3KDXRN2OTANCNFSM6AAAAAA2QXGNNE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Here is the output pi30:
|
Beta Was this translation helpful? Give feedback.
-
|
So still decoding charger priority wrong
I guess we're adding a different protocol
…On Sat, 22 Jul 2023, 7:06 pm Cordel, ***@***.***> wrote:
Here is the output pi30:
`# mpp-solar -P pi30 -c QPGS0
Command: QPGS0 - Parallel Information inquiry
Parameter Value Unit
parallel_instance_number valid
serial_number 96342112100901
work_mode Line Mode
fault_code No fault
grid_voltage 120.6 V
grid_frequency 59.97 Hz
ac_output_voltage 120.6 V
ac_output_frequency 59.97 Hz
ac_output_apparent_power 1049 VA
ac_output_active_power 991 W
load_percentage 16 %
battery_voltage 53.1 V
battery_charging_current 20 A
battery_capacity 69 %
pv_input_voltage 0.0 V
total_charging_current 40 A
total_ac_output_apparent_power 1508 VA
total_output_active_power 1459 W
total_ac_output_percentage 11 %
is_scc_ok 0 bool
is_ac_charging 1 bool
is_scc_charging 0 bool
is_battery_over_voltage 0 bool
is_battery_under_voltage 0 bool
is_line_lost 0 bool
is_load_on 1 bool
is_configuration_changed 0 bool
output_mode Phase 1 of 2 phase output
charger_source_priority Utility first
max_charger_current 50 A
max_charger_range 120 A
max_ac_charger_current 20 A
pv_input_current 0 A
battery_discharge_current 0 A
unknown_float 0.0
unknown_flags? 00`
`# mpp-solar -P pi30 -c QPGS1
Command: QPGS1 - Parallel Information inquiry
Parameter Value Unit
parallel_instance_number valid
serial_number 96342112100901
work_mode Line Mode
fault_code No fault
grid_voltage 120.7 V
grid_frequency 60.01 Hz
ac_output_voltage 120.7 V
ac_output_frequency 60.01 Hz
ac_output_apparent_power 1025 VA
ac_output_active_power 985 W
load_percentage 15 %
battery_voltage 53.1 V
battery_charging_current 20 A
battery_capacity 69 %
pv_input_voltage 0.0 V
total_charging_current 40 A
total_ac_output_apparent_power 1496 VA
total_output_active_power 1454 W
total_ac_output_percentage 11 %
is_scc_ok 0 bool
is_ac_charging 1 bool
is_scc_charging 0 bool
is_battery_over_voltage 0 bool
is_battery_under_voltage 0 bool
is_line_lost 0 bool
is_load_on 1 bool
is_configuration_changed 0 bool
output_mode Phase 1 of 2 phase output
charger_source_priority Utility first
max_charger_current 50 A
max_charger_range 120 A
max_ac_charger_current 20 A
pv_input_current 0 A
battery_discharge_current 0 A
unknown_float 0.0
unknown_flags? 00`
—
Reply to this email directly, view it on GitHub
<#372 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJVKNTC5RZMCMVYENPUIQ3XRN3YRANCNFSM6AAAAAA2QXGNNE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
John let me know what you need from me to assist.
Mean while, I'll dig through the source and get familiar with it. |
Beta Was this translation helpful? Give feedback.
-
|
I believe there was an error with the requested output we overlooked and I just spotted it today and producing what it suspect was being looked for:
I also now have serial plugged into both units, just in case... ;) |
Beta Was this translation helpful? Give feedback.
-
|
So using QPGS1 & 2 the answers are 'correct'? (but only for the phase 1 inverter for charger source priority?) If not can you highlight which parts are wrong and what they should be |
Beta Was this translation helpful? Give feedback.
-
|
I'm looking into this a bit more. I think and maybe you know there are some more dynamic flags here than whats just in the inverter settings. Now that I have the dashboard though prometheus, I see a dynamic behavior that suggests some of these my play of other settings. For example if you have a minimum battery level set while mains is available. I have mine programed for 50.2v and I see work_mode represent those modes accurately. I'm going to create another dash board of tables to compare what is pulled though mpp_solar and what it sees compared to the values from QPGS. Any suggestions on what command you might like to see in comparison since now this is so simple? |
Beta Was this translation helpful? Give feedback.
-
|
I have gone through Settings on the inverters, Status on the inverter display, and compared output from commands. There are several dynamic type flags that change according to either timer tables ( I am using ), and Low voltage battery/ battery voltage resume using battery voltage settings ( battery_redischarge_voltage, battery_recharge_voltage ). That said, I did how ever find that in the Rich Solar 6548 inverters at least (don't have enough background to speak to the various pi30 supported models), there are only 3 charger_source_priority modes ( Solar First, Solar + Utility, Solar only ) so that with any of the varieties of PI30 protocol, this is off by one for the LV6548 Rich Solar clone as each existing pi30 protocol as coded expects a possibility of 4 starting with [Utility First] ( Utility First, Solar First, Solar + Utility, Solar only ) . To test I created a new class pi30lv with the following changes from pi30max: Everything as far as QPIRI and QPGS now report correctly and the raw value suggests the same though don't line up with the protocal. All other ramblings prior to this post in this thread can be ignored and likely this one as well. I can't find why is is returning that bit as "0" where all else demonstrates it should be returning a 1 as according to the protocol in all instances/variations of pi30. I have cleared all the schedulers, battery is within threshold, etc and I have no wattage being pulled via utility mains, so it is running solar/battery. I'm going to reset the inverters once the others are in bed and make sure there is not some dynamic flag set somewhere and all the schedulers are really clear. |
Beta Was this translation helpful? Give feedback.
-
|
Great - I'll get this added (however I will name it |
Beta Was this translation helpful? Give feedback.
-
|
I dont think adding this to your code is the appropriate approach here,
else I would have submitted a pull request.
I'm still investigating when I have the chance and working condition/state
on the inverter systems permits.
Before we commit, let me exhaust all avenues including engagement with mpp
on this model.
Seems odd the watch power (when it works) seems to negotiate just fine,
there has to be something I haven't considered.
…On Mon, Aug 7, 2023, 16:08 John Blance ***@***.***> wrote:
Great - I'll get this added (however I will name it PI30M045 after the
model number (hoping that model number is more unique....)
—
Reply to this email directly, view it on GitHub
<#372 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABERV53ZCZU677KVXEXKKHLXUFYOJANCNFSM6AAAAAA2QXGNNE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Adding a protocol is low risk, we can always change/improve it later |
Beta Was this translation helpful? Give feedback.
-
|
Okay ill upload what I have if you haven't created it yet.
Corey
…On Mon, Aug 7, 2023, 19:10 John Blance ***@***.***> wrote:
Adding a protocol is low risk, we can always change/improve it later
My approach is to add stuff as long as it doesnt break other stuff and
then improve later - so I say just do a PR and if you have changes
implement them later
—
Reply to this email directly, view it on GitHub
<#372 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABERV5Y5IS6YK32WF7Q4WWTXUGNXRANCNFSM6AAAAAA2QXGNNE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
awesome thanks! |
Beta Was this translation helpful? Give feedback.
-
Am I missing something or is there a bobo in the library file for QPGS and QDI?
I looked into the code (running version: 0.15.62) though I'm not as comfortable in python as I'd like to be (work in progress).
Anything I can do to assist i'm willing.
Rich Solar 6548 aka LV6548 SCC
QPIRI reports 100% spot on:
# mpp-solar -c QPIRI -P pi30maxAs compared to QPGS:
# mpp-solar -c QPGS1 -P pi30maxOr QDI:
# mpp-solar -c QDI -P pi30max# mpp-solar -c QPGS1 -P pi30max -o rawI double checked lcd_backlight, over_temperature_restart, battery_type, output_source_priority, charger_source_priority on the SCC directly and confirmed my active settings:
lcd_backlight - disabled
over_temperature_restart - enabled
battery_type - user
output_source_priority - Solar Battery Utility
charger_source_priority - Solar first
New Protocol type maybe?
Beta Was this translation helpful? Give feedback.
All reactions