Duke COM1 & COM2 doesn't transmit on VATSIM
-
Hi all.
The other day I wanted to fly a VFR cross country on VATSIM and despite pressing the PTT button, the TX cell didn't changed to blue in vPilot.
vPilot did recognise the frequency, but just didn't transimt, tried it with other buttons and keys set as PTT with no success. Also it worked with other planes, so I recon this is an issue with either the Duke aircrafts or the vPilot client.Does any of you experience(d) this phenomenon?
-
Have you tried enabling the "VATSIM 'Monitor All' When COM 1 & 2 Selected" option on the tablet? What you describe doesn't exactly fit the reason I created that option, but it might be related.
-
Hi Black Square.
I tried it with both options enabled and disabled regarding that EFB option.
Does the type code in vPilot matters? I mean choosing the incorrect one can result in limited communication between vPilot and the aircraft?
I was flying the Grand Duke and tried with both from the upper two (see pic for reference), the rest are turbine Dukes.
-
@GreenHat
Type code is only really for how you show up on the network. So BE60 for piston version B60T for turbine. The names in the dropdown is just to help you identify the right type code. Makes no difference in operation of plane and radio on Vatsim.Note, that you need to set the radio panel right in order to transmit on COM1, and with other planes working it sounds like the most likely problem. Could be that you are transmitting on COM2 fx. So have a closer look at the radio and Vpilot window. It shows you what COM1/2 are tuned to and your TX RX status.
Here is how Vpilot looks when pressing the PTT on 123.45 and monitoring guard on COM2
Hope it helps, and if it still causes you trouble, post a screenshot of Vpilot + your radio panel.
-
Dear Avionic, I just finished testing again, and for some reason it worked now on both COM1 and COM2. I didn't change anything in FS'20, on the Duke's EFB and neither in the vPilot App. I remember clrearly that it didn't matter what COM was selected TX didn't light up in blue on neither COM1 & COM2.
vPilot done this on my end a few times, usually afer a vPilot update, I start to think I might have to restart the computer after an update, because that is the only thing I have done differently between today's test and last weekend's. There were numerous shut down and turn on cycles.
Anyways, I am glad it is working for now. Now I know it is not an issue with the Duke. Thank you for your ideas and time and effort trying to help. Same goes to @Black-Square .
Wish you all the best and great health and happyness. Cheers.
