Shadowhunter241

Added some new panels to the cockpit recently and updated the HELIOS profile to add said panels. Tested everything, it all went great. Went to work, came back, booted up DCS, and almost all the bindings were borked. Pulled up HELIOS to check the profile, and find that it has shuffled around all the bindings for each interface card and placed them on different cards. For example, Card A has Binding A, Card B has Binding B, Card C has Binding C, etc. Then HELIOS f**** it up, and now Card A still has Binding A, but Card B has Binding C, C has F, D has C, E has D, etc. I'm wondering if this has happened to anyone else, if a fix has been discovered, and if there's an easier way to fix it than to delete everything and pend several hours reassigning all 3,000,000 bindings? Oh, and my DCS-BIOS also refuses to connect, so that's fun. Not as bad as the HELIOS issue though. Shouldn't be too hard to fix.

Interesting. I'll sticky note this and see about implementing it the next time I have the pit set up. It's currently unplugged and pulled away from the desk so I can use the computer for other things. Hopefully fairly soon, I'll have a video switch and some tv's set up so I don't have to dismantle the thing to get to the pc

I'm leaning more towards it being a weird game mechanic, unless nobody else is having this issue. The wiring is just 4 wires running from each switch to the pins on the bodnar board. That's it. They work for every other switch bind I've tried for other panels. It's just the CMSP that's derpy.

While the switches do need to be synced, they still don't want to go from OFF to ON even after several cycles. It's only ever OFF->MENU->ON. I'm not too terribly worried about it though, as the switches I have are momentary in the MENU position so they automatically flip down to ON once I let go. I have sync option turned off for now, as the pit isn't 100% completed yet. Also, I mostly fly singleplayer right now, and some missions start with the aircraft already running and in the air, which would be not so great if I had the pit configured for a cold start before the sync. Maybe when the pit is finished and I start flying online, I'll turn the sync on.

None of the BU0836A's have a matrix. They're only used for the analog inputs. I bound the switches on the CMSP panel directly through DCS yesterday, and they appear to be working, kinda. The switches still don't go directly from the OFF to ON positions, but instead have to be first set from OFF to MENU then ON. Not sure if that's "working as intended" for this panel, but I'll take it. I can at least turn my countermeasures on now. I appreciate the help.

Ah. Yeah, let's chalk that one up to a miscommunication. Couldn't tell if it was a legitimate question, or an attempt at being a smarta**. This being the internet, I defaulted to the latter. As far as coding goes, the only things in the pit that are coded through the arduinos are the various lcd screens, servos, 7-segments, and indicator lights. None of the switches/buttons/rotaries/etc. are coded. I'll try binding it straight through DCS in a moment. Kinda embarrassed that I didn't think of that tbh. I was so focused on the HELIOS aspect that I forgot going through the game itself was even an option. The bodnars are all either BBI-64's or BU0836A's. The inputs are all wired to the boards via dupont connectors plugged into the pins on the boards. As far as I know, diodes are not needed for these particular boards. However, if they are required, I haven't had any issues without them. This is the only panel in the entire pit that's being ornery.

I am. It's easier to write "programming" than "spending however long digging through HELIOS to find the correct interface card, correct input, and correct function, then assigning each individual input to it's desired function". Also, if it makes you feel better, there is an Arduino connected to the panel as well, that is programmed (with actual lines of code) to run the display. In both instances and context, using "programming" to describe what I'm doing is still a correct use of the word, according to the definition.

I have. HELIOS doesn't automatically assign anything, all the binds are manually assigned, so no worries there. I'll double check DCS to make sure everything is unbound in game Everything is unbound in game, but either way, it shouldn't clash like that. It would just do 2 different things at the same time when I flip the switch. The toggles in question are ON-OFF-(ON), and the binds look like this: I just updated HELIOS, so we'll see if that fixes it it did not fix the issue.

I'm currently in the process of building an A-10 cockpit. The basic I/O layout is: all the switches, buttons, rotaries, etc are run by Leo Bodnar cards; all the indicator lights, 7-segments, servos, and lcd's (CMSC, CMSP, ARC-210) are run by arduino and DCS-BIOS; and a 27" monitor running the MIP, 7" usb screen running the Fuel/Hyd panel (for now), and a 5" screen running the CDU, all with HELIOS. So far, everything has been running fairly smoothly. However, I have recently run into an interesting snag... After wiring up and programming my CMSP panel, I went to test it and found that the 4 x 3Pos switches controlling the MWS, JMR, RWR, and DISP are all acting strange. Starting in the down (OFF) position, I flip the switch to the middle (ON) position, but nothing happens in the sim. I then flip the switch(es) to the up (MENU) position, and the switch(es) in game all flip to that position. When I try flipping them back to the middle (ON) position, nothing happens again, and when flipping to the down (OFF) position, the switch(es) flip down in game. [EDIT] I forgot to mention in the original post that I have tried programming the switches in HELIOS to act like: Up=ON, Middle=N/A, Down=OFF, but that did not work either. All switches just stayed in the OFF position in game. All 4 switches show up and function correctly in both windows and HELIOS, they are all programmed correctly in HELIOS, and none of the other 3Pos switches in the pit have this problem. When I get home from work tomorrow, I will swap out the switches for new ones to see if (somehow) that fixes the issue, but since all the switches do function as intended I'm not gonna hold my breath. I currently have no other ideas as to how to fix this, so any help would be fantastic.

Hey all! Name's Will. I'm new around the forum, but I've been playing DCS ever since the A-10C and Black Shark modules were standalone. I'm mostly singleplayer only, but am hoping to start branching out into online pretty soon. I'm currently working on building an A-10 cockpit, which has taken the better part of 2 years to (mostly) complete, and I promised myself that I wouldn't fly again until it's finished. So, being that it's taken so long, I'm fairly rusty. Luckily, the muscle memory is starting to come back. As far as IRL goes, my day job is a Firefighter for the USAF, currently stationed in the frozen north that is Minot, ND. I'm in the process of obtaining my private pilot license, but have taken a brief break for the holiday to let the wallet recover. Anyways, it's nice to meet y'all, and I'm looking forward to seeing everyone in the virtual skies!