Hi, thanks, it was pre built and seems to work fine apart from not behaving as you describe in the v
Hi, thanks, it was pre built and seems to work fine apart from not behaving as you describe in the video!
HIf you have a pre built rhino by walmis then definitely reach out to him
WYou have a decently steep spring gain map applied. I've loaded your config and tuned the filters a bit, works reasonably well at high pot gain (the attached .vpconf file will only patch the filter values so you can apply it on top of your current profiles)
R@mark turner what is the reason you have such a steep spring gain? I’ve tried steep spring gains to make the centering stronger for holding the long extension but I get reverberations still.
1It appears my ingame Trim control for dcs is no longer working. Not sure when it happened as I’ve been using hardware trim for helicopters and haven’t been in a fixed wing for a while so I haven’t noticed the issue until now. Has anyone ran into this or have any ideas as to what the issue could be?
Nmake sure you uncheck both "sticky" spring and "override trim" in configurator. Beyond that, its just simply binding the trim controls in DCS (and the normal stuff like making sure FFB is enabled globally)
WAlso check dcs.log, if it lists vJoy input device it could cause problems with trim
1Nothing is checked and also turned off telemffb to be double sure…. Thank you for the answer!
1I will check that, thanks!
1i did find this in the logs
02 19:21:39.194 INFO INPUT (Main): created [vJoy Device] with full id [vJoy Device {6BE6F3E0-7745-11ed-8002-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}
02 19:21:39.194 INFO INPUT (Main): created [vJoy Device] with full id [vJoy Device {6BE6F3E0-7745-11ed-8002-444553540000}], ForceFeedBack: yes, guidFFDriver: {EEC6993A-B3FD-11d2-A916-00C04FB98638}
1Still having the issue...
i removed the vjoy device, no longer appears in logs,.
no effects are sticky in vpconfig
there are no curves or saturation in the axis within dcs
nothing that i can see in telemffb whould be causing it but i closed it just in case and it still will not trim.
when i hold the trimmer button the spring force is removed but it will not hold the new trimmer position
the trimmer mode is in either default or instant if "ffb friendly" is present
global ffb is checked in dcs
this is challenging my patience!
i removed the vjoy device, no longer appears in logs,.
no effects are sticky in vpconfig
there are no curves or saturation in the axis within dcs
nothing that i can see in telemffb whould be causing it but i closed it just in case and it still will not trim.
when i hold the trimmer button the spring force is removed but it will not hold the new trimmer position
the trimmer mode is in either default or instant if "ffb friendly" is present
global ffb is checked in dcs
this is challenging my patience!
WSee the thread here: https://discord.com/channels/965234441511383080/1230852705593851964/1324122150206050344
someone had the same issue, check the points outlined in the thread
someone had the same issue, check the points outlined in the thread
WThe trim (blue circle) indicator should jump to the trimmed position:
1i updated/reupdated everything to do with vpforce and the problem seems to have fixed itself!!
MThis is to make the stick feel harder to pull the more I pull it….I wanted some appreciable resistance at around 3 or 4 G which is commonly used for most tactical turns.
MBy the way, I am also suffering with oscillations around the centre and despite some hours of tinkering, not managed to isolate any settings which help.
MGoing to try Walmis settings above
MIt would be good to know exactly what causes it….Last year when I had the issue again, Walmis advised reducing damping voltage - but this time adjusting those settings seemed to make no difference. I will check now with the supplied .conf file
MIt’s frustrating as I am not sure what I did to bring it back again, apart from adjust the gain curve. Making it straight again does not get rid of the issue
WIt's best to reset to defaults and go from there
MWhich is why I started doing the calibration as recommended above which kick started the questions……as I could not get the stick to behave as per the suggested process.
MWhile I have your attention Walmis, is it correct that I should feel the notching and clogging as described above when I wipeout the stick around the circle?
WCan you test with default rhino parameters? I think you had some deadband set in your spring setting which would introduce notches in the center
MAm recalibrating now.....the notches and cogging feeling are not in the centre, they are at the outer extremes of movement, I have a distinct notch at approx 4 & 8 oclock and it feels like several smaller notches as I move the stick from approx 10 - 2 oclock. My stick is mounted backwards BTW so the pots are nearest me. I have inverted X axis so the purple dot mirrors the physical position of the stick when it moves
MThis is with the default config loaded and all boxes in effects unchecked
MI am going to try the adjustment to balance spring as per the linked video again now.......
MOK, have just been adjusting as per the video, but I think the issue lies with the extension. The guy in the video has an S bend extension that keeps the stick not far from the centre. My Z extension displaces it 150mm to the rear. So there is no setting that works to keep it in place, once you go past centre point against the displaced weight. I can get it roughly to stay but there are certain parts of teh range of movement where no amount of slider setting will offset the weight of the displaced grip.
MAnd of course it behaves differently above and below the centre
WFor the Z extension you might need to use some static force on the Y axis, since it works more like a counter balance
WThe cogging is only on one axis?
BI have the z-extension and all I've applied is 6% static force.
OHello, i am new. I have the diy kit. There are 2 motors with the same label “pitch”. Can I still use this or was I sent a wrong motor?
MSo have managed to iron out the oscillation using Walmis's settings, thanks And got the stick balanced best as its going to get with the Z extension I think.......thanks for teh advice all
OCan I use both? They have the same id! Or did I get a wrong motor?
FI think Walmis may be able to reconfigure one of them to be the X axis.
OOk. How can he do that? How can I contact him?
F@walmis ??
FDM ??
FTo save time until he can help you, do you have a power supply you can use to test the motor and connect it to a PC using the USB cable? That will be needed if he is to flash the motor firmware.
OOk, thank you very much first, but I have to get one first. Then I'll get back to you
MDo we have the ability to edit the grip profiles? The HATs on my FC Technologies NS-37 don't work with any of the existing grip profiles.
SHi all, I have a question / sanity check here. I've noticed through some searches and firmware changelogs there have been issues with passthroughs/all joystick buttons seemingly pressed? I've updated to the latest firmware (b17).
Issue When I try to use the passthrough feature for the Warthog, now all buttons are shown as pressed in windows
Context: I've not used my gear realistically in like ~3 months as I've been assembling a motion rig. That being said, there is any number of things that could have happened to the device as it was moved/mounted on said rig. I have an early Rhino (SN37) if that matters, I know initially Walmis found an issue with mine he later fixed.
My setup is currently running a cable from a special port on the Rhino to my TM base with the warthog grip on the Rhino. The purpose, although not relevant is to keep using TARGET with the Rhino. I thought maybe my TM base finally gave up the ghost and/or my cable. So I'm using a brand new TM base, and a freshly re-soldered cable (I actually redid the cable twice to make sure It wasn't something wonky).
Things I've tried
Issue When I try to use the passthrough feature for the Warthog, now all buttons are shown as pressed in windows
Context: I've not used my gear realistically in like ~3 months as I've been assembling a motion rig. That being said, there is any number of things that could have happened to the device as it was moved/mounted on said rig. I have an early Rhino (SN37) if that matters, I know initially Walmis found an issue with mine he later fixed.
My setup is currently running a cable from a special port on the Rhino to my TM base with the warthog grip on the Rhino. The purpose, although not relevant is to keep using TARGET with the Rhino. I thought maybe my TM base finally gave up the ghost and/or my cable. So I'm using a brand new TM base, and a freshly re-soldered cable (I actually redid the cable twice to make sure It wasn't something wonky).
Things I've tried
- Updating firmware / Buying new TM base / Resoldering link cable (both sides)
- Continuity check with multimeter for my link cable (nothing on the Rhino yet)
- Checked checked and re-checked I aligned the right wires/pins for the cable
- Tried different "Grip Type" options in the VPForce software just in case (Disabled/Generic) the Rhino will work in 'native' mode
- Toggling the .5v option in the software to see if it had an impact
Rwhat settings were used? I want to add a bit of a steep angle to my spring gain to make hold the center easier, as the adaptive centering isnt strong enough for my needs and extension length. I still get osciallation, they are better after newest update, but still present.
R
R
R
STry dropping Spring dependent damping. I see you have it kinda high at 80%.
ROk
MHi, got the shift register board.....looking for sockets to solder on them......is it the JST-PH 2.0 size used for these? Found some PH 2.0 plugs and sockets on Amazon and want to check before purchase. Ta
MAlso damping slider very high. Will post my settings shortly
M
