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.

Sign up for GitHub

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

Jump to bottom

Fix Heidelberg unhandled status logging #2234

Merged
merged 1 commit into from Jan 7, 2022
Merged

Fix Heidelberg unhandled status logging #2234

merged 1 commit into from Jan 7, 2022

Conversation

premultiply
Copy link
Member

No description provided.

@andig
Copy link
Member

andig commented Jan 7, 2022

Warum? Wenn hier was unerwartetes kommt würde ich gerne das Bitmuster verstehen, da hilft dezimal nicht.

@premultiply
Copy link
Member Author

premultiply commented Jan 7, 2022 •
edited

Weil es eben so im Protokoll steht und dies mit Integern und nicht mit Bitmustern arbeitet.
Das hat mich gerade schon viel Zeit gekostet zu erkennen dass das kein Datenfehler sondern ein definierter Zustand nach der Heidelberg-Protokollbeschreibung ist.

@premultiply
Copy link
Member Author

grafik

@andig andig merged commit a0ea097 into master Jan 7, 2022
@andig andig deleted the fix/heidelberg-status branch January 7, 2022 20:20
@premultiply premultiply mentioned this pull request Jan 7, 2022
Closed
dontbyte pushed a commit to dontbyte/evcc that referenced this pull request Aug 2, 2022
@premultiply @dontbyte
Heidelberg: log decimal status (evcc-io#2234)
df7eebc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@premultiply @andig