Repository navigation
Conversation
Signed-off-by: Segran <goran@andersson-stehag.se>
Signed-off-by: Segran <goran@andersson-stehag.se>
Signed-off-by: Segran <goran@andersson-stehag.se>
segran2
force-pushed
the
fix/pixii-calibration-service
branch
from
November 15, 2026 00:41
ef41395 to
a5ded98
Compare
miravoss26
reviewed
Nov 16, 2026
miravoss26
left a comment
There was a problem hiding this comment.
Pixii 2.1.10: reads StVnd (40108) and treats code 116 as calibration, so dispatch is suspended when SunSpec ChaSt is unsupported. Version, index, manifest and sha256 are bumped consistently, and the new test covers 116, 0xffff (keeps the last verdict) and 119 (clears).
- Needs a human decision: this adds
host.set_calibratingtospec/host-api-profile.json. Older Core falls back toset_device_fault, which is fine. But is the Core side that implementsset_calibratingmerged or planned? If not, the new API is spec-only for now. - Nit: the 101-129 range for
service_knownis from the Pixii mapping (table 23). A one-line link in the comment would help whoever extends it. - No secrets, no new hosts or dependencies.
Logic looks right to me. Safe to merge from my read once the Core question is answered.
Contributor
Author
|
Thanks, Mira. I haven’t confirmed whether |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On a Pixii undergoing scheduled SoC calibration, a read of SunSpec 802 register 40137 (
ChaSt) returned0xffffwhile Pixii register 40108 (StVnd) returned 116, the documented battery calibration service. FTW kept requesting idle and the battery continued charging under its local calibration.Recognize either calibration signal and keep battery and meter telemetry live. Use the Core calibration state when the host provides it. Older hosts continue to suspend control through the existing fault gate.
On the affected Pixii, the local driver derived from this change reported service 116 and stopped dispatching power commands once calibration was detected. The Pi journal shows no Pixii power setpoints between calibration detection at 01:24:41 and the status transition at 03:00:11 CET on 15 November 2026. The same FTW process resumed dispatch automatically and issued a 463 W Modbus charge setpoint at 03:00:12, then 0 W at 03:00:17. A later live read confirmed calibration was cleared and battery telemetry remained fresh.
Companion Core change: srcfl/ftw#2017.