I mean in the saitek radiopanel, all is OK in the virtualcocpit. Only com1 don't appear in the saitek radiopanel : all the leds are off, if I put the buttom of the radiopanel on com1

Ok now I get it! You don't mean the A2A aircraft virtual cockpit, but the external 3rd party device.

Then I'm not sure what could be the problem. Our GNS V2 merely reads the sim variables to get the frequencies, or writes them when they change in the GNS V2. This is the only 'set' action taking place, all the rest is 'get'.

Either there is something in the Saitek driver (there must be some form of driver in-sim or via SimConnect) which is not found of having our GNS V2 running at the same time, or they are 'hacking' the internals of FltSim somehow and  this fails when our gauge is loaded, or anything else in between.

Can you please describe how this hardware communicates with FltSim? Is there a Windows Driver? Is there a SimConnect module? Does this rely on FSUIPC only?

I don't think the problem is with the driver because all is ok with other planes and default gps. I think there is a little   mess in my aircraft.cfg. I will try the gns430 in another plane and  I will let you know

Hi !
I reinstalled the plane and all is right now ! I should have started here 

 

Hi, please don't be embarrassed, this always give everyone pointers and ideas to help resolve similar problems.

I'm glad you've got all sorted out, as what matters most, is that you're now enjoying flying with us!

Thanks for all