VRinsight devices (CDUII) in game. VRi2DCSBIOS.exe

G'day John, I've sent a PM.

This may be of help.

http://www.brass-em.com/portal/work-log/130-flight-simulator-controllers/vri2dcsbios-exe

I just discovered your VRi2DCSBIOS. I have an original MCP Combo, installed VRi2DCSBIOS and it says

Creating Socket...

socket succeeded: 336

Begin searching for VRinsight Units...

1-VRi Unit(s) fould!

Unit 0: FMER 2.520 \\.\COM3

Ready...

GREAT

looked at your <keys - CDU2_MCP2B.ini> and see you got the encoders to work for DCS CRS/HDG

and I wonder how did you come up with the name list of variables/designators, and can also MPCombo buttons be translated into DCS actions?

Will the [MCP2B] section work with the original MPCombi v1?

What is the syntax for all of this, like gear up/down, landing lights, and is there any chance to get the radio part to work (prob not) ?

THX

Problem

Connected everything, installed DCS-BIOS in the :\Saved Games\DCS\Scripts folder

renamed keys - CDU2_MCP2B.ini to keys.ini

changed 'MCP2B = COM13' to 'MCP2B = COM3'

commented out / deleted ;CDU2 = COM8 etc

Run Vri2DCS.exe

Start DCS

Start FA-18C

Rotate BORA/HDG/CRS but

Vri2DCS.exe output says:

VRi ID : 0

VRi Unit : FMER

VRi Button : HDG344-

DCS Key : NotUsed

VRi ID : 0

VRi Unit : FMER

VRi Button : HDG345+

DCS Key : NotUsed

VRi ID : 0

VRi Unit : FMER

VRi Button : HDG346+

DCS Key : NotUsed

VRi ID : 0

VRi Unit : FMER

VRi Button : HDG347+

DCS Key : NotUsed

same with BARO and CRS rotary

“DCS Key : NotUsed”?

perhaps is meant for A10C?

perhaps "VRi ID : 0" is an error?

How do I get FA-18C to work?

What are the "DCS Key :" syntaxes/how do I find them?

what do I need to do?

THX

I looked in the DCS-BIOS

:\Saved Games\DCS\Scripts\DCS-BIOS\lib\FA-18C_hornet.lua

and tried "STROBE_SW" with the A/T switch as per the output APLAT+ APLAT-

; MCP Switches

APLAT+ = STROBE_SW 1

APLAT- = STROBE_SW 0

but get

VRi ID : 0

VRi Unit : FMER

VRi Button : APLAT-

DCS Key : NotUsed

VRi ID : 0

VRi Unit : FMER

VRi Button : APLAT+

DCS Key : NotUsed

[updated...]

G'day majahit,

Sorry but I just saw your posts now.

It is good that you are getting the MCP to be seen as sending. The software is not translating the device via the keys.ini file correctly. Your device reports as FMER and the software looks up the appropriate key translation under the [FMER] section of the keys.ini file. If it found XYZ it would look under [XYZ] in the keys.ini If it's not there add it. (Although I have most devices listed on my website.)

i.e. I've cut and pasted the VRInsight MCPB2 outputs under [FMER]. I am assuming they are the same as the MCP V1 (FMER) but from your example it looks like they are not. (Still looking for my MCP V1 notes.) You may have to populate the keys.ini with what you get shown with your device.

[DEVICES]
;VRinsight Devices.
FMER = COM3

[FMER]
; EFIS Encoders
EFIMIN * = 
EFIMIN - = 
EFIMIN-- = 
EFIMIN + = 
EFIMIN++ = 
EFINDM * = 
EFINDM - = 
EFINDM-- = 
EFINDM + = 
EFINDM++ = 
EFINDR * = 
EFINDR - = 
EFINDR-- = 
EFINDR + = 
EFINDR++ = 
EFIBAR * = 
; Pure encoder rotation. values not precalculated.
EFIBAR - = ALT_SET_PRESSURE -3200 
EFIBAR-- = ALT_SET_PRESSURE -32000 
EFIBAR + = ALT_SET_PRESSURE +3200 
EFIBAR++ = ALT_SET_PRESSURE +32000

