Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
    Cape Town, South Africa
  • Interests
    MTB, Diving, RF, Electronics, IT

Recent Profile Visitors

309 profile views
  1. I haven't been to this site in a while haha. My Must inverter burnt out/failed after a while and I replaced it with a Voltronic Axpert King unit. I think the Must unit failed due to me turning on a dodgy setting (setting 09 I think? It's "auto restart on overload" I think). I think the failure is related to the TVS diodes. I've still got the unit, need to get it repaired. Both the Must unit I had and the Axpert that replaced it have some oddities to them. The King offers a lot more control via it's comms system than the Must unit, so I have a NodeRed automation flow that manages the state
  2. I reconfigured the solar array from 3:2 (series:parallel) to 2:3. This brought the theoretical open circuit voltage from 130 VDC down to 86.8 VDC (Pmax of 105 V to 70 V). The inverter seems to target 62 V as the Pmax voltage. The inverter still continuously cuts out the array if the battery float voltage is set to anything lower than 57.2 V. There seems to be an improvement in power generation of around 33% - so that's nice (this could also be due to renewal of the connectors during array reconfiguration).
  3. Ah that is insightful. On that note, I thought you might find the bus voltage graph for today interesting (along with the PV output). The bus voltage seemingly dropped in sympathy with the PV output during the course of the day. There were no drop-outs; the gap in the afternoon data was due to me refining the bridge software. The inverter also indicated occasional "battery discharge current"... which is odd. I assume this is something to do with 57.2 V being above 57 V probably not great.
  4. I experimented a bit more today: it seems to start disconnecting/connecting the PV array when the float voltage is set to a value lower than 57.1 VDC. I'm guessing that it can't bring the voltage from the array close enough to the normal float voltage, so it just drops the array (in simplistic terms). I originally based the wiring of the panels on wanting reduced current and the Must Power clone unit, which indicated that up to 130 VDC was acceptable (the panels don't seem to get above 121 VDC open circuit) - whoops. I'm really not in the mood to rewire them haha . Thanks for the in
  5. It was a somewhat rushed purchase due to load shedding. I have a generator, but naturally it makes a noise (despite it being "silenced), so I don't run it at night/early morning. The generator output is also unstable. We had existing solar panels with *very* dodgy grid-tie inverters installed circa 2012 (DIY/self-install). These micro-inverters generated a ton of RF noise. The King is mostly great because it smooths out the generator output (in online mode), utilises the existing PV array and provides a load-shedding backup. It's definitely on my to-do list to upgrade both the batteries and pa
  6. Ah interesting! Is there any way of dumping the current firmware without opening the machine? (I don't want to break the warranty, like I did with the Must Power unit... long story, I was trying to clean it) I'm *mostly* not planning on adding fancy batteries currently (sticking with VRLA(?) mostly for backup). It mostly works, it seems, it just sometimes disconnects the array, waits a few seconds, reconnects and repeats continuously until the sun goes down. It generally doesn't seem to be as efficient with solar conversion as the dodgy MUST POWER unit I had - but the MP unit m
  7. Hi all Please help: can I install the "Beta Version of Patched Firmware 71.80d for PIP-5048MK/Axpert King 5K" on my machine (details below)? I've got a machine that says "Model: SOL-I-AX-5KP" on the side. It's branded Mecer. Solar charger is rated at Max 145 VDC, rated current 80A. As far as I can tell it is a genuine Axpert King 5 kW machine. I purchased it a few days ago to replace a dodgy CB Solar clone unit (Must Power PH1800). Current firmware versions (app): Main CPU: 71.90 Bluetooth: 0.24 SCC CPU1: 1.10 and firmware versions on display: V1: 7
  8. A STAR inverter? interesting, do you have a link so I can get a better look at it? Ah yes, that's Grafana, although it looks like you're missing data? I run Grafana separately and can graph any metric Home Assistant logs - so I dump everything into a database via HA and then pick through the data when I need to :). My inverter behaves very weirdly - I can't get it to stop charging the battery haha. It'll use solar to charge the battery at 10w and then dumps the rest of the power. The only way to get it to use the full solar output is to kill the Eskom supply. Sometimes it magically s
  9. Hey Luminous So I should have mentioned that the inverter's LCD display indicates two main states when it comes to the battery: power goes from the PV array either solely into the battery or both into the battery and the house power supply (downstream from the inverter, 230VAC). Sometimes it decides to both charge the battery and power the house, but sometimes it only charges the battery - this is unaffected by it having an oversupply of energy and the battery being flat or full. ^ On the left is how the LCD indicates power being delivered to both the battery and house. On th
  10. Hi all I'm new, so I apologise in advance if this post is wrong/misplaced/etc. I recently bought a CB Solar Synapse 4.0+ Inverter. It looked like an Axpert unit, but as I've since discovered it is actually made by a company called MUST POWER in China. My entire house is automated (self built system) and long story short I reverse engineered their Windows app to communicate with the inverter using a Raspberry Pi Zero - so I now have all the inverter status data in my Home Assistant system. I've put a JSON dump of the output I'm getting from the inverter at the bottom of this post if a
  • Create New...