On 2024/05/08 at 11:34 PM, nanev said:

how the display has the symbols L1 and L2 from the factory if it only has one AC output

I assume that they use the same LC Display hardware in the standard and twin models, and probably also the duplex (dual AC input) models. Presumably the display firmware sends commands to the DSP to find out what capabilities it has, and turn on the symbols or not as appropriate.

[  Edit: Duo → Duplex ]

Edited October 23, 20241 yr by Coulomb

I tried it now. 61.65+39.16=error 32

I just tried this. 61.03+22.21=WORKING.

4 hours ago, usr023 said:

I tried it now. 61.65+39.16=error 32

39.xx is for Twins; 61.xx is non-twin. It looks like you can't use a Twin display firmware with non-twin DSP firmware.

My guess is that when it sends PTOPxxx commands and gets no response, warning code 32 results.

4 hours ago, usr023 said:

I just tried this. 61.03+22.21=WORKING.

DSP 61.xx and display 22.xx are both non-twin, and so are compatible.

On 2024/05/08 at 3:34 PM, nanev said:

Today I discovered another new thing with these firmware installed, it turns out that the panel reports L1 in the current output, so I understand that this version of U2 is really for the model that has two AC outputs, what I don't understand is how it works in this equipment and especially how the display has the symbols L1 and L2 from the factory if it only has one AC output

Twin models has two AC output, this allow to prioritize some loads connected on L2 or L1 based on your settings.

Axpert Twin and non-twin models shares the same display, so you can see L2 also in non-twin models.

Hello, good morning, I am new to the forum and I was reading you because I have the vm IV 5600w inverter.
I have two problems, first the inverter does not recognize the greenheiis batteries,
I have tried several cable configurations and not even in PYL, Lib or Lic mode does it recognize the batteries.

I attach a photo of the configuration of the can pins on the battery and inverter. 4-5 to 6-7, is correct?

Another problem is that the inverter does not charge the generator set. I'm thinking about upgrading the inverter.
 The version I have now is 61.01 with 22.20 to see if it solves the problem. Any advice?

Thank you

23 hours ago, AlfredCE said:

I have tried several cable configurations and not even in PYL, Lib or Lic mode does it recognize the batteries.

You seem to be expecting the inverter to talk to the BMS via CAN bus, but these three protocols use  RS-485. Only Weco, Soltaro, and LiA protocols use the CAN bus. I know that Pylontech can communicate both CAN and RS-485, but to talk to the Axpert inverters, they must be configured to talk RS-485.

I don't know what protocol "greenheiis" batteries might use; it's not guaranteed that any random battery's BMS will talk to an Axpert.

23 hours ago, AlfredCE said:

The version I have now is 61.01 with 22.20

I don't know about 61.01, but 61.03 is almost a year old as I type. The only other two I have in the 61.xx series (61.64, 61.65) are several months older than that.

22.20 is almost 2 years old; 22.21 about 6 months old. The "display" firmwares are really display / comms / BMS firmwares, so it might be good to update this.

Edited July 6, 20241 yr by Coulomb

On 2024/07/05 at 5:35 PM, AlfredCE said:

Another problem is that the inverter does not charge the generator set.

I assume you mean it won't accept the generator as an AC input. That's a common problem with many inverters: they csn be very picky about waveform quality. You can sometimes use a small load on them before you connect to the inverter. Sometimes you can tweak the governor to get the frequency closer (yet still close enough under load to stay connected). Other times, you just need a better generator (e.g. one with an inverter built in), or use the generator only to charge the battery via a beefy 48V battery charger. 

