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
Modbus polling rate is taken for the subscription interval whereas it is the maximum polling rate in the modbus binding. Even though this is a false understanding, I do not know how to fix it in the best possible way. Some thoughts:
The polling rate can be given as an interaction option. node-wot can check whether it is lower than the max rate. Is this clear from scripting api perspective?
The polling rate can be set in the config. Even though this would work, it would limit it to same number to all affordances and this may go against the binding template spec.
The text was updated successfully, but these errors were encountered:
Modbus polling rate is taken for the subscription interval whereas it is the maximum polling rate in the modbus binding. Even though this is a false understanding, I do not know how to fix it in the best possible way. Some thoughts:
The text was updated successfully, but these errors were encountered: