plane finder client on Win 11 - Failed to open serial port

BenderCigar

New Member
Hi, I am running the PlaneFinder client on Windows 11. I am using a serial connected receiver that can either speak BEAST or AVR protocols. My receiver uses an FTDI USB to serial interface and requires a baud rate of 3000000 and RTS/CTS handshaking. I can create a Putty profile and connect to my receiver and, in AVR mode, see what looks like sensible information being sent from the receiver. The problem that I am running into with the plane finder client is that it says in the logs that it can not open the serial port. I have verified that I do not have an active Putty session (or other software) running that has the port open. I tried enabling the plane finder client to run as administrator. I rebooted my machine, all to no avail.

I tried specifying the serial port as “COM4”. “COM4:” and “com4” but no luck. Device Manager does not show any other serial deice named “COM4” or any variant. I verified that when I unplug my receiver, the COM4 device in Device Manager goes away (and comes back when I replug it).

The only thing that I can think of is that plane finder client does not support 3000000 baud. Also, how do I configure the serial port to use RTS/CTS (hardware) handshaking?

Log File:
2023-06-19 06:33:43.423595 [-] Attemping to open serial port 'COM4'
2023-06-19 06:33:38.415939 [!] Failed to open serial port: COM4
2023-06-19 06:33:38.415792 [-] Attemping to open serial port 'COM4'
2023-06-19 06:33:33.404500 [!] Failed to open serial port: COM4
2023-06-19 06:33:33.404467 [-] Attemping to open serial port 'COM4'
2023-06-19 06:33:33.404362 [-] Client restarted successfully
2023-06-19 06:33:32.665345 [-] Restarting due to configuration change
2023-06-19 06:33:17.834049 [-] Received a restart request, restarting...
 

Attachments

  • plane finder client win 11.png
    plane finder client win 11.png
    574.8 KB · Views: 7
Not a bug, it has never been supported there.

99% of users use a Linux based OS.

Out of interest what receivers on Windows use a serial port and the AVR format?
 
I am evaluating different ADS-B receiver modules, and am currently working with the GNS – 5894TAC ADS-B Starterkit. The one reason I tried to get it working on Windows is because I happen to have a Dell rugged laptop that I take in the field with me and I have not yet partitioned the drive to dual-boot Windows and Ubuntu. My eventual deployment of an ADS-B module will be on a Raspberry Pi (likely a CM4) based system. So no serial support on Windows is not a blocker for me and this will be the impetus to get my drive partitioned :)

This particular module has a standard serial port on the module itself but the dev kit I linked above puts the module on a PCB with antenna connectors and an FTDI USB to serial converter chip. The module that I am evaluating is a GNS 5894TAC.
 
Yes, no matter what driver is installed serial is not supported on Windows. In fact as time goes on Windows is becoming harder and harder to support for us.
 
Yes, no matter what driver is installed serial is not supported on Windows. In fact as time goes on Windows is becoming harder and harder to support for us.
I installed Ubuntu on my laptop and my serial-connected receiver came right up (in AVR mode) with no issues. Now I don’t need to worry about Windows.
 
Back
Top