hc625ma's cozy hangar

I have noticed a few bugs in DCS compat mode and fixed it. Also, I decided to pair it with “BUTTON_PRESS_ON_THROTTLE_CUTOFF” option, which from now on must be enabled for the Huey compat mode to work. Here are a few notes about it:

• IDLE REL joystick button (compact coll. head joystick button 5 by default) MUST be assigned to the corresponding button in the sim!
• connect your Simchair with closed throttle. In this case, no additional actions are necessary =)
• if you are not sure, before starting the helicopter, open the throttle past the detent mark, press and hold the IDLE REL button (red button on the compact collective head by default), and close the throttle. When you will turn the throttle grip to the left, the firmware will then send PgUp button press to open the throttle from “fully closed” position.
• DCS Huey compat mode only works in the middle position of the mode switch, this allows you to avoid sending PgUp / PgDn keys when you close the throttle in other sims, without disabling compat mode in the firmware each time.
• sadly, with the way it’s implemented in DCS, precise control of throttle below the idle stop detent is not possible. Therefore, for maximal realism, perform the startup with GPU connected. With external power supply connected, you can be sure that the battery won’t die during the startup and you will have enough power to open the solenoid driven throttle latch of the Huey. That allows you to perform startup at flight idle position of the throttle. Without GPU, the startup is usually performed with the throttle pushed slightly below the idle stop detent.
• Before closing the throttle, take a look at the state of the virtual IDLE REL button in the cockpit. If you have accidentally pressed it in flight and the virtual one is pushed in, just press it once more before shutting down the engine.

And a simple guide on how to use it:

1. open the throttle past the detent, press and hold IDLE REL, close the throttle.
2. perform the startup as described in the Flight Manual.
3. prior to shutting down the engine, check the virtual IDLE REL button state. If you see it pushed in, press the IDLE REL button once more to depress the virtual one.
4. to close the throttle completely, press and hold IDLE REL button on your collective and close the physical throttle. The virtual grip will follow.

Enjoy!

A couple of cool features have been ported to the compact collective:

• DCS Huey compatibility mode
• joystick button press on throttle cutoff
• secondary axis stabilizer – adjustable noise filter for potentiometer driven axes
• bug with incorrect button modifiers fixed for both pedestals

I think we can safely say, that with these features added, the compact collective is now complete. Here’s how it behaves by default at the moment:

• DCS Huey compatibility mode is turned on by default. That means, that when advancing throttle from full-right (closed) position, up to idle detent mark, keyboard button for throttle up key will be pressed (PgUp by default). After the mark, regular axis movement will be performed. To close the throttle completely (past the idle stop detent) you need to press the right push button on the compact collective head, which is set up as an IDLE REL button. This button won’t be pressing any joystick buttons when configured as IDLE REL button. If you don’t press the button before advancing the throttle past the idle stop mark, the virtual grip will stay at flight idle. You will have to move the grip back to the detent, press the IDLE REL button, and then close the throttle again.
• joy button press on throttle cutoff is turned on by default – that means that if IDLE REL button has been pressed before closing the throttle, a joystick button (3 by default) on the collective joystick (note that, not the head, but the collective!) will be pressed when the throttle will reach full-right position. This is very useful for XPlane helicopters (like DF 407, for example).
• secondary axis stabilizer is a very simple “digitizer” for potentiometer-driven axes. It allows for setting the minimal axis movement required to register a change in an axis. This kills the jitter completely and does not affect precision for stuff like throttles, zoom, and other secondary stuff where super precision is not really required. Can be set up on per-device basis depending on your potentiometer state =)

You can download the latest firmware from simchair4_software repo on GitHub.

I am happy to announce I’ve just pushed the final part of the controller to the repo =)

The new device looks better than the MKIII one, you can mount it to any 10x20mm rail (the default option is to mount it onto the cyclic base one). With the new software, you can put the needed number of these thingies next to each other, using the standard short blue USB wires that come with Chinese Arduino clone boards and a USB hub.

Standard setup with a compact collective, equipped with a pedestal, requires one master controller, but for stuff like VRMax, you may need two of them.

Internally, its the same thing as MKIII but with an added MCU reset button (which was needed occasionally when there was something wrong with the firmware). The button is connected between RST and GND of the board.

Stay tuned!

I’ve been able to make a couple of videos to show new devices in action, with simple pedestal among them! I really liked it, for me it solves the mouse-in-VR problem perfectly. It can be easily found while wearing the helmet, and position of controls on it allows for comfortable operation.

In the first video, I talk about MKIV line, the new firmware, and show the new collective base, the pedestal, and a simple collective MKIV lever body parts.

