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
Currently using version 3.8.0, same behavior for version ~3.9
The delitem func ensures the slave parameter is between 0xF7 and 0 before deleting the key/node. While I am able to have a slave at an address higher with proper functionality, deleting is not working due to that code throwing an exception.
could this be configurable? This is technically supposed to be outside of the boundaries but these are also considered "reserved" and therefore usable. Thanks
The text was updated successfully, but these errors were encountered:
however I am not sure why you would first add a device and then later delete it. If you delete a device in a running in a running server you will sooner or later have a server breakdown.
Currently using version 3.8.0, same behavior for version ~3.9
The delitem func ensures the slave parameter is between 0xF7 and 0 before deleting the key/node. While I am able to have a slave at an address higher with proper functionality, deleting is not working due to that code throwing an exception.
Line of interest:
pymodbus/pymodbus/datastore/context.py
Line 203 in 28eb319
could this be configurable? This is technically supposed to be outside of the boundaries but these are also considered "reserved" and therefore usable. Thanks
The text was updated successfully, but these errors were encountered: