@@walmis I may have missed your reply but is there any consideration for this: a button to act as a limiter for axis excursion? So that when the button is depressed, the affected axes will only have a limited range mapped to the full stick excursion. Virpil implements this as a 'ceofficient of division -- basically scaling the raw output by a user specified amount.
The relevant box is labeled 'axes zoom'. In the 'action button' field I enter the logical button I want to act as the modifier. In the coeffieicent of division I enter the 'scaling amount' for the axis I am adjusting. In the VP config software, this could be a 'box' in the 'settings tab' . Initially, it would be fine if it applied to all axes uniformly for simplicity.
If building a kit .. do the motors handle stick position as well? Or does there need to be a separate position / hall sensor systsem apart from the motors
If you mean the gimbal? PLA will last a few months, but will eventually fail (in many areas). I have just reprinted in PETG and it definitely seems like it will last much, much longer (if not forever).
350.4W 24V 14.6A Single Output Switchable Power Supply 24 Volts 14.6 Amps Features β’ AC input range selectable by a switch β’ Withstand 300 VAC surge input for 5 seconds β’ No load power consumption β’ 1U low profile β’ High operating temperature, up to 70Β°C β’ Protections: Short circuit / Overload / ...
Having what I hope is a stupid me issue, but my TM Warthog grip seems to only register the trigger and it lights up everything in the VPForce software. Yes, I've verified it's plugged in correctly (tried both extension cable, and directly to the grip) and verified the buttons work by plugging it back into it's old base. I ran the debugging profile too and it just spammed the FF line with button trigger presses showing 00 00 repeating. This is NOT using the passthrough port you installed, was trying to just use the native interface. I also tried power cycling/unplugging USB. Everything else seems fine and during a test flight the base functioned as expected.
We figured out that the USB voltage on the hub was too high - 5.6V, hence the grip didn't register the 3.3V signaling correctly. When plugged directly into PC it works correctly.
To build on this, I believe this hub was previously faulty its not an issue with the Rhino or hubs in general. I was just running out of shit to plug shit into.
If anyone can help out with the install process for the DCS Telemetry app that'd be cool. I have python installed & the .zip file downloaded from Walmis's github but I'm lost as to what to do with the cmd prompt stuff, I'll be online for a while if anyone is keen to help? Cheers
alright, looks like for some reason the installer for python that I got from their site didn't install correctly for this to work, instead I did what Skypickle told me to do in cmd type python & it lead me to windows store, once I did the python install again through the store this time the commands you gave me worked
I haven't read everything but, would it not be possible to add the base in the simshaker software? It would be easier then to make profil with different effect