Limit the MAX_APDU length used for configuration in a global ETS parameterCompleted
Dear Madame and sir,
it seems as if there are various problems in the market with the support of extended frames and the available MAX_APDU length.
Sometimes values in the devices seem to be wrong and the detected maximum value for the configuration does not work.
Even a miscalculated value by one single octet, can break the configuration procedure.
To have a worst case scenario fall back possibility, I propose to add a ETS wide parameter (e.g. in the " Bus - Options" or in the "Settings - Troubleshooting") to limit the MAX_APDU length for the configuration procedures, as a top limiter of the detected maximum value.
With such a parameter, even a false self description in a device would give the user a possibility to configure the device. Today the user is lost, because the procedure just breaks.
Hello, there is already the option 'Use slowed bus communication' checkbox, in the project properties that limits that to 15. Isn't that sufficient?
Post is closed for comments.