Skip to content

Conversation

@gunicsba
Copy link

I noticed that the Müller Elektronik sprayer working widths weren't correct.

Now it has fallbacks according to: https://www.isobus.net/isobus/attachments/345/ISO11783-11-DDI-290-SetpointWorkState-v1.pdf

Each Section Device Element shall at least provide one type of Working Width. If
more than one type of Working Width is provided, then the Section Controller shall be
capable to use the different Working Width types with the following priority:

  1. Actual Working Width (DDI 67)
  2. Maximum Working Width (DDI 70)
  3. Default Working Width (DDI 68)

GwnDaan and others added 6 commits March 15, 2025 21:36
Also adds extra measurement commands logging and clarifies some documentation
According to: https://www.isobus.net/isobus/attachments/345/ISO11783-11-DDI-290-SetpointWorkState-v1.pdf

Each Section Device Element shall at least provide one type of Working Width. If
more than one type of Working Width is provided, then the Section Controller shall be
capable to use the different Working Width types with the following priority:
1. Actual Working Width (DDI 67)
2. Maximum Working Width (DDI 70)
3. Default Working Width (DDI 68)
Comment on lines +239 to +246
if (!retVal.width_mm.isValuePresent)
{
set_value_from_property(retVal.width_mm, property, DataDescriptionIndex::MaximumWorkingWidth);
}
if (!retVal.width_mm.isValuePresent)
{
set_value_from_property(retVal.width_mm, property, DataDescriptionIndex::DefaultWorkingWidth);
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem with this implementation is that it's dependent on the order. Example: when the DefaultWorkingWidth comes first in the iteration, that value is chosen

My suggestion: we save all 3 properties in the section variable, and then we have a member function of the Section class that chooses the correct one based on the priority given by the standard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants