Results 11 to 20 of 44
-
06-06-2011, 01:55 AM #11
- Join Date
- Feb 2005
- Location
- Hamburg / Germany
- Posts
- 174
Re: FSX and XPNDR737 issues... need help guys !!!
Hi there! I think it has nothing to do with PM. Maybe I am wrong, but we had the same problem with the FDS Hardware and this was solved by an driver update.
As the CP Flight modules also work without PM it must be a CP Fligth issue. Try to ask in the CP Flight Forum.
Regards
JanVisit my project on Facebook and become a fan www.facebook.de/homecockpit
-
06-06-2011, 02:02 AM #12
Re: FSX and XPNDR737 issues... need help guys !!!
Why not send a second e-mail to CPflight then ?
Thanks
Nick
-
06-06-2011, 04:25 AM #13
Re: FSX and XPNDR737 issues... need help guys !!!
I'm not sure it's a PM issue either. And didn't you have tyhis problem with FS9? I do.
-
06-06-2011, 04:49 AM #14
Re: FSX and XPNDR737 issues... need help guys !!!
-
06-06-2011, 06:26 AM #15
Re: FSX and XPNDR737 issues... need help guys !!!
I'm not 100% sure. My sim hasn't flown for a while but I've only ever used FS9 and seem to remember a similar problem with my CPFlight transponder.
-
06-06-2011, 07:27 AM #16
- Join Date
- Sep 2009
- Location
- Netherlands
- Posts
- 158
Re: FSX and XPNDR737 issues... need help guys !!!
No, this is a very simple issue.
Your CPFlight hardware is accessed through a virtual COM port.
Only one program can ever access this COM port at the same time.
The program that is accessing the COM port is the program that gets notified of the transponder mode and the ident switch.
This is the only program who can take action to notify squawkbox.
The CPFlight "drivers" are actually programs embedded in FS to open the COM port and make the default aircraft work with the MCP. If they are in charge, they must provide the info for squawkbox.
If you are using PM, the PM software is opening the port and is responsible for notifying SB. No CPFlight drivers are active in this scenario.
The key thing to remember is that there is always one and only one program communicating with your hardware, and this program is the one that must provide the support.
-
Post Thanks / Like - 1 Thanks, 0 Likes, 0 Dislikes
Sean Nixon thanked for this post
-
06-06-2011, 04:25 PM #17
- Join Date
- Dec 2005
- Location
- Italy
- Posts
- 46
Re: FSX and XPNDR737 issues... need help guys !!!
The operation of the standby value is the very same, whether it is FSX or FS9. The hardware sends a command, the MCP sets the offset.
It worked with FS9, so possibly there is something with FSX that makes it not work. Possibly with SB.
When you set the XPDR to standby, it should and does write 1 into offset 0x7B91. When you remove it it sets it back to 0. And it worked for you with FS9, no? You can check that with pmFileCheck or any other program that reads offsets.
Did you check the SB settings by any chance? There might be an option for that.
Please let me know.
-
Post Thanks / Like - 1 Thanks, 0 Likes, 0 Dislikes
Nick1150 thanked for this post
-
06-06-2011, 11:50 PM #18
Re: FSX and XPNDR737 issues... need help guys !!!
Thanks Enrico,
As stated in my e-mail, it worked in FS9. SB does not have sych an option.
My question would be.... Is it only me and Clive or it is an issue with every FSX setup ?
-
06-07-2011, 01:05 AM #19
- Join Date
- Dec 2005
- Location
- Italy
- Posts
- 46
Re: FSX and XPNDR737 issues... need help guys !!!
Strange... I very vaguely remember that something like that needed to be set. We had a notam out years ago when FSX came out.
To find that out you best try what I suggested. In pmFileCheck you enter in the text box to the right of 'Offset Check' 7B91 1 and see what value it is. If you want to set it use 7891 1 1 (see whether anything happens in SquawkBox.
But then again, if you google that offset you find several people are having issues (i think with squawkbox 4)... I think it was all connected to the fact that SB dropped using FSUIPC. (which i never really understood)
http://forum.avsim.net/topic/283143-...x/page__st__50
Go to reply #69... Peter Dowson himself writes:
someone else>You can look at the FSUIPC offsets associated with SB to see if the values are set when the transponder gauge settings are changed. In the FSUIPC logging tab, check the Display to FS Window checkbox, set one of the boxes to offset value 7B91 and select type U8 from the adjacent type dropdown box. A value of 0 means it's in standby, 1 means it's in normal.
Likewise, 7B93 (also type Uindicates ident pressed.
If these two change when you actuate their respective switches, then it's safe to assume the panel is interfacing with SB.
I've been wanting to try flying on-line with SB4 for several years, and wrote to the SB authors regularly for a while asking for some transponder facility to use in a cockpit, and I got a couple of rpelies long ago saying they'd "discuss it". But to my knowledge nothing ever happened. so I gave up.
Regards
Pete
-
06-11-2011, 09:58 AM #20
- Join Date
- Feb 2005
- Location
- Hamburg / Germany
- Posts
- 174
Re: FSX and XPNDR737 issues... need help guys !!!
Maybe this will help: http://www.flightdecksolutions.com/f...pic.php?t=4426
That was my solution for me, but I do not use CPFlight!Visit my project on Facebook and become a fan www.facebook.de/homecockpit
-
Post Thanks / Like - 1 Thanks, 0 Likes, 0 Dislikes
Nick1150 thanked for this post
Hi...realize this has been a long time, but I'm heading down the path of building my own 777...
B777 Overhead Panel Design