; EFIS Switches
EFIVORL. = 
EFIVORL: = 
EFIVORR. = 
EFIVORR: =

; EFIS Keys
EFIFPV . = 
EFIMTR . = 
EFIWX . = 
EFISTA . = 
EFIWPT . = 
EFIARPT. = 
EFIDATA. = 
EFIPOS . = 
EFITERR. =

; MCP Encoders
MCPHDG * = 
;Approx 11466 counts per 10 degrees = 229.3 per 0.2 degrees.
MCPHDG - = HSI_HDG -229 
MCPHDG-- = HSI_HDG -3640 
MCPHDG + = HSI_HDG +229 
MCPHDG++ = HSI_HDG +3640 
MCPALT * = 
MCPALT - = 
MCPALT-- = 
MCPALT + = 
MCPALT++ = 
MCPVVS * =
;Approx 11466 counts per 10 degrees = 229 per 0.2 degrees. 
MCPVVS - = HSI_CRS -229 
MCPVVS-- = HSI_CRS -3640 
MCPVVS + = HSI_CRS +229
MCPVVS++ = HSI_CRS +3640

; MCP Switches
MCPAT . = 
MCPAT : = 
MCPFD . = 
MCPFD : = 
MCPAP . = 
MCPAP : =

; MCP Keys
MCPTO . = 
MCPGA . = 
MCPCMDA. = 
MCPCMDC. = 
MCPCMDB. = 
MCPCWSA. = 
MCPCWSB. = 
MCPSEL . = 
MCPN1 . = 
MCPSPD . = 
MCPLNAV. = 
MCPVNAV. = 
MCPFLCH. = 
MCPHHLD. = 
MCPAHLD. = 
MCPVHLD. = 
MCPLOC . = 
MCPAPP . =

; RAD Encoders
RADFRE * = 
RADFRE - = 
RADFRE-- = 
RADFRE + = 
RADFRE++ =

; RAD Keys
RADCOM . = 
RADNAV . = 
RADADF . = 
RADDME . = 
RADTRAN. = 
RADTFR . = 
RADLAMP. = 
RADSTBY. =

; USRBTN Keys
USRBTN1. = 
USRBTN2. = 
USRBTN3. = 
USRBTN4. = 
USRBTN5. = 
USRBTN6. = 
USRBTN7. = 
USRBTN8. =

Also make sure of any spaces and full stops on the VRInsight code on the left hand side. Is it APLAT+ or APLAT +?

Have you seen this link?

I hope this helps you get started. If not let us know.

Cheers,

Hi Majapahit

I saw your post and I am using VR Insight all MCP FMER

You have inside Keys.init the right form in your case for example

APLAT+ = STROBE_SW 1: STROBE_SW 1

APLAT- = STROBE_SW 0: STROBE_SW 0

If it is not too late I can help you.

I sent a PM

Regards:)

Hi Majapahit

 

I saw your post and I am using VR Insight all MCP FMER

You have inside Keys.init the right form in your case for example

 

APLAT+ = STROBE_SW 1: STROBE_SW 1

APLAT- = STROBE_SW 0: STROBE_SW 0

 

If it is not too late I can help you.

I sent a PM

Regards:)

I need the proper Vri2DCS.exe keys.ini & how to syntax the keystrokes to the button names

THX

I can

- connect DCS-BIOS to DCS export (FA-18C)

- start Crome control reference live preview APP, and works OK

- start Vri2DCS.exe, and connects, and I can push/turn MCP buttons:

VRi2DCS
Version 1.0.0
by BrassEm

VRinsight CDUII to DCS World interface controller

Connecting to 127.0.0.1:7778

Initialising Winsock...
WSAStartup succeeded...
WSA Information:
high ver: 2.2 ver: 2.2
desc: WinSock 2.0
stat: Running
max sock: 0 max udp size: 0

Creating Socket...
socket succeeded: 364

Begin searching for VRinsight Units...

1-VRi Unit(s) fould!

Unit 0: FMER 2.520 \\.\COM3

Ready...

VRi ID     : 0
VRi Unit   : FMER
VRi Button : CTLBN0ON
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : CTLBN1ON
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : CTLBN2ON
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : APLAT+
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : APLAT-
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : VVS+
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : VVS+
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : VVS+
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : VVS+
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : VVS+
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : APLMAST+
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : APLMAST-
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : BAR-
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : BAR--
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : BAR--
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : BAR-
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : BAR--
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : BAR-
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : BAR+
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : BAR++
DCS Key    : NotUsed

VRi ID     : 0
VRi Unit   : FMER
VRi Button : BAR+
DCS Key    : NotUsed

etc.

Hi Majapahit

First I think that you do not use the correct syntax inside your keys.ini

APLAT+ = STROBE_SW 1

APLAT- = STROBE_SW 0

Here is the right in my opinion conform to key example you found in this post

APLAT+ = STROBE_SW 1: STROBE_SW 1

APLAT- = STROBE_SW 0: STROBE_SW 0

Good it seems that DCS bios works.

You use FMER I saw is it correct

Now you have to create from Keys.init your own keys file but you do not change the name Keys.init with Note Pad++

What are your F18-A buttons you will use?

Send me your list and I create and verify inside I had the plane if all is in function.

As I explained you create for every button for example if you want to use APLAT+ and APLAT-

APLAT+ = STROBE_SW 1: STROBE_SW 1

APLAT- = STROBE_SW 0: STROBE_SW 0

You can find all the buttons and position inside DCS Bios and Control reference

example or if it is a Switch 3 positions you modify

Button1=XXXX 0:XXXX 1

Button2=XXXX 1:XXXX 2

Button3=XXXX 2:XXXX 0

Do not hesitate to send me what you want

Cheers

Jean-Charles

Hi Majapahit

 

 

Good it seems that DCS bios works.

You use FMER I saw is it correct

Now you have to create from Keys.init your own keys file but you do not change the name Keys.init with Note Pad++

What are your F18-A buttons you will use?

Send me your list and I create and verify inside I had the plane if all is in function.

As I explained you create for every button for example if you want to use APLAT+ and APLAT-

 

APLAT+ = STROBE_SW 1: STROBE_SW 1

APLAT- = STROBE_SW 0: STROBE_SW 0

 

 

You can find all the buttons and position inside DCS Bios and Control reference

example or if it is a Switch 3 positions you modify

Button1=XXXX 0:XXXX 1

Button2=XXXX 1:XXXX 2

Button3=XXXX 2:XXXX 0

 

 

Do not hesitate to send me what you want

Cheers

 

 

Jean-Charles

Is it keys.ini or keys.init ? (because I used keys.ini)

A: Do you need with KEY binding definitions? Does (DCS-BIOS) Vri2DCS.exe work with B,

B: are controls “Action” descriptions enough? (like FSUIPC in FSX) which are:

C: the names in \Scripts\DCS-BIOS\lib\FA-18C_hornet.lua

D: I need the ‘syntax’ “APLAT- = STROBE_SW 0: STROBE_SW 0” etc EXAMPLES

E: the ‘headers’ in the keys.ini or are [DEVICES] [MCP] all there is?

A:

"LShift - Num4" UFC COMM 1 Channel Selector Knob - CCW/Decrease Instrument Panel; UFC

"LShift - Num7" UFC COMM 1 Channel Selector Knob - CW/Increase Instrument Panel; UFC

"LShift - Num1" UFC COMM 1 Channel Selector Knob - PULL Instrument Panel; UFC

B:

Push to Test Switch - CCW/Decrease Right Vertical Panel

Push to Test Switch - CW/Increase Right Vertical Panel

C:

VRi Button : CTLBN0ON

