Task controller server

ad3154 commented 5 months ago

This is an abstract interface for an ISO11783-10 version 4 task controller or data logger server. This portion of a TC server handles communication with the implement, receives the DDOP, and provides hooks into your application so that you can command the implements' sections, change triggers, set values, and generally manage each implement.

Features

Automatic DDOP upload/handshaking with clients
Settable measurement commands and triggers for getting data back from the implement
Value commands and acknowledgements
Integrates well with our DeviceDescriptorObjectPool class for parsing received DDOPs.
Has a minimum example to help

Todo/things to consider

I made this PR a draft while I consider or improve the following:

[x] Improve unit test coverage
[x] Consider abstraction/helper for gathering geometry data from an implement as mentioned in #350 Edit: see #427
[x] Consider abstraction/helper for "products" and rate control in general as mentioned in #350 Edit: see #427
[x] ~~Similar to how we have an ISOXML serializer, add an ISOXML reader/deserializer~~ Edit: It would not be too bad to only parse out DDOP information, but to accurately do this would require > 50 classes! So I think we can put that in a different PR.
[x] Documentation? ~~Consider additions to the sphinx docs.~~ Edit: Added sphinx docs

Screenshot

GwnDaan commented 5 months ago

I did some testing with the current interface - I know it's still draft - it's working exceptionally well from the start, just a few lines of code on top of the boilerplate and I had section control over ISOBUS working! Here's a simple demonstration using AOG as the guidance system providing the section states:

https://github.com/Open-Agriculture/AgIsoStack-plus-plus/assets/29043784/95a5b102-8b5d-4041-8acf-4957b765447e

Great stuff @ad3154!