| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
new option in frame.py -> ReceiveFrame Class -> consume Class and consume function is backward compatible. Only if new parameter "strict_start_check" is set to True, the start of frame search will be stricter as before and expect a '00' preamble before the start-token. This helps to avoid the "invalid command" errors seen with newer inverter software versions.
|
A small note from reading the current diff: the property setter assigns self._strict_start_smatch = newval (extra s), while the constructor and consume() use self._strict_start_match — so enabling the option via the property setter silently does nothing; only the constructor argument takes effect. From our field testing on a Power Storage 6.0, a boundary-tolerant variant (accepting + directly at the resync boundary) additionally avoided losing valid frames that immediately follow discarded garbage. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
new option in frame.py -> ReceiveFrame Class -> consume
Class and consume function is backward compatible. Only if new parameter "strict_start_check" is set to True, the start of frame search will be stricter as before and expect a '00' preamble before the start-token. This helps to avoid the "invalid command" errors seen with newer inverter software versions.