You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created my own Task Controller server instance for communicating with Gaspardo corn seeder ISOBUS controller unit for automatic section control. I am testing Gaspardo controller on my desk (disconnected from all real machinery: sections, vacuum and speed sensors) powered by my laboratory power supply and simply connected to my device with CAN lines.
In general it works well:
I can talk with Gaspardo ISOBUS Task Controller client,
I parse implement DDOP and can see supported DDIs,
I can finally even modify value for one of DDI: turning on SectionControlState (0x00A0),
But I am unable to actually control sections - I constantly read value 0xfffff000 from DDI ActualCondensedWorkState1_16 (0x00A) and setting SetpointCondensedWorkState1_16 (0x0122):
does not change anything (still value 0xfffff000 on ActualCondensedWorkState1_16).
My assumption is that maybe seeder controller detects that it is disconnected from physical machinery so it does not reacts on my tries of section controlling (which is kind of logical). If so then I assume it would broadcast some messages/errors via ISOBUS diagnostic protocol to the network informing it detects some hardware issues.
I have seen that AgIsoStack++ has support for diagnostic protocol but as far as I understand implementation (and available example) it covers a case that I can use it for transmitting/broadcasting diagnostic messages from my own node to the network.
My question: is it possible to read/fetch/parse diagnostic messages sent by foreign implement connected to the network? In my case I would like to print diagnostic from connected Gaspardo ISOBUS unit.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have created my own
Task Controller server
instance for communicating with Gaspardo corn seeder ISOBUS controller unit for automatic section control. I am testing Gaspardo controller on my desk (disconnected from all real machinery: sections, vacuum and speed sensors) powered by my laboratory power supply and simply connected to my device with CAN lines.In general it works well:
SectionControlState
(0x00A0),But I am unable to actually control sections - I constantly read value
0xfffff000
from DDIActualCondensedWorkState1_16
(0x00A) and settingSetpointCondensedWorkState1_16
(0x0122):does not change anything (still value
0xfffff000
onActualCondensedWorkState1_16
).My assumption is that maybe seeder controller detects that it is disconnected from physical machinery so it does not reacts on my tries of section controlling (which is kind of logical). If so then I assume it would broadcast some messages/errors via ISOBUS diagnostic protocol to the network informing it detects some hardware issues.
I have seen that AgIsoStack++ has support for diagnostic protocol but as far as I understand implementation (and available example) it covers a case that I can use it for transmitting/broadcasting diagnostic messages from my own node to the network.
My question: is it possible to read/fetch/parse diagnostic messages sent by foreign implement connected to the network? In my case I would like to print diagnostic from connected Gaspardo ISOBUS unit.
Beta Was this translation helpful? Give feedback.
All reactions