VRi Button : CTLBN1ON

VRi Button : BAR-

VRi Button : BAR+

VRi Button : BAR++

VRi Button : BAR+

etcetera

D:

EXAMPLE what is the entry for instance for

TFC rotary on MCP EFIS side:

F18 COM2-pull = EFIS TFC - push

F18 COM2-CW = EFIS TFC - CW

F18 COM2-CCW = EFIS TFC - CCW

F18 Course Set Switch Left = EFIS ADF2/VOR2 Up

F18 Course Set Switch Right = = EFIS ADF2/VOR2 Down

etcetera?

I would like HDG CRS Altimeter Radar_altimeter_warning COM1&2/pull/CW/CCW binded to MPC buttons

(and anything I can come up with later)

THX

I defined both keys.ini and keys.init

Entry:

[MCP]

APLAT+ = STROBE_SW 1: STROBE_SW 1

APLAT- = STROBE_SW 0: STROBE_SW 0

but Vri2DCS.exe commands window still says:

VRi ID : 0

VRi Unit : FMER

VRi Button : APLAT+

DCS Key : NotUsed

VRi ID : 0

VRi Unit : FMER

VRi Button : APLAT-

DCS Key : NotUsed

?

HI

Sorry it is Keys.ini not init does not exist.

You take the keys.ini you find in software and modify it as you want

I am looking for on Contyrol Panel and I saw that Strobe Lights Switch has 2 positions 0,1,2

in that case it is different I think if you take APLAT+ it is a single switch O,1

I think that APLAT + is Ok forGenerator for example

try this

L_GEN_SW

APLAT+ = L_GEN_SW 1: L_GEN_SW 1

APLAT- = L_GEN_SW 0: L_GEN_SW 0

Said if it is OK

About Strobe there are 3 position and FMER does not have it.

In that case you can use 3 pos buttons try this WX,STA,WPT in ths left corner of MCP in bottom

EFIWX=STROBE_SW 0: STROBE_SW 1

EFISTA=STROBE_SW 1: STROBE_SW 2

EFIWPT=STROBE_SW 2: STROBE_SW 0

I am going to see if there are others possibilities.

I use this software with A10-C and M2000

I am going tos see your post and request about encoders and COM it is more complicated COM does not works today and I hope in future find solutions?

Here is attached for example a keys.init be carefull it is a txt file and you cannot use before update file with note pad++ but sure you know :smilewink:

I am going to launch FA-18 and try some switch

This syntax works I launch at this moment the plane

I saw that it is written Ready and your COM3 is declare (Suppose you have also verify with your VR Insight .exe)

CTLBN0OF = L_GEN_SW 0:L_GEN_SW 0

CTLBN0ON = L_GEN_SW 1:L_GEN_SW 1

CTLBN1OF = R_GEN_SW 0:R_GEN_SW 0

CTLBN1ON = R_GEN_SW 1:R_GEN_SW 1

CTLBN2OF = APU_CONTROL_SW 0:APU_CONTROL_SW 0

CTLBN2ON = APU_CONTROL_SW 1:APU_CONTROL_SW 1

CTLBN3OF =

CTLBN3ON =

CTLBN4OF =

CTLBN4ON =

CTLBN5OF =

CTLBN5ON =

CTLBN6OF =

CTLBN6ON =

EFIWX=STROBE_SW 0: STROBE_SW 1

EFISTA=STROBE_SW 1: STROBE_SW 2

EFIWPT=STROBE_SW 2: STROBE_SW 0

You spoke of FSX do you use Linda especialy with Vr Insight I use also this perfect software. :) as VRI2DCS Brassem

About material do you have SAITEK material as PZ55 70 and 69?

If it is YES it exists another Sofware DCSFP marvelous as VRI2DCS it use the same application DCSBIOS and I can help you if need

If it does not Work open Keys.ini with note Pad++ copy inside model I propose and launch VRI2DCS.exe normaly you see the keys when you use buttons it changes and it is not necessary to launch DCS

