My version of a multipurpose VR cockpit

[marques]

After literally years of reading almost daily this forum and not having much to give, I can finally start my own thread.

The first thing I´ve to do is to ask forgiveness to my english. It´s not bad, hopefully, but maybe not good enough for a technicak post like this. Anyway, I´ll do my best to make myself understood.

 

 

That said, let´s start. What´s my idea? I want to create phisical panels for being used in VR, and be able to use them in different modules, just changing the location. For that, I have the intention to create a framework around the seat (Work in progress, or in two weeks if you prefer) were I can allocate box modules in the aproximate location in which I see them in the VR cockpit. Therefore, I will naturally send my hand in the direction of the instrument and find it phisically. The concept means that aesthetics are not so important and that I don´t need to deal with lights or screens, witch I hope will facilitate greatly the project. Another think to take into account is that my intention is to create only those commands that are used in flight and/or very frequently. Cold start and shutting down are not an issue to be done with the mouse.

 

 

I´ve had this idea for a while, but only recently I received the tool that I think will make the projet feasible: a 3D printer. With this I can design the module, print it (easily and very cheap), test and modify as needed and print a final version.

 

 

Ok, what I aready had was a leo bodnar 32 and six rotary encoders, one of them including a push button in the axis. Also I have a few switches (ON-OFF-ON) and buttons. So the first step is to test the concept and see if it is true that I can reach and operate naturally a module without actually seing it.

 

 

For that I´ve started designing the landing gear lever box and an UHF and TACAN boxes. Why those ones? The landing gear was an easy decision because almost all modules have one. And the two radio modules are used in many US modules and specially in the F-5, which I´m flying a lot lately, you have to operate them quite a lot in flight, as this aircraft is essentially manual.

 

 

Finally, time for showing what I´ve done. You will see that I´m still using the table to hold the modules. As I said before, the final pit will hopefully have it´s own structure.

This is the landing gear module. As you can see it has a simple switch with a printed lever and a button to depict the emergency release that all aircraft has in one way or another. Here you see it in the aproximate place of the ka-50.

 

 

 

 

 

 

 

 

 

 

 

 

The next one is the UHF module, that can be used horizontally like in the A-10 or vertically like in the f-5.

 

 

 

 

And the modules printed and located like in the f-5:

 

 

 

 

I´ve already tested it in a couple of flights and it works great. I think that the concept is correct, so I´m eager to start making final modules.

 

 

And here are my first questions:

- I think I remember reading that the leo bodnar boards does not read well the ON-ON switches, or the On-on-on ones for that matter. Is that true?

- I think I´ll need more USB boards. Leo bodnar has a 64 button board that cost around 40€. As I don´t foresee the need of axis, and in any case I already have up to 8 axis I think this is enough. But I´ve seen dcs bios and arduino boards here being used. I don´t need fancy capacities but arduino may be simply cheaper and solve the problem with the on-on switches. Any initial guidance with arduino? How many buttons can handle a, let´s say, an arduino mega? are they easy to setup and configure only for switches, buttons, etc..?

[BIGNEWY]

Looks great :)

[marques]

Looks great :)

thanks, bignewy, but truth be told the looks are not good at all.

In any case, it does not matter because now is just a proof of concept. A draft if I may say so.

By the way, yesterday I digged a little in this forum and in internet and I think now I have clear that an arduino mega or two is a better option to continue this projet. Look as easy as with the leo bodnar and much cheaper.

The only issue that I can imagine is that I have to rely on dcs bios, and not all modules are available.

[Hansolo]

And here are my first questions:

- I think I remember reading that the leo bodnar boards does not read well the ON-ON switches, or the On-on-on ones for that matter. Is that true?

- I think I´ll need more USB boards. Leo bodnar has a 64 button board that cost around 40€. As I don´t foresee the need of axis, and in any case I already have up to 8 axis I think this is enough. But I´ve seen dcs bios and arduino boards here being used. I don´t need fancy capacities but arduino may be simply cheaper and solve the problem with the on-on switches. Any initial guidance with arduino? How many buttons can handle a, let´s say, an arduino mega? are they easy to setup and configure only for switches, buttons, etc..?

 

Looks like you are off to a good start Sir.

 

- I don't think the Leo Bodnar card has any problem reading ON-ON nor ON-ON-ON. The problem may be in the joystick lua you need to change to facilitate this.

 

- It's true that you can only use modules where the software package has been done for DCS-BIOS. Or you can do it yourself.

Alternatively you may want to look at Overpro's mod for an Arduino Mega which turns into a joystick controller https://forums.eagle.ru/showthread.php?t=117011

 

As for DCS-BIOS, Ian has a Youtube page where you can find some initial answers;

 

https://www.youtube.com/channel/UCwECFPfC3QJiNYS5fskF2vg

 

As long as you are using 'just' switches then it very easy to use. When you want to do more advanced stuff it may get more tricky but the options are there to do it or learn how to do it.

 

Cheers

Hans

[Capt Zeen]

:smilewink: Nice work Marques !

[marques]

Hansolo, Zeen thanks!

Hansolo, that information is gold! to convert the arduino to a joystick simplifies a lot my work. I had a look to the links and a thing poped up fast: apparently an arduino mega can support up to 256 buttons,at least doing that modification. Is it correct? is this also the numbers of buttons supported in normal mode, i.e., with dcs bios?

 

And now, a few more pictures of the "furniture".

 

 

 

It was done with the final cockpit framework in mind, but meanwhile it can be folded a bit. It also include 3D printed wheel stops for the chair that work fairly well.

And to finish, my warthog extension:

 

