Falcon MFD Software for android tablets
-
Good decision, thanks for making your project open source!
All the best,
Uwe
-
Thanks to make your Code open source. I’m the first who forked it :D.
Nevertheless I have your app and Server running with on Win 10 1909 on a Motorola Xoom2 with Android 4 and BMS 4.34.2 and it still serves perfect to my needs -
Thanks
-
I have read this entire thread, the instructions and anything else I can get my hands on. Everything seems to work except I cannot get the MDF to display any information (pictures) on the android app.
I follow the setup instructions carefully and the green lights on the FalconMDF.exe are on. The displays are imported from BMS. But when I press “Send Img. To And.” I get a pop up message from FalconMFDServer that says “Unable to connect to the IP Address”
I have tried adding the FalconMFDServer.exe to the firewall, turning off the firewall, no matter what I get the same message every time I try “Send Img. To And.”
The button on the android app works the mdf’s in BMS, but I get no MDF display on the Android app no matter what I try. I’m trying to get this to work with BMS 4.34
Any help would be greatly appreciated.
-
I have read this entire thread, the instructions and anything else I can get my hands on. Everything seems to work except I cannot get the MDF to display any information (pictures) on the android app.
I follow the setup instructions carefully and the green lights on the FalconMDF.exe are on. The displays are imported from BMS. But when I press “Send Img. To And.” I get a pop up message from FalconMFDServer that says “Unable to connect to the IP Address”
I have tried adding the FalconMFDServer.exe to the firewall, turning off the firewall, no matter what I get the same message every time I try “Send Img. To And.”
The button on the android app works the mdf’s in BMS, but I get no MDF display on the Android app no matter what I try. I’m trying to get this to work with BMS 4.34
Any help would be greatly appreciated.
1. You have a registry entry for BMS 4.33 that points to your 4.34. base dir?
2. In the Andriod app if you click on the green button on the top left and select SET both your server IP and Client IP match to the settings you have in the Windows Android server program.
3. You are running the Windows MFDServer.exe as administrator
-
Thank you for your reply.
1. You have a registry entry for BMS 4.33 that points to your 4.34. base dir? Yes I did edit the registry and the program no longer gives me the error that it cannot find 4.33
2. In the Andriod app if you click on the green button on the top left and select SET both your server IP and Client IP match to the settings you have in the Windows Android server program. Yes. I have to change the ip address on the test part of the program every time I open the it. I haven’t found a way to save the ip address there
3. You are running the Windows MFDServer.exe as administrator Yes
I can also ping the tablet and get a reply.
-
Can you check what’s the Android APP LOG is logging
If you switch the Android App to ICP mode and press any button do you get any Incomming Message on the server side?If you try to use the button Send Img. To And. Make sure you havent started reading Shared Mem yet. So nothing should be green in the lower left corner
-
This post is deleted! -
None of your Attachments are visible
Another thing to mention. On my installation in the rare case that the Android app stops receiving or sending data and shows ERR in the Log Message. only stopping and starting the App on the tablet doesn’t help, I have to reboot the tablet. Happens mainly if my tablet lost wifi. But in general I have it up and running 24/7 without any problems.
Try to reupload or reattach your Screenshots, make picture of your Android LOG and SET as well, to be able to further analyze
-
This post is deleted! -
When I first start FalconMFD
This is when the android app is connected and I select the MFD
This is when I try and send the image to the android
This is when I’m connected to BMS. But still the MFD data does not show up on the android tablet
Thank you for trying to help me.
-
Hi Woodboy,
From anlaysing your Screenshoots all I can say so far is that we would have to further analyse on the Android side as on the Windows side everything Shows up correct and functional.
1. you don’t have to set your Tablet IP #1 there if you start MFDServer.exe on Windows. You only set it if you want to use one of the send Buttons #2. For normal usage the Android app establish the Connection to the Server Application
2. MFDServer.exe is reading Data from Falcon Shared Memory as the buffered Image is shown #4
3. Your Tablet has established a connection to the Windoes application #3 as the incomming Message Shows the handshake and even the Start reading of the MFDData.So I would try to test the communication Tablet->Windows by sending ICP button presses.
As you don’t get the MFD Image displayed on the tablet, as already set check the LOG of the Android app. You should be able to send the log via mail to yourself and than Maybe post it here -
Thank you so much for your time.
I just ran it this morning after following the set up directions. I can change the screen on the BMS MFD from the android tablet. I can change the ICP panel from the android tablet. Some of the buttons are not paired to the right buttons or switches, but I figure I can straighten that out later if I get the MDF data to work on the tablet.
Here is the log from the android table. BTW it is a Samsung Galaxy SM-T800. I also rooted it yesterday in another attempt to get it to work. It does not appear that root is necessary because the superuser app never asks for root permissions for FalconMFD. (I could be wrong about that though)
Msg 2020.02.04 08:51:39 Falcon MFD –> Welcome
Msg 2020.02.04 08:51:39 onCreate --> WhichScreen : w1280
Msg 2020.02.04 08:51:39 onCreate --> Screen Width : 1920
Msg 2020.02.04 08:51:39 onCreate --> Screen Height : 1200
Msg 2020.02.04 08:51:39 onCreate --> Screen Density : 1.5
Msg 2020.02.04 08:51:39 Falcon MFD --> Log File Path : /storage/emulated/0/FalconMFD.log
Msg 2020.02.04 08:51:39 fnkReadXML --> connection_params Readed
Msg 2020.02.04 08:51:39 fnkReadXML --> ServerIP : 192.168.1.14
Msg 2020.02.04 08:51:39 fnkReadXML --> AndroidIP : 192.168.1.6
Msg 2020.02.04 08:51:39 fnkReadXML --> ServerPort : 21111
Msg 2020.02.04 08:51:39 fnkReadXML --> MsgPort : 21111
Msg 2020.02.04 08:51:39 fnkReadXML --> LMFDPort : 21112
Msg 2020.02.04 08:51:39 fnkReadXML --> RMFDPort : 21113
Msg 2020.02.04 08:51:39 fnkReadXML --> DEDPort : 21114
Msg 2020.02.04 08:51:39 fnkReadXML --> MisSchPort : 21115
Msg 2020.02.04 08:51:39 fnkReadXML --> RWRPort : 21116
Msg 2020.02.04 08:51:39 fnkReadXML --> RefreshRate : 100
Msg 2020.02.04 08:51:39 SocketListenerMsgPort --> Listen Started on Port : 21111
Log 2020.02.04 08:51:39 ThSendKey --> CmdHandShake@21111
Log 2020.02.04 08:51:43 fnkMFD_ICIDEDModal --> MFD Started
Log 2020.02.04 08:51:44 ThSendKey --> CmdStopDED@21111@21114@100
Log 2020.02.04 08:51:44 ThSendKey --> CmdStopRWR@21111@21116@100
Log 2020.02.04 08:51:44 ThSendKey --> CmdStartSolMFD@21111@21112@100
Log 2020.02.04 08:51:44 ThSendKey --> CmdStartSagMFD@21111@21113@100
Log 2020.02.04 08:56:02 ThSendKey --> SimCBEOSB_14R@21111
Log 2020.02.04 08:56:04 ThSendKey --> SimCBEOSB_13R@21111
Log 2020.02.04 08:56:06 fnkMFD_ICIDEDModal --> ICP-RWR Started
Log 2020.02.04 08:56:06 ThSendKey --> CmdStopSagMFD@21111@21113@100
Log 2020.02.04 08:56:06 ThSendKey --> CmdStopSolMFD@21111@21112@100
Log 2020.02.04 08:56:06 ThSendKey --> CmdStartDED@21111@21114@100
Log 2020.02.04 08:56:06 ThSendKey --> CmdStartRWR@21111@21116@100
Log 2020.02.04 08:56:12 ThSendKey --> SimICPCom1@21111
Log 2020.02.04 08:56:13 ThSendKey --> SimICPCom2@21111
Log 2020.02.04 08:56:14 ThSendKey --> SimICPIFF@21111
Log 2020.02.04 08:56:15 ThSendKey --> SimICPLIST@21111
Log 2020.02.04 08:56:18 ThSendKey --> SimICPAA@21111
Log 2020.02.04 08:56:19 ThSendKey --> SimICPAG@21111
Log 2020.02.04 08:56:21 ThSendKey --> SimICPResetDED@21111
Log 2020.02.04 08:56:22 ThSendKey --> SimICPResetDED@21111
Log 2020.02.04 08:56:25 ThSendKey --> SimICPTILS@21111
Log 2020.02.04 08:56:26 ThSendKey --> SimICPALOW@21111
Log 2020.02.04 08:56:28 ThSendKey --> SimICPResetDED@21111
Log 2020.02.04 08:56:29 ThSendKey --> SimICPALOW@21111
Log 2020.02.04 08:56:31 ThSendKey --> SimICPResetDED@21111
Log 2020.02.04 08:56:31 ThSendKey --> SimICPResetDED@21111
Log 2020.02.04 08:56:33 ThSendKey --> SimICPTHREE@21111
Log 2020.02.04 08:56:34 ThSendKey --> SimICPResetDED@21111
Log 2020.02.04 08:56:36 fnkMFD_ICIDEDModal --> MFD Started
Log 2020.02.04 08:56:36 ThSendKey --> CmdStopDED@21111@21114@100
Log 2020.02.04 08:56:36 ThSendKey --> CmdStopRWR@21111@21116@100
Log 2020.02.04 08:56:36 ThSendKey --> CmdStartSolMFD@21111@21112@100
Log 2020.02.04 08:56:36 ThSendKey --> CmdStartSagMFD@21111@21113@100The Log from the Windows FalconMFD Program
Falcon MFD 2/4/2020 8:47:01 AM Başladı
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 1 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 2 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 3 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 4 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 5 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 6 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 7 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 8 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 9 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 10 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 11 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 12 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 13 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 14 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 15 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 16 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 17 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 18 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 19 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 20 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 21 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 22 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 23 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM target 24 [email protected]@0.000000@-1@Notset
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 1 [email protected]@[email protected]@TNK
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 2 [email protected]@[email protected]@TNK
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 3 [email protected]@[email protected]@AWC
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 4 [email protected]@[email protected]@AWC
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 5 [email protected]@[email protected]@
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 6 [email protected]@[email protected]@
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 7 [email protected]@[email protected]@
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 8 [email protected]@[email protected]@
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 9 [email protected]@[email protected]@
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 10 [email protected]@[email protected]@
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 11 [email protected]@[email protected]@
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 12 [email protected]@[email protected]@
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 13 [email protected]@[email protected]@
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 14 [email protected]@[email protected]@
fnkReadCallSign_INI_File Log 2/4/2020 8:47:03 AM ppt 15 [email protected]@[email protected]@ -
Currently scratching my head a bit.
So no ERR Logged at all. I was expecting to Maybe see an error once you switchted from ICP to MFD Mode, but apparently not.
Sadly to say I just gave away 10 Android devices I had, cause I don’t do mobile development no more for Real Live work, so I can’t test with other devices on my side for the moment.
Maybe Scratching my head a little bit longer might bring up another idea.
-
That would be just my luck lol. A one off problem that can’t be solved. As a last ditch effort I’ll post a few more pictures to see if you see anything wrong.
Tablet Start up Screen
What I see when I select MFD with BMS running. I noticed that the top bar with fuel and flares and thing are all showing zero
The ICP Screen. The button all seem to work, but not all of them work the correct things. ICP button 1-9 seem to work correctly and change the screen in BMS, but the screen on the tablet does not change
The Setting on the tablet
The only errors I seem to get on the FalconMFD windows program
Thanks again for all your efforts. I’m about to accept that I’m just not meant to use this lol.
-
Wood boy
The flare, chaff, and fuel have to be started on the first screen
Start FLIGHT DATA
Touch the above first and it will highlight and then select start icp OR mfd start.
Not sure about others.
-
Wood boy
The flare, chaff, and fuel have to be started on the first screen
Touch the above first and it will highlight and then select start icp OR mfd start.
Not sure about others.
His main issue is not reading Flight Data, is that the MFD don’t show the extracted data even so the communication to the Server App is working and don’t show any errors
-
Bugler is right - when you start server on PC , then start APP on tablet - first you have to “START FLIGHT DATA” … so ONLY then you’ll receive fuel , chf/flr , status bar
Do you have those lines set in “Falcon BMS.cfg” ? - you MUST
Line 119: set g_bExportRTTTextures 1 // This enables the shared texture memory area for HUD/MFDs/HMS/RWR/DED/PFL. This is independent from BMS external window usage Line 120: set g_nRTTExportBatchSize 2 // This determines how often the shared texture memory area (if it is enabled) will be updated (every Nth frame, default is 2) Line 129: set g_bDoubleRTTResolution 1 // Doubles the resolution of the cockpit displays (MFDs, HUD, HMS, RWR, DED, PFL), internal and external
Also - CHECK what keyfile are you using with the Server application on PC …
AAAH,… now I recall… This software is kinda obsolete … What is the problem -> Registry entries for BMS 4.34 … the server doesn’t know for the 4.34 registry … it just CHECKS 4.33 registry …
BUT! … I’ve “bypassed” that problem with a CHEAT - I gave it 4.33 registry , at least what it needs , you don’t need all , just disk location
Note the line where in registry 4.33 key points to 4.34 disk location… CRUCIAL
Try this - Make 4.33 registry key and follow the pictures , you need just disk location for your install … Then “Falcon MFD Server” will KNOW where to look for your config directory and keyfile ,
try this first then we’ll seeCheers
-
I have a version of the Windows Server part which doesn’t require the registry hack anymore. It just let’s you select 4.34 natively. As I had to change the position of reading the DED/RWR out of the SharedMemoryTexture as well and havn’t had the time to analyze it as well I won’t make this version public at the moment.
If anyone is interseted PM me. I’ll provide a version that just needs to be unzipped so can even be tested alongside an installed version with registry hack
-
any known issues with Android “O” ?