keys.ini.txt

HI

others ansswer

About COM UFC

"LShift - Num4" UFC COMM 1 Channel Selector Knob - CCW/Decrease Instrument Panel; UFC

"LShift - Num7" UFC COMM 1 Channel Selector Knob - CW/Increase Instrument Panel; UFC

"LShift - Num1" UFC COMM 1 Channel Selector Knob - PULL Instrument Panel; UFC

If you are right panel is UP Front Controller UFC

COMM1 Channel Selector Knob Pull FA-18C_hornet/UFC_COMM1_PULL

You see that it is a 0,1

You can use

APLAT+ = UFC_COMM1_PULL 1: UFC_COMM1_PULL 1

APLAT- = UFC_COMM1_PULL 0: UFC_COMM1_PULL 0

or

CTLBN0OF = UFC_COMM1_PULL 0: UFC_COMM1_PULL 0

CTLBN0ON =UFC_COMM1_PULL 1: UFC_COMM1_PULL 1

or

CTLBN0ON =UFC_COMM1_PULL 0: UFC_COMM1_PULL 1 but in that case you can switch on ON but not return OFF

The most important is to see the number of positions you have 1,2,3 or rotary for encoders it is more difficult but you have example and have to try it.

idem for Keyboard Pushbutooon CLR FA-18C_hornet/UFC_CLR

I hope to help you

Cheers

Jean-Charles

Got this now working FA-18C, unfortunately HDG and CRS won't

[DEVICES]

;Manually added for reference only. Modify yours COM
;VRinsight Devices
FMER = COM3

[FMER]
;EFIS

;MINS = MIN ;Radar Altitude warning 
MIN- = RADALT_HEIGHT -3200
MIN-- = RADALT_HEIGHT -13200
MIN+ = RADALT_HEIGHT +3200
MIN++ = RADALT_HEIGHT +13200

;BARO ;Altimiter
BAR- = STBY_PRESS_ALT -4200
BAR-- = STBY_PRESS_ALT -42000
BAR+ = STBY_PRESS_ALT +4200
BAR++ = STBY_PRESS_ALT +42000

;NDR = TFC NDM=EFIS_CTR ;CTR TFC = COM1 COM2 channels select
NDM- = UFC_COMM1_CHANNEL_SELECT -229
NDM+ = UFC_COMM1_CHANNEL_SELECT +229

NDR- = UFC_COMM2_CHANNEL_SELECT -229
NDR+ = UFC_COMM2_CHANNEL_SELECT +229

Hi Majapahit

Excellent if your plane works.

I agree that concerning rotary it is more difficult.

;BARO ;Altimiter

BAR- = STBY_PRESS_ALT -4200

BAR-- = STBY_PRESS_ALT -42000

BAR+ = STBY_PRESS_ALT +4200

BAR++ = STBY_PRESS_ALT +42000

I do not know why because this syntax works perfectly for A10-C

Difference was 3200 but I think that it is not the problem.

