When the command interpreter handles messages (from the commands registered against adapter methods) the message remains as a string instead of being cast to the type defined in the command.
This becomes an issue when using both a TCP and epics adapter on a single device. Numeric device parameters set via TCP are set as strings instead. When epics adapter tries to update the record with this new value, pythonSoftIOC hangs as it fails to convert string to numeric ctype. In this case string -> c_double.
When the command interpreter handles messages (from the commands registered against adapter methods) the message remains as a string instead of being cast to the type defined in the command.
This becomes an issue when using both a TCP and epics adapter on a single device. Numeric device parameters set via TCP are set as strings instead. When epics adapter tries to update the record with this new value, pythonSoftIOC hangs as it fails to convert string to numeric ctype. In this case string -> c_double.