Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Axpert_KSMKSV_RS232_Protocol #131

Open
SeByDocKy opened this issue Jun 1, 2024 · 8 comments
Open

Axpert_KSMKSV_RS232_Protocol #131

SeByDocKy opened this issue Jun 1, 2024 · 8 comments

Comments

@SeByDocKy
Copy link
Collaborator

SeByDocKy commented Jun 1, 2024

Hi @syssi,

Not sure if it was already implemented but seems there is a new variant of the protocol :
Axpert_KSMKSV_RS232_Protocol-C20170821.pdf

Can you confirm if it's a new protocol ?

@jopl
Copy link

jopl commented Jun 29, 2024

Dear SeByDocKy,
I can confirm it fits more to my AXPERT MAX 11KW TWIN, at least in QPIRI and QPIGS inquiry commands. And it is very similar to protocol described in attached Communication_Protocol_20150924_Customer.pdf. But "yours" is more corresponding ...
Communication_Protocol_20150924_Customer.pdf

@SeByDocKy
Copy link
Collaborator Author

I don't own myself this inverter but when I will get a bit of time, I will make a PR for this inverter. Modifications from existing are small in a first glance.

@jopl
Copy link

jopl commented Jun 29, 2024

SeByDocKy - thanks so much.
In the meanwhile, I found out addition (uncommenting) of

external_components:
  - source: github://syssi/esphome-pipsolar@2424mse1
    refresh: 0s

plus addition of "select" entity from example of @2424mse1 to my yaml, i.e.:

select:
  - platform: pipsolar
    pipsolar_id: ${inv_id}
    output_source_priority:
      id: ${inv_id}_output_source_priority_select
      name: ${inv_id}_output_source_priority_select
      optionsmap:
        "Utility first": "POP00"
        "Solar only": "POP01"
        "Solar Battery Utility": "POP02"
      statusmap:
        "0": "Utility first"
        "1": "Solar only"
        "2": "Solar Battery Utility"

  - platform: pipsolar
    pipsolar_id: ${inv_id}
    charging_discharging_control:
      # See MAX_Communication_Protocol_20200526.pdf page 18
      name: "${devicename} charging discharging control"
      optionsmap:
        "111": "PBATCD111"
        "011": "PBATCD011"
        "101": "PBATCD101"
        "110": "PBATCD110"
        "010": "PBATCD010"
        "100": "PBATCD100"
        "001": "PBATCD001"
        "000": "PBATCD000"
      statusmap:
        "111": "111"
        "011": "011"
        "101": "101"
        "110": "110"
        "010": "010"
        "100": "100"
        "001": "001"
        "000": "000"

helped me and now I am able to read data without CRC NOK :-).
${inv_id} & ${devicename} should be appropriately defined (in substitutions:).
Regards, Josef.

@SeByDocKy
Copy link
Collaborator Author

Do you mean the branch 2424mse1 is the right one for your inverter ?

@jopl
Copy link

jopl commented Jul 2, 2024

Finally, "- source: github://syssi/esphome-pipsolar@pip8048" showed the best results. It supports 2 FV sections.
Regards, Josef.

@duymelody9x
Copy link

Finally, "- source: github://syssi/esphome-pipsolar@pip8048" showed the best results. It supports 2 FV sections. Regards, Josef.

hi can you show me your yaml file i am also having problem with add select

@syssi
Copy link
Owner

syssi commented Jul 26, 2024

@duymelody9x Do you want to use an ESP32 or ESP8266?

@syssi
Copy link
Owner

syssi commented Jul 26, 2024

These are the YAMLs you are looking for:

https://github.com/syssi/esphome-pipsolar/blob/pip8048/esp8266-example.yaml
https://github.com/syssi/esphome-pipsolar/blob/pip8048/esp32-example.yaml

If the build fails please try a clean build: esphome clean esp8266-example.yaml. If you use the ESPHome Dashboard there is a CLEAN build button:

Clean build files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants