Repository navigation
Conversation
Until now an implement stayed in manual mode after connecting until the operator pressed AOG's ISOBUS SC button, which sends PGN 241. The TC now remembers the section control state it wants and applies it to each client 2 s after its pool is activated: it sets the local auto flag and writes DDI 160 when the implement declares it. The initial state comes from the new settings.json key "sectionControlOnConnect" (default true). Pressing AOG's button still switches all clients and also becomes the state for implements that connect later. The implement can still decline or go back to manual; its DDI 160 report is followed as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 12, 2026
New sectionControlOnFieldOpen setting (default on): when AOG opens a field, the TC switches section control on as if AOG's SC button was pressed (the same update_section_control_enabled(true) that PGN 241 "enabled" triggers). AOG sends the field name (PGN 0xF3) on every field open and close, and again when the TC reconnects. Older AOG versions do not, so PGN 229 starting after a 2 s gap (AOG sends it only while a field is open) counts as a field opening too. Both report the same opening, so it is acted on at most once per 5 s. Field open and close are logged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
Closes #94.
An implement used to stay in manual mode after connecting until someone pressed AOG's ISOBUS SC button. With this change the TC switches section control on by itself.
settings.jsonkey,sectionControlOnConnect, which defaults totrue.ClientState, so this also covers implements that connect after startup, reconnects and pool re-uploads.AOG only sends PGN 241 when the button is pressed, and the button shows the state from the TC heartbeat. That means AOG doesn't override the default, and its button shows ON once the implement is switched on.
Switching on when AOG opens a field
A second setting,
sectionControlOnFieldOpen(defaulttrue), does the same thing when AOG opens a field: the TC calls the same code as PGN 241 "enabled", as if the SC button had been pressed.[Field] AOG opened field '...'and[Field] AOG closed the field.Background: in a field log from 2026-10-13, after field changes a spreader in automatic spread full width without receiving setpoints (see #106). This option makes a field change restart automatic section control in the TC without anyone pressing the button.
Notes
"sectionControlOnConnect": falseor"sectionControlOnFieldOpen": falseinsettings.json. Both are listed in the readme. There is no VT Config toggle yet.Testing
[TC] Applying initial section control state: enabledabout 2 s after the pool is activated, the implement reports DDI 160 = 1, and AOG's button shows ON.🤖 Generated with Claude Code