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

[Request] VE.Direct MPPT: Process "RELAY" and "FWE" messages #1037

Closed
schlimmchen opened this issue Jun 7, 2024 · 7 comments · Fixed by #1376
Closed

[Request] VE.Direct MPPT: Process "RELAY" and "FWE" messages #1037

schlimmchen opened this issue Jun 7, 2024 · 7 comments · Fixed by #1376
Labels
enhancement New feature or request

Comments

@schlimmchen
Copy link
Member

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

Process this info received over VE.Direct from a charge controller with relay output:

22:21:22.976 > [VE.Direct MPPT 10/9] Unknown text data 'RELAY' (value 'OFF')

Describe alternatives you've considered

No response

Additional context

No response

@schlimmchen schlimmchen added the enhancement New feature or request label Jun 7, 2024
@ingrimsch
Copy link

My MPPT 250/85 sends an additional "FWE" message, that is also not processed yet.
Example: [VE.Direct MPPT 34/-1] Unknown text data 'FWE' (value '315FF')

According to Victrons Protocol description this is the Firmware Version as 24Bit Value.

Citing https://www.victronenergy.com/upload/documents/VE.Direct-Protocol-3.33.pdf:
"The firmware version of the device. The version contains up to 6 digits, 0 padding on the left side is
not mandatory. Examples: 0208FF or 208FF for firmware version 2.08 (last digit FF indicates an
official release), 020801 for firmware version 2.08-beta-01."

@schlimmchen schlimmchen changed the title [Request] VE.Direct MPPT: Process "RELAY" message [Request] VE.Direct MPPT: Process "RELAY" and "FWE" messages Oct 31, 2024
@SW-Niko
Copy link

SW-Niko commented Nov 4, 2024

Hello @ingrimsch ,
I have a question regarding the "FWE" message.
According the documentation (VE.Direct-Protocol-3.33.pdf) from Victron: "FWE" is for "Phoenix Charger" and "Smart BuckBoost" only.

grafik

Can you verify again?

@SW-Niko
Copy link

SW-Niko commented Nov 4, 2024

Hello @schlimmchen ,
regarding the "RELAY" message. I can implement the missing functions, (web view, MTTQ and HASS) in the same way like the "IR" / "LOAD" messages, if you like.

grafik

@schlimmchen
Copy link
Member Author

schlimmchen commented Nov 6, 2024

Yes, please, that is highly appreciated.

@ingrimsch
Copy link

ingrimsch commented Nov 18, 2024

Hello @ingrimsch , I have a question regarding the "FWE" message. According the documentation (VE.Direct-Protocol-3.33.pdf) from Victron: "FWE" is for "Phoenix Charger" and "Smart BuckBoost" only.

Can you verify again?

Hi @SW-Niko,

sorry for my late response. Yes, I can confirm the FWE message represents the current FW version for my Victron MPPT 250|85 (identified as "SmartSolar MPPT VE.Can 250|85 rev2"). Firmware version is currently shown as "Firmware-Version: ." on the Live-View page.

This is the message I see in the "Konsole" log:
11:14:04.324 > [VE.Direct MPPT 34/-1] Unknown text data 'FWE' (value '315FF')

@SW-Niko
Copy link

SW-Niko commented Nov 18, 2024

Thanks @ingrimsch,
it seems the Victron documentation is outdated or wrong.

Firmware version is currently shown as "Firmware-Version: ."

On your device Victron do not send "FW" Data. Now I understand why you want to process FWE.
How do you connect the CAN? Converter to UART?

@schlimmchen
How about to process FW and FWE. If FW is not available we use FWE and ignore the 2 last characters.

(value '315FF')

Means firmware 3.15

Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants