Would something like this work with Yame64? Does Yame64 support touchscreens? On sale right now, good deal?
Thanks for any input.
Would something like this work with Yame64? Does Yame64 support touchscreens? On sale right now, good deal?
Thanks for any input.
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.
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@100
The 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]@
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.
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.
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.
Just beginning the BMS-Training.pdf and have a couple questions,
Firstly, when I’m in the cockpit, should I not be able to see the throttle and stick move?
Also, how long do I hold the “FLCS PWR TEST switch” to test the system? Even in the NATOPS manual, all it says is;
2. FLCS PWR TEST switch-TEST and hold.
3. FLCS PWR TEST switch-Release.How do I close the canopy (spider)?
Lastly, what is my best reference towards learning all the abbreviations as quickly as possible?
Correct me if I am wrong, I believe the manual says most of the test functions are “eye candy” only and not really necessary to fly the jet.
I had exactly the same problem. I had luck following the directions from this thread -> https://www.benchmarksims.org/forum/showthread.php?27042-X52-Ministick-Bands-Radar-Cursors-Issue-with-latest-saitek-drivers Thanks nomis
Essentially uninstall the current drivers and STT (profile software) and install these older drivers and STT software from the Saitek FTP site listed below.
"Driver version: 6.0.4.1
Software version: 9.9.9.9
They are provided by these two files available at saitek ftp site (ftp://ftp.saitek.com/pub/software/full/)
Saitek_X52_Flight_Controller_SD6_64.exe
SST_Software_64_6_6_6_9.exe
PS.: It beats me why the SST version is “9.9.9.9” and the filename has “6_6_6_6_9” on it."
I was then able to use the X52 profile supplied in 4.34 and the mouse works fine now.