Can I connect the Hotas Warthog Grip directly to the SPI port of the VPForce motherboard?
Can I connect the Hotas Warthog Grip directly to the SPI port of the VPForce motherboard?
WYes!
II’m making and assumption here, but I take it that board doesn’t allow for a analog axis to pass through to the main board. Does the main board have the analog input built in?
WMain board has 2 pot ports, other than that analog data could be digitized and piggy-backed on the SPI bus with an arduino as SPI-slave for example.
IAwesome thanks
PHey Walmis, to do the firmware update do I just have the Rhino plugged in & then hit 'update firmware' on the web page?
WYep
Poh cool & the loopback exe, just run that & then follow the gui?
WYep. Select Loopback grip type in the Rhino GUI too.
Phey m8 can I ask what's the 'Balanced Spring' option do?
Pis it just to help heavier grips like the vkb mcgu to stay upright?
WThe idea is turn off all other effects and adjust the balance spring so when you move the grip to the sides at various deflections and leave it there it stays put. Heavy grips tend to weigh down the more deflected they are from center, this is to counter that (if needed)
Poh ok cheers for the explanation, I might give that a go when I swap over to my mcgu next. wow firmware update was extremely easy to do! good work with that streamlined process. Oh sorry but one more question, am I missing something is there a way to save different profiles for the config software? Thanks again m8
Poh lol, ignore the profiles question
WUse Export/import functions to save the profiles 
Plmao I must of had a huge brain fart! I blame Christmas!
Poh hey, you got stick balancing in!
PAlso the endstop seems to be working nice to
PI haven't tried the force trim yet, likely give it a go in msfs heli when I get the chance, you know after this whole christmas thing is done! lol
Phi there, @walmis , how are you?
Hey, a quick question/request: is there a way to force a re-write of the current firmware version?
Reason: was just flying DCS on the previous firmware version of Rhino. The game crashed during a plane crash, so there were joystick vibration effects. Anyway, after the game process got killed the joystick continued to vibrate.
- I powercycled it, still vibrations. Loaded default config, no dice, still vibrates.
- Rebooted the pc: still the same. Anyway, no matter how many times I cycled it, rebooted my PC, re-applied configs/resets: the vibration wouldn't go away.
- When launching Autocalibrate the vibration stops, allows me to calibrate and then stop it. As soon as I 'send/store' to the device the vibration comes back.
- In debug it showed different effects loaded, so I re-disable/re-enable, no matter which way I apply them the 'ghost' effects continue to work/show up in debug.
Now, I think you know where this is going : yup, to your website, luckily you had the new version up, I flashed Rhino and voila: all back to normal.
Soo... help a brotha out! 
Hey, a quick question/request: is there a way to force a re-write of the current firmware version?
Reason: was just flying DCS on the previous firmware version of Rhino. The game crashed during a plane crash, so there were joystick vibration effects. Anyway, after the game process got killed the joystick continued to vibrate.
- I powercycled it, still vibrations. Loaded default config, no dice, still vibrates.
- Rebooted the pc: still the same. Anyway, no matter how many times I cycled it, rebooted my PC, re-applied configs/resets: the vibration wouldn't go away.
- When launching Autocalibrate the vibration stops, allows me to calibrate and then stop it. As soon as I 'send/store' to the device the vibration comes back.
- In debug it showed different effects loaded, so I re-disable/re-enable, no matter which way I apply them the 'ghost' effects continue to work/show up in debug.
Now, I think you know where this is going
: yup, to your website, luckily you had the new version up, I flashed Rhino and voila: all back to normal. Soo...
help a brotha out! 
WHey, sorry I don't quite understand what's going on. Did it sort itself out? Could you post a screenshot of your configuration/debug screen?
WAhh, I think when DCS crashed it left the vibro effect still running, you can unplug/replug the Rhino USB to reset completely, the Estop switch only controls power to the motors.
Might be a good idea to add a software reset in the app in the future.
Might be a good idea to add a software reset in the app in the future.
KIs it long delivery times now? Ordered a base last week but its not shipped yet
AHey! According to the bot 28 Rhinos have been sent atm. Walmis is, I believe, currently ramping up production, but the queue is something like 200+ units long. Mine is 116, ordered in mid-October. Sooo, I'd expect 4-6 months-ish. You can DM the VPforceBot with !status and !info <your e-mail here> for more info.
KThank you, but I just get "sorry, your email was not found"
AI think you'll want to message Walmis about that. The bot worked good for me just now.
WHey, which form did you fill?
WGoogle Docs
Enter your details here, so you can enter the waiting queue for the Rhino FFB base.
Once the queue progresses I will get in touch with further details.
Once the queue progresses I will get in touch with further details.
KNo I just ordered the collective base with grip. With an order number and everything
KNever heard of the Rhino before, what is it?
KBase I see.. Will it support helicopters?
WYeah, DCS force trim is well supported. You can find more info in the #
faq channel about the dimensions, etc.
faq channel about the dimensions, etc.
YYou've got something mixed up. Walmis doesn't have a collective
KIt's not part of the virpil product line? 
Wthis is VPforce Discord, nothing to do with Virpil. While the initials might seem similar, VP is my actual first/last name initials
KLol sorry I mixed it up
KDefinately interested though, I signed up 
KCan I ask how tall this base is from top to bottom? Doing measurements on my rig
Wthere's a drawing in the #faq channel
faq channelKOh, 29cm,thats pretty huge!
KIt looks smaller on videos
KI'll make it fit
Pit's worth it!
KI bet. I love that it's already extended to some extent. Will be good for helicopter maneuvers etc. I hope itll support no centering, or that we can change cebterpoint/trim on the fly for simulators that's not otherwise supported
PAlready a thing m8! Force trim has worked perfectly for me in the dcs huey & Black Shark 2, msfs2020 dosen't support ffb natively but XPForce or other 3rd party software will give you ffb in msfs, I use XPForce atm & it's good, however it doesn't support force trim, Walmis has just updated the software/firmware for the RHINO base & you can now set force trim in the config software for the RHINO base, so for games that don't support force trim you can still do it through the software.
PFlying heli's in DCS has been so much better!, also the RHINO has a huge throw on it, I use a 200mm extension, but the software allows you to adjust the length of throw for the x & y axis & it auto-magically adjusts the calibration to fit, this is awesome for going from aircraft to aircraft that may have different throw, or even just to make it fit your pit size.
FNext step: a hook for DCS to automatically detect which aircraft you fly and adjust throw accordingly
KThis is literally what I just asked some real pilots about. That was actually my next question.. 20cm extender would be too tall on my rig. I did some measurements, and I cannot use an extender, because the base will cover the whole height.. So I guess with VPforce I won't get as realistic throw as with a real cyclic.. But maybe the fact that it's a freaking force feedback base will weight up for the lack of throw
KMy current rig for reference.. It's 29cm from my wooden plate up to the pillow, exactly the same measurement as the VPforce base.
KCould be a bit too short throw, I don't know