The second one is an extension to the 1st one, in which we can see how the new hardware and software work together in flight. This time controls were captured with a separate wide-angle-lens camera!

I have ported essential stuff to the MKIV master firmware today and had a few minutes to make a couple of circles around the runway to test it. At the moment, we have the support of the following peripherals in the firmware:

• compact collective (at the moment MKIII simple collective- axes only)
• simple pedestal
• cyclic base (MKIII/MKIV)
• B8 grip
• pedals

All special stuff like force trim, sensitivity switching, etc, works already. For now, each device shows as a separate joystick. Here are a few key features of the new firmware:

• the user specifies connected devices manually by uncommenting corresponding lines in “device_definitions” tab
• software is now modular by design – every device can be disabled or enabled separately
• controllers are now infinitely stackable – user can choose what device goes where, the only limitation is – cyclic base, grip, and pedals should belong to the same controller for special stuff to work!
• an infinite number of devices can be included in the firmware thanks to the new modular design
• custom devices (mods, variations, etc) can be added in a way so those won’t interfere with firmware updates!
• no more limits on axes and buttons – if we need more for some particular device, we just add another controller! All devices have unique joystick ids that will provide at least a certain order of controllers in games. That means, e.g. a throttle quadrant plugged into controller #3 will still appear in joy.cpl with e.g. id #5 – below other devices plugged into controller #1, that e.g. have ids #6 and #7.
• minimalism – joysticks only have what’s needed now instead of trying to fit stuff into 3 predefined joysticks, e.g. pedals only have 1 rudder axis and nothing else. Among other things, this helps with identifying devices. It results in some overhead, that may lead to additional controllers needed. I may unite essential flight controls into 1st joystick (axes only) while keeping the rest of the stuff separate.
• the code is mostly cleaned and reformatted for better readability
• it feels great in flight! =)

The new MKIV firmware is now live! So far it supports the simple collective (MKIII one) and a new “simple pedestal”, the name will most likely change =)

The most important part about the new software is, it uses a different approach to how devices are set up. If MKIII software was autodetecting devices on startup, MKIV one requires a user to define what devices to expect. This approach allows for saving both RAM and flash memory, and thus we may even end up using a single Leo board, while the library of supported devices can grow infinitely!

The only limit is the number of devices actually connected simulatenously!

Another important change is how joystick objects are used. In MKIII, there were 3 joysticks with a large number of buttons, and all devices used the same set of buttons. In MKIV, different joystick objects are generated for different devices. Some of them will share joystick IDs (e.g. collective levers), others will be unique (e.g. collective heads).

Other devices will be ported into MKIV as soon as possible, starting from MKIV gimbal, B8 grip, and pedals.

More cool stuff is on the way, so stay tuned!

I have just finished building the 1st MKIV collective base, and can say it’s great!

Not only its much stronger and more precise, but has a built-in mode switch that can be used for various functions in the software, 2 Ethernet sockets instead of a cable with a plug, and can be flashed through any of these sockets – with any USB-UART board! For cheaper boards without the DTR pin it has an MCU RESET button, that allows it to be flashed with manual reset in the process with stuff like PL2303 (which I no longer recommend using, just buy an FT232TL based board which is roughly the same price but installs drivers for itself and resets ProMinis automatically).

I actually liked ” live ” flashing and calibration more than I thought I would. The lever body itself is the first one intended to work with motion platforms – it’s strong yet lightweight, so lateral loads should not be a problem for it. The head also features the same set of buttons as the Huey-style head – but can be operated without the pneumatic mod.

Now, let’s look at what has changed. The new base has its Pro Mini connected in the following way:

• Mode switch left pin -> Pro Mini pin 2
• Mode switch GND -> GND next to RST
• Mode switch right pin -> Pro Mini pin 3
• MCU RST button -> between RST and GND next to it
• SS495A1 pin 1 -> THR POT left pin (on the left when the lever is mounted as usual) VCC cable tie <- Pro Mini VCC <- Ethernet sockets pin 1
• SS495A1 pin 2 -> THR POT right pin -> GND cable tie <- Pro Mini GND <- Ethernet sockets pin 2
• A0 -> SS495A1 signal
• A1 -> THR POT signal
• A4 -> SDA cable tie <- Ethernet sockets pin 3
• A5 -> SCL cable tie <- Ethernet sockets pin 4
• Collective head I2C cable -> VCC, GND, SCL,SDA cable ties
• Pro Mini Rx -> Ethernet sockets pin 5
• Pro Mini Tx -> Ethernet sockets pin 6
• Pro Mini DTR -> Ethernet sockets pin 7