Good Day Guys

I managed to connect my Axpert to the laptop running Watchpower using the network port on the inverter and usb on the laptop. This was with a serial converter cable. 

I bought the ICC software with the Raspberry pi. My previous cable does not seem to work with the pi. 

The micro usb connector on the inverter to usb on the pi has also been unsuccessful to date. Ive read the micro usb cables can be tricky to find the right one  

To maybe prevent serious further frustration is there any tips/tricks to connect the Axpert to the Raspberry pi via the micro usb port on the inverter  

any input will be appreciated  

Greetings

Albert

 

13 hours ago, SnoopySniper said:

The micro usb connector on the inverter

It would probably help to say what model of Axpert 5 kVA inverter you have. From the connector size, it sounds like a King or a VM III, but it might be an Aerox or something else.

Edit: from your duplicate post, it seems more likely that it's a King. Perhaps ICC experts can chime in.

Edited August 20, 20196 yr by Coulomb

Miracles apparently still happen. After leaving the Pi of throughout the night and re-connecting it this morning ICC sees the inverter (axpert King).

Everything setup now. must say the software is super compared to watchpower.

Cheers

Hello there, I have a 5KVA inverter connected to a 100 Ah Huawei lithium battery. When starting, I get an H5 error code - the display is showing me that the inverter is connected to the grid, but it is not charging the battery. Any hints? Thanks, Thomas

HS is not an error code (no warning or error icon), it just means it's a master in a paralleled and/or 3-phase system. If you have only one inverter, change setting 28 (AC output mode) to SnG (need the power switch off to be able to change this one setting).

If you have more problems than that, we'll need a lot more information.

Please check the communication cable between display and main board. Remove the display connector and reconnect it. 

Thanks. 

Hi all,

Have anyone resolved the error 61 yet?

US3000 x4 with communication cable to one of my inverters in parallel.

If setting 05 on USE, no problem, as soon as you set it to PYL (which setting was not available when other batteries was installed without comms cable), error 61.

I have the whole system on the grid without any load as I am on the grid by way of a switch over.

The batteries are charging from PV, been charging for almost two hours while i was searching for the error code.

What is funny though is that the battery SOC is dropping in line with the PV availability or power as per PI and ICC.

Just switched off the inverters so that they show that they are in "bypass" mode, the battery jumped back from 56% SOC to 67% SOC. The lights (SOC) on the batteries are steady at the 2nd to last on from full.

 

2 hours ago, Wilfred said:

Hi all,

Have anyone resolved the error 61 yet?

US3000 x4 with communication cable to one of my inverters in parallel.

If setting 05 on USE, no problem, as soon as you set it to PYL (which setting was not available when other batteries was installed without comms cable), error 61.

I have the whole system on the grid without any load as I am on the grid by way of a switch over.

The batteries are charging from PV, been charging for almost two hours while i was searching for the error code.

What is funny though is that the battery SOC is dropping in line with the PV availability or power as per PI and ICC.

Just switched off the inverters so that they show that they are in "bypass" mode, the battery jumped back from 56% SOC to 67% SOC. The lights (SOC) on the batteries are steady at the 2nd to last on from full.

 

Okay, now I see a potential issue:

1) US3000 x4 with communication cable to one of my inverters in parallel.

As far as I know, Axpert firmware does not work correctly when you have more inverters running in parallel while having Pylontech BMS connected to one of them at the same time. Simply, the master inverter is not passing the BMS values to the slave inverter. Since slave inverter is not able to communicate with the BMS, system throws an error.

A possible workaround would be to logically reorganize your four Pylontech batteries to 2+2 setup. Leave all the DC cables connected as they are, but remove the short UTP communication cable that's between brick #2 and #3. Then reboot the battery. This would create two logical stacks with two master batteries. Connect RS485 port of one master battery to the first Axpert and RS485 port of other master battery to the second Axpert. This way, both Axperts will be able to communicate with BMS. Just remember to keep all the DC power cables as they are - still having all 4 bricks paralleled together and acting as a single large battery bank.

2) Just switched off the inverters so that they show that they are in "bypass" mode, the battery jumped back from 56% SOC to 67% SOC. The lights (SOC) on the batteries are steady at the 2nd to last on from full.

This clearly indicates that the Axpert is not reading SOC from the Pylontech BMS, but is guessing the SOC from the battery voltage instead. As with the common lead-acid cells.

 

Makes sense?

 

On 2019/10/29 at 7:47 PM, Youda said:

Makes sense?

It does actually :)

Axpert 5kva inverter fault 55 initial on 230vac but after 5 seconds error 55

3 hours ago, Saqlain said:

Axpert 5kva inverter fault 55 initial on 230vac but after 5 seconds error 55

Is one of those 55s a typo?

Fault code 55 (error 55) is restartable (you can continue operation after a while), unless you get three fault code 55s in a row (I think). Fault code 55 is "over DC voltage in AC output", which I believe occurs when the output reads 20 V or more DC (should average to nearly zero) for 10 seconds in a row (1000 times total, that task runs at 100 Hz).

I think I've speculated on what might cause this before; perhaps the transformer saturated due to a spike on the mains, or an IGBT or other component has gone leaky. Unless you're very adept at electronics faultfinding yourself, you'll need to take this one in for repair. Though I suppose there is a small chance that some faulty load might cause this. You could try and eliminate loads one by one or in batches, starting with no load at all. Obviously if it faults on no load, then it's a hardware problem with the Axpert.

