ARC-210 #929
Replies: 10 comments 19 replies
Mine does not show anything in the display (update: helps if you turn it on!)
Wouldn't hurt, but I'd rather have the changes need to remove the patches for the 7 seg displays.
possibly, but if they've pulled the same trick with the GUIDs then it would be a "probably not". |
|
I did not think it worked either, but as I was binding controls in real time with the module running, it turned on. I'm not sure how "Implemented/ operational" it really is as the comms all work through the cnbp and cni. But the knobs and buttons all function and the display will fire up if you turn it off then back on again. |
|
Now that we know that it is working, I think I need to do some investigation into the display. |
|
I'm going to build a patch for the ARC-210 display after dinner, and see how that goes. Probably the path of least resistance, and we can always remove it at a later date if ASC come up with the goods. |
|
At this stage, I think we should go with a viewport for the ARC-210. I've built and tested a patch for the viewport, and included a template for it in the toolbox. |
multiswitch("ARC-210 Squelch Switch", devices.VOLUME_MANAGER, VOL_CTRL.arc_sql, 532, {-1, 1}, 2) |
|
I'm using a rotary switch for it currently where I can't set the value.. I can change it to a toggle or a pot where I can set value range and do a step value of 1 |
|
The problem with the data coming from DCS is that the values are between -2.0 and 2.0 where typically you would expect -1.0 and 1.0 to be the range. Easy to fix. I suggest you stick to using the rotary switch for this one. I currently have a Rotary Switch working with the squelch |
|
Should be fixed by d3f06c3 |
multiswitch("ARC-210 Operational Mode Switch", devices.VOLUME_MANAGER, VOL_CTRL.arc_op_mode, 543, {0, 1}, 1/6) |
|
Should be fixed by d3f06c3 |
multiswitch("ARC-210 Frequency Mode Switch", devices.VOLUME_MANAGER, VOL_CTRL.arc_q_mode, 545, {0, 1}, 1/6) |
|
Should be fixed by d3f06c3 |
multiswitch("ARC-210 100 MHz Selector", devices.VOLUME_MANAGER, VOL_CTRL.arc_rcu_1, 542, {0, 1}, 1/3) |
|
Note, a fix for the multiswitch reversal will result in changes to the following: "Pilot Window Open/Close" |
|
Should be fixed by d3f06c3 |
knob_360("ARC-210 Channel Selector", VOL_CTRL.arc_channel, 544, 0.2, nil, devices.VOLUME_MANAGER) |
|
Should be fixed by d3f06c3 |
|
New build 17/1/26: Toolbox Arc-210 |
|
removed the viewport from the toolbox version.. Text display functions, all the controls function, but still getting the Console "reference errors"
|
While this is true, you should be getting better results than you are. You obviously spotted that there is a tick box which describes whether the viewport or text displays are being used by the control. These are the bindings you should have (it is always best to delete the control from the profile and replace it from the toolbox if you are seeing binding issues) DetailsI quickly ran this test to check the functionality and demonstrate what you should expect from the textual display. As I mentioned before, it is not perfect and I might be able to improve it a little, but for now, I'm thinking that it is usable (at least for me). Recording.2026-01-18.085112.mp4The only change that I am planning to make at this stage to the bindings is to allow the in-cockpit brightness buttons to change the brightness of the textual display (the Helios brightness buttons already do this). Since there is no way to know the brightness of the display, I can't keep these brightnesses in sync, but I think it is still a useful thing to have available. If you're continuing to see problems with the ARC-210, then we can certainly investigate further. |
The only thing I would dispute is the "Intermittent". I needed to add a few more bindings to have this work as it is supposed to. The problem also exists on the A-10C II ARC-210.
I have not been able to reproduce this
Not seen this myself, but it is possible that this is a timing issue caused by the amount of display data being passed to Helios. This should all be processed in sequence, but maybe if the display data is changing quickly, a problem happens (just speculating). I'll keep my eyes open for this. |
|
|
Setting the viewport to blank is interpreted as meaning you want to use the textual display. Nice guessing. |
|
-Operation Mode switch- On "takeoff at senaki" just after hitting "fly". In-game Arc-210 is set on Position 2 ( TR) . Helios arc-210 stays on Position 4 until one of the knobs is moved. Then the positions sync.
|
|
I've seen the same issue, and can't immediately think of another reason for this happening apart from DCS not sending the initial value., or that value is not quite meeting the value needed for the initial switch position. |
|
In this most recent build:
|
|
I'm of a similar view, but I might do a little more thinking about the lack of initial sync. |
|
The problem is that when you turn the in-cockpit operation mode knob, position 2 returns "0.17", but on resuming the in-cockpit with the switch at position 2, it returns "0.22" which does not match the Helios value for this position so it does not move. I should be able to address this by reducing the precision of argument 543 to %.1f and rounding the switch position values. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
- Squelch/ On/off switch- reversed values.. - Output functioning but for some reason I'm not getting inputs
- Operational Mode Rotary switch- reversed values
- Frequency Mode Rotary Switch - reversed values
- All Frequency Selector Rotary Switches- reversed values
- Channel selector- Currently an axis. I believe it needs to be an Encoder
- Display- I did not realize the Arc-210 actually functioned. Should I beg ASC for a viewport, or do you think an adaptation of the a-10c2 text display is possible? I think you mentioned that MIGHT be an option early on. The init files are very similar but there are some differences.
All reactions