I'm positive I edited the correct .flt file and the new code (7000) did show up first when loading the NGX but like I said above once I had put the NGX back to cold & dark then when I switched the power on again I was back with 1200. As for 1200 vs 7000 I might be wrong but as I always understood it both these codes are considered VFR codes and the codes you will use if you haven't been assigned another code. The only difference between the codes is the 1200 one is mostly used in North America where the 7000 is used in Europe. Might have misunderstood this though, guess for anyone interested should be fairly easy to Google. Honestly it's not really a big deal so please don't vaste you time on this if you don't want to for your own needs.

Hi, alright no problem, no no in fact I edited my start up files manually a great deal as well, so this is actually a welcome addition (should it work at last). For example I edited all the radio/baro minima, as well as set all my QNH baro knobs to standard hPa, and not inHg. Again EUR thing as you know, and I never fly inHg, and since it's a "hardware" switch on the real thing that wouldn't reset on a electrical power loss, I like the fact that it now always loads up readily set to hPa. You are basically correct about the codes, 1200 is US standard, 7000 is EUR standard for VFR. I don't know about their practice over there but here at least 2000 is the standard IFR code if you are assigned nothing else. I think this makes sense as you don't want to show up as VFR traffic at any time as airline traffic. Could be a country specific thing, but as I said I have never come across an airliner that set a VFR code at any time. As for actual setting of squawks, I really hope for this transponder and radios for some future SP. I'd definately like the numpad style for a change.

Changing the .flt file doesn't work cause apparently the NGX is internally setting the xponder code as you switch on the battery and the STBY power, so if you start from a C&D configuration, as soon as you switch on the battery, the squawk code is overwritten (initialized to 1200)

Yes, I'm using the registered version of FSUIPC.

This one seems to work

XPONDER_INIT_CODE = "2000"ipc.writeUW(0x0354, "0x" .. XPONDER_INIT_CODE)function xponderInit(controlnum, val)--ipc.log("controlnum " .. controlnum .. " val " .. val)if val == 4608 then  ipc.writeUW(0x0354, "0x" .. XPONDER_INIT_CODE)endendevent.control(65715, "xponderInit")

Just save that to a file called for example "NGXInit.lua" in the Modules folder and add an entry to your FSUIPC4.ini like this:

[Auto.737-823NGX American Airlines Winglets]1=Lua NGXInit

Hi, alright no problem, no no in fact I edited my start up files manually a great deal as well, so this is actually a welcome addition (should it work at last). For example I edited all the radio/baro minima, as well as set all my QNH baro knobs to standard hPa, and not inHg. Again EUR thing as you know, and I never fly inHg, and since it's a "hardware" switch on the real thing that wouldn't reset on a electrical power loss, I like the fact that it now always loads up readily set to hPa. You are basically correct about the codes, 1200 is US standard, 7000 is EUR standard for VFR. I don't know about their practice over there but here at least 2000 is the standard IFR code if you are assigned nothing else. I think this makes sense as you don't want to show up as VFR traffic at any time as airline traffic. Could be a country specific thing, but as I said I have never come across an airliner that set a VFR code at any time. As for actual setting of squawks, I really hope for this transponder and radios for some future SP. I'd definately like the numpad style for a change.

Didn't know of the 2000 code, thanks for the heads-up - that will be the code I use from now on when there is not ATC online. I wonder howcome PMDG doesn't use the 2000 code as the default code instead of 1200?

Changing the .flt file doesn't work cause apparently the NGX is internally setting the xponder code as you switch on the battery and the STBY power, so if you start from a C&D configuration, as soon as you switch on the battery, the squawk code is overwritten (initialized to 1200) This one seems to work

XPONDER_INIT_CODE = "2000"ipc.writeUW(0x0354, "0x" .. XPONDER_INIT_CODE)function xponderInit(controlnum, val)--ipc.log("controlnum " .. controlnum .. " val " .. val)if val == 4608 then  ipc.writeUW(0x0354, "0x" .. XPONDER_INIT_CODE)endendevent.control(65715, "xponderInit")

