Thanks. So as I understand, the effects tab doesn't affect DCS in any way? It doesn't matter whether I have various options checkmarked, they will work regardless?
Spring is overridden by DCS, however Damper and others will work, since DCS doesn't control the damper effect for example. The whole idea is to make the stick work as a regular springed/damped stick that you set it in the configurator when no FFB aware programs are controlling it.
Oh jeez, reverse polarity could kill most ICs, depends on luck. That TVS took the most of it. You can try unsoldering it and checking for shorts on 5V and 3V3 lines to GND.
Got everything wired up to bench test and I am getting smooth movement in the motors like the anti-cogging is working but not getting any signal to the VP-Force Software that I can tell. X, Y, dx, dy, etc are all "-" and do not change when plugged into USB or with power on. Is there a setting I am missing before I can start seeing input from the board?
idk if this is part of the telemetry or dcs, but with the SU-25, when you extend the airbrake, the stick "clicks" back and forth weirdly. It doesn't feel like a normal effect, feels like a bug
Motor signal wires needed to be swapped on one end of the plugs. I noticed on the board the plug was B/A and on the motor the plug was A/B. Cable needed to have a crossover between the two plugs to get A/A and B/B to match.
The cables as supplied with the kit. I went back and looked at pics of other kits and they have it configured with the crossover as I mentioned. Based on that I think mine is an isolated issue but probably fair to say if you DIY then just double check.
When I plug it in, I get the normal beeps from the base, but windows throws an error saying the device isn't recognized (Device Descriptor Request Failed)
It briefly showed up in the FFB configurator earlier today when I was trying out different USB ports to see if I could get one to recognize it, but it went back to not being recognized again shortly thereafter, and crashed the configurator in the process
I got this same error when I plugged in my board for the first time due to an improperly wired USB connector. If your Rhino was working previously maybe something jiggled loose between the main board and USB plug. @leninjahd described something similar above too when I asked about my error.
Could be the USB wiring on the usb socket side. You can try to unscrew it and pull it from the front and check if any wires didn't come loose. Either way it's a bummer, but I'll send you a replacement cable or main board if needed.
Hi. Got life in one axis of my kit build for the first time. (Waiting on belt for other axis) It all feels really nice, however there is quite a lot of natural dampening going on. I want to use this for helis as well, which will mean I want an almost "floppy" stick with very little resistance/dampening. How can I achieve this ? Natural Damping compensation goes some of the way, but any higher than about 17% and I get sound uncontrolled bouncing off the limits.
nice work m8, what's the 'extra' roller for that looks adjustable, at the fron of the picture touching the belt. Is that just to adjust the belt tension?