FSX and XPNDR737 issues... need help guys !!!

[Nick1150]

Thanks for the hint

So it seems I am not the only one....

So if it is a FSUIPC4 issue, why FDS has solved it ?

[eschiratti]

So http://www.squawkbox.ca/doc/sdk/fsuipc.php is just a fix because SB does not use FSUIPC anymore in FSX... the mystery has been solved. Thank you Jan.

[Clive]

I don't understand offsets very well ... is the solution to assign FSUIPC offsets to the squark mode switch in buttons and switshes?

[eschiratti]

No... this needs to be re-worded.

SB4 has nothing to do with offsets anymore. They chose to go another route with FSX, probably because people were complaining about having to buy FSUIPC. I do not know why the authors of SB didn't at least include code on theirs side to check whether someone does have FSUIPC and for reverse compatibilitie's sake allow the transponder mode and other settings.

What is needed is a bridge between SB4 and FSUIPC and I think the link in the post above provides that.

I have no way into SB directly, only through FSUIPC.

[eschiratti]

You shouldn't have to worry directly about those offsets, only about the bridge. Just read the article.

I vaguely remember there was a similar issue with FSInn a while back.

[Nick1150]

You shouldn't have to worry directly about those offsets, only about the bridge. Just read the article.

I vaguely remember there was a similar issue with FSInn a while back.

Hi Enrico,

you mean this ?

Transponder mode
0 = normal
1 = standby
SquawkBox reads this value to determine which transponder mode to send to the network. Your transponder gauge should set this offset when the user changes modes with your gauge.


If yes can you please direct us on which way to direct our enquiry ? If not PM, FSUIPC ? CPflight ?

I really cannot understand who can give us the solution on that !!!

[eschiratti]

Nick... the old Squawkbox read that offset under FS2004. The new one apparently does not.

The CPFlight Hardware is telling the MCP to set the transponder to Standby.
The PM MCP gets that command and sets the standby offset in FSUIPC (you do not have to deal with that part as a user)
You can verify that by entering 7b91 1 into the offset check field in pmFileCheck. It *is* being set.
SB3 reads that offset and sets the transponder to standby.

The disconnect is here:

SB4 in FSX *does not care* that that bit is set. It did in the FS2004 version.

So if you contact the people who make SB4 and ask them to please, for backwards compatibility's sake, make a very quick function call to that offset, all problems are solved. Or perhaps there is another solution?

I can't talk to the SB4 software directly... if I could I would have done it a while ago. My hands are tied.

[eschiratti]

If yes can you please direct us on which way to direct our enquiry ? If not PM, FSUIPC ? CPflight ?

Why don't you mention SB4 in that list? Those three components are all doing their job right?

Please just *google* 'sb4 fsuipc offsets' and read the threads, and you will see that several are having the issue and the disconnect is not on this end.

Should anyone reading this have or know of a solution, please share it?

[eschiratti]

This is a completely private non-project magenta comment.

This thread is based on a need, and I have been writing software based on needs ever since FS4 back in ... 1754. Before many normal people even had an internet connection available, we were flying online on Compuserve, using a *chat forum* to transfer latitudes and longitudes altitudes and speed. The controlling took place by writing texts into that chat room and they were filtered out so the pilots and controllers could communicate with each other.

I also made add-ons dedicated to online flying, countless hours of work for freeware.

The present issue we are talking about involves two lines of code:

if hardware says on, set value 1
if hardware says off, set value 0

We are doing that. It takes more time to compile the MCP than to make whatever change is needed. It takes more time to upload the zip file with the change than to make the change itself. Just to put it into perspective.

I would only have to change the code to say:

if sb4 is used
do whatever it takes
else
if hardware says on, set value 1
if hardware says off, set value 0
endif

So if IVAO, VATSIM, EUROCONTROL, NASA or the Cartoon Network have a special convention for a transponder code that equates standby, as we can't talk to SB4, say for instance 7171... i w i l l d o t h a t.

Sigh.

[Nick1150]

This seems chinese to me, but maybe for the most experience this could mean something (?)

http://www.squawkbox.ca/forum/viewto...aa4cbd9ff6bc35

...