The configurator has a setting for that.
The configurator has a setting for that.
PI thought it did but I couldn't figure out which one did it, you got a screenshot maybe? cjeers for the help m8
![[OR] SerGeant](https://cdn.discordapp.com/avatars/290181622832168961/338cff3e564800fa5a1068e9c25e28f5.webp?size=40)
[Hey everyone,
The Y-axis motor of my Rhino suddenly died.
USB Connection lost and buzzing noise on USB-Type A connector and USB Hub.
When i unplug the Power connector of the motor, the system comes alive.
Plugging the motor of my other rhino works fine. PCB ok, Motor defective? Any chance to get it back running?
The Y-axis motor of my Rhino suddenly died.
USB Connection lost and buzzing noise on USB-Type A connector and USB Hub.
When i unplug the Power connector of the motor, the system comes alive.
Plugging the motor of my other rhino works fine. PCB ok, Motor defective? Any chance to get it back running?
LCross check by switching to the USB port and 
supply of your other 
to pin point the problem is inside the other if you didn't already
supply of your other to pin point the problem is inside the other if you didn't already[Already solved. Motor is defective. Another motor works fine in this rhino.
Walmis helped me out.
Walmis helped me out.
SHi @walmis i require you insight into this: today i did a small opsy and accidentally lowered a height adjustable table onto my rhino (it pressed down on the grip which was on a 200mm extensions and the rhino was off) it was enough force to crack the 3d printed tightening collar on the extension (QR4Rigs Extension) so in response i went back to a sidestick Layout with only the winwingadapter and my F-16EX grip but after calibrating the rhino again it seems the stick has a slight left tendency (wen in the accident the stick was leaned the other direction) im not sure if i broke the rhino or its normal since adding a balance spring doesnt help
Scurrent settings
Ayou might need to re-calibrate both your axies?
Abut also there could definitely be internal damage on the gimbal
Ayou can easily unscrew the 4 bolts holding the base of the leather cover, and lift all that up to inspect things inside
Aalso probably worth seeing if the aluminum bar between the gimbal and grip is bent or something, which you can also inspect by the cover thing above
SA bit late in the day to do it today but i kinda doubt it because i dont think the bar should be the weakest point in the whole system (not sure but the 3d printed extension should break b4 the bar right?) but then again it could be any of the small Parts that broke in it
Awell i wasn't there for the incident, so impossible for me to say, but i think at the vary least, start with a re-calibration of the axis, then if that doesn't fix, do the visual inspection check above, which allows you to see various parts
SAh s*** i just thought it wouldnt make any sense that it would have a left tendency since it would have been bend to the right but ive got the rhino currently mounted the other way round compared to when i had the opsy so it is still possible :AkashiSweat:
SI guess a quick check would be to turn the grip 180° and see if it tilts the other way in case its just the asymetric grip weight
CHello,
Is there a way to define a dead zone, thanks for your help.
Is there a way to define a dead zone, thanks for your help.
HI don't think there is. It would mess with the FFB I assume.
Ptry playing with the breakout force setting in effects
DI'm a long way from my PC (on vacation!) but from memory I don't think Telemffb handles this (???). Nor the configurator (but I'll have to confirm this with those who have a better memory than me).
SIf i wanna disassemble the winwing adapter i just remove the screws on the face right?
SYou can use 3rd party tools like Joystick Gremlin
E@walmis returning to this topic is I have now three Rhinos connected to my PC. The problems are with VPForce configurator. Devices work just fine
Issue:
Joystick & Collective & Pedals connected:
Issue:
Joystick & Collective & Pedals connected:
- Joystick fails to configure
- Collective fails to configure
- Pedals CAN configure
RHello everyone. I have a small issue with my new Rhino (arrived earlier this week):
Every time DCS starts, the Rhino controls in DCS reset to default (including axes that don't exist and all keybinds are cleared). This happens with every module, and only with the Rhino (my Virpil controls work just fine).
This means every time I load a new DCS session I have to load the input profile manually, for each aircraft I want to fly. This is fairly annoying... Is there a way to fix that, please?
Every time DCS starts, the Rhino controls in DCS reset to default (including axes that don't exist and all keybinds are cleared). This happens with every module, and only with the Rhino (my Virpil controls work just fine).
This means every time I load a new DCS session I have to load the input profile manually, for each aircraft I want to fly. This is fairly annoying... Is there a way to fix that, please?
VDo you maybe plug it in the different port every time? It could be worth to check if you get different UUID everytime you plug it in
RNo, the USB cable is connected to the same hub my other sim peripherals are.
RI'll check next time anyway if there is some device ID shenanigans going on, but the cable stays where it is 
VYeah, I can't think of anything else than UUID getting changed each time. Why it's happening though, I have no clue
RIt's a good suggestion.
RI have my BIOS set to disconnect USB power every time my PC enters S4/S5 state, but that affects all my USB devices not just the Rhino. Perhaps somehow this confuses Windows?
VIt might be, never played with that option.
RI only have that enabled because I have a pre-amplifier that I use as external sound card, which has an OLED display that stays on if there is power, and I want to prevent burn-in.
TI was having a similar thing and rather than use the BIOS I went into device manager and under each USB device properties/power management tab unchecked “allow this device to wake”. This turned my USBs off while the PC was off. You could try this as an alternate.
RIn that case you’d also need to use the kill switch more often on the Rhino, wouldn’t you? Is there a downside to that?
TI don’t think so, I believe it is the recommended method to turn off power when not in use.
TSince the power supply isn’t switched, the E-stop is the only switch
HHi Everyone, I have a Rhino and love it! I'm selling my Brunner CLS-E FFB Joystick for like 700USD plus shipping in USA only. I made a youtube of it showing that it works. Shoot me a DM if you are interested.
EHow can I get rid of this icon? Pressing the cross does nothing. It doesnt respond to anything I do. This ain't the first time this has happened.
EDisconnecting Rhino doesnt help either
EKilling edge process doesnt do anything
Athere's a task called like Widgets in the task manager that killing it will remove it
Ai made a post a while back how to permanently get rid of the edge version of this, since it doesn't seem to respect the advanced setting: https://canary.discord.com/channels/965234441511383080/965234441511383083/1259226124731416617
A(i've been running that fix for a few months now and it's never re-appeared, and i've had no ill side effects of killing that process from ever running)
Ajust a reply bump in case ^
Si booted up War Thunder again and thought i could do some sim flight but for some reason WT doesnt recognize any button inputs from my WinWing F-16EX grip any ideas how/if this can be fixed? (rhino+WW adapter+WW F-16EX Grip+Griptype is WinWing Adapter)
LDo the buttons show up in Windows?
Syes
SWT does recognize the axes just no buttons so it seems to see the rhino but not anything through the adapter?
LWhat about here?
Sthe rhino/grip are working normaly (at least in DCS and MSFS) just everything that isnt an axis isnt getting recognized
NIf you can see the buttons activating in configurator when you press them, there is no reason why WT wouldn't. Unless it has some sort of "too many usb devices" issue like IL2 does.
Slooks at all the MFD frames might be? but shouldnt axis also not work then?