Skip to content
View in the app

A better way to browse. Learn more.

Power Forum - Renewable Energy Discussion

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

robert1968

Members
  • Joined

  • Last visited

Everything posted by robert1968

  1. Thanks Kuba.cz Just a quick feedback: my inverter still works perfectly with the removed derate firmware. :) For just analysis purpose today i made 3 get status within 10 minutes in the mid of the day when PVs provides almost maximum (113A). 1st status is with Battery charge current was limited to 10A. 2nd Battery charge current was limited to 100A. 3rd when Battery charge current was limited to 150A. 10A mppsolar --getstatus -P pi30max Command: QPIGS2 - General Status Parameters inquiry 2 -------------------------------------------------------------------------------- Parameter Value Unit ac_input_voltage 235.5 V {'icon': 'mdi:transmission-tower-export', 'device-class': 'voltage'} ac_input_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'} ac_output_voltage 228.6 V {'icon': 'mdi:power-plug', 'device-class': 'voltage'} ac_output_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'} ac_output_apparent_power 645 VA {'icon': 'mdi:power-plug', 'device-class': 'apparent_power'} ac_output_active_power 525 W {'icon': 'mdi:power-plug', 'device-class': 'power', 'state_class': 'measurement'} ac_output_load 6 % {'icon': 'mdi:brightness-percent'} bus_voltage 465 V {'icon': 'mdi:details', 'device-class': 'voltage'} battery_voltage 52.8 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'} battery_charging_current 10 A {'icon': 'mdi:current-dc', 'device-class': 'current'} battery_capacity 56 % {'device-class': 'battery'} inverter_heat_sink_temperature 44 °C {'icon': 'mdi:details', 'device-class': 'temperature'} pv1_input_current 0.8 A {'icon': 'mdi:solar-power', 'device-class': 'current'} pv1_input_voltage 358.9 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'} battery_voltage_from_scc 0.0 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'} battery_discharge_current 0 A {'icon': 'mdi:battery-negative', 'device-class': 'current'} is_sbu_priority_version_added 0 bool is_configuration_changed 0 bool is_scc_firmware_updated 0 bool is_load_on 1 bool is_battery_voltage_to_steady_while_charging 0 bool is_charging_on 1 bool is_scc_charging_on 1 bool is_ac_charging_on 0 bool battery_voltage_offset_for_fans_on 0 10mV eeprom_version 0 pv1_charging_power 306 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'} is_charging_to_float 0 bool is_switched_on 1 bool is_dustproof_installed 0 bool solar_feed_to_grid Disabled country Invalid key: 3030 solar_feed_to_grid_power 0 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'} pv2_input_current 2.1 A {'icon': 'mdi:solar-power', 'device-class': 'current'} pv2_input_voltage 434.8 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'} pv2_charging_power 935 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'} -------------------------------------------------------------------------------- 100A mppsolar --getstatus -P pi30max Command: QPIGS2 - General Status Parameters inquiry 2 -------------------------------------------------------------------------------- Parameter Value Unit ac_input_voltage 236.9 V {'icon': 'mdi:transmission-tower-export', 'device-class': 'voltage'} ac_input_frequency 49.9 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'} ac_output_voltage 229.9 V {'icon': 'mdi:power-plug', 'device-class': 'voltage'} ac_output_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'} ac_output_apparent_power 666 VA {'icon': 'mdi:power-plug', 'device-class': 'apparent_power'} ac_output_active_power 523 W {'icon': 'mdi:power-plug', 'device-class': 'power', 'state_class': 'measurement'} ac_output_load 6 % {'icon': 'mdi:brightness-percent'} bus_voltage 442 V {'icon': 'mdi:details', 'device-class': 'voltage'} battery_voltage 53.6 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'} battery_charging_current 100 A {'icon': 'mdi:current-dc', 'device-class': 'current'} battery_capacity 64 % {'device-class': 'battery'} inverter_heat_sink_temperature 57 °C {'icon': 'mdi:details', 'device-class': 'temperature'} pv1_input_current 8.1 A {'icon': 'mdi:solar-power', 'device-class': 'current'} pv1_input_voltage 323.9 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'} battery_voltage_from_scc 0.0 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'} battery_discharge_current 0 A {'icon': 'mdi:battery-negative', 'device-class': 'current'} is_sbu_priority_version_added 0 bool is_configuration_changed 0 bool is_scc_firmware_updated 0 bool is_load_on 1 bool is_battery_voltage_to_steady_while_charging 0 bool is_charging_on 1 bool is_scc_charging_on 1 bool is_ac_charging_on 0 bool battery_voltage_offset_for_fans_on 0 10mV eeprom_version 0 pv1_charging_power 2648 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'} is_charging_to_float 0 bool is_switched_on 1 bool is_dustproof_installed 0 bool solar_feed_to_grid Disabled country Invalid key: 3030 solar_feed_to_grid_power 0 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'} pv2_input_current 8.2 A {'icon': 'mdi:solar-power', 'device-class': 'current'} pv2_input_voltage 393.5 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'} pv2_charging_power 3255 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'} -------------------------------------------------------------------------------- 150A mppsolar --getstatus -P pi30max Command: QPIGS2 - General Status Parameters inquiry 2 -------------------------------------------------------------------------------- Parameter Value Unit ac_input_voltage 235.8 V {'icon': 'mdi:transmission-tower-export', 'device-class': 'voltage'} ac_input_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'} ac_output_voltage 229.6 V {'icon': 'mdi:power-plug', 'device-class': 'voltage'} ac_output_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'} ac_output_apparent_power 574 VA {'icon': 'mdi:power-plug', 'device-class': 'apparent_power'} ac_output_active_power 266 W {'icon': 'mdi:power-plug', 'device-class': 'power', 'state_class': 'measurement'} ac_output_load 5 % {'icon': 'mdi:brightness-percent'} bus_voltage 422 V {'icon': 'mdi:details', 'device-class': 'voltage'} battery_voltage 53.8 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'} battery_charging_current 113 A {'icon': 'mdi:current-dc', 'device-class': 'current'} battery_capacity 66 % {'device-class': 'battery'} inverter_heat_sink_temperature 70 °C {'icon': 'mdi:details', 'device-class': 'temperature'} pv1_input_current 9.2 A {'icon': 'mdi:solar-power', 'device-class': 'current'} pv1_input_voltage 304.4 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'} battery_voltage_from_scc 0.0 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'} battery_discharge_current 0 A {'icon': 'mdi:battery-negative', 'device-class': 'current'} is_sbu_priority_version_added 0 bool is_configuration_changed 0 bool is_scc_firmware_updated 0 bool is_load_on 1 bool is_battery_voltage_to_steady_while_charging 0 bool is_charging_on 1 bool is_scc_charging_on 1 bool is_ac_charging_on 0 bool battery_voltage_offset_for_fans_on 0 10mV eeprom_version 0 pv1_charging_power 2814 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'} is_charging_to_float 0 bool is_switched_on 1 bool is_dustproof_installed 0 bool solar_feed_to_grid Disabled country Invalid key: 3030 solar_feed_to_grid_power 0 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'} pv2_input_current 9.4 A {'icon': 'mdi:solar-power', 'device-class': 'current'} pv2_input_voltage 370.4 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'} pv2_charging_power 3514 W {'icon': 'mdi:solar-power', 'device-class': 'power', 'state_class': 'measurement'} -------------------------------------------------------------------------------- The bus voltage is highest in the lowest load of course.
  2. Yes. See longterm. But seems very promising, it went ~4 hours when battery full charged. So the first test is proved the concept. Many thanks again for modifying fw ! :) I'm curious which of the many temperature sensors has related to 100A derate. Because I saw few temperature sensors are listed in serial queries. I will very wary for the next days.
  3. Upgrade went smooth. Seconds later I'm recoverd from heart attack:) Now we are stable above 100A!!! 118A ! You did it Kuba.cz ! You are my genius 😍 Many many thanks 🙏! Since here we should wait for see is this change is a success or failure - how the inverter tolerates the uprised load! Fingers 🤞 crossing :)
  4. Seems solved. Find another USB UART dongle (cp2102) and this seems working. Upgrade running still.. :)
  5. Hi Thanks for responding. Unfortunately windows firmware update failed and inverter shows blinking 32 on the screen... Inverter was powered off and on, but still blinking 32 on the screen. Pls help 🥺
  6. Is there a way to ensure which DSP i have? Is there a linux based serial firmware update ? I try ArenaINVReflashTool.exe tomorrow....
  7. Hi, Kuba.cz Thanks for the support. :) You assumed upgrade was not successful and you are probably right. Can you please confirm based on screenshots, and U03 - this means upgrade error ? So this is the screenshots from upgrade video. Step 1: Upgrade approved: timestamp 0:15 Step 2 - timestamp 0:15 - 0:48 - button1 green led blinking (1 sec on 1 sec off.) Step 3 - timestamp 0:48 - (Error??) message: U3 >But, looking at the inverter status, your PV voltage is below 350V which means that the derating condition That strange why it says pv_input_voltage 328.6 V because PV2 is about 420V-440V. All the Deshmonitor and WatchPower application report only one PV but MAX TWIN - his has TWO strings! Probably this query shows only PV1 voltage which is usually under 350V. FYI. - See the settings query: root@beelink1:~# mppsolar --getsettings Command: QFLAG - Flag Status inquiry -------------------------------------------------------------------------------- Parameter Value Unit ac_input_voltage 230.0 V ac_input_current 47.8 A ac_output_voltage 230.0 V ac_output_frequency 50.0 Hz ac_output_current 47.8 A ac_output_apparent_power 11000 VA ac_output_active_power 11000 W battery_voltage 48.0 V battery_recharge_voltage 48.0 V battery_under_voltage 47.0 V battery_bulk_charge_voltage 55.3 V battery_float_charge_voltage 54.0 V battery_type User max_ac_charging_current 10 A max_charging_current 150 A input_voltage_range Appliance output_source_priority SBU first charger_source_priority Only solar charging permitted max_parallel_units 6 units machine_type Off Grid topology transformerless output_mode single machine output battery_redischarge_voltage 54.0 V pv_ok_condition As long as one unit of inverters has connect PV, parallel system will consider PV OK pv_power_balance PV input max power will be the sum of the max charged power and loads power max_charging_time_for_cv_stage 480 min operation_logic Automatic mode unknown_value_in_response_27 b'000' overload_bypass enabled overload_restart enabled lcd_backlight enabled primary_source_interrupt_alarm enabled record_fault_code enabled buzzer disabled unknown_d disabled power_saving disabled lcd_reset_to_default disabled unknown_l disabled unknown_n disabled over_temperature_restart disabled -------------------------------------------------------------------------------- So i'll read the second and 3rd Upgrade option - unfortunately i have difficulties with windows. Best Regards, Robert
  8. Hi, i started Upgrade in the morning. i confirmed the question with yes. Then screen put a kind of progress bar but after a few seconds it went back to default screen. Seemed nothing happened. no restart no disconnect or interrupt of battery charge. I expected 10 minutes upgrade as Coulomb wrote but it takes a few seconds.... So i assume maybe it does not run upgrade?? Max battery_charging_current is still 100A I restarted the inverter but still 100A is the max. See the inverter status: root@beelink1:~# mppsolar --getstatus Command: Q1 - Q1 query -------------------------------------------------------------------------------- Parameter Value Unit ac_input_voltage 235.2 V {'icon': 'mdi:lightning'} ac_input_frequency 50.0 Hz ac_output_voltage 230.3 V ac_output_frequency 50.0 Hz ac_output_apparent_power 529 VA ac_output_active_power 396 W ac_output_load 4 % bus_voltage 445 V battery_voltage 53.6 V battery_charging_current 100 A battery_capacity 64 % inverter_heat_sink_temperature 59 °C pv_input_current_for_battery 9.8 A pv_input_voltage 328.6 V battery_voltage_from_scc 0.0 V battery_discharge_current 0 A is_sbu_priority_version_added 0 bool is_configuration_changed 0 bool is_scc_firmware_updated 0 bool is_load_on 1 bool is_battery_voltage_to_steady_while_charging 0 bool is_charging_on 1 bool is_scc_charging_on 1 bool is_ac_charging_on 0 bool rsv1 0 A rsv2 0 A pv_input_power 3226 W is_charging_to_float 0 bool is_switched_on 1 bool is_reserved 0 bool unknown_value_in_response_22 b'030' unknown_value_in_response_23 b'58.40' unknown_value_in_response_24 b'000' time_until_the_end_of_absorb_charging 1 sec time_until_the_end_of_float_charging 0 sec scc_flag SCC not communicating? allowscconflag 00 chargeaveragecurrent 00 scc_pwm_temperature 59 °C {'device-class': 'temperature'} inverter_temperature 33 °C {'device-class': 'temperature'} battery_temperature 36 °C {'device-class': 'temperature'} transformer_temperature 36 °C {'device-class': 'temperature'} gpio13 2 fan_lock_status Not locked not_used 000 fan_pwm_speed 100 % scc_charge_power 3231 W {'icon': 'mdi:solar-power', 'device-class': 'power'} parallel_warning 0000 sync_frequency 0.0 inverter_charge_status bulk stage {'icon': 'mdi:book-open'} unknown_value_in_response_18 b'0' unknown_value_in_response_19 b'060' unknown_value_in_response_20 b'030' unknown_value_in_response_21 b'150' unknown_value_in_response_25 b'120' unknown_value_in_response_26 b'0' unknown_value_in_response_27 b'0000' -------------------------------------------------------------------------------- Should i record the a video from upgrade ? maybe you see is it passed or not.
  9. Hi Kuba.cz I found how to run firmware upgrade here: https://forums.aeva.asn.au/viewtopic.php?p=87767#p87767 There are 3 way to do. I choose option one. i have USB OTG (i hope mine is also OTG, because looks exactly same as it is in the instruction page picture) Formatted a PEN drive with Fat32 then extracted MAXE11K_TWIN_7808_derate450V.inv file and renamed to mks2.hex then copied to the pen drive root folder. No other file copied - Is this right? Now i should go to the inverter put the pen with USB OTG to the Inverter USB and initiate upgrade Access the USB transfer menu by holding down the display's top left button for 3 seconds. Select Upgrade Firmware by pressing the button next to UPG; confirm by pressing the button next to "YES". The reflash process takes about 10 minutes. Can you pls confirm this is OK ? Update: I followed the step until Confirm upgrade - to check there is no error with steps until this. Now i postponed the upgrade till morning. (i choose 'No') I don't take any risk in night...
  10. Many Many thanks to you Kuba.cz making the firmware so fast! I'm really appreciated. And thanks Coulomb for the very interesting background information. :) I start to read the firmware update topic. I'm afraid I should buy some interface if I don't have on the shelf.
  11. I'm really sorry I said something without checking it. I assumed this the only option. Apologies. How can I check I have F28066 DSP?
  12. Many thanks to be open for patching. Can export Easun firmware somehow? Or only manufacturers can provide? I contacted them with questions, but no response since two weeks. So I ve doubt they will help. If we have Easun firmware then can you compare to Axpert one? I would prefer to take only one risk at once. (Change PV 350V limit to let's say 450V) Best regards Robert
  13. Hmm. All your words are true. Thanks. I'm always meets with 100A limit (never see 90A) so this is because of 420V pv2 voltage and not because of the high internal temperature. Basefd on what Coulomb said: > "if PV voltage is over 360V, the charge current would be derated to a maximum of 90A." If we leave the temp protection then risk is maybe less. I'm still thinking to take the risk, and try it... At least to see it's works -as Proof of concept. Can you please make only this modification on my current software version? (CPU: 78.08 Secondary CPU: 38.17 )
  14. Hi Coulomb and Kuba.cz Many thanks for taking time and investigating the issue! I'm very happy to hear you found this strange settings in code. I'm amazed by the magic you have. :) Anyway thank you! Especially thanks for the solution proposal. However I don't really like it, because I didn't plan to have another inverter and add rearrange cables on roof. Is it an option to modify the software with disable the voltage limit? Or just simple overwrite it to 500 V? Is it ethical from a company not even mentioning this conditions and advertising 150A charge current??? I'm very upset about this sales behaviour! I feel that is not correct. Anyway many thanks again for you 😀 Best regards Robert
  15. Many thanks Coulomb for all your efforts! I found this issue were already raised in this forum: Here (But no solution yet.)
  16. Hi Same issue with Easun - ISolar SMW 11Kw TWIN CPU: 78.08 Secondary CPU: 38.17 Do you have connected inverter -BMS communication? ( I saw LiFePOWER use Solar Assistant for the BMS communication. ) My JK BMS communication doesn't work. And maybe this is the key?, if BMS communication works then inverter can reach 150A limit? I just thinking... Did you find solution? Coulomb started to see the issue but not found any obvious reason. Best regards Robert
  17. Hi Stakoz, Sorry to say it, but I'm happy to see I'm not alone with this issue, :) because I find only one similar reports on one forum, but there was no solution for it. Maybe I should open a new topic for it? BTW, when I switched from OSO (charge from Solar only) to SOlar and Utility together charge, then the charge current went to ~130A for a few seconds but then went back to 100A within 10 seconds. Thanks Robert
  18. Hi, I have Easun - ISolar SMW 11Kw TWIN. which i identified same as Axpert Max E 11 kW '28066 Twin (with removeable display). I faced "stacked at 90V" issue once but restart helped. Since then it not came again. But i have a different problem which is not solved with restarting the inverter. My problem The maximum charging current is limited to 100A. It should be 150A by specification but I have a problem with maximum battery charging current not goes above 100A (~ around 5400W) in spite of solar panels are provides ~7KWh power. Settings 02 (maximum charging current) is set to 150A and charging current is increasing only to 100A, and then stay at there. PV1- has 10 x 430W panel. PV2- has 12 x 430W panel. Relevant settings: 01- SBU. 02- 150A 11- Uti - 50A - but this not relevant 16- OSO Software version: CPU: 78.08 Secondary CPU: 38.17 Pls help. Best Regards, Robert

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.