W86BLF04. The biggest ones.
DTek Creations
SVery sweet build!!
WThe damping compensation is essentially negative damping, so you can find a value that's on threshold of stability. A nudge test is a good indication. If you nudge it and it starts to accelerate it means the value is too big.
RThat’s amazing.
WOK, thank you.
RIt’s a dangerously slippery slope for the poor wallet.
MWhat is the approximate shipping cost to Indianapolis US for motors kit?
WIt's roughly 50EUR using FEDEX for the smaller motors kit
Sdont forget you'lll also get a bill from fedex for $35 for import tariff
TKits might be less than the tariff threshold.
YI didn't get hit with a tariff for my motor kit
F$800 above gets hit into the US.
Danything over $1000 in Australia gets hit with Import tax
Ddoes anyone have the WinWing F18 grip? for some reason my right hat switch does not work (up/down/left/right), but the push does work
WIt's mapped to a hat as I recall
W@mike_aka_mugs has this grip
Dah, apologies, it works in DCS, didn't show up to be working in the vpforce program
Dthe button it's assigned to is 45,46,47,48
AQuestion: when updating firmware, will existing settings be wiped out? Just want to check if I should screenshot them before updootin
WNope, it should migrate automatically. But you can always export them to a file as a backup.
PUmmm bugger, I seem to have lost all my config's. I just did the firmware update & downloaded the newest config app, when I moved my config folder I made to the new app to tidy things up I launched the config app & when I try to import my configs they're gone?
P
PI found them
P
Aso one question i have -- it would be nice to be able to manually define the center position raw value -- i'm finding that with calibration and tweaks -- it's basically impossible for me to get my Y axis to have 2048 as my center without severely limiting the throw (or I am perhaps doing something wrong?)
Aafter a calibration and some manual tweaks of the end points -- i have around these settings (was able to tweak X to have 2048 exactly tho
WYou don't need to
WJust run the calibration and the values will be "correct"
Ai guess i am confused by this note then:
WYeah, this is for when you are putting on belts, so the motor encoder values are not in between turns.
P
Pthat's mine & my Rhino acts fine
Pthough if you don't know it wrong you won't know it's wrong so always ask
Pis mine wrong?
Awell each device will be different
Abut yeah -- what walmis said makes sense, i should mostly ignore how those C values turn out, since calibration will basically sort that
A(or i assume -- center will just be whatever the halfway point between the min and max are)
WYeah, this is the motor "physical" center
WYou guys can set up Force Comp defaults for the Rhino, so you will get full axis travel when under force tension.
Ayup! that's what i am tuning now -- takes a bit of math or trial and error to figure out
A(setting the spring to 100%, turn it completely down, move it to full deflection, figure out how far off from 4096 it, and use that approx value)
ASmall thing — after this new firmware update (and it may be unrelated), but fans sometimes are making a different sound?
AFor reference, this is what they generally sound like
WHow did you make this comparison? 
Ait sometimes happens heh
Ai used the test fans button tho
Asounds like something might be sometimes contacting a fan blade?
Wthe grill maybe slightly touches the fan hub perhaps?
Dissue resolved in the new firmware/software