Acuario

I doubt with your 4050W array you will actually achieve 4000W. I usually allow for a 15-20% reduction in power from the panels stated power so I would imagine your arrays will produce less than the 8K.

Probably for a different discussion but... Have users of IOT devices ever really thought about the implications of what they are doing/connecting? I'm a true lover of IOT and think it is wonderful BUT I don't want control of my devices in the hands of some unknown company, no matter how much they say they are trusted. I have full control over ALL my devices as I write my own software to run them, always with both remote and local control of the device, and NEVER use any of the hosting companies. eWeLink claim to have 30,000,000 users in 172+ countries. Tuya (another similar platform) probably have as many or more, and there are other platforms as well. Most are Chinese companies. Every time you register a device your data is stored on their servers. Even if you use their device locally (some such as SonOff can be used this way), using their default firmware does not prevent your device being registered with the manufacturer. This bit of javascript is from a SonOff S26R2 IOT smart socket, from the HTML that is embedded in the device that you use to initially set up WiFi on the device: postReport: function(e, t) { return fetch("https://apia.coolkit.cn/report/ops_mode", { method: "POST", headers: { "Content-Type": "application/json" }, body: JSON.stringify({ deviceid: e, sign: t }) }).then(function(e) { return 200 != e.status ? Promise.reject("status error " + e.status) : e.json() }) a.postReport(e, t).then(function(e) { e.error || (i = !0, s.showDialog("Success", "WiFi configuration is completed.", !0)) This is part of the code that is run when you configure and connect the device to your WiFi. As you can see, your device is being registered on their server without your knowledge and as soon as it is connected to your WiFi, in fact if it can't register itself it causes an error. So combined these companies probably have control of several 10's if not 100's of millions of devices. This 'power' could easily be abused should their government wish. Imagine many millions of devices set to switch on/off at the same time - what sort of chaos would this cause on a countries power grid? And what happens should these companies go out of business (that has happened in some cases) - you end up with a pile of scrap if you can't re-program the device. ..and when they decide they want to charge for their currently 'free' service? ..worth considering

Then they should be ok as they are nearly new, it's unlikely you'll notice anything unless the old(er) batteries have been seriously abused.

Due to the problem with BMS comms between Axpert and Pylontech I ran a test on a Pylontech US2000C battery. I was concerned about over charging as the RS485 BMS reports the maximum charge current to the inverter and the inverter progressively reduces its maximum charge current setting automatically based on the values coming from the BMS. My concern was that setting USE for battery type, and then voltage, it would not be sufficient and that the batteries would continue to charge. The result was that as the battery approached 100% it automatically reduced the charge rate without any intervention. My conclusion was that the USE settings are fine and overcharging will not happen.

I understand this means means you are adding 2 new 12V batteries (to provide 24V) in series with 2 older 12V batteries (providing the original 24V) to get a 48V battery pack. How old are the original batteries that provided the 24V system? As with any lead acid battery it isn't recommended to add to the pack when the batteries are more than X months old - X is 6 months or a year depending on who you talk to.

Are they both the same style, i.e. low maintenance, gel, regular 'top up' batteries or sealed? Also why? Are you replacing an old dead battery and keeping an old working battery, or just 2 different makes but both new? It's not recommended to add new batteries to old batteries as the old battery will tend to drag the new battery down. If they are both new, both the same style and both the same Ah rating then you should be fine.

Yes correct. This is one of the common failures made when batteries are connected in parallel. The rating is per battery both charge and discharge so it needs to be multiplied by the number of batteries.

Depending on the version of firmware on the inverter it may or may not be able to communicate with the batteries using the BMS - it seems they introduced a bug so they don't communicate. For the charge current, in the booklet it will say the maximum recommended charge current. As you have 2 batteries this will be that value x 2. The BMS takes care of reducing the charge current when the batteries reach 100% To set the timer for setting output source priority check program 99 in the booklet for the inverter, here you can change the output source. Note however that if the inverter is connected to a grid supply it will still consume power from the grid, possibly up to 1.5kW. The only way to avoid this is to physically disconnect the grid supply.

This is what can happen when lightning strikes.. the molten mass at the bottom is the remains of a 3-phase professional lightning surge arrestor. Did it work? Well, nothing in the house got fried so you could say that yes, it did it's job.

If you plug it into your pc it won't see it as a new device as you are plugging into an existing com port, not adding a com port. You will need a bluetooth adaptor for the PC, this will show up as a new com port on the PC. The data speed that Watchpower uses is only 2400 baud so your old pc should be fine. With the adaptor plugged into the pc you can use something like termite to use the com port. If you install a serial bluetooth terminal on your phone then the pc and phone should be able to communicate across the bluetooth connection. If this works then when you get the bluetooth adaptor for the pc you can try the same from phone to pc. The female/female adaptor should be fine to connect the JINOU to the inverter.

If you search for BT-JINOU you'll get several hits. You can find out the pinout for the DB9 connector etc. If you link TX and RX on the adaptor it will work in loopback. You can then connect from the bluetooth on the pc (built in or dongle) - you need to pair the devices - usually the code to pair is 0000 or 1234 When they are paired use a terminal program such as Termite to see if you can get a response to the loopback - what you type should come back on the received data. If this works then connect tx/rx/gnd from the adaptor to the inverter and try to get a response from it - you can use the MAX protocol, you need to send a command with checksum - elsewhere on this forum that is described. You could skip this step and try Watchpower, changing the COM port to the Bluetooth com port. In theory it should all work.

The box he has is not running 2.71 but he is upgrading it to show the process. He says it is version 2.71 that has problems. The box he upgrades is running 2.61 and upgrades to 102.73 @CoulombI thought I read somewhere that versions 1XX were for a different processor than 0XX versions due to the chip shortage so were incompatible?

The King 5kW I have at the moment (it's a customers so will be gone soon) was bought in November last year. Firmware U1: 71.93 U2: 2.60 This works perfectly with the BMS cable on Pylontech setting - Brown/White -> 5, Brown ->3 (inverter end) I'm wondering if they have migrated the MAX II bug that stops it working with Pylontech to the version of firmware your inverter is running.

After running some tests today it seems the CAN data does not change the charge current limitation value when it approaches 100% SOC so it's not possible to use this as a way to regulate the charger on the inverter. It seems this is only available on the RS485 protocol. However, it seems the BMS automatically limits the charge when the battery approaches 100% - the readings from register 356 reduce down at the battery approaches 100% and finally drop and stay between 0A and 2.1A (no load on the inverter). This is good news as my concern was overcharging. I set the maximum voltage to 53.0V and it holds steady and charges to 100% at this voltage. The CAN data is useful as it can be used to set the charge limit of the inverter based on the BMS charge limit X number of batteries (both of which are on the CAN data). It also reports the real SOC, the inverter reports much lower as soon as the voltage drops from 53.0V

Additionally I've incorporated an RTC and SD card. I use the EEPROM to record hourly and daily statistics and the SD card to record solar and system performance that can be shown on a graph via the system web interface.