raytry

I did not noticed RXTX library here, but rather jSerialComm2.7.jar, which seems to not use native libraries.
Only thing which uses native code, is libUSBDevice.so, used by WatchPower.jar directly.
I installed 32-bit Linux version of WatchPower on x86 Linux PC, copied it over Raspberry Pi, made some modifications to LAX config to not use embedded Java VM (because it is x86 one) and some other modifications, to launch it. Still, for having working USB connection, I written my own libUSBDevice.so replacement, and it works quite well so far.

 

272.66 fixes the premature float bug. In some cases, this might be reason  enough to choose it all by itself.
The only other change is that the threshold to skip the "race to the bottom" code (which leads to being stuck at 90 V on the panels) is reduced from 0.50 A to 0.05 A. This is usually enough to provide a noticeable improvement in PV production, especially in cloudy or rainy weather when you really could use every joule of energy you can get.
In all my patched firmware update files, there is a .txt or more recently a .asm file that has comments on what it changes. As an example, dsp_272.66_patched_05.asm starts with:
Edit: As for which one is "better", it's a user preference. The patched files are all amateur experiments, but sadly, they tend to perform better than the factory firmware.

There wasn't.
Yes, it turns out that patching the voltage is only 5 locations, not too hard.
So this is patched firmware version 192.04 (yes, my numbering isn't all that consistent), based on factory firmware version 92.04, for Axpert Max 1 (with removable display) 8kW and the TMS320F28066 DSP chip. It fixes the premature float bug, and applies Georg's patch set (apart from one set that doesn't apply), for a minimum MPPT voltage of 175 V. Will not work with models with the '2809 chip. Do not use with other inverter models.
Original .inv (hex) file is dated 2022/Sep/22. So fairly recent.
Use at your own risk.
 

Today i got a new EASUN 8 KW
it comes with firmware 46.08 main and 12.21 secondary.
flash without any problems to 90.06 based firmware(90.09)
 
 

Website claims company started in 2020
Facebook Page only created in 2021
Facebook Page lists business as "opening soon" so therefore no customer reviews or complaints
All social media mentions are from "giveaway" draws
Yeah, this stinks. Buyer Beware

And does  the FiveStar use geniuine Voltronic parts and subassemblies.? 

And who supports them, do you have a repair centre? 

Ok, that blows my earlier theory. 
Maybe when the grid is connected, the firmware keeps a small power coming in from the grid, so that common drops in load don't burp energy back into the grid. 
When the grid is disconnected, that power comes from PV instead, dropping the PV voltage if the sun is weak. 

Yes, where the voltage flatlines at 200 V. The MPPT could be taxing the panels a little harder, increasing the current in those regions.
Wonderful data, BGD; thanks a heap for that. I wonder about some of the sunny days, where maybe the current started to rise later on the 200 V version compared to the factory firmware. But that might have just been differences between the weather the two days.
It occurs to me that the best comparison would be to build a sort of "hybrid" patch, where say MPPT1 has 200 V firmware, and MPPT2 is unpatched (factory code), or 175 V in one and 200 V in the other, etc. I imagine that the two sets of panels would see almost identical sun, whereas successive "sunny" days might see different sun. Probably it's too much work for little reward, but if we have a question that can't be answered any other way, I'd be happy to patch one up.

@Coulomb
I think the original code to reduce mppt voltage when current is below a limit is to archive if one or two modules get shade to pull down the voltage until the bypass diodes will get active and so the other modules can bring full power.....
 
But the code is so bad that there is no check if this routine makes it more worse .....
 
On professional Inverter it's shade management and really highly complex 
 
Maybe we can bring back this function but with intelligent logic 

Maybe a look in the datasheet of PV moduls will bring us more information.
Just have a look at the performance curve in correlation to sun power .....when you look there you will see voltage and MPPT point is always relative high
If you think mppt logic is surging not enough current open your PV string and Check idle voltage....dont do it under higher power levels.... dangerous DC sparks will occur.
 
Mppt calculates voltage X current= power ...and it plays with the voltage to archive maximum power .
 
Look at my Trina tsm graph
Maximum power is always at nearly the same voltage......
 

I have no idea why you need the Arena flash tool and Biondiba does not. You both seem to have Axpert MAX 8kW inverters. [ Edit: It was later concluded that the Arena flash tool and 1xx.xx main firmware version numbers are used with the '28066 processor; standard reflash tool and xx.xx main firmware version numbers are used with the '2809 processor. ]
So it seems you need a modified version of 92.04 firmware. I've taken Georg's changes and applied them to 92.04. It should identify as 92.05. This is the 200 V minimum MPPT voltage version. I can fairly easily change that to 100V or whatever other value. 
I have no way of testing this, so use at your own risk. But I'm very confident that it will have the same effects as Georg's patches to 90.06.
Though I have to say that I don't really understand completely how Georg's changes work. 
There was one change that I could not implement, because that code simply doesn't exist in 92.04. Hopefully, it's not a critical one. If it turns out that it is critical, it can be implemented with a larger patch. But I'm 99% sure this won't be necessary.
Naturally, I'll be very interested to hear what happens.
Edit: This patched firmware is essentially obsoleted by patched firmware version 92.06, which has a better-named zip file, and  fixes the premature float bug as well.
 
MAX_8K_28066_9204 patched.zip

Good evening.
So the firmware from Georg594 is flashed and the inverter works fine.
The voltage value on the south-eastern string PV1 was around 300V for a long time and the current slowly decreased. At the end of the day, when the current reached almost zero, the voltage dropped to about 100V.
In one sentence, PV1 kept producing until the last moment. I have never had such a smooth end of day production.
I will continue to test it in the scope of my free time.
Georg594 thank you again for your help and your time.

If the voltage is below 280v MPPT will stop surging current....
But if you look at his configuration of 10 Canadian moduls in series.... there will be a current below 0.1A if you are at 280v.... then it will fall down to ~90v of the hardware limit....
At this point there is everything "pressed" out of it .... solar power is so weak that it's just useless 
 
Mine jumps in the morning from 89v  to 380v when there is a current of more than 0.1A . In the evening the same but opposite.
 
 

INTRO:
Long ago i had the theory that Internal Supply of the inverter will cause currents on both mppts inputs which will interference with mppt regulation.
 
NOW IT'S PROVEN:
The simple solution is to pull of the plug on the supply pcb which is marked with "SOLAR".
The downside:   1. Loosing of Batteryless Operation .
                            2. Inverter will not start from PV inputs when its switched off by the button to charge the battery.
MPPT works now with a minimum current of 0.0002A    really   0.2mA   (first time i cant believe the measurement)
 
FIRMWARE Modification is still needed but just only a littlebit .....not so much as in the past.
 
@Coulomb
Only the subtraction value needs to be zero, no longer need to set the minimum MPPT voltage higher than 90V or reset mppt code. Maybe we can even lower this for maximum compatibility.(eg 60v like in the twin models)  
 
 
Here a picture of the disconnected plug (on the upper right)
The safest way is to completely disconnect your inverter from any powersource before pull of the plug .

 
RESULT :
 
I supply PV 2 input with a isolation tester which provide 250V
MPPT point found by the firmware at 168V and 0,000487A 
 
WOW this is 0,082 watts 😅
 
MAYBE IT CAN USE THE MOONLIGHT FOR SOLAR PRODUCTION??? I'll check
 

I can't wait to test it, TX for the hard work!!
My setup is 2 string on 375w * 10 pic's Canadian Solar and 25Kw li ion battery Nissan Leaf with Orion Jr 2 BMS and Victron Smart Shut for monitor the pack in solar assistant 

I thought I'd start a new thread about the various chipsets in the Voltronic Axpert inverters.
The main DSP chips have until about mid 2022 been TMS320F2809s, except for some low power models with 8-bit microcontrollers, and the VM series which have the TMS320F28062 chip, which has half the flash size of the '2809. Since about mid 2022, the TMS320F28066 is used. [ Edit: The Axpert King 1 probably used the '28066  DSP earlier than that. ] The '28066 is a more modern DSP chip, with only a single power supply (3.3 V), where the '2809 used two power supplies (3.3 V and 1.8 V). As a result of this, you can tell by looking at a control board whether it uses the older or newer chip: the older ('2809) chip will have two voltage regulators, and the newer chip ('28066) will have one:

There is also the confounding factor of the "experimental" main firmwares, version 9x.yy. These numbers seem to be almost randomly assigned, so you can't read anything into the major version number, except that it's experimental in some sense.
The DSP firmwares for the two chipsets are incompatible, and have different major version numbers (the digits to the left of the period). If you try to flash the wrong chipset (but get everything else right), the firmware upload will fail, and your inverter should not be bricked. It should come good after a restart.
At about the same time, the displays (removable and colour with round LED ring) started changing microcontroller. This may or may not be a result of the worldwide chip shortage, and the same could be said about the main DSP chip change. Until about mid 2022, the displays always had an ST Microsystems STM32F107VCT6, which is an ARM Cortex-M3 V7 or V7M3. Some later displays have used the GigaDevice GD32F105VCT6.
The display firmwares for the two display chipsets have also been incompatible. Unfortunately, if you reflash a display with the wrong type of firmware, there is no anti-bricking protection! Fortunately, the display is usually not permanently bricked, but it can be quite an effort to recover it, requiring patience and multiple attempts with varying timing from power-on to clicking the update firmware button on the PC. Firmware version numbers were at least segregated: the GigaDevice firmware version numbers started with a leading "1" (e.g. 122.34), and the ST Microsystems firmware version numbers do not start with a leading "1" (e.g. 22.34). But here is the kicker: the displays can only show the last 4 digits!! Fortunately, the round colour GigaDevice displays attempt to indicate the leading one with a column of dots, like extended decimal points:

I finally found a pair of comparable xx.yy and 1xx.yy display firmwares: 36.01 and 136.01. My theory, not totally confirmed, is that these only differ in whatever customisations are needed for the different chipsets; the functionality and logic would, per this theory, be identical. So I was curious to compare the firmwares.
Alas, internal addresses used in the firmware seem to be different. For example, different addresses appear to be used on the I2C bus, and extra GPIO bits seem to be used. If I'm right, that means that the display boards may have different circuits, even though at first glance they seem to be the same except for the brand of ARM chip. So that makes it impractical to take a 1xx.yy firmware and with a few patches turn it into a xx.yy firmware, or vice versa. With the difficulty of obtaining certain firmware versions, that might have been a useful ability. [ Edit: Fortunately, this is not the case; see below. ]
Edit 16/Mar/2023: One concrete difference seems to be how the two chips send and receive I2C data. I2C seems to be used for the EEPROM chip and some other functions I have yet to identify. In the ST chips, there is hardware that implements I2C; in the GigaDevice chips, this seems to be missing. However, I believe that ARM input/output pins are very programmable, so it seems likely that they were able to use the same pins for I2C data, clock, and enable pins, and emulate the I2C hardware with "bit banging" and busy wait loops. Crude, but if you can't buy the ST chips, what else can you do? It's not like the display chips are chock full of time critical functions.
Edit 2 16/Mar/2023: When I went to look at the I2C code in firmware version 12.21, which is supposedly able to run on both chipsets, I expected both hardware and bit banging code, selecting the appropriate one for the present hardware. But I just found the bit banging code. Then I realised: ST chips can bit bang just as well as GigaDevice chips, and the speed of both would be close enough for I2C, which from vague memory is more or less synchronous (each side waits for the  other to transition, except for the actual data bits). There may be more to the unification than that, i.e. it's possible that older 1xx.yy firmware won't automatically work in hardware that came with 1xx.zz firmware. But at least the I2C hardware difference is easy to address.
Edit 3 12/Oct/2023: For the Axpert King 1 and Axpert VM III display firmwares (02.xx and 102.xx), they seem to have switched exclusively to bit banging firmware (which should be compatible with both chipsets, i.e. universal) somewhere between 02.70 (not universal) and 02.81 (universal). Probably 02.73 was also not universal, since 102.73 is not universal. For Axpert MAX display firmware, the existence of 112.19 strongly suggests that 12.19 was non-universal. 12.21 is known to be universal. So with the latest display firmwares, it is no longer necessary to know which chipset the display firmware is written for; it should work on both chipsets equally well.
Edit: Added paragraph on experimental firmware versions.
Edit: Added more on the display firmware differences.
Edit: Added that the Axpert King 1 uses '28066 DSP.
Edit 3: Added a paragraph about which King 1 and Max display firmwares are universal.

According to information from TommaTech Support dated 11 Jan 2023, the latest version 12.21 is applicable for all Removable Displays with previous 12.xx or 112.xx version but so far is not confirmed yet in practise.
I am planning to re-flash one of my Displays with 112.19 with 12.21 in close future (after receive spare one on hands) and will post results after that.
If somebody already make such attempt already, please to share results too. Thank You in advance!
Remote_Panel_Reflash_MCU_12.21.rar