MHi, Got the DIY Kit 57BLF03. I tested the kit once this morning, all went well. But when I plugin the second time to test, found out one of the motor will shutdown its power after a min. I tried restarting the power several times, same result. The configuration software detected the USB connected but cannot read all the data. I may have wrongly switched the motor1 data cable with the motor 2 power cable once, will this cause this problem? Thanks
BThere will apparently be a kit to FFB-etize the MFG Crosswind pedals, needing 4 holes drilled in the MFGs. I am not aware of a planned release date, but then I can't keep up with the backscroll here.
WThe motor shuts down automatically when it receives no data. Not sure what's the state of your setup currently and I'm also not sure how it's possible to switch motor data and power wires? I mean the plugs are all different sizes.
MThanks @walmis Fixed the problem. Yes, motor 0 receive no data because one of the data plug pin was pushed inside the case. So I open up the motor back cover and push it back, now all are working. 
VAre you flying DCS with these? Do you use a rhino joystick as well? I'm curious if DCS works flawlessly with both FFB joystick and pedals simultaneously
NDCS doesn’t understand FFB pedals at all. In fact, it treats the axes as if they were a joystick.
TelemFFB fixes that and implements pedal effects and dynamic spring mode switching.
TelemFFB fixes that and implements pedal effects and dynamic spring mode switching.
VAh okay so you have to run telemffb , I can do that- im enjoying my rhino without any extra software going currently
VThat sucks it doesn't have native support considering the joystick works flawlessly
VBut doesn't surprise me
Iyeah I am flying with a DIY rhino as well and for now it is flawless
IGood morning everyone! I have the Rhino N. 0007 and if possible I would need the .stl file of the USB B (female port) Bracket. My strangely broke in the part of the slats that block the female connector. I thank in advance whoever wanted to give me a hand.
Bhi if i buy kit with two motors and usb ... what else do i need
base i know but on electronic side of things ... is the USB the controler for servos or i need something else... and power suply does it just go to usb bord ???
sory for stupid questions ...
base i know but on electronic side of things ... is the USB the controler for servos or i need something else... and power suply does it just go to usb bord ???
sory for stupid questions ...
TPower supply and USB cord are required. Recommended also are some potentiometers and an emergency stop button. You will also need a grip but I am assuming you have one that is compatible but make sure you don’t need any of the optional adapters.
Bnice tnx
TAdd fans also on the recommendation list for motor cooling.
SToday while flying the Spit in DCS I heard a loud crack and the stick went limp in the Y axis. Fearing the worst I took of my VR googles and turned the Rhino off and on after a quick inspection where I found no obvious fault. I then preceded to try and replicate this, and it looks like my belt in the Y axis is way looser than the X axis causing it to skip. I also get a Fault_Encoder_Magnet or Fault_Unexpected_D_Current then the belt skips. Hopefully I have not damaged anything and it’s just the loose belt. Any way to tighten the belt?
Ithe new version doesn't support windows scale layout at 3840x2160 and scale layout 150%
Iafter launch with joystick and pedals
NCongratulations on being the first to report an issue. Not even sure how to start going about the resolution issue but will look into it.
How do you have the launch settings set up? You don’t want to start TelemFFB with any launch args. Just open the exe
How do you have the launch settings set up? You don’t want to start TelemFFB with any launch args. Just open the exe
N(p.s.) fix identified for the scaling issue
II launched TelemFFB as always and said yes to the auto-update after finished the new TelemFFB, which was displayed with the wrong UI size.
On the second error, I checked in System Settings the auto-launch and start headless for pedals and collective but I don't have collective, and because it is not visible, I couldn't enable the joystick option
On the second error, I checked in System Settings the auto-launch and start headless for pedals and collective but I don't have collective, and because it is not visible, I couldn't enable the joystick option
Ialso, it will be great to have a revert to last previous version as a safe
Nwere you on the very latest version before you updated to this version?
Nwhy did you enable auto launch for a device you dont have? 
OK.. so it shouldn't let you save under that condition but....
OK.. so it shouldn't let you save under that condition but....Nif so.. check this folder for your backup... if not.. well... moving forward... you can check this folder for the backup from the previous version
Iyes
Ithnaks for the tip about the last version, I didn't know
NIts a brand new feature that I shoved into the very last commit before this new version and didn't document anywhere.. 
NWere you able to get the new version started with only the pedals selected in the launch options? Because of the error state you may need to delete the system settings from the registry... Computer\HKEY_CURRENT_USER\Software\VPforce\TelemFFB you can just delete the whole TelemFFB key
Njust pushed a new build that should fix the DPI scaling, disallow erroneous autolaunch configs and allow you to at least startup with your corrupted registry settings (though you will see "cant connect to "FFFF:" errors)...
E@walmis Recently, I've been experiencing frequent protective shutdowns on the Y-axis. I will make a video to show the situation. At that time, I will also share my debugging and configuration files. Could you help me take a look and see where the problem might be?
E@walmis Recently, I've been experiencing frequent protective shutdowns on the Y-axis. I will make a video to show the situation. At that time, I will also share my debugging and configuration files. Could you help me take a look and see where the problem might be?
EThis issue often occurs during stall shuddering and the instant of firing the machine gun, and it always results in a shutdown of the Y-axis.
WHey, try reducing the damper/inertia/friction LPFs in the configurator, I see you use all the effects simultaneously (damper/inertia/friction) so that might cause instabilities with the current settings.
EWhat would be the appropriate values to set for each LPF?
WTry experimenting, but I've found down to 2Hz is slow, but reliable
WNo worries, your Rhino is safe, motors enter into self protection if there is unusual stuff happening.
You can follow the manual to retighten the belts:
https://docs.google.com/document/d/1YL5DLkiTxlaNx_zKHEYSs25PjmGtQ6_WZDk58_SGt8Y/edit#heading=h.z337ya
You can follow the manual to retighten the belts:
https://docs.google.com/document/d/1YL5DLkiTxlaNx_zKHEYSs25PjmGtQ6_WZDk58_SGt8Y/edit#heading=h.z337ya
PHey guys how do I go about downloading & installing the new TelemFFB software? can I just do a git pull? or should I reinstall?
Plol, nvn I used my brain & found the download
Nif you're running the exe package, it will auto-update
Poh I've just been using the python install of telemffb & doing a git pull to update, but I just dl'ed the new version & used the .exe, will that be ok? cheers
Palso thanks heaps for all the work you & others done with this
Nyeah, just make sure you grab the latest zip from #VPforce-TelemFFB . The 'stable release' posted on GitHub is a snapshot of the WiP branch from a couple days ago.
Poh the bottom link?
P3017d8df
Nyeah.. or you can hit the link in the pinned messages in that channel which should bring you to the download site with the page already sorted by newest
Pyeah sweet looks like I dl'ed the 3017d8df one, so I'm on the new one?
Nyessir