Vitaliy

Hmm. After I revisited configuration documentation and looked precisely ti screenshots I found that probably it possible to draw generator as an aux.
The problem only that probably only sunsilk/deye users familiar with AUX word. Users of other inverters just may not recognize this ability. And showing generator is not explicitly explained in documentation as a use case.

[ Edit: See also Axpert King 1 main firmware version 72.05. ]
I  recently came across main (DSP, U1) firmware for the Axpert King 1 (5 kVA, 145 V max PV voltage), version 72.04. The differences I have noticed compared to firmware version 72.00:
* When a main firmware reflash is started, it shuts down more completely
* Solar charger output current in QPIGS is reported differently, using PV power / PV voltage and PV voltage, and the factor 100/90. Similarly, PV power uses the 100/90 factor. The PV power is measured by the Solar Charge Controller firmware, so it's possible that this firmware should be matched with a different SCC firmware, though that seems unlikely.
* There is different logic in the code that compares the transformed battery voltage (voltage at the high voltage end of the DC-DC converter) with the bus voltage.
*  There is new code in the task that protects the battery and DC bus, where the solar charger output current is compared with 1.7 A. If more than this, there is a factor of 1/0.93 used.
* Immediately after the above change, there is another change that adds the PFC current to the solar charger current.
* Does not support the QDOP command, and so cannot support SoC% for settings 12, 13, and 29.
So most of the changes seem to be to  do with solar charger current, and indeed I and others have noted weird, inconsistent behaviour with respect to solar charge current. Hopefully, these changes go a long way to fixing those issues.
The premature float bug is alive and well in 72.04, as it has been in every Voltronic main firmware I've looked at.
The dsp.hex file is dated 09/Jan/2024.
It will be some time before I can produce a 72.04 version of the fully patched  firmware, if I get around to it at all (I do hope to).
Do not use this firmware update file with any other model, and use at your own risk.
[ Edit April 2024: Do not confuse with the Axpert Max 8 kW firmware with the same version number. ]
Firmware upload instructions
The .rar file's password is 111:
AxpertKING_5KW_STANDARD_72.04 pw 111.rar
 
 
 
 

All Axperts have these three relays:
* AC-in "safety" relays (switches AC-in Line and Neutral) to load and possibly DC-AC converter
* Load relay (disconnects AC-out from everything else)
* Older models had a fourth relay, at the output of the DC-AC converter. Later models don't bother the the DC-AC converter live connects to the junction of the other two live relays.
* It's possible that the Kings have a fourth relay associated with the PFC stage (the AC-DC converter/rectifier). [ Edit: This is confirmed by the block diagram in the King service manual; see a few posts down. ] It's also possible that the King's service manual is inaccurate or out of date.
There is also a relay at the output of the solar charger (MPPT) in 145 V max PV models, including the King 1 but not the King II. This is actually two relays in parallel to make the current rating. To me, these relays make more of a long"tiiiing" sound than a click, but it possibly depends on what particular brand of relay is used.
My wild guess is that it's the MPPT relay that is making the sound, and that you have older firmware. Anything older than 72.00 (71.xx) had issues with solar charging, and 72.00 still has a few. I have no experience personally using firmware version 72.04.

What is your main (U1) firmware version? If earlier than 71.94 or so, there were strange PV problems, including "dips" and "freezes". 72.00 is available in the files section of this forum.
Otherwise, like you say, it's really weird, and I have no idea what's going on. My suspicion would be something to do with water (melted snow) and panels or their wiring; maybe there is a leakage somewhere, but that should hardly stop a 5P setup. Unless perhaps the water gets into connectors after the panels are paralleled. The long time constant (hours) suggests either temperature or something getting wet and drying out over time. Or of course simply intermittent.
 

Hi guys,
I noticed a number of questions on the forum recently, on the topic of how to include Pylontech batteries in your homebrew monitoring and automation solutions. So, here's the summary to help you with the start. Also, it contains links to protocol descriptions, examples and downloadable source code archives. Just for the case that these files would be deleted from their original locations.
Technically, there are 3 interfaces available on the Pylontech master battery:
RJ-11 Serial Console RJ-45 CAN bus RJ-45 RS485 The actual pinout of the each interface is described in the US2000/US3000 manuals:



