Hi, I don’t have any lua script for the default 787, so I am confused about your previous post, but anyway, there is a way to use multiple scripts, but I prefer to merge alle the script into one single script that I call normally “sioc_active.txt” that is the name that must be inserted in sioc.ini file.
[ Configuration File ]
CONFIG_FILE=sioc_active.txt
in sioc_active.txt I merge all the single files for all devices, specifying the device number
MCP does not require any device assignement, let consider it 0.
Then you have to find all the “device” part on efis code, and set it to 1
Var 0130, name I_5, Link IOCARD_SW, Device 1, Input 0
{
IF &I_5 = 1
{
&PM_RANG = 0
}
}
I have also a radio and I set it as device 2.
These numbers are those you can see when you launch sioc and they should correspond, otherwise nothing will work.
Really, all this is well explained in different tutorials and maybe also in sioc guide.
It is difficult to explain here.
Hi Airmax,
I did not mention any lua script in my previous post, so I do not understand You mentioning it…
I am not sure if I understand script merging with You example, but there is an helper program “Muliple Scripts” …
I still do not know, which “FSX default” scriptfile You are using for the MCP.
I am triying fs_737.txt, which gives me some default numnbers in the 7-segement-displays but do not work at any case.
With the 787 loaded the only thing that does something is when I press HDG SEL or LVL CHG the number of the IAS deceases. And when I press N1 the COURSE number raises.
So the module does something, but totally wrong and is not repsonding to the sim via FSUIPC and vice versa.
So this MCP file is not the one You used, I guess…
Wow happy it worked, flying with a real MCP is really another world!
Well, currently not, I can’t change neither mode nor scale, so if you use the 787 displays unfortunately it doesn’t work. It could be pretty easy to update it if only there were the offsets for the new gauges, but I can only hope that the official release of FSUIPC 7 will include those variables.
Probably they are the same for other airplanes, but surely they are not the same as the fsx 737…
I use my OC EFIS for the NAV display on secondary monitor that run an old program named CRGsim unfortunately dismissed and no longer available, but it works with MSFS2020. It also had a PFD and an EICAS all working.
Well, I forgot to mention the issue with the heading lock control, that is automatically activated on 787 and prevent MCP heading knob to work properly.
You have to go on VC and press the button on the HDG knob, so you can deactivate the heading lock and then the OC heading knob becomes perfectly functional.
Hi thanks for this information, I didn’t know this product. Prices are reasonable, and if they guarantee a complete support for all modules it is an interesting choice, specially for those planes that don’t have a dedicated SIOC code available.
FSSymphony is unfindable even if I email the guy that developed it. Mak-a-me so mad! So, forced to run P3D 5 and prosim. X-plane, still the most realistic sim, works with Zibo and some of my hardware. I use Pokeys, Opencockpits, Cockpit for you, Leo Bodnar and SIOC or FSUIPC 7. None really work correctly for my 737NG sim. It’s still a game of half truths when it comes to hardware.
Yes FSSymphony is available only contacting the developer, but I don’t know if he is still answering to that emai address.
It was almost the only way to use the Pokeys board without writing the code from your own.
When I decided to buy and use the Pokeys boards, Arduino was not yet available.
Today, comparing the price of a Mega (clone) and a Pokeys, with more or less the same number of I/O pins, Arduino costs 1/3rd of the Pokeys. But what is worse, Pokeys has a very little (if not null) support from the producer, and no other free or payware tools are available today (unless you use Prosim…).
So I abandoned definitively the Pokeys for the Arduino, 3 Mega at the cost of 1 Pokeys can handle three times the devices handled by one Pokeys, and you find a lot of code and MobiFlight is very good and free.
I use the USB Pokeys (56U) as a joystick emulator, with 32 buttons and many analog axis.
Another way to control the Pokeys would be with FSUIPC 7 and LUACOM, but unfortunately I couldn’t get luacom library to work (it gives me an error of “is not a valid Win32 application” or something like this; a pity because with FSUIPC and Luacom, it was pretty easy to write some code to control everything needed…
Hey Owlface
Thank you for the time and yes, they (pokeys) aren’t cheap but they work so well (Prosim). I have B737 compass from custom simulator parts with the arduino and yes, quite familiar with Mobiflight and its capabilities. I went all in on pokeys. I haven’t broken the surface with Pascal7 and all my Hispapanels yet, doubting seriously if the work with msfs220, at least for another 6 months- a year.
Anyway, I appreciate your response and will follow along,
Hey! I can’t remember how the owl came out, I remember I selected a pic of my homecockpit for the “avatar” but I got this… maybe they used an imaged that resembles my face!
That being said, no doubts about the fact that if you can afford Prosim, it opens a lot of possibilities (don’t know the current situation with MSFS2020 but surery was extraordinary with FSX, but I just tested the demo version.)
To me is completely absurd to ask more than 1.000 euros (I remember 1.200 ??? - now you only can contact them to have a price) for NON COMMERCIAL users.
Yes, the product is extremely good and powerful (even though it only allows a very specific aircraft configuration to what I remember) but it’s pointless to offer it to non commercial users for almost the money I spent for 90% of my cockpit excluding, of course, PC and monitor that I use also for all my other needs. So I don’t even consider it anymore as a choice!
I use the 5 0 B5, is quite old (2014 maybe) but it still works fine, of course you have to check if the offsets used are active for the specific plane you want to use.
I use my MCP mostlty for airliners, B787 or private jets, and also radio and EFIS, but I had to change some offsets in order to have some functions working.
