Blue73

Cheers Andreiru, If you look at my modular panel I'd build a switch mount like that as this panel is specifically sized to push the toggle's in like plugs (no nuts required) If you want to use the same toggles there's a datasheet on the link below where I bought them from. I know they're sold in bulk on Alibaba. https://www.jaycar.com.au/spst-ip56-heavy-duty-toggle-switch/p/ST0581

Using DCSBIOS makes it all very easy, just need some MAX487's to drive a pair of bus wires. Connect the 487's to your Arduino's serial ports and a single pin that controls rx/tx and you're good. When I'm back home I'll dig up a code sample from the A-10 panel. cheers John

Thanks TechRoss! That is exactly my intention with this, to be able to easily change the layout depending on the aircraft. When the F-14 module is released I want to be able to print F-14 modules or reuse modules that are similar by reprogramming slaves. I may repeat the same method as my A-10 Fuel Panel where I first learn which aircraft is loaded then dynamically instance/release controls during runtime. Yes your understanding is correct, Mega as the master and then the Nano's as slaves that can be easily reprogrammed. That's why I've exposed the USB port on the top, hidden under the face plate, so when I have a full bank of modules I can quickly reprogram if necessary. When I started to imagine this solution it started with the concept of modules interconnected with D-SUBS so I could easily change the layout. I didn't want to custom build modules for every aircraft. I have more design layouts that are yet to be realized. For now I'm getting the basics fleshed out. I have 3D templates that will allow me to rapidly knock out 3D models for the various modules once I'm happy with the basic design. This is an early concept model showing slaves arranged around the throttle. cheers John

Hi Andreiru, I use Fusion360. Cheers John

That looks awesome Brun!!

Thanks! It's just RS485 as designed into DCSBIOS. Really simple to get working. Each Slave has it's own vertically mounted Arduino Nano, you can see it's exposed mini-usb port in one of the pictures. If I want to change any control I just pop the top panel, plug in and upload new code. Which thanks to DCSBIOS is basically copy paste. cheers John

Thanks 98abaile. I have a Zortrax M200, it's been good to me so far, one failed print (clogged nozzle) in over year of use, the printer before that was a nightmare. Can you repost the link? The one you posted doesn't work. I am using DCSBIOS to drive these panels. The master is the 80mm unit and the two 40mm units are slaves. I have a MAX487's driving the bus in all units. Arduino Mega in master and Nano's in slaves. edit - working now must be my end, that's a nice setup!

Thanks DeadMeat, As long as you're aware of 3D printing's limitations what you can design is pretty much limited by your CAD skills.

Hi All, I've been developing this modular panel solution for the past few weeks. The idea is to able to readily interchange or add new modules. The basics are functional, moving onto designing double width panels, portrait panels, lighting up the second and third buses and tweaking the overall design. Two prototype slave 40mm panels are shown here connected to the master. Footer braces and side clips lock everything together. It's very solid, the switches can be toggled with the throttle off the ground. Modules are rigidly locked to the base plate, sandwiched between the two throttle metal plates. To program the slaves the top plate is removed as shown. The panels interlock via DB9 male/female sockets. Eventually there will be a complete set of panels running down the left side. The other two buses are intended for centre and right panels. Showing the throttle mounting braces Top panel removed for slave programming. Throttle Sandwich. cheers John

All good thanks Andrew, DeadMeat has been helping me out.

Thanks Capt Zeen, I'm using your DCSBIOS files now. DeadMeat pointed me in the right direction, my documentation was out of date, all good now. cheers John

Thanks DeadMeat you helped me once again, I do appreciate it! You were correct, my documentation was out of date. cheers John

