Kverneland Tellus can't load VT

[gunicsba]

[gunicsba]

Need to check if the default values are correct?

define ConfigHydliftAuxN 10001

Boolean default value is out of range.

Need to check if this is something we could put in the build step:

isobus::IOPFileInterface::read_iop_file() loads a raw .iop blob from disk — no CAN bus needed.
Every VT object class (DataMask, InputString, Macro, WorkingSet, etc., all in isobus_virtual_terminal_objects.hpp/.cpp) implements a get_is_valid()-style method that does exactly the "basic error checking on the object" your Kverneland bug hits — attribute range checks, object ID references, etc.

Ideally we should have a validator in the stack that would be able to flag these errors and halt the build if the iop wouldn't load on devices.

[gunicsba]

The affected objects are:

Object ID Name Value Should be

10001 ConfigHydliftAuxN 24 0 or 1

10002 ConfigNmeaRead 24 0 or 1

10003 ConfigNmeaSend 24 0 or 1

10004 ConfigTecuEnabled 24 0 or 1

The value 24 (0x18) is almost certainly a font size code that was accidentally placed in the value field — font size 24pt is a common ISO 11783-6 font attribute value. This looks like a copy-paste or tool error in the IOP generator where the font attributes bled into the boolean value field.

The rest of the IOP I can audit appears correct:

The InputList at id=10000 (ConfigHydliftAuxN input list) has value=0, n_list=2 — valid.

The enabled fields are correct (0 for inputs that should start disabled, 1 for those that should start enabled).

The fg_colour_obj=23001 (a FontAttributes object) and var_ref=65535 (no variable reference) look intentional and correct.

All four need their value byte corrected — 10001 and 10002 to 0 (disabled by default), and 10003 and 10004 to 1 (enabled by default), based on their current enabled field pattern

[gunicsba]

Possible fix in #68

Windows Installer (10).zip

[sujandumaru]

Hopefully the new iop file will fix this bug and we can close it.

[gunicsba]

Works on the Kverneland Tellus