Works great, it interfaces directly with Il2's FFB support
Works great, it interfaces directly with Il2's FFB support
Ddoes it? you better send me mine so I can check 
1has anybody documented a 3dprinted DIY Rhino ? like, starting from upper link and then integrating with @walmis motor kit ?
1same goes for vpc warbrd base, is it doable to convert it to Rhino motors ?
W@Roller25 did one, but not sure if it's documented
LNope, way too small
Phttps://www.youtube.com/watch?v=MUK2omoil2U It is possible to convert virtually any base to FFB one... with some immagination 
LSure, but at what point does it stop being a warbrd? I think he's asking if it's possible to use the warbrd base and just add motors, and a single 57BLF03 is nearly the same size as the gimbal system, you would need an entirely new base
L
LI totally expect to see smaller motor kits popping up, but it'll be a little while still I think
LThere are motors that would fit and work, but the warbrd's are really tiny, hard to fit all the mechanicals and motors in em
1we misunderstood - I would not try to pack the motors into warbrd base - just use the gimbal of it with a kit
1and then make another "box" for motors and electronics for Rhino components
1so the real question is, how would somebody convert a VPC warbrd gimbal to work with the FFB kit 
Rthats using a donor MSFFB2, so it's still having issues with the hardware deadzone and gear teeth feeling
PIt is only idea how to add ffb to any stick. Instead of MSFFB2 could be any system you want.
1would be lovely to hear more ideas for using a freely moveable gimbal like on a VPC warbrd base
1I feel like this upper solution of Proteus simpit will probably have too much leeway since it's mechanically connected three times (so to say)
1also, where to order cogs and pulleys online ? can you guys share your favourite suppliers (I'm in Germany)
WI can machine the small pulleys for the motors, the larger ones are usually 3d printed. Also AliExpress is a good source for everything, but there's a long waiting time.
1have you thought about selling Rhino Kits for DIY assembly ?
1(I'm probably not the first with the idea ^^)
WI have, but scrapped the idea for the time being, to better focus on optimizing Rhino production.
Phi, all, I started to read up on the 'break out' force setting, however there isn't much info on what it is and what it does. Per my understanding it's a force that keeps the stick 'in the ffb center' and unable to move until I apply a certain amount of force in pitch or roll axis. Does anyone have an idea on what it should be for the ww2 planes? I'd think it's different per airframe, does anyone have any recommended values for it?
RI 3d printed the propeler gimbal (has held up great so far) and cnc cut the Rhino housing from plywood.
Hwhat are the specifications for the controller board?
Hor is there a schematic for it?
Halso, is it fine to run off 24V?
H@walmis I was trying to make cable connections to your USB controller and found the onboard 2.5mm pitch headers didn't mate perfectly with my JST XH connectors. The pitch seems to be the same 2.5mm but the locking mechanisms are different. I did some research on the web and found this type of connectors with the same pitch called XHB that looks similar to what you have installed on the USB controller but not sure. Can you please confirm so I can procure the right type? JST XH: https://www.jst.com/products/crimp-style-connectors-wire-to-board-type/xh-connector/ XHB: https://www.lhecn.com/a2502/
LHE Electronicslhe_admin
A2502(XHB) Connector 2.5mm Pitch is replacement of YEONHO SMH250-NN connectors. 2.5mm pitch.It’s widely used in wire to board connectors.
WI have put the top level schematic in #showcase pinned. The motor controllers work at 12-24V, 30A max motor current.
Let me know what kind of specs are you interested in.
Let me know what kind of specs are you interested in.
HAh, sorry for the unclear formulation, i meant the dimensions so i can integrate it into my case.
WThanks
Here's the board dimensions
Here's the board dimensions
W
HThanks!
H@walmis Hi, I finally had a chance to put it all together with the motor/USB controller kit you sent me. As I was test flying the F-14B and P-51D modules with this newly assembled FFB stick in DCS, I noticed I would lose the stick control in the middle of flying and DCS would even stop respond to the ESC key. Sometimes I could unplug and re-plug the USB cable to the stick to get DCS to come back and respond to key strokes but at that time the stick would go limp and would not talk to DCS anymore. I also noticed, throughout this occurrence, VPforce FFB Configuration did not complain and the telemetry data were consistently getting updated. Have you experienced anything like this before? I tried the released and open-beta DCS and they both exhibited the same symptom. Restarting the computer with a fresh Windows 10 loaded up did not seem to help. Please help!
WThis sounds awfully like USB host controller issues, do you use a USB hub perhaps?
Walso an event log from the Debug tab would be helpful
WAlso if this happens during high forces could indicate electrical problems (bad grounding usually, or ground loops)
HNo, I connected directly to one of the computer's USB ports. Also, another piece of info, as long as I uncheck Misc-> Force Feedback in DCS Options menu, I seem to be able to go on forever without stick control dropping out but the stick stays limp due to DCS overwrite.
Wwhat if you reduce force to a very low value and try with DCS FFB enabled?
HFFB appears to have something to do with the drop-out. The grounding issue sounds very plausible. I'll reduce the string and periodic effects to see if anything changes.
WAlso you may try it with a hub if you have one
HWill do! I really appreciate your quick support!
Wnice build btw!
HThanks but I cannot take the credit. Credit should go to you, Propeler3D, and Washout! I just hacked my way through borrowing everyone's wisdom along...
H
H@walmis Hi, I'm still trying to debug the DCS freeze issue even though that I have improved all of the ground and power supply connections. The USB controller is now directly connected to a 24V lab power supply and the freeze issue still persists. I use a program called Wireshark to capture the USB traffic in order to understand the underline activities that cause DCS to freeze. I notice on the captured data that at some point the URB interrupt from the host (i.e. DCS) is not acknowledged by the USB controller. Maybe either something times out or prolonged waiting on the ACK causes DCS to hang. Funny enough, unplugging the USB cable to the USB controller after freezing forces the corresponding ACK's to be finally sent so these ACK's have been in the buffer all along and just didn't get sent timely. Have you seen anything like this before? Please refer to the screenshots and captured data for detail. The relevant data packets are:
USB Host to Stick URB_INTERRUPT
64992 46.373221 IRP ID:0xffffd782f98bc010
66728 47.427333 IRP ID:0xffffd782fe1196e0
USB Stick to Host URB_INTERRUPT
78621 61.816345 IRP ID:0xffffd782f98bc010
78622 61.816350 IRP ID:0xffffd782fe1196e0
Any suggestion is welcome!
USB Host to Stick URB_INTERRUPT
64992 46.373221 IRP ID:0xffffd782f98bc010
66728 47.427333 IRP ID:0xffffd782fe1196e0
USB Stick to Host URB_INTERRUPT
78621 61.816345 IRP ID:0xffffd782f98bc010
78622 61.816350 IRP ID:0xffffd782fe1196e0
Any suggestion is welcome!
WAh Sh!t these USB issues are hard to debug. And yours is the first such case to my knowledge. Did you try running it through a usb hub? Also could you check the FFB board revision number for me?
HI'm sorry to ruin your day. I'm like a magnet that seems to attract outliers. Anyway, I did try using a USB hub earlier as you suggested and observed pretty much the same freeze symptom. The revision of my Rhino FFB board is Rev. 1.2, dated 2022.06.02.
WThanks, I'll do some stress testing by flooding that endpoint with data.
WHopefully will be able to reproduce it
