MPPT 100|30 24V System Command

Modifications
, ,
1

Hi All,

We have 2 panels and the 100|30 charger, and can switch the system from 12V to 24V via the BT app. I have ~46V input.

We prefer to send the command via wired serial, and hope to implement a wider command set.

Per the BlueSolar-HEX-protocol, I send the command:

:8022001180012

But have no success. I am seeing the ASCII command updates being constantly transmitted, so know baud rate is correct.

Was wondering if anybody has had success implementing the serial protocol and could give a correct command sample?

Cheers,

Matthew

2

Constantly switching from 12 to 24 and back again with these units is probably not a good idea, as this will wear out the memory.

image
image732×595 87 KB

The register that you appear to be trying to write to is 0x2002 (LSB first) which is the battery sense voltage.

your command also seems to have too many digits in it., should be in the form:

: [command] [dataHighNibble, dataLowNibble][……] [checkHigh, checkLow] \n

e.g. msg_get_AbsV =str.encode( “:7F7ED006A”+chr(0x0a))

Where values are in a hexadecimal representation. What are you actually trying to command?

3

Hi Mike,

Thanks for the response.

Noted - I’ll be careful not to make too many requests if there is an NVM event that occurs each time.

We would like to charge our battery pack using the MPPT as a ~46V to ~24V DC-DC converter. The battery pack has it’s own input power switch and charger ICs.

My understanding is because our device does not present battery voltage at its charge input, the MPPT won’t automatically switch to 24V mode at start-up.

That’s why I would like to issue the ‘switch to 24V mode’ serially. Later, we would like to adjust the charge current on-the-fly with serial commands also.

Based on your input, perhaps there are NVM implications there also?

Best Regards,

Matthew

4

I found a solution. The data packet :8EFED000C65 sets the battery voltage to 12V. To set the battery voltage to 24V, use :8EFED001859.

5

Regardless of how the instruction is issued - either through VE Connect or via the ve-direct interface, it still affecte the same memory location. These EEPROM memories have a very limited number of erase / write cycles, so frequent changing of the data should be avoided. Parameters that are written into RAM can be changed much more frequently. The trick is knowing where the data is stored. If it’s non volatile, it is in EEPROM and should not be changed frequently.