Hi, I've posted this in the F-18 thread but it may not be the correct area so I'm re-posting here in the hopes that someone understands DCS-BIOS much better than me. I'm having issues with DCS BIOS with Andrew's F-18 profile. His function looks good but non of the intercomms work. There's also allot of other controls that don't work. It doesn't sound right so it must be something I have wrong. Is my understanding below correct? Are there any other factors I'm not considering? This for the RWR volume. The device ID was incorrect (41, changed them to 40.) ...\Saved Games\DCS.openbeta\Scripts\DCS-BIOS\lib\ FA-18C_hornet.lau: definePotentiometer("COM_RWR", 40, 3004, 359, {0, 1}, "Communication Panel", "RWR Volume Control Knob") ...\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\ devices.lau: devices["INTERCOM"] = counter()--40 -- Intercommunication Amplifier-Control - AM-7360/A command_defs.lua: -- intercom count = start_command intercom_commands = { CommSw = counter(); -- 3001 VOX_Volume = counter(); -- 3002 ICS_Volume = counter(); -- 3003 RWR_Volume = counter(); -- 3004 WPN_Volume = counter(); ... clickabledata.lau: elements["pnt_359"] = default_axis_limited(_("RWR Volume Control Knob"), devices.INTERCOM, intercom_commands.RWR_Volume, 359, 0.0, 0.1, false, false, {0,1}) Thanks! cheers John

Also can't get any of the intercomm controls to work. The device ID's were incorrect (41, changed them to 40.) But still can't get them to work. I've confirmed all parameters are correct. I must be missing something. e.g. ...\Saved Games\DCS.openbeta\Scripts\DCS-BIOS\lib\ FA-18C_hornet.lau: definePotentiometer("COM_RWR", 40, 3004, 359, {0, 1}, "Communication Panel", "RWR Volume Control Knob") ...\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\ devices.lau: devices["INTERCOM"] = counter()--40 -- Intercommunication Amplifier-Control - AM-7360/A command_defs.lua: -- intercom count = start_command intercom_commands = { CommSw = counter(); -- 3001 VOX_Volume = counter(); -- 3002 ICS_Volume = counter(); -- 3003 RWR_Volume = counter(); -- 3004 WPN_Volume = counter(); ... clickabledata.lau: elements["pnt_359"] = default_axis_limited(_("RWR Volume Control Knob"), devices.INTERCOM, intercom_commands.RWR_Volume, 359, 0.0, 0.1, false, false, {0,1}) Thanks cheers John

Hi DeadMeat, I'm having an issue with the buttons for the Flight Control Interface Panel, I was wondering if you could help? Looking in the devices.lau file it's (DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts) it's ID 2. devices["CONTROL_INTERFACE"] = counter()--2 Looking in the FA-18C_hornet.lau file (\Saved Games\DCS.openbeta\Scripts\DCS-BIOS\lib) defineToggleSwitch("FCS_RESET_BTN", 2, 3003, 349, "Flight Control System Panel", "FCS RESET Button") The device ID's look okay yet none of the buttons work. RUD_TRIM assigned to a rotary does work. I'm calling DcsBios::Switch2Pos fcsResetButton("FCS_RESET_BUTTON", PIN); I see the DCSBIOS messages, < 2018/09/06 21:07:47.503926 length=19 from=27104 to=27122 FCS_RESET_BUTTON 1 < 2018/09/06 21:07:47.613633 length=19 from=27123 to=27141 FCS_RESET_BUTTON 0 < 2018/09/06 21:07:47.963708 length=19 from=27142 to=27160 FCS_RESET_BUTTON 1 < 2018/09/06 21:07:48.083893 length=19 from=27161 to=27179 FCS_RESET_BUTTON 0 Yet the sim button doesn't respond. Thanks. cheers John

Awesome Bovsam! I'll check it out. Thanks.

Hi DeadMeat, Thanks for the heads up. Your first paragraph has me thinking, how do you deal with the initial position of the switches? I've had to scan all switches then call tryToSendDcsBiosMessage for each switch to update the sim switches. Wondering if there's a better way. cheers John

same issue, 4K monitor.

Thank you DeadMeat! Works now.

ASW allows me to run near max gfx settings so I prefer it on, there are trade-offs of course. The other issue is lag in head movement and it crashes when I exit to desktop from flight.

The CR-10 looks like a great printer, and with a glass bed. For the white lettering, you could do a colour change at the embossed lettering layer, you'd just end up with a white band around the toggle switches.

Hi James, Hand painted :) I embossed the lettering so I could flood each letter with white acrylic paint. If I had a 3D printer with a glass bed I could have printed it face down and got a polished top face.

Looking under the VR thread in the bugs section, I'm not alone.

Hi, I played DCS last night with no issues, ever since the update I get no ASW. Works okay for my other games. Oculus Tray tools shows it's active yet I get the double image issue you see when you're <90fps and ASW disabled. Has anyone else had this issue? Thanks.

Hi BlacleyCole, The files are now attached. I don't mind at all go right ahead! The past few weeks I've been working on a new modular version so I can adapt my controls to any aircraft. cheers John