Hello all. I have installed 2 mecer 5kva inverters in parallel. On one of them I have gotten an fault 73 (high PV voltage) but there is no PV connected to it. And the voltage was at 119V before I disconnected it. Does anyone know how I can fix this problem?

9 hours ago, Brandon said:

I have gotten an fault 73 (high PV voltage)

You didn't say exactly what model of Mecer 5 kVA inverter you have. In the Axpert MKS, error 73 means "inconsistent output voltage", e.g. one set to 230 VAC and the other set to 220 VAC. Use WatchPower or similar to set the output voltages to be the same.

Hi guys. Does anybody have any tip for solving Axperts inverters failures 05 (short circuit) and/or 07 (overload)? I have an inverter and a motherboard in fault 05, and an additional inverter in fault 07, and of course I would like to fix them. I have checked all of the IGBTs, mosfets, transistors, diodes ....(and even all of the resistors of them), and couldn't be able to find any component in failure. I appreciate any suggestion

7 hours ago, Alberto said:

Axperts inverters failures 05 (short circuit) and...

So do you measure an actual short, or low resistance, from live to neutral output? If so, you should be able to trace that back by temporarily disconnecting components.

Of course, these are all moderately high current components, so that's non trivial. Sometimes a current limited power supply pushing into the short, coupled with a multimeter on millivolts, can help and not require disconnection.

Edited February 6, 20206 yr by Coulomb
Added "current limited"

I'm in Spain. I've just installed one of these inverters - the 5kW version. It ran fine today. I'm using a Pylontech US2000 LiPo battery. I was setting the date this evening and also set the battery type to Pyl (Pylontech). After about 5 minutes the inverter started flashing Fault Code 61 and then turned itself off! Bit odd. I reverted back it to the default AGn and it's working fine again. What's going on? 

Also the BT connection doesn't work, I can pair with it but Watchpower doesn't see the inverter. Any ideas? Do I need to run the PC configuration software? 

 

Looks as though I have to take that back, it's giving me the same Fault Code 61 again. 

Edited June 5, 20206 yr by Greg Ford
Updated information

Update
I hadn't set the first dipswitch to on
I did that and restarted everything. The fault code persists.
Reset the battery type to AGn - fault cleared.

Wondering whether the RJ45 cable is not twisted. I'll look at that tomorrow.

5 hours ago, Greg Ford said:

After about 5 minutes the inverter started flashing Fault Code 61 and then turned itself off! What's going on? 

61 means communications lost. I'd say you don't have the correct cable pinout.

My understanding is that warning (not fault) code 61 can only happen with setting 05 (battery type) set to PyL.

When you say "turned itself off", do you mean the inverter-charger or the battery? I didn't think that the inverter-charger would turn itself off after merely a warning.

Thanks Coulomb for taking the time to reply.

Some good news, I installed the Watchpower application on my laptop and it connects to the inverter. Thank goodness for that anyway.

I have the inverter/charger connected to the Pylontech US2000 using an RJ45 cable from the CAN jack on the battery to the Lithium Battery RJ45 connector on the LCD panel. Is that correct?  The inverter/charger still refuses to talk to the battery. I'll check the wiring of the cable to see whether it is twisted - I'll scope it if necessary.
The BT connection still doesn't work, it pairs fine but doesn't transmit any data.  I suppose that could be a firmware issue.

3 hours ago, Greg Ford said:

I have the inverter/charger connected to the Pylontech US2000 using an RJ45 cable from the CAN jack on the battery to the Lithium Battery RJ45 connector on the LCD panel. Is that correct?

No, it should be the RS-485 port on the Pylontech. Axperts don't have user accessible CAN ports.

Error 53 on inverter 

Its a new inverter, when i switch it on if fails to close the link which show it’s now on and the output ranges from 7~9v 

Battery is on 50.2vdc, No PV connected at the moment.

Kindly assist what could be the problem 

 

 

5 hours ago, roosterzw said:

Error 53 on inverter 

Its a new inverter,

On an Axpert inverter, this is "inverter soft start error". I believe what happens is that after the bus has charged up, the next test is to run the inverter at a low PWM (that's possibly the few volts you saw), and wait for a zero crossing of the inverter output. My guess is that either the output relay failed to close, or there is a fault with the full bridge inverter IGBTs or their gate drivers.

Do you have any loads connected? If so, try disconnecting all AC loads.

If not, then since this is a new inverter, this is definitely a fault, and you should get it replaced or repaired by your supplier.

This appears to be a clone that I'm not familiar with, so it's possible that error 53 has another meaning, but it seems to fit your symptoms.

Hi.  Hope you all well.

I've got 3 x 5kva Mecer Model name: SOL-I-AX-5NB which give an error code 80.  Any ideas on that code.

Can't get it in any manual.

Thanks.

 

3 hours ago, R Cerva said:

which give an error code 80.  Any ideas on that code.

Can't get it in any manual.

It's in the parallel guide. It's called "CAN fault" or "CAN data loss". It's CAN bus that connects between inverters (through the round grey cables with connectors that look like VGA connectors). My guess is that there must be a fault with one of the parallel boards or cables. Check for tightness of connectors (they should be screwed in), and also the connectors inside the inverter to the ribbon cables.

Hi, i have a 5kva Mecer Model name: SOL-I-AX-5M (July 2015) and I get a error code 57 after relay toggles for a number of times, then goes to this error (57), so

bypassed the inverter and switched it off as I could not get the inverter to work with this error, any ideas?