Hot mic issue on new CTAF vpilot update

Support Pilot Software
1

So I had a bit of a mishap departing from Denver earlier tonight, March 1st. Apparently I had a hot mic of the Denver CTAF 124.300. However, vpilot did not show that I was transmitting. The blue TX light in the top right corner was not illuminated. At the time, I was explaining things to my wife about departure procedures, as she was curious about it all.

I had several pilots and a controller message me about it who were upset about it and rightfully sow. However, I strongly believe that there is an issue withy vPilot after the latest update that implemented CTAFs.

2

It is unlikely (but not impossible) that the 3.8 update caused this issue given that the only thing this update has to do with CTAF is that it added the .ctaf command to look up the CTAF freq for an airport. That doesn’t impact actual transmitting at all.

That being said, I have no explanation for how you could be transmitting without the TX light illuminating on the vPilot window. Seems like it would have to be a bug in the AFV code library, but I’ve never seen that reported before. It’s something we’ll have to keep an eye out for, I guess.

3

William, could you send me your log file from around the time this happened?

4

Sorry for the late reply. Got busy with work. Where would one find the log file?

5

Type .showlogs in the vPilot command line and it will open your vPilot folder, where the logs are stored.

6

Ah I found it. I was looking in the wrong place lol

I believe this is the one. Ignore the multiple disconnect errors. Currently undergoing some wifi issues.

2024-03-01 18:26:11.395 -08:00 [INF] vPilot version 3.8.1 starting up
2024-03-01 18:26:11.430 -08:00 [INF] Running in “Standalone” mode
2024-03-01 18:26:20.025 -08:00 [INF] Downloaded 1 servers
2024-03-01 18:28:16.840 -08:00 [INF] Validating “Msfs”
2024-03-01 18:28:27.056 -08:00 [INF] Aircraft config paths hash is different
2024-03-01 18:28:57.319 -08:00 [INF] “FbwVpilotActive” value changed: false
2024-03-01 18:28:57.326 -08:00 [INF] Custom model matching rules loaded.
2024-03-01 18:28:57.830 -08:00 [INF] Model matching rules generated.
2024-03-01 18:29:20.300 -08:00 [INF] Connecting to network
2024-03-01 18:29:20.328 -08:00 [INF] Connected to network
2024-03-01 19:14:13.547 -08:00 [ERR] Network error: EndReceive failed: (10060) A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2024-03-01 19:14:13.566 -08:00 [ERR] Disconnected from network
2024-03-01 19:14:26.282 -08:00 [INF] Connecting to network
2024-03-01 19:14:26.313 -08:00 [INF] Connected to network
2024-03-01 20:20:59.351 -08:00 [ERR] Network error: EndReceive failed: (10060) A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2024-03-01 20:20:59.351 -08:00 [ERR] Disconnected from network
2024-03-01 20:29:02.119 -08:00 [INF] Connecting to network
2024-03-01 20:29:02.156 -08:00 [INF] Connected to network
2024-03-01 20:43:42.663 -08:00 [ERR] Network error: EndReceive failed: (10060) A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2024-03-01 20:43:42.664 -08:00 [ERR] Disconnected from network
2024-03-01 20:44:03.499 -08:00 [INF] Connecting to network
2024-03-01 20:44:03.525 -08:00 [INF] Connected to network
2024-03-01 22:17:49.370 -08:00 [ERR] Network error: EndReceive failed: (10060) A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2024-03-01 22:17:49.370 -08:00 [ERR] Disconnected from network
2024-03-01 22:18:42.001 -08:00 [INF] Connecting to network
2024-03-01 22:18:42.031 -08:00 [INF] Connected to network
2024-03-01 22:26:40.694 -08:00 [INF] Disconnected from network

7

I don’t see any PTT on/off messages in the log, which makes sense given that you said the TX light was not lit. I’m not sure what might have happened. Are you still having this hot mic issue consistently?

8

I’ve only flown through one other CTAF since then, but will monitor to see if it happens again.

9

It wouldn’t have anything to do with CTAF … the voice system (both on the client and on the server) doesn’t “know” that you are on a CTAF versus a regular ATC freq.