I try to make the same thing with my M2000-C without success.:(

It works with control reference but not when I try to use VRI2DCS.

But all yhe keys are recognized inside VRI2DCS

If you find solution please give us

Cheers

Jean-Charles

FMER and rotaries

Hi Majapahit

Today I found a solution in my case to use rotary with BARO Pressure 1013 inside my M2000C

I use SPD it is more complicated but you can try this solution with your FA-18C.

It is the same for HDG001 to HDG360

SPDSEL- = BARO_PRESS_CALIB -6000000

SPD100- = BARO_PRESS_CALIB +950

SPD101- = BARO_PRESS_CALIB +951

SPD102- = BARO_PRESS_CALIB +952

SPD103- = BARO_PRESS_CALIB +953

SPD104- = BARO_PRESS_CALIB +954

SPD105- = BARO_PRESS_CALIB +955

SPD106- = BARO_PRESS_CALIB +956

SPD107- = BARO_PRESS_CALIB +957

SPD108- = BARO_PRESS_CALIB +958

SPD109- = BARO_PRESS_CALIB +959

SPD110- = BARO_PRESS_CALIB +960

SPD111- = BARO_PRESS_CALIB +961

SPD112- = BARO_PRESS_CALIB +962

etc until I want

SPD161- = BARO_PRESS_CALIB +1011

SPD162- = BARO_PRESS_CALIB +1012

SPD163- = BARO_PRESS_CALIB +1013

SPD164- = BARO_PRESS_CALIB +1014

SPD165- = BARO_PRESS_CALIB +1015

SPD166- = BARO_PRESS_CALIB +1016

SPD167- = BARO_PRESS_CALIB +1017

SPD168- = BARO_PRESS_CALIB +1018

SPD169- = BARO_PRESS_CALIB +1019

SPD170- = BARO_PRESS_CALIB +1020

etc

and the same with the negartive but I use always the same +

SPDSEL- = BARO_PRESS_CALIB -6000000

SPD100- = BARO_PRESS_CALIB +950

SPD101- = BARO_PRESS_CALIB +951

SPD102- = BARO_PRESS_CALIB +952

SPD103- = BARO_PRESS_CALIB +953

SPD104- = BARO_PRESS_CALIB +954

SPD105- = BARO_PRESS_CALIB +955

SPD106- = BARO_PRESS_CALIB +956

SPD107- = BARO_PRESS_CALIB +957

SPD108- = BARO_PRESS_CALIB +958

SPD109- = BARO_PRESS_CALIB +959

SPD110- = BARO_PRESS_CALIB +960

SPD111- = BARO_PRESS_CALIB +961

SPD112- = BARO_PRESS_CALIB +962

etc

SPD161- = BARO_PRESS_CALIB +1011

SPD162- = BARO_PRESS_CALIB +1012

SPD163- = BARO_PRESS_CALIB +1013

SPD164- = BARO_PRESS_CALIB +1014

SPD165- = BARO_PRESS_CALIB +1015

SPD166- = BARO_PRESS_CALIB +1016

SPD167- = BARO_PRESS_CALIB +1017

SPD168- = BARO_PRESS_CALIB +1018

SPD169- = BARO_PRESS_CALIB +1019

SPD170- = BARO_PRESS_CALIB +1020

In SPD+ clockwise and SPD- underclockwise

It is Ok for my pressure

You can try it and if you found solution please do not hesitate to post it.:)

I am also interessted with your key int for FA18-C for a friend:thumbup:

Hi, sorry for reactivating this old thread. I'm trying to set up my own VRinsight MCP-Panel for usage with DCS. Thank you for the wonderful small program. It seems to work quite well, however I have some issues. It seems as the signal sent from the panel through your program and the DCS-Bios is very short and causes issues. For example in the F18 pressing the A/A or A/G-button sometimes works, but most of the time it does not. A longer push seems to be needed. Is there an option/value I can add in the key.ini file to make the signal longer or even as long as I press the button?

Thanks for your help!

Kind regards,

chris

G'day Chrjs,

I have not programmed for that option. I have had a look at the coding and there is a 20ms debounce with a 100ms keyscan loop. I have changed these to 50ms and 200ms. Make sure you back up before running the exe to be safe. Let us know if that helped at all. Not sure whether this change will fubar the encoder rates.

Oooops. Wrong exe linked. Will edit this here when the right .exe uploaded. Sincere apologies for the problems caused.

Cheers,

BrassEm.

Hey BrassEm,

I've been fiddling around with this for my mpanel. Using the keys.ini file from your site, i could only get the buttons to be detected on the initial load e.g. COMSEL1/COMSEL2, NAVSEL1/NAVSEL2, ADFSEL1/ADFSEL2, DMESEL1/DMESEL2,TRNSEL and the respective rotatry functions. But once I press on the red button to toggle modes, all button press and rotary change is no longer detected. Only the Gear Up/Down + Flaps Inc/Dec is detected.

Am I doing something wrong here?

Thanks!

Faiz