If you mean it won't charge the generator's starter battery via a built-in 12V supply (I don't know if VM IVs have this), I know nothing about that. 

El 06/07/2024 a las 8:42, Coulomb dijo:

Parece esperar que el inversor se comunique con el BMS a través del bus CAN, pero estos tres protocolos utilizan RS-485. Sólo los protocolos Weco, Soltaro y LiA utilizan el bus CAN. Sé que Pylontech puede comunicar tanto CAN como RS-485, pero para hablar con los inversores Axpert, deben estar configurados para hablar RS-485.

No sé qué protocolo podrían usar las baterías "greenheiis"; No se garantiza que el BMS de cualquier batería aleatoria se comunique con un Axpert.

No sé sobre 61.01, pero 61.03 tiene casi un año mientras escribo. Los únicos otros dos que tengo en la serie 61.xx (61.64, 61.65) tienen varios meses más que eso.

22.20 tiene casi 2 años; 22.21 aproximadamente 6 meses. Los firmwares de "pantalla" son en realidad firmwares de pantalla/comunicaciones/BMS, por lo que podría ser bueno actualizarlos.

Thanks for the response, if the Greenheiss technician confirms that the batteries communicate via RS485. I have tried and it doesn't work. Let's try updating to see if it recognizes them.

El 06/07/2024 a las 13:25, Coulomb dijo:

Supongo que quiere decir que no aceptará el generador como entrada de CA. Ese es un problema común con muchos inversores: pueden ser muy exigentes con la calidad de la forma de onda. A veces puedes utilizar una pequeña carga sobre ellos antes de conectarlos al inversor. A veces puedes ajustar el regulador para acercar la frecuencia (pero aún lo suficientemente cerca bajo carga para permanecer conectado). Otras veces, sólo necesitas un generador mejor (por ejemplo, uno con un inversor incorporado), o usar el generador sólo para cargar la batería a través de un robusto cargador de batería de 48 V. 

Si quiere decir que no cargará la batería de arranque del generador mediante un suministro incorporado de 12 V (no sé si los VM IV tienen esto), no sé nada al respecto. 

Thanks for the response, we will try another group, but we have already had this same problem with several Voltronics.

On 2024/07/06 at 8:42 AM, Coulomb said:

You seem to be expecting the inverter to talk to the BMS via CAN bus, but these three protocols use  RS-485. Only Weco, Soltaro, and LiA protocols use the CAN bus. I know that Pylontech can communicate both CAN and RS-485, but to talk to the Axpert inverters, they must be configured to talk RS-485.

I don't know what protocol "greenheiis" batteries might use; it's not guaranteed that any random battery's BMS will talk to an Axpert.

I don't know about 61.01, but 61.03 is almost a year old as I type. The only other two I have in the 61.xx series (61.64, 61.65) are several months older than that.

22.20 is almost 2 years old; 22.21 about 6 months old. The "display" firmwares are really display / comms / BMS firmwares, so it might be good to update this.

Hello, the technician sends me the screen firmware, 122.15, 102.73, 112.19, why is he sending me these?
 Why don't you send me 22.21? What is the difference between those firmware? My inverter is the VM IV.

19 hours ago, AlfredCE said:

the technician sends me the screen firmware, 122.15,

That's a quite old VM IV display firmware. They haven't use 1xx.xx version numbers for many years now.

19 hours ago, AlfredCE said:

102.73,

That's a very old display firmware for VM IIIs, with the removable display.

19 hours ago, AlfredCE said:

112.19,

That's a very old display firmware for Axpert Max E, with removable display.

19 hours ago, AlfredCE said:

why is he sending me these?

Lack of training and/or experience? My guess is that it's a bit of a chore talking to Voltronic, so they do it as little as possible. Sales are much more interesting than support.

19 hours ago, AlfredCE said:

Why don't you send me 22.21?

I assume you mean why don't they send it? In any case, it's available here: 

 

19 hours ago, AlfredCE said:

What is the difference between those firmware?

There are special cases for each model. For example, the VM series send slightly different commands to tell the display firmware what model it's dealing with. VM display should not present setting 28 (output mode, single/parallel/3 phase), since VMs can't be paralleled. Other models don't have timed output source priority (I have no idea why), and so on.

And of course, there are bug fixes, more battery BMSs are supported as time goes on, and so on.

5 hours ago, Coulomb said:

That's a quite old VM IV display firmware. They haven't use 1xx.xx version numbers for many years now.

That's a very old display firmware for VM IIIs, with the removable display.

That's a very old display firmware for Axpert Max E, with removable display.

Lack of training and/or experience? My guess is that it's a bit of a chore talking to Voltronic, so they do it as little as possible. Sales are much more interesting than support.

I assume you mean why don't they send it? In any case, it's available here: 

 

There are special cases for each model. For example, the VM series send slightly different commands to tell the display firmware what model it's dealing with. VM display should not present setting 28 (output mode, single/parallel/3 phase), since VMs can't be paralleled. Other models don't have timed output source priority (I have no idea why), and so on.

And of course, there are bug fixes, more battery BMSs are supported as time goes on, and so on.

Good morning, thanks for the response. Very difficult to contact Voltronic, you can't talk to anyone.
I have versions 22.21 and 61.65 which, according to what I have read, are compatible with this inverter.
But I'm afraid because I've never done this and I'm afraid of breaking the inverter.
But I have to do it to see if I solve the battery problem at least.

ERROR 32. I am looking for firmware for AXPERT VM 4 3600v. The flood was 61.01 and 22.20

Axpert VM IV non-twin firmware version 61.03 is here:

 

Hello guys 

im new here 

I have an mv IV with round display 

i wanted to get the SOC settings working insteas of voltage so 

I upgraded the firmware to 61.65 and 20.21 

So now I have the settings correct but the inverter is not communicating with the battery anymore 

it was working fine before the upgrade 

Does anyone else had this issue and which firmware has the bms profiles is it the remote panel or the other one 

thanks in advance 

2024/08/03 18:42-kor a Smartsolar azt mondta:

Helló srácok 

új vagyok itt 

Van egy mv IV-em kerek kijelzővel 

Azt akartam, hogy az SOC beállítások a feszültség helyett működjenek 

Frissítettem a firmware-t 61.65-re és 20.21-re 

Tehát a beállítások rendben vannak, de az inverter már nem kommunikál az akkumulátorral 

a frissítés előtt jól működött 

Másnak is volt ilyen problémája, és melyik firmware-en vannak a bms profilok, a távoli panelen vagy a másikon 

előre is köszönöm 

Try this: 61.03+22.21

On 2024/08/04 at 2:42 AM, Smartsolar said:

I have an mv IV with round display 

...

I upgraded the firmware to 61.65 and 20.21 

Sorry, I somehow missed your post.

20.xx are for removable displays; your VM IV does not have this removable display.

As indicated above, you need a 22.xx display firmware, such as 22.21 (the latest that I'm aware of).

61.03 is indeed later than 61.65; the xx.6x firmwares seem to be out-of-order and sometimes experimental versions. However, 61.03 does not have the SoC as a percentage support, whereas 61.65 does. So I suggest that you stick with 61.65 since you want this.

On 2024/08/06 at 2:42 PM, Coulomb said:

Sorry, I somehow missed your post.

20.xx are for removable displays; your VM IV does not have this removable display.

As indicated above, you need a 22.xx display firmware, such as 22.21 (the latest that I'm aware of).

61.03 is indeed later than 61.65; the xx.6x firmwares seem to be out-of-order and sometimes experimental versions. However, 61.03 does not have the SoC as a percentage support, whereas 61.65 does. So I suggest that you stick with 61.65 since you want this.

Hello Coulumb, I hope you are well, I have a problem with the update, let's see if you can help me.
I try to connect the inverter to the PC with the UTP/RS232 cable, I have bought an RS232 to USB transformer, the PC recognizes the transformer but I cannot connect the inverter with the watch power program.
If I connect the inverter with the mini USB cable it does connect me with the watch power program, but I understand that the screen can only be updated with the UTP/RS232 cable.
Another question I have is that there are two types of UTP/RS232 cable, one with 3 cables (pin 1,2,8) and another with 4 cables (pin 1,2,4,8) where pin 4 is power.
I have tried the 3-wire one and I cannot connect two of the same inverters that I have tried.
Where do you think the problem must be?

Could there be a problem with the baud? Both the program and the USB input are configured at 19200.

I attach a link to the rs232/usb cable that I purchased.

https://www.amazon.es/dp/B0753HBT12?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1

 

Thanks for the help

Edited September 12, 20241 yr by AlfredCE

On 2024/09/12 at 4:13 PM, AlfredCE said:

If I connect the inverter with the mini USB cable it does connect me with the watch power program,

That's a good sign; it means that the display isn't bricked. Is this using a type A to micro-USB cable direct to the PC?

On 2024/09/12 at 4:13 PM, AlfredCE said:

I try to connect the inverter to the PC with the UTP/RS232 cable,

Is that the cable that came with the inverter, RJ-45 at one end, and D9 (RS-232) at the other? And are you plugging the two cables together?

It should be display -> cable that came with inverter -> USB to RS-232 adapter -> USB port of Windows computer.

That should be able to run Watchpower.

It's possible that the USB to RS-232 adapter isn't one that the Voltronic software works with. Check for a COM port appearing in the Windows Device Manager, and that the COM port is COM1 through COM9. I don't know about the display update tool, but early Axpert reflash tools would not work with COM10 or higher.

On 2024/09/12 at 4:13 PM, AlfredCE said:

Could there be a problem with the baud?

No, the reflash tools set the baud rate automatically. It actually starts at 2400 bps, and changes to 9600 bps as the reflash actually starts. I have no idea why they put a baud rate drop-down box there.

On 2024/09/12 at 4:13 PM, AlfredCE said:

I attach a link to the rs232/usb cable that I purchased.

That looks OK, but as usual it doesn't say what the chipset is. The AEVA pages have suggested bands, and known good brands available from South Africa, but I don't know where you're from, and what may be available.

When trying to reflash, I assume that you're following the upload instructions, and are getting the UPG YES on the display? But you probably need to get it working with Watchpower via RS-232 first.

I also assume that you're plugging the cable that came with the inverter into the port nearest the PC/monitor icon.

Edited September 14, 20241 yr by Coulomb

On 2024/09/14 at 4:49 AM, Coulomb said:

That's a good sign; it means that the display isn't bricked. Is this using a type A to micro-USB cable direct to the PC?

Is that the cable that came with the inverter, RJ-45 at one end, and D9 (RS-232) at the other? And are you plugging the two cables together?

It should be display -> cable that came with inverter -> USB to RS-232 adapter -> USB port of Windows computer.

That should be able to run Watchpower.

It's possible that the USB to RS-232 adapter isn't one that the Voltronic software works with. Check for a COM port appearing in the Windows Device Manager, and that the COM port is COM1 through COM9. I don't know about the display update tool, but early Axpert reflash tools would not work with COM10 or higher.

No, the reflash tools set the baud rate automatically. It actually starts at 2400 bps, and changes to 9600 bps as the reflash actually starts. I have no idea why they put a baud rate drop-down box there.

That looks OK, but as usual it doesn't say what the chipset is. The AEVA pages have suggested bands, and known good brands available from South Africa, but I don't know where you're from, and what may be available.

When trying to reflash, I assume that you're following the upload instructions, and are getting the UPG YES on the display? But you probably need to get it working with Watchpower via RS-232 first.

I also assume that you're plugging the cable that came with the inverter into the port nearest the PC/monitor icon.

First of all, thank you very much for the answers. I have tried two different inverters and it does not connect to either of them. I saw the cable that I bought on Amazon in a video where they updated a Voltronic, so I bought the same one.
When I connect the cable, Windows recognizes it with com 5, but I can't get it to connect with watch power. I tried to update the inverter screen but it tells me that there is no connection to the inverter.

The problem is that I don't know which cable came with the utp/rs232 inverter, I mixed it with others and then I realized that there are some with 3 cables and others with 4. I attach photos
If it could be updated with the USB cable to the PC directly, there is no problem because it recognizes it well, but it cannot be done with the UTP cable. Do you have any idea what it could be?

17 hours ago, AlfredCE said:

4. I attach photos

Those both look ok, but perhaps check the connections anyway. The connection to pin 4 or 7 doesn't matter as it's not used in this application; you need the connections to pins 1,2 and 8 as per this post:

https://forums.aeva.asn.au/viewtopic.php?p=57914#p57914

It could be that you have the wrong driver for the PL2032 chip and your version of Windows. Google it. 

You can check the wiring by shorting pins 2 and 3 (tx to rx) on the D9 connector, and using a comms program connected to COM5. Everything that you type should be echoed back to you. With local echo turned on, you should see double echoes (e.g. type h, see two h characters). 

5 hours ago, Coulomb said:

Those both look ok, but perhaps check the connections anyway. The connection to pin 4 or 7 doesn't matter as it's not used in this application; you need the connections to pins 1,2 and 8 as per this post:

https://forums.aeva.asn.au/viewtopic.php?p=57914#p57914

It could be that you have the wrong driver for the PL2032 chip and your version of Windows. Google it. 

You can check the wiring by shorting pins 2 and 3 (tx to rx) on the D9 connector, and using a comms program connected to COM5. Everything that you type should be echoed back to you. With local echo turned on, you should see double echoes (e.g. type h, see two h characters). 

I have already been able to connect the inverter with the PC, I send a photo of the modbus configuration. Now I need to try updating. 
I'll tell you. Thanks for the answers. All the best

 

17 hours ago, AlfredCE said:

I have already been able to connect the inverter with the PC,

But still only via USB, not RS-232? The update tool only talks RS-232. 

17 hours ago, AlfredCE said:

I send a photo of the modbus configuration.

I note that Modbus is RS-485, not RS-232. You also have to make sure that nothing else is using COM3. 

Hace 2 horas, Coulomb dijo:

¿Pero todavía sólo a través de USB, no RS-232? La herramienta de actualización solo habla RS-232. 

Observo que Modbus es RS-485, no RS-232. También debe asegurarse de que nada más esté usando COM3. 

Yes, in the end I was able to connect with the rj45/rs232 cable, with the cable that I bought on Amazon it works perfectly. With com port 3, changing the stop bit to 2, and the baud to 9600, the connection between inverter and PC worked. Now we need to test the update.
Let's see if I can solve the fact that the generator set is not detected by the inverter, and that the inverter detects the lithium batteries with the SOC percentages.
Now I have another problem with this inverter, it does not close the contact to start the generating set, when I change parameters 12 and 13 so that it starts and charges batteries, it does not close contact, and before it did... let's see if it works with the update.
I'll tell you, thanks for the help.

On 2024/09/20 at 8:25 AM, AlfredCE said:

Yes, in the end I was able to connect with the rj45/rs232 cable, with the cable that I bought on Amazon it works perfectly. With com port 3, changing the stop bit to 2, and the baud to 9600, the connection between inverter and PC worked. Now we need to test the update.
Let's see if I can solve the fact that the generator set is not detected by the inverter, and that the inverter detects the lithium batteries with the SOC percentages.
Now I have another problem with this inverter, it does not close the contact to start the generating set, when I change parameters 12 and 13 so that it starts and charges batteries, it does not close contact, and before it did... let's see if it works with the update.
I'll tell you, thanks for the help.

Did it worked? I have got the SAME IDENTICAL PROBLEM with U1 61.01 AND U2 22.20