Just save that to a file called for example "NGXInit.lua" in the Modules folder and add an entry to your FSUIPC4.ini like this:

[Auto.737-823NGX American Airlines Winglets]1=Lua NGXInit

Thanks alot! Must admit this is more advanced than I though I would have to go to set another code than the default 1200 one but I'll give it a try or otherwise I'll just tune 2000 as part of the preflight items whenever there is no ATC online.

I wonder howcome PMDG doesn't use the 2000 code as the default code instead of 1200?

Noone knows, but maybe since the NG is of American brand maybe they have 1200 after power reset.

Noone knows, but maybe since the NG is of American brand maybe they have 1200 after power reset.

Guess you're right about that.

1200 is an FSX default !! Nothing to do with the NGX.

I'm not sure that is totally correct since the NGX does revert back to 1200 after going from powerd on to cold and dark and back to powered on again but it doesn't really matter. It's not a big problem changing to whatever code I like/need and I also got this FSUIPC script I'll try. Thanks again for everyone's input!

Changing the .flt file doesn't work cause apparently the NGX is internally setting the xponder code as you switch on the battery and the STBY power, so if you start from a C&D configuration, as soon as you switch on the battery, the squawk code is overwritten (initialized to 1200) This one seems to work

XPONDER_INIT_CODE = "2000"ipc.writeUW(0x0354, "0x" .. XPONDER_INIT_CODE)function xponderInit(controlnum, val)--ipc.log("controlnum " .. controlnum .. " val " .. val)if val == 4608 then  ipc.writeUW(0x0354, "0x" .. XPONDER_INIT_CODE)endendevent.control(65715, "xponderInit")

Just save that to a file called for example "NGXInit.lua" in the Modules folder and add an entry to your FSUIPC4.ini like this:

[Auto.737-823NGX American Airlines Winglets]1=Lua NGXInit

Tried this now but I still get 1200 when turning ON the battery from a cold & dark state...probably I did something wrong because I never tried any lua scripts/files before. I guess I'll just stick to manually changing the code the way I'm used to, thanks anyway!

Tried this now but I still get 1200 when turning ON the battery from a cold & dark state...probably I did something wrong because I never tried any lua scripts/files before. I guess I'll just stick to manually changing the code the way I'm used to, thanks anyway!

I can help you troubleshoot if you want.You'll need V4.60 or later of FSUIPC to have Lua support Also, the line<pre class="prettyprint">[Auto.737-823NGX American Airlines Winglets]</pre>you have to use the variant id you have loaded in the SIM. It comes from the aircraft.cfg (title) so for the variant [fltsim.2]title=Boeing 737-85PNGX Air Europa Wingletssim=B737-800WLmodel=panel=sound=texture=UXkb_checklists=Boeing737-800_checkkb_reference=Boeing737-800_refatc_airline=Air Europaatc_id=EC-HGP12atc_flight_number=154atc_model=737-800atc_parking_types=GATE,RAMPatc_type=BOEINGui_createdby=PMDGui_manufacturer=Boeingui_type=737-800NGXui_typerole=737-800ui_variation=Air Europa Wingletsairline_name=Air Europadescription=Boeing 737-85P powered by CFM engines v 1.0\nPMDG Simulations\nwww.precisionmanuals.com \n\nProduced under license from Boeing Management Company.\n\nBoeing 737, 737-800, 737-900 & Boeing are among the trademarks owned by Boeing.visual_damage=0 it would be: [Auto.Boeing 737-85PNGX Air Europa Winglets]1=Lua NGXInit

I believe that's how I did it. Very kind of your offering to help but I will just set the code manually, no big deal.

1200 is an FSX default !! Nothing to do with the NGX.

No it's not. You might think so simply because FSX default flights might have 1200 set and you never changed it. But the XPDR is saved as part of any FLT file, and, in case of aircraft that use the SDK variables, loaded as such if any different value.