mafiose13

Thank you Coulomb, flashed 2 units and running perfectly as far as I can tell. The other 2 units are a bit farther geographically from me, for now ill let them be as is since I am not getting any complaints from the users.

So 55.81 is unpatched, factory firmware!? I have 4 units at my direct disposal that could use a fix of the "stuck at 60".

So the 55.81 is the latest compatible U1 to VMIIIs 4kw (24v system), that replace the outdated 2 year old 455.06 (patched version of 55.06)?

Hello everyone, so I have decided to take on a challenging project to build an external power management system that can communicate with Voltronic inverters and manage external load, load shedding, schedules, etc...I appreciate your ideas, input. Problem/Scenario: - In my country we have 2 sources of grid power, let's call them G1 and G2 (G1 = goverment Grid, G2 = Neighbourhood Common generator), both have load shedding schedules covering about 16 hours of the 24hr day. - Most installs never utilize their PV production potential - Charging batteries on G2 is more expensive than G1, so charging needs to be prioritized, based on availability, time of day and battery charge status. - As far as load, besides general household loads, I would like to dedicate 2 loads to a special handling system, that uses excess PV power throughout the day and divert it to those 2 loads in priority (P1 = Water heater, P2 = Home heating). - PV System priorities would be to power current loads, charge batteries, use excess to power G1 until a certain temp is reached with the excess PV power, then taper that and introduce G2. Since I want this setup to be a universal solution to replicate with different models and later custom produce it for commercial use, it's best to assume the we will be talking to the inverter via it's communication port, and not tapping into any hardware modifications. I am thinking about creating a board with different microprocessors for the different tasks at hand and have it communicate with the inverter by command parameters then processing those parameters to various elements based on feedback received back to the inverter. Any implementation ideas? What would be a practical solution to always get the maximum PV output from inverter, externally? and this has to have a feedback to taper off and re-prioritize based on PV irradiance fluctuations (clouds, weather inclements and time of day).

No wonder why I can't get any internet connection from connecting to the inverter "LAN" 😆😆😆

On this particular installation, the LAN goes to a dedicated pc with Watchtower software always on for continuous monitoring from a nearby shed to inside the house about 20m length cable. The wifi watchpower or other wifi apps are not live data ....they typically update every few minutes, as opposed to pc version.

I wish i can, it's not an easy task i hear, unless there are some clear instructions/tutorials out there to walk me through it.

It's a non-twin.

Sorry for not reporting back to you on this, had a big installation over the past 2+ days. So about 3 days on this version, no errors, no warnings, no "never float" issue. To narrow things down, the current patch work on this version is not the culprit. Probably compatibility issue between the original code and whatever code is being inserted as premature float fix.

I just happen to have installed this 11k max E unit 3 days ago. U1 93.04 U2 144.01 Completely different stock firmware and numbers way off. Although, so far very stable other than the typical voltronic known bugs, which on this installation will not likely to be noticed. Unfortunately, i have no means to extract this firmware for the OP.

Patch 455.06 flashed...tomorrow by this time I'll have a definite answer as to whether it has isolated the "never float" issue at least. No worries....many thank for you zealous work and patience. Cheers

It's probably the case since it's patch-related somehow. Last night I had grid power overnight from 3-8am, so sunshine came in with battery already at 29.2V @ 4amps charge current, within 1 hr current dropped to 0amps, it stayed like this till sunset with occasional trickle charge to maintain bulk set voltage of 29.2v (over 8hrs). During the day i switched back n forth User to Fld and changed float from 26.5 to 27.2 a few times. Nothing triggered floating. The behavior seems to consider bulk voltage as float voltage. Out of fear of ruining the batteries I reflashed stock 55.06 again last night. Today, bulk/float works fine. While this is figured out, Can we meanwhile do a version without the "premature float" patch code, this way I can test and tell you if that code is the source of the problem or not. At least we know which path to take in finding the solution. Unless you have other ideas. PS: Edit: I don't know if this clue makes any difference. when flashing the patched firmware the unit behaves normally on that day. It's only when it starts a new solar charging cycle (ie next morning) that it goes into the never floating mode.

Hey @Coulomb I flashed 355.06 last night, no errors or warnings since then. I also did not notice any foul play with MPPT stuck at any odd voltage so far, I'll keep observing as some of these issues started 1.5-2 days into the previous patch flash. However, the "Never floating" issue & staying stuck all day till sunset at bulk voltage 29.2v (even when charging amps drip to zero) has returned with this patched version as well, it had disappeared on the upatched version when i reflashed it in the interim between patch buggy 255.06 and this 355.06 . Somehow it's related to the patching code, placement...no idea

24hrs after reflashing the unpatched 55.06. All is functioning normally. No errors, no warnings, Battery reaches bulk n returns to float at 27v. Obviously what was happening was post patching. Any chance this bug above was causing this haywire behavior or something else missed? Ill flash this later tonight, test it tomorrow and report back, unless you figure out some other root for this.

I volunteered this 1 unit for testing purposes and if that's what it takes...it is what it is. No worries 🙂👍...luckily as is it seems there was no permanent harm done, hopefully the next 24hr will tell. I'll keep a close eye. cheers