I´m trying to use my ipad to have access to MSFS 2024 based airliner FMCs using the WebFMC vol2. files. When using my computer browser with "//localhost:43380/.../index.html" it shows up the index and i can requested the airliner FMC. But when i use the link on the external device browser with the local host ip "//xxx.xxx.xxx:43380/.../index.html, nothing is shown except an connection error. Using other solutions like simbox the FMC is shown up on the external device. Therefore a connection between an external device should be possible.

Some hints and suggestion how to start finding an aao based solution would be perfect. In use is the latest build you can download from the webpage.

Thanks in advance

Norbert

 

Edited July 14, 2025Jul 14 by Norwenkel

Make sure to create both incoming and outgoing rules that allow the TCP ports 43380, 43381 and 43280 access through your firewall. The first two are for the WebAPI, the last one is for the WebFIPs.

On the download page there is also a  PDF with tipps for troubleshooting the WebAPI.

1 hour ago, Lorby_SI said:

Make sure to create both incoming and outgoing rules that allow the TCP ports 43380, 43381 and 43280 access through your firewall. The first two are for the WebAPI, the last one is for the WebFIPs.

On the download page there is also a  PDF with tipps for troubleshooting the WebAPI.

The incoming and outgoing rules for the TCP ports where not present. Thanks for your help

"Wer lesen kann ist im Vorteil"

Gruß

Norbert

Right now there is just problem with ifly 737 fmc showing nothing on the fmc display nor in 2020 neither in 2024. But pressing the buttons shows the response on the ingame fmc.

45 minutes ago, Norwenkel said:

Right now there is just problem with ifly 737 fmc showing nothing on the fmc display nor in 2020 neither in 2024. But pressing the buttons shows the response on the ingame fmc.

Sorry, no clue. Working fine here. The iFly has an internal, programmatic interface, it doesn't work like the others. I don't think that you have to activate the data transmission though (like you have to with the PMDG planes)

Make sure that the aircraft is fully loaded before calling up the FMC web page. The page wants to trigger a script in AAO, but that only works when everything else is ready.
When in doubt, force a reload of the page (go back to the index and call up the page again).

If all fails, configure the AAO script "iFly 737 MAX-IFLY_737MAX_CDU" as an Aircraft Automated Script, one-shot, beginning.

Edited July 14, 2025Jul 14 by Lorby_SI

12 minutes ago, Lorby_SI said:

If all fails, configure the AAO script "iFly 737 MAX-IFLY_737MAX_CDU" as an Aircraft Automated Script, one-shot, beginning.

I will give it a try later on. Thanks again

sorry no luck with the automated script 😞

38 minutes ago, Norwenkel said:

sorry no luck with the automated script 😞

Is the problem on the PC itself or on the remote device? 

Edited July 15, 2025Jul 15 by Lorby_SI

43 minutes ago, Lorby_SI said:

Is the problem on the PC itself or on the remote device? 

it is on both devices. As i wrote earlier the buttons in both browsers give a response. The inibuild a310 fmc seems to work as it should do on both systems. Using the 310 fmc (vol2) there was once an adidtional screen on the PC showing the fmc display content but the fmc is working on the secound and primary device.

Edited July 15, 2025Jul 15 by Norwenkel

35 minutes ago, Norwenkel said:

it is on both devices. As i wrote earlier the buttons in both browsers give a response. The inibuild a310 fmc seems to work as it should do on both systems. Using the 310 fmc (vol2) there was once an adidtional screen on the PC showing the fmc display content but the fmc is working on the secound and primary device.

You cannot compare the iFly FMC to the ones that use the popout-tech. It uses a completely different technology (the same as PMDG actually). iFly has a built in data interface that is read by the AAO script and then sent on to the webpage. So either your iFly is not sending the data, or something else is wrong. Couldn't say what that should be though, it works absolutely perfectly for me and it seems to work fine for most people? Maybe use the developer tools in your webbrowser to check for errors on the console? Or maybe check if the text is there but just not visible? But I am just guessing, I haven't got a single clue what could go wrong with this (except for the script not being called correctly)

 

Again thanks for your support. I will report when the problem is solved.

Just a short note: MSG lits up when a message should be displayed.

7 hours ago, Norwenkel said:

Just a short note: MSG lits up when a message should be displayed.

When you see the FMC image, then the WebAPI is generally working - that is why the buttons etc. are working too. It is just the data from the iFly plane's internals that is either not provided by their API or is not visible for some reason. Check that aircraft automated script again, maybe change it to "repeating". Be mindful that this script must be established for every livery of this aircraft.

Edited July 16, 2025Jul 16 by Lorby_SI