Roborun+ not detecting/skipping virtual COM port on Wifi RS232 interface.

Can Roborun+ software force or specify port to open on start-up instead of scanning through all the ports real fast?
eg: \"roboteq.exe -com5\"

I\'m using a wireless RS232 port Airolinx STW-601C, and Roborun+ seems to skip its port, unless I log into the web/telnet interface of the STW-601C under serial port options and do a save settings, without changing anything, just to refresh then Roborun+ app suddenly finds the serial port and it works fine after that until I unplug the controller again. It seems like a timing issue of some sort in port detection.

I need to have the software knock at the port a little longer or force the port. Other software seem to work fine with the wifi rs232 virtual/tunelled port and connects fine to the controller. If the SDC2130 is left sending data, Roborun+ detects the port fine unless we power off and on, then it needs that bump/refresh again.

Using the STW-601C with the Tactial Software Serial/IP \"vcomm394\"

Can this be updated in software?

I seem to have a similar problem with my Snap Link rs232 wireless radios.
Also in my case the ports are detected but not seen as open because, probably because of the delay in the return character from the controller.

I really hope the software engineers can make this more flexible in Roborun+. There are many applications where we must have the possibility to communicate via a wireless link.

So urgent request: Please allow for adjustable connectivity, ping-time(out), possibly lower data baud rate?

Thanks,
Rob

We are looking at adding the option to manually force a com port number. It is probably doable but it will take a bit of effort and time.