Posted January 16, 20232 yr Hey Guys I have an Axpert VM iv that was running on 4 x 100ah gel batteries. I recently changed the gel battery's for 10.24kw Dyness Powerbox Pro. Since changing the battery I have had a random issue where the power to loads are cut for a few seconds and then restored, this has happened twice in the past two days, I managed to catch an error code F08 bus voltage too high. Could this be a firmware bug since the error clears itself? Any help would be appreciated
January 23, 20232 yr On 2023/01/17 at 5:09 AM, chipmunk008 said: I managed to catch an error code F08 bus voltage too high. It could be electrical leakage from the panels to earth. With the high voltage Solar Charge Controller models, this can somehow pump up the bus voltage. Do you notice that the problem is worst when or soon after it rains? You could try disconnecting your panels at night to see if that stops night time F08s. I've heard of some readers that automatically disconnect the panels at sundown, and reconnect again in the morning, to work around these issues. On 2023/01/17 at 5:09 AM, chipmunk008 said: Could this be a firmware bug since the error clears itself? Most likely not. But see this page re fault code 08 (some of it is a bit technical): https://forums.aeva.asn.au/viewtopic.php?p=53951#p53951
January 31, 20232 yr Author Hey Coulomb thanks for the reply. We got the error at night so no panels active at that point and the error does not maintain it is momentary then restores back to normal. What we did try was changing the priority setting to SBU this did solve the issue. We then got a firmware update from the supplier, version was 7204, and since the update we havent had the issue on both SUB or SBU. I will post if it does reoccur.
January 31, 20232 yr 6 hours ago, chipmunk008 said: We got the error at night so no panels active at that point... Fault code 08 from panels leaking to earth can and often does happen at night, it seems. But you to have hopefully solved the problem anyway. As a point of interest, was your main firmware 72.xx before the update? My notes say that 72.04 comes with Axpert Max 1 8kW for '28066 DSPs. It could be yet another firmware version numbering clash; the 72.xx series seem to have the most conflicts. Edited January 31, 20232 yr by Coulomb
February 16, 20232 yr I'll just add for the record that the new firmware version is actually 74.04, and it does seem to fix this fault. It may have been an uninitialised variable in a function that seems to soft start the solar charger.
February 16, 20232 yr Hi guys, i have a Kodak OGS5.6, brand new install, system only has inverter and 1 hubble am2 battery and no panels so far. Also have a problem that sounds like yours of it cutting power to loads for a few seconds and my automatic change over swapping over to eskom and then swapping back to inverter like 3 sec later. Im not sure where to get the error code, but this is the screenshot i took on the Watchpower App (not sure why it shows the error a couple of times as all the time stamps are the same)
February 16, 20232 yr @Steve87 i know you installed a fair amount of these Kodak's maybe you have encountered this problem before. Or maybe the techs at @SEGEN SOLAR will know?
February 16, 20232 yr Hi @Ravenshieldtry to record the fault code that comes up on the inverter. It start with F & has some numbers after. Eg. F72 or F51. By the way this is not normal operation at all & one needs to try to decipher what is the fault code.
February 17, 20232 yr 15 hours ago, Steve87 said: Hi @Ravenshieldtry to record the fault code that comes up on the inverter. It start with F & has some numbers after. Eg. F72 or F51. By the way this is not normal operation at all & one needs to try to decipher what is the fault code. Thanx for the reply, im new to this inverter, how can i record the fault code?
February 17, 20232 yr If possible, be near the inverter when it glitches like that, and check for Fnn (where nn is the two digit code) near the bottom of the display. You may have to press a button to wake up the display. I don't know why your app is recording code 0x00000001 all the time. But it sounds like it's F08, "bus voltage is too high". There is a known problem with leaky panels causing this problem, but obviously that can't be the case for you. What is your main firmware version number? It should be in the app somewhere.
February 17, 20232 yr 8 hours ago, Coulomb said: If possible, be near the inverter when it glitches like that, and check for Fnn (where nn is the two digit code) near the bottom of the display. You may have to press a button to wake up the display. I don't know why your app is recording code 0x00000001 all the time. But it sounds like it's F08, "bus voltage is too high". There is a known problem with leaky panels causing this problem, but obviously that can't be the case for you. What is your main firmware version number? It should be in the app somewhere. I managed to be at the inverter this afternoon when it happened and took a video of the event. Error code is indeed F08. And i am starting to see a pattern of when it occurred, it seems to me that i drain some of the battery during loadshedding off course, then when eskom comes back on and battery starts charging, and as soon as the battery hits full charge it happens! According to the app "Main CPU Firmware Version 00072.00 and Secondary CPU Firmware Version 00036.03"
February 22, 20232 yr On 2023/02/18 at 12:21 AM, Ravenshield said: I managed to be at the inverter this afternoon when it happened and took a video of the event. Error code is indeed F08. And i am starting to see a pattern of when it occurred, it seems to me that i drain some of the battery during loadshedding off course, then when eskom comes back on and battery starts charging, and as soon as the battery hits full charge it happens! According to the app "Main CPU Firmware Version 00072.00 and Secondary CPU Firmware Version 00036.03" I received advice from @Devanté to change the charge current to 20A. I have been using a 30A setting when getting the F08 error. I changed to LIB and 20A and so far no F08 error (2 charge cycles so far)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.