Sergey_Pe

Well, quite frustrating since your programming sequence looks correct. OK; for a start let's check if your chips are really working in analog mode. After you wire up VCC, OUT and GROUND and rotate the axis, does the OUT signal change? The second question- have you defined the direction of axis rotation by shorting the DIR pin either to VCC or to GROUND as described in the Wiki? BTW- merry Christmas and happy New Year!

If the chip is really a 74HC165 (the description says serial input/ parallel output while it should be the opposite)- yes, it can be used with both controllers.

Absolutely correct. But this is a thread about MMJoy2, not TM controller, and the guy who asked about the boards didn't mention TM at all. So it might be an easier solution, providing that MMJoy is working with both shift register types.

Or you can simply buy THIS or THIS.

T80 switches from Salecom are quite good, being an almost 1:1 copy of C&K 7000 series. But be careful- there is a lot of "clones" of a real T80 series at Aliexpress that might be quite unreliable (I've seen a lot of these clones breaking down). To be sure look for a "Salecom T80" at Aliexpress; the real ones have a "Salecom" logo on the switch body, as in your picture. Speaking of the other options- this is a locking switch that is being used in real planes (like Cessna); both the 2-position and 3-position versions are available, but they may be quite expensive/ hard to find. I've managed to pick up both versions unused on eBay together with a Cessna knob.

An encoder is essentially a pair of buttons. And as with the regular buttons, you can connect them to the shift register inputs; diodes are not required but the pullup resistors are. This way you'll get two physical buttons that can be defined as encoders in the "Joystick Buttons" tab. I'm just guessing here as I never connected a 3008 to MMJoy myself, but the logic is that the shift registers are not sharing the data line with the SPI-connected peripherals. For each shift register (single or daisy-chained) you are defining the CS and Data pins in the configurator separately. However if you use, say, the TLE50XX sensors for the axes then these sensor boards WILL share the MOSI line with the 3008. Still (as mentioned in one of the posts above) I'd recommend to move to a FreeJoy project based on a BluePill (STM32) board. It's way more advanced/ stable and offers an excellent online manual (in English as well). Just an example- with the FreeJoy you don't need the pullup resistors for the buttons/ shift registers. What's also important is that the project is constantly evolving with more functions added by the community requests.

Well, I've finally installed an AS5600 magnetic sensor into Saitek throttle. A small round magnet (approximately the diameter of a lever bearing which was cut flush with the lever body) was super-glued to the lever, working as a new bearing. A small circular PCB with AS5600 was hot-glued in place of a stock resistor as seen on the picture. Then AS5600 was calibrated to provide a full output voltage swing within a lever movement angle. Of course it works like a charm, as expected. The trick is to find a a magnet with the appropriate diameter (I had one as a leftover from one of the old projects).

No it's not. How did you define these buttons in MMJoy configurator- as "Button (norm)"?

As opposed to Shift, Ctrl and Alt keys, the Win key is typically not supposed to be duplicated on the right side of the keyboard- it depends on the manufacturer. If you don't want to use an additional app, then buying a different keyboard is the only option.

It's an encoder.

No, because it was an initial small batch for Gunfighter base owners. Full-scale production will start right after the Chinese Year.

Sorry, you are right- I've automatically mentioned the old connector as I'm still using it in all my VKB gear: it's more reliable than the current 3-pin proprietary version. Not sure how easy/ difficult it would be to install a mating part into a Gladiator base... The info about removing the connector (both Rev. A and Rev. B) from the adapter is valid anyway.

No, it's not. In earlier versions there was a threaded pin that had to be screwed out to free the connector, now it's just a rubber block that holds the connector in place and is very easy to remove. And then the connector goes out. Besides, the connector itself can be purchased from AliExpress or eBay- here is the link.

In case of VKB everything can be fixed (seriously!). The magnets on the axes that are used in the sensors are glues to the shafts (threaded pins) of the axis bearings. In extremely rare cases (especially with an extension/ heavy grip/ strong springs) one of the shafts can get loose so that the shaft + magnet start rotating, hence the calibration shift. You'll need to take the gimbal mechanism out of the body, remove a Y-sensor (2 screws) and tighten the nut that holds the Y-axis shaft in place. Here is the photo; I don't have a Gunfighter, this is a previous VKB gimbal, but it's very similar (just the dampers are missing). The nut that you need to tighten is marked with an arrow.

Sokol is keeping an eye on everything interesting and useful coming up in simulation area. And he is always eager to share his findings which is great!

Just to clarify- with all my huge respect to Sokol1_br, who is doing a lot for the community, MMJoy2 was written by a different person. It's Mega_Mozg, who is now a chief software designer at Virpil Controls.

All the supported A/D modules are listed under the "Source" tab in MMJoy configurator, and these are MCP3201-3208. MMJoy firmware will not be updated as the project is closed and the developer is now working for Virpil team.

You are welcome:).

All the axis have to be calibrated. If you choose "auto" then you need to move all the axes to the extremes every time you connect the joystick to the computer which is inconvenient (from my point of view). I prefer "save with center" option which has to be applied once using the "calibrate helper", and don't forget to save the settings to the device as you do with axis/ button assignments.

How did you calibrate these axis? The Axis to Button function is using the raw axis range that needs to be set first. If "auto" calibration mode is used, then the range is set only after the joystick is moved to the extremes. Try using the "saved" mode, calibrating and saving the range first.

It looks like a part of your text is hidden behind the picture. Are you using the short-press buttons or ON-ON switches? It might be that you are missing the logic behind the different logical button modes. "Switch On" means that when a physical button is pressed or held there will be a brief logical button press and then immediately a release. Typically you won't see it in Windows game controllers setup screen as the press duration is very short. Try a Button (norm) mode instead- it will deliver a logical button press as long as you have a physical button pressed.

Hey rel4y, No I haven't. So far I used the blue pill's internal ADC with AS5600's in a throttle quadrant project without any noise-related problems. Maybe I'm lucky with the USB ports on my PC... Anyway I consider the internal ADC as an auxiliary functionality- TLE5011 (or TLE5012 after it's included in the firmware, as promised) would be my sensor choice. And yes, I'm using Sprint Layout but no plans for any FreeJoy shields so far. Best regards

Wrong. Calibration always needs to be done for the actual angle- this is exactly what it's done for. Otherwise you won't get a full range of OUTPUT signal for the particular axis. However the INPUT signal with the 360 deg. sensor will be much smaller, so much of the ADC resolution will be lost, as you correctly mentioned. I would strongly recommend using AS5600 sensor- calibrating it after installation (before MMJoy calibration) you'll get a full 0-5V voltage swing for any angle more than 18 degrees without any hassle with the magnet/ sensor positioning as with SSxx or Allegro sensors.

On your second screenshot- DZ boxes. You'll need to set "DZ center".

FreeJoy project. I've switched to it from MMJoy2 (which is very good) for my own projects. More flexible, works with the same sensor types as MMJoy, much more user-friendly configurator software, well-documented. Constantly evolves based on community feedback, but is 100% stable already now. The board (STM-32 based) is as cheap as ProMicro.