I am happy to show you yet another Simchair MKIV device – the Bell 206 style collective head. Its made from photos with measurements, so it should be almost exact 1:1 scale.
To make GOV RPM switch look scale, I’ve made a special adaptor for MTS-123 E1 switch. Another option is to use a regular 12mm spring-loaded SPDT switch for GOV RPM control. Small parts need to be printed at the highest possible quality and have built-in supports.
I will also be releasing a scale 206-style version of throttle frame part 1 with 104 degrees throttle grip travel range, as per information from an IRL 206 pilot.
This head is best to be used with MKIV collective with a physical throttle latch. Will release firmware for it in a few days =) You can find it in simchair4_models repo on GitHub.
Finally, after months of testing, all problems are addressed, and the new cyclic is here – and it feels great! Here’s the video which shows the new base up close – and then there’s a test ride in an epic freeware Hughes 500 for XPlane11 by Brett S – which is a pure joy to fly!
I have just rolled out an important software update, that includes some cool new features:
Huey head support added
Single throttle MKIII collective support added (all spring-loaded switches so far)
fast EMA filtering added for cyclic and pedals
ADS1115 sample rate reduced for absolute smoothness of controls
Addition of support for single MKIII collective lever along with the Huey-style head means that most of MKIII users can now try upgrading to MKIV version! And the latter two features is why they probably should.
The idea of EMA filtering and sample rate reduction was offered by our DIY community member, Pablo Castro, quite a while ago. Sadly I could only try it today, and results turned out to be great! While controls were already very smooth, now they are even more precise, yet filtering doesn’t add noticeable input lag.
Note that for the new version to compile, you will need to remove old ADS1115 library from your IDE and install the new one from z_libraries folder in simchair4_software repo. That library is a fork by soligen2010 that allows ADS sample rate tuning.
If you are upgrading from MKIII version, please don’t forget to select your devices in device_definitions tab manually.
I have been able to calibrate my printer in a perfect way using a micrometer recently, and found that some clearances between certain parts may be too wide. That made me think that maybe we need to adjust models for a perfectly calibrated printer. Right now it seems that everything is tuned for a slight over extrusion.
There are a few problems that worry me:
How to reliably calibrate any printer? – We can use a method of calibration that assumes using a micrometer to measure the wall thickness of a calibration cube model printed in vase mode.
How will tuned extrusion affect durability? What needs to be changed in print settings? – This requires testing.
Is there a problem with an average factory-made printer at all?
So I decided to make a poll, if you’ve built something and used PLA for that, please select one of the options and write a comment about your experience. The comment part is important – because otherwise, I wouldn’t be able to distinguish real builders from bots.
I am happy to tell that our nice documentation wiki grows every day. Our awesome DIY community helped me to port MKIII docs, so now we finally have MKIV collective build process completely documented! The first lever body added is the most advanced one – single collective body with a physical throttle latch. If you need other lever bodies, just use this one as a reference.
You can find all of supported (and planned for now) MKIV hardware modules on the modules list page of the wiki. If you’re here for the first time and want to know more about the project, please visit the start page.
I have adjusted MKIV menu on the site accordingly.
I have been asked multiple times to change documentation format to wiki – so other guys who build Simchair could fix errors in manuals, or improve them, or even write their own.
So, here it is! I have already ported the manual for the collective base, fixed some errors along the way. My first impression is – a wiki is a MUCH better place to write docs, rather than WordPress pages. The result seems to look a lot better, formatting options are way richer, I really like how it looks =)
Hopefully, this step will help the project to grow further! If you want write access to the wiki, please contact me, and I will sign you up.
Here’s the MKIV stackable quadrant, the helicopter edition!
If you fly twin-engine stuff like MI-8, BK-117, etc – and also want to be able to fly warbirds sometimes – you’ll like the new quadrant!
The current, helicopter themed, version supports 2 axes with detents (for things like WEP and reverse in planes, implemented as button presses, because why not) – but you can stack as many of axis modules as you want. The default “GA” version that will soon be available will include 3 axes and trimmers.
This version is much more thought out than the MKIII one – so the latter will be outdated with its release. Each lever is equipped with a spring-loaded pull handle that allows movement past tactile detents on both ends of each axis and provides friction at the same time. Lever caps are fixed with screws – so you can change them to whatever design you like.
The first helicopter-themed version will come with spherical caps and no trimmers. I have just added support for it to the software.
The first MKIV variant of this head is a generalized device – it has 8 spring-loaded switches in it. This means, with the mode switch, we can use 3 sets of 19 joystick buttons each!
The head itself was updated to MKIV standards – it features 2 Ethernet sockets and an MCU RST button for easier flashing. The former mode switch on the side of the head no longer works as one (we have it on the base now!) but is left in place for generic purposes (e.g. gear, floats, etc, why not!). The 2-pot version is now a default one. Expect an updated manual soon!
Joy button presses on middle positions of the switch and non-spring-loaded switches support are not yet implemented, will be adding those a bit later.
Do you guys use MKIII switch modes and non-spring-loaded switches in your heads, or do you prefer a more generic approach of having a lot of joystick buttons instead? Please let me know in comments =)
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:
open the throttle past the detent, press and hold IDLE REL, close the throttle.
perform the startup as described in the Flight Manual.
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.
to close the throttle completely, press and hold IDLE REL button on your collective and close the physical throttle. The virtual grip will follow.
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 =)