When connecting to a deployed Rapiscan system there is typically no router between the computer/laptop running OSH and the Rapiscan hardware. There is only a a few moments when the Hardware will accept the TCP Request. It seems like it is only when the hardware is producing data that it will accept the connect. We tested this by putting the RPM into an. occupied state where it generates messages every second (when it is not occupied it is only generating data every 5 seconds). I believe the solution would be to allow for the TCP module to retry the initial connection for a set period of time. It looks like this option is available via the TCP Config but it did not seem to change anything.
Use Case
Connecting directly to a Rapiscan System via ethernet only or through dummy switch.
Expected Behavior
TCP Comms should reattempt a connection for a set time period.
Current Behavior
TCP Comms does not seem to try any reattempt to connect to endpoint.
Bug/Feature Request
Description
When connecting to a deployed Rapiscan system there is typically no router between the computer/laptop running OSH and the Rapiscan hardware. There is only a a few moments when the Hardware will accept the TCP Request. It seems like it is only when the hardware is producing data that it will accept the connect. We tested this by putting the RPM into an. occupied state where it generates messages every second (when it is not occupied it is only generating data every 5 seconds). I believe the solution would be to allow for the TCP module to retry the initial connection for a set period of time. It looks like this option is available via the TCP Config but it did not seem to change anything.
Use Case
Connecting directly to a Rapiscan System via ethernet only or through dummy switch.
Expected Behavior
TCP Comms should reattempt a connection for a set time period.
Current Behavior
TCP Comms does not seem to try any reattempt to connect to endpoint.