Search the Community
Showing results for tags 'av8bna'.
Found 8 results
-
I'm making a dedicated thread on a throttle nozzle quadrant build that I'm working on. This is something that started a while ago with a pretty detailed design effort that was put on hold for two reasons: 1. my 3D printer was having issues that needed to be investigated, and 2. designing the throttle grip was quickly determined to be too difficult based on the information I had at the time. Since then I have bought a new 3d printer and the old one has now been stripped down for parts for the quadrant. I have also stumbled across several excellent photos from @mattjonesgr9 that were posted on a UFC build thread. This is now enough, along with a short break in work travel madness, to allow me to hit this project hard again. I'm hoping I can keep enough momentum to get a working prototype finished in a few weeks. These are the original renderings of the quadrant enclosure assembly: I did manage to print out this first grip effort, but it was so far off the mark, I didn't know where to start. Since then I have come up with this design for the shell: Whilst not perfect, for a solid body, it's close enough. I've also scaled down the component by a factor of 0.9 as the printed version felt a tad too big for an ungloved hand. This first prototype won't be made of sheet metal as originally planned, but will be assembled from 2020 extruded aluminium and 3D printed parts. I will also be using a hall effect sensor for each of the three rotating axis instead of potentiometers.
-
Question to VR Harrier Drivers out there: Just got a Quest 2 and couldn't be happier! Things are pretty well sorted out for me in the F/A-18 (though always tweaking to get it better). Harrier looks great and is a blast to fly in VR as well, but I have one issue: When doing Cold Start or Shut Down, I have a lot of trouble "reaching" the switches and controls at the back of the panels. Ejection Seat Safe, OBOGS, DECM, Fuel Cutoff lever etc.. Seems like my head tracking doesn't work that far even when I crank myself around and when I try to get the mouse back there it kicks the dreaded "WINDOW IS NOT THE FOCUS" error. I have the checkbox in DCS VR for keeping the Mouse within Window Boundaries so I don't know why it keeps kicking the focus out. Happens in the F/A-18 as well, but for that the head tracking pointer works great, and I have been using THIS METHOD: Any ideas for a setting? Mask maybe?
-
Hello, after my glorious throttle mod I also came across a quite dirty but cheap CH Combat Stick game port version... So I made a plan to turn it into USB using once more the MMJoy arduino path. I took an arduino sparkfun pro micro and the MMjoy firmware, another MCP-3208 ADC for the stick axes and wired up everything in the base. While in the CH Pro Throttle game port version the poti had idk like 100 Ohms or something and needed an additional resistor before the MCP-3208 input to keep it from freaking out, the Combat Stick came with high resistance potis (100k?) and that way was ready out of the box for the modding. Meanwhile I also took apart the grip, and threw all the plastic pieces into the dishwasher (ymmv) to remove ten years of somebody else's palm sweat and grease residue (eew). I think that's the early version of a Combat Stick as the gimbal springs are tiny. In the original setup, the 14 or so grip buttons are all wired down into the base individually; I decided to use an array of shift registers in the grip to reduce the length of the wiring significantly. So after all this, a mere 5 wires (VCC, GND, DATA, CS and CLK) were left, plus one empty I was too lazy to pull out of the cable assembly. Note I marked which colour means what on the base before closing it, and of course not without testing everything with the help of some cheap breakout 74HC165 shift registers and a breadboard. Also note the mega unprofessional use of red/black wire for ground and white/black for VCC For the grip, the Combat Stick I had came with two hats and two buttons at the top thumb area (trim, sensor select, pickle and perhaps sensor select down for the AV8BNA), and a single button on the thumbrest halfway down the stick. On the box, there is a version pictured that has one of the hat switches in that position, and the button moved up to the main area. Now I still had a spare hat switch from my CH Pro Throttle, the index finger one to be precise, which I had replaced with an analogue stick mod by the mighty @rel4y. I decided that this needs to go into the thumbrest, increasing the actual number of buttons on the stick to 17. It required some grinding to fit into the button well, as the Throttle variant came with a square PCB while the CH Fighterstick variant that fits the same spot does not have a PCB but directly connects the microswitches. The rest is exactly fitting, including the little notch that prevents the hat switch from turning in its round socket. I tried fitting 3 x 74HC165 shift register breakout boards in, plus the necessary pullup resistor networks - which had to be SIL because my SMD soldering capability is not existing. Of course I failed miserably, but I came across a very nice 3 x 4021 shift register SMD setup on ebay classifieds. And, shame on me, until I read his name on the PCB when it arrived yesterday, I had failed to realize that the guy selling it was in fact our very own @rel4y. Hi mate, thank you for doing this! From then on everything was really just plug-and-play, also switching from 74HC165 to 4021 shift registers was as easy as 1 2 3. Cramming all that into the stick handle was still a nightmare, but at that point I could also no longer be asked to reduce the truly excessive wire lengths. To make everything fit, also around all the different studs and screw wells, I had to bend one of the pin header arrangements on the shift registers to 90 degrees inwards, but then *** ta-daaaa *** everything closed nicely, snapped into place and works like a charm. The only thing now is, I am missing a rudder axis dearly, especially for the half-helicopter AV8BNA. Perhaps that's my next mod? Who knows
-
Hello, For training mission 19, Unable to take-off or taxi. Wheel chock removal request request will not comply. Radio keybind "\" default calls F8 - ground operations, F4 Remove Wheel chocks. No response or Unable to comply. Have made attempts while engine off, Engine on, Canopy open, Canopy closed, Mission Start, and fully started aircraft. I really wish wheel chocks were not implemented in training scenarios, unless the intent was to never have take off or taxi ability during that mission. The voice instructions never reference wheel chocks in any of the training missions. -
Hello, Lua File ...\Eagle Dynamics\DCS World\Mods\aircraft\AV8BNA\Cockpit\MPCD\indicator\EPCD EPCD_Base.lua Has the following errors: (in red) Line 191: mpcd_mm_btn_16b.init_pos = { 0.65, -0.86, 0} Line 218: mpcd_mm_btn_17b.init_pos = { 0.33, -0.86, 0} Line 346: EPCD_OPT_16.init_pos = { 0.65, -0.85, 0} Line 352: EPCD_OPT_17.init_pos = { 0.33, -0.85, 0} For line 191, Assuming the order of the text should Read, CONT FLT CNPY For line 218, Assuming the order of the text should Read, DC EMER FAIL For Line 191 and 218 The suggested value would be -0.74 This will resolve the alignment of the text in vertical position. This does not resolve the position of the textured box once this button is selected. For Line 346 and 352, Assuming the box size is correct. To center the textured box around the text, the minimum suggested value change should be be -0.80 This change will center the box around the text vertically. I would also recommend addressing the text wrapping for the data shown with the EMER button 17 menu and DC EMER FAIL sub menu Button 17 selection. Text is clipping on two lines. Sorry for lack of photos. But, the detailed description of the errors should allow users to make their own modifications to this file(in administrative mode, Suggest using Notepad ++)
-
Welcome to Joint Task Force 191 - Task Force Jupiter! JTF-191 was formed in June of 2020 and is composed of 13 squadrons with 60+ active members. We operate as a milsim group with an emphasis on realism and joint operations with all branches of military aviation. We have a detailed training program for all new pilots that focuses on teaching a working knowledge of the airframe and relevant tactics. Our training is built to both teach new pilots about their chosen airframes or to provide refreshers to experienced pilots. With detailed courses on everything from take-off and landings to air-to-air tactics, the training program is designed to ensure you are comfortable in your role and up to the task of joining our ranks. Upon finishing your training, you are placed into an operational squadron with a custom livery made just for you. Each squadron handles their own training, keeping their pilots skills up to par with the unit standards. We have several dedicated servers that are up 24/7 and a unit-wide mission night every Saturday. Saturday missions range from fun PvP missions to organized pre-planned sorties built in an ongoing deployment campaign. We are always actively looking for pilots to fly with us! We are looking for: Pilots for the F/A-18, F-16, F14B (RIO’s too!), A-10, and the AV8B Mission planners of any experience C2 Personnel (AWACS, GCI, Marshall/ATC) Instructor pilots to strengthen our training program Developers Our basic requirements to join: Be at least 18 years of age Have a cockpit visualization set-up (Pit build, TrackIR, VR, etc.) Hands on Throttle and Stick (HOTAS) Be able to make required time commitments, approx. 2-3 nights a week for 2 hours at 2000EST, including mission nights on Saturday (we are flexible). Have a good attitude and willingness to learn! Click HERE to apply on our website! We will respond to you promptly.
-
Hi, I'm not active here, but I took a lot of info from your posts, in order to do this small project so I'd like to share the result. Essentially what I started out to do is turn a CH Pro Throttle game port version into a USB throttle. The Ch Pro Throttle comes with one low-ohm poti for the throttle axis. Four dedicated buttons and four digital four-way hats make for 20 buttons, which are wired into a button matrix. In a first step I took an arduino sparkfun pro micro and the MMjoy firmware. I wired up the button matrix, liberally reusing the available cables and connectors. The poti also needed some rewiring, as the gameport joystick "protocol" is just wired to read resistance of an analogue axis poti, while the arduino already expects a voltage divider setup. Now since I really enjoy the AV8B I decided to add more potis to the throttle grip. And, to my demise, I found @rel4y's excellent Playstation thumbstick mod 3D printed parts, which replace the index finger 4-way hat with 2 analogue axes and a push button; which is really nice for the TDC slew and TDC down/action part of a HOTAS. You already see that I was quickly running out of arduino inputs. Therefore I decided to use an MCP-3208 ADC to digitize all 5 analogue axes. This required me to put a static resistor into the voltage divider of the slider axis, to reduce the charge going into the ADC at each sampling interval. I know my mechanical skills are crude, please bear with me. After some hours of soldering and grinding I now have this nice USB throttle, and still 3 analogue axes and 3 buttons not used in hardware. Also when I'm grown up I maybe use some shift registers to put even more buttons.
- 1 reply
-
- 1
-
-
- ch products
- ch pro throttle
- (and 4 more)
-
I've got a lua script set up to display the main viewport on one monitor, and two MFDs (and apache TEDAC) on a second monitor. I use the same script in the apache, Ka-50, F-16 and F/A-18 the MFDs all appear in the monitor in the correct place. When I switch to the AV8B harrier, the MFD displays do not show up in the F1 cockpit view, but do display when I switch to the F2 external view, and disappear when I switch back to the F1 view. The script uses the generic LEFT_MFCD and RIGHT_MFCD identifiers as they seem to work in the modules listed above. _ = function(p) return p; end; name = _('AH-64D Apache CPG Dual Monitor: m1 - Viewport, m2 - MFDs, TEDAC (equal)'); Description = 'dual monitor: viewport on main 2560 x 1080 (21:9 aspect ratio), MFDs and TEDAC on second monitor: 1680 x 1050 (16/10 aspect ratio) bottom aligned' Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1080; viewDx = 0; viewDy = 0; aspect = 21/9; } } LEFT_MFCD = { x = 2560; y = 30; width = 554; height = 554; } RIGHT_MFCD = { x = 3668; y = 30; width = 554; height = 554; } TEDAC = { x = 3114; y = 30; width = 554; height = 554; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center Is it a case of using specific IDs for the AV8b displays instead of the generic IDs, or is just a weird bug with the harrier?