The conectors are taken from a design in thingverse, made by No3BoB. The design was modified by me adding a "welded" and curved extension tube. The cable was a PS2 keyboard extension cable, cut to lenght and with a pin withdrawn in the male conector.

I have to say that it works ok, but I have the impression that I will have to reprint the extension once I have ABS and a better knowledge of printing.

[javelina1]

Great work OP! looking good.

[BlacleyCole]

when you finalize the 3d printouts how about posting your printer files for those following behind you

[Hansolo]

I had a look to the links and a thing poped up fast: apparently an arduino mega can support up to 256 buttons,at least doing that modification. Is it correct? is this also the numbers of buttons supported in normal mode, i.e., with dcs bios?

 

Yes if I read the description correctly you get the Mega to show up as two joystick controller each of 128 bottons. This is quite similar to the B256A13 boards I have and as Overpro states then Windows can't show more than 128 buttons.

 

As far as I understand you configure the Mega to be a joystick controller but then cannot function with DCS-BIOS. You have to make the choise whether to go with DCS-BIOS or joystick controller per board.

 

But there is nothing wrong with using both systems in your pit.

 

I am still in the transfer phase from joystick controller to DCS-BIOS so I am running a little of both.

There can also be some flexibillity in running some of your things with joystick controllers. When using DCS-BIOS you program the Arduino to become e.g. landing gear panel for the A-10. Which also means that you can't use this for e.g. the F-5 unless you reprogram the Arduino.

 

With a joystick controller you can just map the inputs to a new module.

 

Hope it made a little sense.

 

Cheers

Hans

[marques]

Yes if I read the description correctly you get the Mega to show up as two joystick controller each of 128 bottons. This is quite similar to the B256A13 boards I have and as Overpro states then Windows can't show more than 128 buttons.

 

As far as I understand you configure the Mega to be a joystick controller but then cannot function with DCS-BIOS. You have to make the choise whether to go with DCS-BIOS or joystick controller per board.

 

But there is nothing wrong with using both systems in your pit.

 

I am still in the transfer phase from joystick controller to DCS-BIOS so I am running a little of both.

There can also be some flexibillity in running some of your things with joystick controllers. When using DCS-BIOS you program the Arduino to become e.g. landing gear panel for the A-10. Which also means that you can't use this for e.g. the F-5 unless you reprogram the Arduino.

 

With a joystick controller you can just map the inputs to a new module.

 

Hope it made a little sense.

 

Cheers

Hans

Thanks a lot, Hans, it makes a lot of sense.

Only one thing is not fully clear. I understood that you an only setup one phisical element (switch, button, whatever) to just one element of an specific module. That meas that I cannot have a landing gear for every module, isn´t it? But the question is: Can I have different module´s elements programmed at the same time in just one arduino?

I mean, for example, having in one arduino the ka-50´s ABRIS and the A-10 CDU at the same time, provided they are phisically different.

Just in case, is there a simple and fast way of reprogramming an arduino for a module?

 

 

And a related question with arduino, in either mode: the diode matrix needed to reach those 256 buttons: are they sold or you have to make one yourself?

 

 

Now I have a more or less comprehensive list of elements needed, and I intend to make a first buy in aliexpress soon. Afterwards, I should start building...

[Hansolo]

Thanks a lot, Hans, it makes a lot of sense.

Only one thing is not fully clear. I understood that you an only setup one phisical element (switch, button, whatever) to just one element of an specific module. That meas that I cannot have a landing gear for every module, isn´t it? But the question is: Can I have different module´s elements programmed at the same time in just one arduino?

I mean, for example, having in one arduino the ka-50´s ABRIS and the A-10 CDU at the same time, provided they are phisically different.

Just in case, is there a simple and fast way of reprogramming an arduino for a module?

 

 

And a related question with arduino, in either mode: the diode matrix needed to reach those 256 buttons: are they sold or you have to make one yourself?

 

 

Now I have a more or less comprehensive list of elements needed, and I intend to make a first buy in aliexpress soon. Afterwards, I should start building...

If you want one landing gear panel that works for all your aircrafts then you need to have that panel run on a joystick controller board.

 

I can't see anything technically wrong with running an Arduino for KA-50's ABRIS and another for the A-10C's CDU. If you fly the KA-50 and by accident press the CDU on the A-10C the Arduino will send a command to DCS but since the module doesn't match nothing will happen.

 

It's fairly simple task to re-program the Arduino if you are running it via USB. If you are running it via RS485 then you need to disconnet it from the communications chip before programming it, otherwise the program wont load.

 

As for the diode matrix I seen a ready made one so best guess you will have to do it yourself.

 

Cheers

Hans

[marques]

If you want one landing gear panel that works for all your aircrafts then you need to have that panel run on a joystick controller board.

 

I can't see anything technically wrong with running an Arduino for KA-50's ABRIS and another for the A-10C's CDU. If you fly the KA-50 and by accident press the CDU on the A-10C the Arduino will send a command to DCS but since the module doesn't match nothing will happen.

 

It's fairly simple task to re-program the Arduino if you are running it via USB. If you are running it via RS485 then you need to disconnet it from the communications chip before programming it, otherwise the program wont load.

 

As for the diode matrix I seen a ready made one so best guess you will have to do it yourself.

 

Cheers

Hans

 

Good, I have a clearer picture now. I think, then, that it´s worth it to have two Arduino boards, one for generic elements in joystick mode an the other for specific and more difficult elements that can run in DCS BIOS mode.

It´s good news, because I´ve done a rough count of how many connections I could need, and they are plenty!