yeah, when I push it hard down it works but on release it fails…not workable really
yeah, when I push it hard down it works but on release it fails…not workable really
![Prometheus [Prom]](https://cdn.discordapp.com/avatars/777496628579401739/90d1e9e0a05c7bafd59a74ba942bd870.webp?size=40)
Pmine got sent after a week, add on vacation
(Help please my rhino has started losing aileron feedback during flight
I get a mid freq vibration for about 5 secs then the ailerons go limp with no force at all
Vp rhino configurator shows a motor encoder fault
A reset brings back feedback for about two mins then same again
I get a mid freq vibration for about 5 secs then the ailerons go limp with no force at all
Vp rhino configurator shows a motor encoder fault
A reset brings back feedback for about two mins then same again
HWhat value has the middle position of the axis?
HI assume something wrong with the position encoder on the motor driver circuit. Probably something @walmis needs to look into.
(I will check next time in on my rig and will open up to see if anything loose
WThat's probably just general instability, sometimes it throws encoder fault when it loses track to fast oscillations. Can you show your settings?
![Prometheus [Prom]](https://cdn.discordapp.com/avatars/777496628579401739/90d1e9e0a05c7bafd59a74ba942bd870.webp?size=16)
Phaving tested if a ps2 plug is also a poor fit, it was…..so to resolve this I engaged QR4rigs to disassemble the adaptor and use the pcb in one of their extensions….at a cost of £50. A little bit disappointed tbh
TWalmis is back, you can try pinging him to help. He is usually able to troubleshoot any issues with grip adapters pretty quickly.
SHello everyone! Set up my Rhino today and have a bit of a strange issue. I noticed that (unsurprisingly) I have to rebind all of my controls, as although my WinWing F-16EX stick is the same as before it recognises that the base has changed. I copied the contents of the lua config files for my old stick/base combo in the hope that the controls would map over, and it seems to have mostly worked, apart from the trim hat.
SIt seems like the VPForce software is recognising the trim hat as somehow 'different' from the other switches, like so:
S
SAll the other hat switch presses correspond to buttons on the right-hand side of the window, but the trim hat presses seem to correspond with this bit on the left-hand side
Pspeculating but the winwing conversion might be generic, have you calibrated in windows usb games settings?
SNot entirely sure what you mean by that, sorry! Is that a program I need to open?
TThere is an option to do hat switches as buttons, may have got that setting swapped from original?
TOn the settings tab
SThat was it, thank you!
SFor some reason, I had to check this box but only for the trim hat (Hat 1). The others worked fine by default!
PI see number 7 is lit, I had that too, couldn’t figure out if it is feature or a bug.
SNo, that's intentional I believe - buttons 1 and 7 correspond to the resting positions of the flip-down trigger and pinky lever respectively. They're bindable buttons 
Pthanks!
Ppost if your LUA sets up nicely, it never worked for me, you must have the ‘secret sauce’ 
SThe lua mostly works, but still not with the trim hat - I think it might be something to do with the fact that this diagram implies it's actually an 8-way hat
SSo here's the issue: I load up DCS and open the controls menu for the Mi-24P, which has my controls from the WinWing stick/base copied over to the WinWing stick/Rhino base. Most of the keybinds work as intended, e.g. the depress of the trim hat is written as JOY_BTN19 which corresponds correctly. However, the up/down/left/right of the trim hat are displayed as JOY_BTN_POV1_U, JOY_BTN_POV1_D, JOY_BTN_POV1_L, and JOY_BTN_POV1_R respectively.
SThe VPForce software has instead written these inputs to 45, 46, 47 and 48, and does not recognise the diagonal inputs as buttons.
(@walmis here’s my settings
(I had the master gain at 100% too
NWhat version is the latest Rhino firmware? Mine is v1.0.16. Is this old?
Hno, it‘s the latest. you‘re fine
NThanks. I am waiting for a new firmware. I already asked Walmis to include my grip support.
HYeah, me too. For the support of custom fan control.
SHey everybody,
Since weeks now, I don't understand why my Rhino self disconnects while I'm holding it about 3/5 seconds during a hard corner while in Dogfight on IL-2 or DCS.
Since weeks now, I don't understand why my Rhino self disconnects while I'm holding it about 3/5 seconds during a hard corner while in Dogfight on IL-2 or DCS.
SIt's very disapointing.
KWhat is your amps settings in the configurator?
CThat is not normal. Most likely a setting issue. Also what do you have to do to recover the ffb?
HCheck the telemetry in the VP configurator while holding the G and see if the Amps exceed the set Amps, if so you need to reduce the spring force a bit. When you overpower the max strength of the motor (which is easy with the wrong settings) it will quit and need resetting.
HBasically you want settings, that do not exceed the maximal amps when you pull maximum deflection with a given spring setting.
S
Smy actual settings
HSpring 100 is too much probably. I drive mine at 75 or something (at most). However the interesting part is the telemetry left of what is depicted in your screenshot.
CWow that is some serious spring gain.
BSpring is usually overriden by pot 1.
Its at 100 for me as well but the pot is at 40%
Its at 100 for me as well but the pot is at 40%
BBut that part is cropped out from the screenshot
HWithout seeing the actual telemetry it's all guesswork
H@Subtile The math goes master gain x spring gain x poti (if set to spring). The result shouldn't be any higher than 70-80%, otherwise you will reach max amps before you reach max deflection - and this is the cause of the tilt out.
HYou could also increase the max motor current to 30A. Your motors will heat up slightly faster under max load though. -> earlier engagement of the fan.
ASpring gain is most likely not the reason for the disconnects (I assume by disconnects you mean it does that beep and it turns off the motors forcing you to cycle the emergency switch).
The problem is most likely one of the lpf settings in conjunction with other effects
The problem is most likely one of the lpf settings in conjunction with other effects
SOk, I'll try some parameters
AWhat are your effect settings? Perhaps a screenshot of those
A(Also do you have an extension?)