March 4, 20206 yr Ok cool. Is it necessary to update the display firmware first? not sure on the mcu.hex thats the file which was part of the download. There was no AXPERT.TXT file. There was also and "important.txt" file but there seems to be an error with it.
March 4, 20206 yr 3 hours ago, Abnormal said: Is it necessary to update the display firmware first? Unknown. Per this post, it's probably a good idea. In fact, I've edited the comments in my 71.86 firmware upload to say so. 3 hours ago, Abnormal said: not sure on the mcu.hex thats the file which was part of the download. That's the file that the upload process needs (it contains the actual firmware binary data), and is most of what is sent between the PC and the inverter-charger. 3 hours ago, Abnormal said: There was no AXPERT.TXT file. I have no idea what, if anything, this file does. Just ignore it. Quote There was also and "important.txt" file but there seems to be an error with it. That file seems to be "important" to the developers, not we users. It seems to be in a mixture of Chinese and Vietnamese. Again, ignore it.
March 7, 20206 yr Managed to update both successfully using a laptop with a com port. Was pretty straightforward. U03 version also changed when updating the Panel. Old Versions U01 - 71.50 U02 - 01.21 U03 - 00.21 U04 - 00.00 After updating the Panel it changed to U01 - 71.50 U02 - 02.00 U03 - 88.88 U04 - 00.00 After updating the the Main firmware it changed to U01 - 71.86 U02 - 02.00 U03 - 88.88 U04 - 00.00
March 8, 20206 yr 13 hours ago, Abnormal said: Managed to update both successfully using a laptop with a com port. Was pretty straightforward. U03 version also changed when updating the Panel. U03 - 88.88 I suspect that 88.88 is an invalid version number. Perhaps the Bluetooth processor did not respond in time. It seems common for 88.88 to come up after the display firmware has been updated to 02.00. I believe it will "come good" in time, and will be back to version 00.21.
March 31, 20206 yr Hi there guys, I have been reading this topic with interest. I am having an issue with my clients Axpert King 5kVA that I installed for him. So, here's what is happening... I am getting a continual looped warning (Warning 69) when the batteries (Pylon US2000B x2) are fully charged. Its almost like the BMS is telling the inverter that the batteries are fully charged and not to charge them further. When this warning flashes, battery charging stops. After a few seconds, the warning disappears and the unit charges the batteries as usual. A few seconds later and the warning reappears. This cycle continues endlessly... During the changing of modes of charging, theres is clicking of relays back and forth, and the fan cycles 100%, then stops, as the loop continues... I have tried to change settings in the back to battery voltage range and see if this affects the issue, but it does not. No matter what I set the value at, the loop continues endlessly. Does anyone have any feedback on this? Current version of firmware... U1 - 71 90 U2 - 02 40 U3 - 00 24 U4 - 01 10 I have set the batteries from PYL back to USE and input the suggested ICC Pylon battery settings of: Bulk - 53.2v, Float - 53.2v, Back 2 Discharge - 50.0v, Back 2 Grid - 48.0v, Battery Cutoff - 46.5v Thanx guys
March 31, 20206 yr @RichieRich Its setup in SUB mode The client has 4000w of solar on the roof and it is setup in this manner so that he can run "off grid" to a degree during the day when the sun is shining. If the grid fails and its an overcast day, then he has his fully charged lithium batteries to power his installation.
March 31, 20206 yr On 2020/03/04 at 1:22 PM, Coulomb said: Unknown. Per this post, it's probably a good idea. In fact, I've edited the comments in my 71.86 firmware upload to say so. I did the inverter first, then the panel. Once my display panel was updated successfully, it started up but had 2 problems The bluetooth version command no longer worked. "VERFW:" it would return "(" and nothing more I could no longer connect using USB (didn't try serial) To rectify this, I had to turn off power to the inverter and disconnect the battery so it would fully shutdown. Then when I started it up, I still couldn't connect using USB. I held down the USB button and it complained about something, then went back to the main screen. At that point everything was back to normal. All firmware versions are now the latest. I was running 81.40 on the inverter and my panel was the same as other people running 81.50 Edited March 31, 20206 yr by Gnome
March 31, 20206 yr 1 hour ago, DeeJay said: Current version of firmware... U1 - 71 90 U2 - 02 40 U3 - 00 24 U4 - 01 10 I've seen mention of this version, but I don't know of anyone who has uploaded the files anywhere yet... So to be honest, it is hard to be sure because most people here are not running that version. 1 hour ago, DeeJay said: I have set the batteries from PYL back to USE and input the suggested ICC Pylon battery settings of: Bulk - 53.2v, Float - 53.2v, Back 2 Discharge - 50.0v, Back 2 Grid - 48.0v, Battery Cutoff - 46.5v So you were running using PYL before or were you using "ICC" before?
March 31, 20206 yr I was using PYL setting for this inverter. I was using ICC on a different inverter as it did not have a BMS system, which is where I got the Pylon settings from.
March 31, 20206 yr @Gnome Is it possible to roll back to previous firmware to see if this solves the probem? I have not seen anyone mention this problem on this thread as yet... Maybe it's only in the new firmware??
March 31, 20206 yr 11 minutes ago, DeeJay said: @RichieRich Its setup in SUB mode The client has 4000w of solar on the roof and it is setup in this manner so that he can run "off grid" to a degree during the day when the sun is shining. If the grid fails and its an overcast day, then he has his fully charged lithium batteries to power his installation. Check and see if it does it in SbU. Ive noticed in SUB that the solar supply seems to "hunt" a bit when the batteries are full and the load is low. This could be what you are seeing. I don't use SUB very often so can't really offer more at the moment. Do you have ICC monitoring the King ?
March 31, 20206 yr Just now, RichieRich said: Check and see if it does it in SbU. Ive noticed in SUB that the solar supply seems to "hunt" a bit when the batteries are full and the load is low. This could be what you are seeing. I don't use SUB very often so can't really offer more at the moment. Do you have ICC monitoring the King ? This could well be what I am seeing. The client wants to run his system in the way described which is why I selected SUB instead of SBU. How would I setup his system to run in SBU? The battery back to grid voltage would need to be set quite high so that it does not run the batteries flat if the solar is not adequate for the load? There is no ICC monitoring this installation, as the BMS was supposed to be doing the job, and the client did not want to pay the extra for ICC.
March 31, 20206 yr 8 minutes ago, DeeJay said: There is no ICC monitoring this installation, as the BMS was supposed to be doing the job, and the client did not want to pay the extra for ICC. Well if you are 100% convinced it'll work with that particular software. But I'm not convinced it will fix it... 18 minutes ago, DeeJay said: @Gnome Is it possible to roll back to previous firmware to see if this solves the probem? I have not seen anyone mention this problem on this thread as yet... Maybe it's only in the new firmware?? You can install older versions, but given @RichieRich post above, it is more likely a bug that exists in all the versions. Only a hero like @Coulomb would be able to fix this because Voltronic don't seem to make much effort fixing these problems. @DeeJay Whatever you do, please report back when you solve it Edited March 31, 20206 yr by Gnome
March 31, 20206 yr I use ICC to control my King. My Pylons are also connected to ICC so im able to use the Pylon SOC to control what the King does. Unfortunately Im not sure how to control "Back to grid" or vise vera with out it.
March 31, 20206 yr @RichieRich So you are suggesting that I connect the ICC again and see how it goes? See if I have better control with the ICC instead of relying on the inverters BMS and controls?
March 31, 20206 yr Just now, DeeJay said: @RichieRich So you are suggesting that I connect the ICC again and see how it goes? See if I have better control with the ICC instead of relying on the inverters BMS and controls? Is your setup in SBU mode?
April 1, 20206 yr 23 hours ago, DeeJay said: During the changing of modes of charging, theres is clicking of relays back and forth, and the fan cycles 100%, then stops, as the loop continues... Just a wild guess: maybe the inverter overshoots the target charge current, which would be quite low or zero when the battery is full, so the battery voltage is excessive (perhaps only on one or two cells); as a result the BMS disconnects the battery from the inverter. This could cause all sorts of weirdness, possibly including the fans going to 100% briefly as the inverter more or less does a power-on-reset. Is is possible to measure the battery voltage when this weirdness happens? It might even be a bit too fast for a multimeter; it might have to be a Digital Storage Oscilloscope. If this turns out to be the case, my guess is that this is due to the ridiculously high recommended charge voltages. Turning down settings 26 and 27 (bulk/absorb and float battery voltages respectively) might fix it. Changing them to around 51.8 V (that's a long way down from 53.2 V) might be a good starting point. If that works, gradually increase the voltages till the problem returns, and back off an eighth of a turn 🙂. I realise that this testing is not easy for some installers with customers, but some owners might be able to sort out suitable figures, so then you just have to change the settings. You might even be able to do that remotely.
April 1, 20206 yr 1 hour ago, Coulomb said: Changing them to around 51.8 V (that's a long way down from 53.2 V) might be a good starting point. If that works, gradually increase the voltages till the problem returns, and back off an eighth of a turn I have had the same problem with these my Kings - as @Coulomb suggests it was an individual cell going over-voltage, causing an error 69 (stop charging) and sometimes a battery shut down. I have gone back to USR on battery type and 52.9V & 52.5V as settings 26 & 27 - it works beautifully. As an aside, battery type PYL does not work at all in paralleled Kings on 71.86 firmware.
April 1, 20206 yr Thanx @Coulomb & @Calvin A quick question then... I have read somewhere, and also been told the same thing, that if you use USR on battery type and setup your individual voltages on the different settings, then the lithium battery does not function as well as if it was working through a BMS. Apparently this is because the inverter reads voltage across terminals instead of reading percentage charge left in the battery. Will this have an impact on overall battery capacity and performance? These are the 2 questions my client is asking me... In particular a video on youtube worries me regarding this... The forum wont let me post the link, but if you search "how to connect and use pylontech cable" on youtube you see a demonstration of how retarded the battery works under the Axpert settings for a lithium battery. I suppose the only option would be to permanently connect an ICC control hardware system to the inverter and batteries...? Edited April 1, 20206 yr by DeeJay
April 2, 20206 yr 12 hours ago, DeeJay said: Will this have an impact on overall battery capacity and performance? It would certainly be better if the inverter and BMS talk to each other properly. This allows for the least hassle when things go wrong. But if everything is working well, the USR route works well enough. It's a pity that Voltronic didn't get all the bugs worked out before advertising this feature. 12 hours ago, DeeJay said: I suppose the only option would be to permanently connect an ICC control hardware system to the inverter and batteries...? That does seem the best option at this point.
April 2, 20206 yr 3 hours ago, Coulomb said: It's a pity that Voltronic didn't get all the bugs worked out before advertising this feature. Yes, well, when you are selling millions of units worldwide, and there are people such as yourself out there who can manipulate code, why should they need to do anything about it. Their job will eventually be done for them, or a workaround will be found. 🤬
April 2, 20206 yr 1 hour ago, DeeJay said: Yes, well, when you are selling millions of units worldwide, and there are people such as yourself out there who can manipulate code, why should they need to do anything about it. Their job will eventually be done for them, or a workaround will be found. 🤬 I don't think they are malicious about it. Software developers cost a lot of money to hire. Especially engineers that are comfortable with coding for a platform like the inverter is running. It is probably being written as C code that runs directly on a CPU. It is a lot more tedious to write code for something like that than it is to write for example Java/Python/etc. As for them not fixing the bugs that @Coulomb, I suspect one of two reasons: 1) They don't consider it a bug 2) Their engineers aren't aware of what is being produced by people like @Coulomb. This is pretty common actually and even more so if you are speaking a completely different language (ie> Chinese). The way they operate is pretty close to how 99% of companies work, they put out a product and only make updates if they need to.
April 2, 20206 yr 1 hour ago, Gnome said: 2) Their engineers aren't aware of what is being produced by people like @Coulomb. This is pretty common actually and even more so if you are speaking a completely different language (ie> Chinese). How do you go about notifying them of the "bug" then?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.