The serial console is used by the manufacturer's diagnostic SW (BatteryView) and also by the ICC. But it's a bit hard to log-in and parse all the information this interface provides, since it was originally intended for running diagnostics and CLI only, not for the automation. Output of the CLI is formatted as human-readable tables and lists. Therefore, parsing this correctly can be a bit tricky. Here's a couple of examples, that are using serial console interface:
https://github.com/irekzielinski/Pylontech-Battery-Monitoring Pylontech-Battery-Monitoring-WIFI-master.zip  
https://www.photovoltaikforum.com/thread/118958-pylontech-us2000b-daten-über-konsole-rs232-auslesen/?t=118958&start=10 Speichersystem_Pylontech.zip PYLON LFP Battery communication protocol - RS232 V2.8 20161216.pdf  
CAN bus communication with Pylontech is the easiest to code. CAN messages are short and easily convertible to the numeric values. Also, there's no need to actively query the batteries, since the messages are broadcasted automatically in a pretty frequent intervals. On the other hand, there are 2 drawbacks: CAN bus HW is not a part of the standard Arduino and Raspberry boards. You have to buy additional shields, hats or converters. The second drawback is, that Pylontech provides just a basic info over the CAN protocol. For example, there's SOC, temperature, voltage, amps, health and state flags. All of this is being reported for a stack as a whole, but you can't get to the individual brick or cell values.
AFAIK, there are no CAN bus examples available on the internet. Luckily, the Pylontech's CAN protocol description is available:
PYLON BMS CAN-Bus-protocol-PYLON-low-voltage-V1.2-20180408.pdf
RS485 provides the most detailed information and even accepts configuration writes. For example, you can monitor individual cell values too. It's the best choice for automation. On the other hand, RS485 messages can be very long and the Pylontech's protocol layer is extremely complicated. There's a lot of circular checksums, numeric values that are not 8bit aligned and variable message length is being used too.
A couple of forum member were already able to successfully implement RS485 comm with the Pylontechs. For example, @Elbow :
https://powerforum.co.za/topic/3429-pylontech-vs-raspberry-arduino-plc/?tab=comments#comment-51956 pylon485-elbow.zip  
https://www.photovoltaikforum.com/user-post-list/106579-ondra234/ pyloncom.zip PYLON RS485-protocol-pylon-low-voltage-V3.3-20180821.pdf  
Hope the above info will help some of you with your Pylontech monitoring efforts.
Youda

The box he has is not running 2.71 but he is upgrading it to show the process. He says it is version 2.71 that has problems. 
The box he upgrades is running 2.61 and upgrades to 102.73
@CoulombI thought I read somewhere that versions 1XX were for a different processor than 0XX versions due to the chip shortage so were incompatible?

Yes, this is correct. If you update the display firmware, the newer Pylontechs will be supported.
You will need to double check what the current display firmware is in Watchpower (not on the display itself as only the last 4 digits are shown).
The newest for the King is 02.81 or 102.73 (see the files on this forum) depending on the display hardware.
Flashing the new firmware with the included Rj45 - RS232 cable and a bought RS232 - USB cable is very easy.
It is absolutely worth doing it as the inverter will then know the exact SoC and will not give you random warning 04 when you use a strong load.
 

I used the firmware posted by @Coulomb 
 

@Vitaliy, I confirm that the approach suggested by @malo is working. It solved today the problem 61 between my Axper King 5000 and two US5000 batteries. 

I personally followed his instructions with his files and the communication passes with a cable of 3/5 Inverter /  7/8 - > with US5000.

Hello, I think I have found a solution with a standard pylontech cable and an update of the panel

Yes. You can't trust the inverter's SoC unless you have the cable working. It might be worth trying harder to get the cable working.
Try setting 29 at 46.0 V. There is an undocumented linkage between that setting and low battery warnings. I suggested 46.5 V to try and keep the SoC higher, but in hindsight it's probably not a great idea. You might have to go even lower on that setting. The inverter can't be used for saving the cells from low voltage; the BMS has to do that job.
When Weber and I finally get the fully patched firmware for Kings done, you will have better options.
[ Edit: Setting 49 -> Setting 29 ]

I guess you mean setting 29 instead of 49?
They didn't change it as you can see above in the US2000 and US5000 manuals.
@VitaliyPlease double check your cable, it should work.
I have recently installed a Axpert King (1) 5K and a US5000 at a friends place and it worked.