Auto Reconnect - how does it work ?

[PGostek]

I have a USB serial port that can be physically disconnected and reconnected during the terminal session.

Can WhippyTerm reconnect to a temporarily missing emulated serial port automatically?

[TheBeef]

Hi PGostek,

The way auto reconnect works is that when a connection is detected as closed, WhippyTerm waits a set amount of time (user configurable) and then tries to reopen the connection. If it fails to open, it waits the time again and tries opening again. It keeps doing this until it opens, or the user closes the connection.

[PGostek]

Does it suppose to detect the removed port? i.e. when you unplug and plug the FTDI device.

[TheBeef]

WhippyTerm doesn't detect that the port was removed. This is what happens:

1. You plug in a USB serial port cable
2. Windows mounts this cable as COM5:
3. You open a new connection in WhippyTerm (COM5:)
4. WhippyTerm opens the COM5: device with a normal device handle
5. You remove the cable from the USB port
6. Windows unmounts COM5:
7. WhippyTerm gets an error from COM5:
8. WhippyTerm closes the device handle
9. WhippyTerm waits it's retry time
10. WhippyTerm tries to open COM5: again and gets an error
11. WhippyTerm waits it's retry time again, and goes back to step 10
12. You plug the USB cable back in
13. Windows mounts this cable as COM5:
14. WhippyTerm finishes it's wait time again
15. WhippyTerm tries to open COM5: again but this time gets a valid device handle
16. WhippyTerm shows the connection as open again and starts talking to that serial port.

This is of course when "Auto reconnect" (under the Connection menu) is turned on, if it's turned off then WhippyTerm gets an error from COM5: marks the connection as closed and is done.

This was a new feature in WhippyTerm 1.1, so it's not in version 1.0

Hope this helps