Hey all - building my own DIY Rhino and have got to the point where i need to order steppers and USB
Hey all - building my own DIY Rhino and have got to the point where i need to order steppers and USB interface. Any advice on which ones to go for?
TIf you are building from the files that are getting shared here, most, if not all, of them are only designed for the 57 series motors. The big motors won’t fit the same housing.
SPerfect! Thanks @TheAmazinGreat. Final thing, The Thrustmaster warthog grip works as standard doesnt it? I dont need an adapter or anything?
MNo adapter needed.
SThanks!
BNevermind, it must have been a bad connection in my extension. I took everything apart to make sure I didn't have any bent pins, and it works now after putting everything back together. Weird that the grip was getting power, but buttons weren't registering on the Rhino, but all is well now.
BHi, i need some help with the A2A Comanche. I can't get autopilot following to work, did some searching in this channel but found no solutions. The TelemFFB software is running fine otherwise, all the effects are working, axis are not bound in MSFS.
Sdo you have the 1.0 release or the WIP version with GUI?
Bit started working yesterday evening...thanks for following up!
BYou mean the Telem software right? I got the GUI version, should i try another?
Sjust making sure, someone the other day was having trouble with the a2a and was using the 'stable' 1.0 version. if you have a bunch of purple sliders, you shoudl be good. what are symptoms exactly
Bbunch of purple ones, some green ones, all effects are working fine and are tuneable. only the autopilot following setting is not working, yoke moves around when i do autopilot turns, but the rhino stays centered
Sare all the sliders inside axis control at default settings?
Byes, similar settings
Show unsimilar? the X trims will contrl how much an autopilot would move things.
Bi played around with them, but nothing changed
Bno movement at default position or 100%
Si havent checked it recently but i think the a2a autopilot is pretty gentile.. it doesnt move all that much. and you have to trim elevator so its not blinking the up/down indicators
Bso all sliders at 100% is maximum ap following movement? the bank is gentile, but pitch can move quite a bit i think, but there were no forces noticable at all
Sthese sliders are weird. 'physical' means that applying 100% trim would move the physical rhino stick to its 100% limit. 'virtual' , which can go from -100 to +100, controls how much offset is sent back to the game, to move the virtual stick, becuase of the way the game assumes you have a regular spring center joystick. it makes more sense in elevator- if you shut off the spring force and adjust trim while keeping the stick centered, the plane should not pitch up and down (you will however see the virtual stick moving). the virtual y slider is adjusted to achieve this. if you are not getting proper roll movement, keep physical at 100 but try different values of virtual x, maybe change 10 at a time
Smaybe number481 can explain better 
NI picked up the comanche a while ago, but I've never really flown it.. and I don't really know how to use the autopilot.. but at least in heading mode, the aircraft is not activating the AP master simvar, which means TelemFFB has no idea the autopilot is active...
Smaybe thats why i thought the feeling was gentile. i know it moved a little bit but might have just been from gusts or soemthing
Nif the autopilot uses trim, and the trim was moving, that would move the stick regardless of the autopilot mode.. but AP following works a little differently than trim following. The trim following uses the physical/virtual offsets you describe above. AP following is a lot simpler. It just enables a static spring force and tells the joystick to "follow the axis". Also possible it worked at one point and an update from A2A did something with the autopilot thats now using an L:Var or something
Boh alright, that explains it.. relevant L:Var is ApMode if that helps
NIts great these guys are able to do all sorts of cool stuff internally with L:Vars and all.. but I wish they would copy values to standard simvars where applicable... I'll have to see if I can come up with a way to do dynamic simvar subscription based on aircraft. Not looking to start subscribing to every random L:var different planes use and putting a bunch of ifs in the code for specific aircraft...
BYeah its a real pain trying to set up LED profiles for my virpil stuff, got pretty good in searching and finding LVARs this way. The Comanches Autopilot has four states, which is why they use a custom LVAR i'm guessing.
MHey, A2A dev here. Unfortunately sometimes weird things happen when we drive those simvars, or sometimes we can't set them at all as there are limits in the sdk. But I'm open to suggestions for improvements.
MIn the case of autopilot, it's fully custom as the stock MSFS code is unsuitable for this model. One thing I'm aware that doesn't play well with FFB on our end, is the automatic disconnect when the joystick is deflected above the threshold (75% defletion)
N1.) Its awesome that your here and that you have a Rhino.. I wish more devs did, and had FFB in mind when working on their aircraft, even if the sim doesn't provide any framework for it.
2.) I meant no disrespect and I do understand how limiting the SDK is in a lot of cases. The FlyInside guys, for example, have to do some really awkward things to keep their flight model separate from the native helicopter flight model.
2.) I meant no disrespect and I do understand how limiting the SDK is in a lot of cases. The FlyInside guys, for example, have to do some really awkward things to keep their flight model separate from the native helicopter flight model.
N3.) It would be really cool to develop some custom secret sauce for FFB between the aircraft and TelemFFB so that it could not only understand the autopilot, but the aircraft could also understand when the axis movement is in response to the autopilot, vs the user actually deflecting the controls
MNo worries, I understand it can be frustrating when you try to write a software that works with every aircraft out there. On our end, we have to deal with at least three separate FFB implementations (Brunner, Xpforce, Vpforce) and each of them has different logic, simvars dependencies and own set of issues, lol.
MI haven't yet tested my VPforce in MSFS, as other developments had higher priorities, but I hope that at least I'll be able to improve our FFB compatibility when working on the next aircraft.
BI have been away for a while for various reasons. Today I'm back in the saddle (cockpit?) and am trying to get the HPG integration working. I have disabled the cyclic axes in MSFS and enabled axis control and the FTR and FT reset buttons on my stick. When I move the stick, the cyclic in the game does not move. I must be doing something dumb -- any ideas?
NMake sure you’ve got enough spring force enabled on the joystick that it can properly center. TelemFFB won’t start sending axis position until it initializes (centers) the joystick.
BNovember 4 8 1 you are Da Man. That was it! Thanks for the quick reply.
BWell shucky darn, I'm having what appears to be the same issue with the H160, Build 57. TelemFFB looks just like the screenshot above, spring is enabled in the Configurator... ?? (Same Rhino/stick config in MSFS that I used with the H145.)
NI haven’t tested the latest dev builds, but I assume they still work or else @exil35 would let me know.
Don’t forget to set up the trim release binding for the 160, too (msfs icon will be a red x while sim is unpaused if it’s not set).
There’s new in-sim settings for the newer versions related to setting up for FFB support https://davux.com/docs/h145/SETTINGS.html#setup-v2
Other than that, the 145/160 work the same way.
Don’t forget to set up the trim release binding for the 160, too (msfs icon will be a red x while sim is unpaused if it’s not set).
There’s new in-sim settings for the newer versions related to setting up for FFB support https://davux.com/docs/h145/SETTINGS.html#setup-v2
Other than that, the 145/160 work the same way.
BThank you. I'll check things tomorrow. I didn't realize the trim release stuff was specific to each aircraft.
NNo problem. I need to make it so the “red x” persists even after you pause. Otherwise you don’t know anything is wrong if you pause the sim before looking at the TelemFFB window 
EI haven't been able to try the latest 160 build but if it works for the 145 it should work for the 160 as well.
Are you sure you are on "none" and "hardware" on the 160 tablet as well?
Are you sure you are on "none" and "hardware" on the 160 tablet as well?
BI completely forgot to check that. Thank you!
CAt some point in the past I think I set up my rhino to have a forward offset center point. Today, I rotated my base 180deg to get better clearance with my SimFab chair (brilliant idea I stole from someone here). For the life of me though, I can't remember how to reset or flip the offset.
CI figured I had just done it with endstops and axis rescale, but resetting that does nothing.
CAww heck, disregard, I figured it out. It was because I was in a DCS aircraft and it was applying a new center point.
WThis may seem like an odd question, but I have a neurological condition that requires I ask this.
Can and how would the Rhino counteract an ~8hz oscillation of input with an amplitude of +/- 10 to 15% of the intended input force? Does it have the ability to smooth/dampen that level of variation of force input?
In a mechanical dampener system this would be smoothed out by the resistance induced by the flow of hydraulic fluid... how would/could the servo coding be adjusted to mimic that dampening effect?
Can and how would the Rhino counteract an ~8hz oscillation of input with an amplitude of +/- 10 to 15% of the intended input force? Does it have the ability to smooth/dampen that level of variation of force input?
In a mechanical dampener system this would be smoothed out by the resistance induced by the flow of hydraulic fluid... how would/could the servo coding be adjusted to mimic that dampening effect?
TThere are dampening and friction effects that can be tuned by the user. This is then all done via electronics rather than by hydraulic fluids like you mentioned. As far as your use case, it’s hard to say how well it could manage those oscillations but from my experience the dampening and friction can truly be felt and tuned so I think it is possible.
TWith no feedback from a game or in games that have no feedback implemented the Rhino behaves like a standard spring stick but has all the features of the other high end bases out there in terms of tuneability for friction, dampening, etc. So you could crank the dampening up to help with the oscillations. Maybe also crank the spring down so you have less force needed to push the stick to the required deflections.
TYou would ultimately end up tuning for your needs but hopefully that helps show how things could be adjusted.
WFor what it's worth I was thinking if it couldn't mimic it through code, it could be done with a 2 axis hydraulic dampening using something like 1/12 scale RC offroad truck dampeners mounted between a custom housing and the stick. Would be tricky to tune it, but might be fun to design regardless.
TThe dampening and friction effects built into the Rhino’s base software options would be equivalent to the 2 axis hydraulic dampening as you described. Much easier to tune though because it’s all done on a slider in the software rather than changing fluids/geometry of the physical dampeners
