• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Developing WiFi Apps

Ralph Freshour

Ralph Freshour

Messages
120
Country
unitedstates
For my FSX add-on camera app, I'd like to develop an Android mobile app that uses wifi to communicate with my windows add-on app, running on the FSX machine, to select camera views.

I'm NOT asking for help on writing the mobile app, I can do that and have done that in the past. I'm asking for pointers/suggestions on how to use wifi to connect to my FSX add-on app so it knows that when I've pressed a button, my add-on app can respond accordingly.

Thanks for any pointers in the right direction to look...
 
Do you know how to send and listen for UDP packets? Both apps could just broadcast a UDP packet to the other on their subnet (e.g. each gets their local IP address, like 192.168.1.7 then change the last number to 255), with both listening for packets on whatever port you decide to use. Packets are just a blob of data you can define however you want.
 
Also when I say "broadcast" I mean when you send to an address ending in 255, the switch/router will send it to the selected port number on every device on that local network, but since only your apps are listening on that specific port, everything else will ignore it and your apps will "magically" be able to find and communicate to each other. That way you don't need to connect first or make the user type in some IP address. It's very convenient.
 
You must log in or register to reply here.
Back
Top