comms issue

[PerWel]

3 minutes ago, Dave-Pilot2ATC said:

Glad you were able to get the Coms working.

The current Navigraph data for P2A has only 25kHz spacing, so 132.13 is not a valid frequency and is changed to 132.125.  You need to get frequencies from the Frequency window, not the charts.

Once Navigraph provides the new data, it will hopefully include the correct frequencies and P2A will be able to support the 8.33kHz spaced frequencies after some testing.

Dave

OK I understand but then the only way to listen to in this case ATIS is to set it in aircraft myself.

This explains whole thing.

OK Thanks again 👍

[Dave-Pilot2ATC]

Or if you set P2A to provide ATIS, then you can use 132.125 and get ATIS from P2A.

This way you'll be getting the weather that P2ATC is using to make decisions about runways, etc.

Dave

Edited December 25, 2024 by Dave-Pilot2ATC

[PerWel]

1 hour ago, Dave-Pilot2ATC said:

Or if you set P2A to provide ATIS, then you can use 132.125 and get ATIS from P2A.

This way you'll be getting the weather that P2ATC is using to make decisions about runways, etc.

Dave

OK I'll try that👍

[Wim Dreves]

Hi Dave, the Laminar 737 works fine no problem it is the Zibo mod that causes this comms issue. 

I think it will be a problem to get P2ATC going again. 

Thank you for your assistance , regards Wim

 

 

[PerWel]

7 hours ago, Wim Dreves said:

Hi Dave, the Laminar 737 works fine no problem it is the Zibo mod that causes this comms issue. 

I think it will be a problem to get P2ATC going again. 

Thank you for your assistance , regards Wim

 

 

Just tested P2A Version 2 and it connected to Zibo 738 with no problem at all. XP ATIS was on after connection.

[Rektor TV]

hello there Dave happy holiday to you

just want to report this same bug i have too, the comm wont available for LevelUp NG families. i tried with other aircraft and its working tho, its just the LevelUp NG having this issue

[PerWel]

3 hours ago, Rektor TV said:

hello there Dave happy holiday to you

just want to report this same bug i have too, the comm wont available for LevelUp NG families. i tried with other aircraft and its working tho, its just the LevelUp NG having this issue

Same problem as with Zibos 738. Zibos is involved with the LevelUp families, I just got them too.

They do work with the P2A 27N version, not fun to say but if you must have P2A with LevelUp it is the only version that works for me anyway.
I do trust that Dave will fix it in 28 or 29

[Dave-Pilot2ATC]

I'm working on this for version 29.  

Dave

[Wim Dreves]

I installed the "old" P2ATC again, the latest 28 update does not work with the zibo comms, I do not understand this, the older version was perfect.

 

 

[Dave-Pilot2ATC]

This is a known issue that should be fixed in 0029.

Dave

[Bob Scott]

I'm trying to get the FF757 in XP12 to work with P2ATC 29C, and seeing the same show-stopping comm problems that were supposed to have been fixed in 29.  Once I fiddle with the audio panel and (sometimes) manage to get the primary COM1 channel to take the ATIS freq, there's no audio.  If I can get to Clearance Delivery, I can make a call and hear it speak, but there's no response, either text or audio.  I can test the voices and that works, so it's not a driver issue.  If I close 3.0.0.0_029C and swap in 2.7.0.2 with everything else remaining the same, it works.

I upgraded to 3.0 with the intent of having an updated ATC program that works in both MSFS and XP12...so far with XP12, it's been a complete and frustrating failure.

Also, the docs contain a link to XPUIPC version 2.0.3.8, and reference a text file that no longer exists for networked setup.  The current readme file in the XPUIPC zip describes setting up the XPWideclient program that comes integrated with the very old XPUIPC version, which absolutely does not work with XP12--it causes a repeatable CTD when connecting from the client PC.  There's an alternative pair of programs written by a good samaritan unknown to me called FSWideServer and FSWideClient--that allows XP12 to communicate with P2ATC over the LAN in conjunction with XPUIPC to avoid the crashes.  Docs for a new P2ATC version should not be describing networked setup using an 11-year-old utility that crashes the current XPlane version.

 

[Dave-Pilot2ATC]

The newer versions of XPUIPC have not been working and it's good to hear there is a newer version out there that does work.  Version 2.0.3.8 has be very reliable for running P2A on the same PC as XPUIPC, but you are correct, it doesn't handle the case where P2A is on a separate machine.

Do you have a link to the site where you obtained the working updated version?  I would like to update the documentation to point to that.

As for the Comms Issue, the trick is to turn off both Vol buttons (the round ones just below the square Mic buttons) before you connect P2A.  Make sure that P2A has COM1 and COM2 showing in the Comms panel and not just COM and COM.

Then the Mic buttons will switch you from COM1 to COM2 as the active channel.  If you want to monitor the inactive channel, press the volume button for that channel.  If you then want to swap active channels, be sure to turn off the Vol button on the monitored button first.

Dave 

[watin]

Hi @Dave

I think I have the same problem with comms on MSFS with Fenix. Not each time but often.

sometimes no number after com but most of the time able to change standby on COM1 but when swapping to active it’s a mess :

COM 1 active Grnd stdby Del 

swapping Del appears on active then :

acticve Grnd stdby Grnd

The main clue it will not work is that active is not set to ATIS on the departure at LFPG for example.

maybe I start P2A, connect and file in the wrong way but I think I use the same pattern each time.

Anyway, I’m flying all P2A versions  for a while so many thanks for your job !

 

 

 

 

[watin]

7 hours ago, watin said:

Hi @Dave

I think I have the same problem with comms on MSFS with Fenix. Not each time but often.

sometimes no number after com but most of the time able to change standby on COM1 but when swapping to active it’s a mess :

COM 1 active Grnd stdby Del 

swapping Del appears on active then :

acticve Grnd stdby Grnd

The main clue it will not work is that active is not set to ATIS on the departure at LFPG for example.

maybe I start P2A, connect and file in the wrong way but I think I use the same pattern each time.

Anyway, I’m flying all P2A versions  for a while so many thanks for your job !

 

 

 

 

My mistake, I was typing @Dave-Pilot2ATC 😁

[watin]

Well, I solved my issue.

reminder : when I connected from P2ATC v3 (or v2) no ATIS available, ground frequency selected and when attempting to swap from stdby Clearance delivery, after 1 second, active freq come back to ground. So I have ground on active and stdby and unable to change it.

solution : for some reasons I have to run MSFS and add-ons as admin. BUT my navaids DB was updated in à non-admin run. Updating while as admin solved my issue.