Yeah, I'd actually prefer all my center stick aircraft be that way, since it more closely mimics how
Yeah, I'd actually prefer all my center stick aircraft be that way, since it more closely mimics how real aircraft are setup
HGiving you all that extra room on the pull gives you a lot better control and feel for how hard you're pulling
MMakes sense, do you have an extension?
HI do
PI think most people are restricting the push of the Y axis as a lot of aircraft have less forward throw than rearward.
Show do you know about the real aircraft? The neutral position only happens in flight and that's where you would see your stick pitched forward.
S@walmis I realized that the axis scaling is supposed to adjust this but it would be far easier if I could just drag the center point in game. The necessary change in vpconfigurator would be a button to adjust center. Like the auto calibrate button but simpler. Click the button, drag the blue circle, click the button again. This could even be automated. Although that might sound complex, DCS actually can export values in game, specifically the name of the aircraft. Simshaker and DCS exports do this through the export.lua. So the Rhino firmware could poll the export lua every 5 minutes, read the data (which aircraft) and set the center point according to an aircraft specific adjustment (like simshaker does). This aircraft specific adjustment can be stored in the firmware and modifiable by the user.
Salso tried running the latest executable version of TelemFFB through the executable. Got this error:
STraceback (most recent call last):
File "main.py", line 282, in <module>
File "main.py", line 261, in main
File "utils.py", line 286, in install_export_lua
File "utils.py", line 266, in write_script
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\Stefan\Desktop\telemffb/export/TelemFFB.lua'"
File "main.py", line 282, in <module>
File "main.py", line 261, in main
File "utils.py", line 286, in install_export_lua
File "utils.py", line 266, in write_script
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\Stefan\Desktop\telemffb/export/TelemFFB.lua'"
SI put the script from the master into the empty folder and that fixed it
G
Ganybody else get this with the new software?
Adid you update the firmware yet from the website?
A(visit this url in chrome to actually also update the firmware: https://vpforcecontrols.com/usb/rhino/ )
TTagging my fellow @FFB/Kit Owner for visibility.
WI'd recommend tapping them to M6
GYes, M6 screws. I used flat hex head bolts
GAnything taller head may start running into the belt. I also added an idler bearing for belt tension on the upper forward bolt of the pitch motor. I can add pics and details after work when I get home if anybody wants
TI’d like to see how you did it. I’ve got my gimbal made and moving on to the housing. I think all the bases are modeled for the 57 series motors so I am looking into how to implement the 86 series.
GOh, the 86 series. Sorry, I didn't read that correctly. I have the 57s
GIt should just take a cad adjustment and bigger hole pattern. You will however run into interference with the gimbal arms and the roll motor. My 57 motor hits the gimbal, but it ends up hitting past where the end stops are so it's fine.
GThe 86s might need some cad readjustment and different belts
TWhich part does the gimbal hit? I’ve got an idea how I want to modify it. Just getting ready to start on modeling it. I’m thinking v-slot extrusion frame with printed panels.
GThe lower arms of the gimbal arm at full throw. Even the 57 motors have bigger cases than the basic cad file case has, but it's not enough to cause problems
WI used M5 hex bolts with a lock nut on the back.
MThe threads in the motor body are M6 so I'm using M6 screws going through through-holes.
TSounds good, mine aren’t tapped but I can tap them.
MScratch that I have the 57xxx motors not the 86's
WDrilled to 6mm and have an m6 bolt with nyloc nut on it.
TThanks for all the replies everyone, lots of good options.
Knewb question - just got my Rhino base! Super impressed so far.
How does one load a stick profile? IE I have a Virpil Alpha grip, and the buttons are acting... odd. I assume that's because I need to load a profile for that specific stick? All the buttons seem to register as double presses...
Update:
Plugged in my old warthog stick and it's fine, thankfully. I'll use it for now, but if anybody has any ideas how to get the Alpha to behave, I'd appreciate it.
UPDATE2: Nevermind - I'm an idiot. I was looking for the stick profile on the web app/not the software. Got it now!
UPDATE3: Where has this been all my life? WOW... simply blown away!
How does one load a stick profile? IE I have a Virpil Alpha grip, and the buttons are acting... odd. I assume that's because I need to load a profile for that specific stick? All the buttons seem to register as double presses...
Update:
Plugged in my old warthog stick and it's fine, thankfully. I'll use it for now, but if anybody has any ideas how to get the Alpha to behave, I'd appreciate it.
UPDATE2: Nevermind - I'm an idiot. I was looking for the stick profile on the web app/not the software. Got it now!
UPDATE3: Where has this been all my life? WOW... simply blown away!
R@walmis
After powering up my base it no longer shows in the game device list. The Google Chrome popup says
I've tried disconnecting USB and power at the base then reconnecting after a delay of around 30 seconds. Also, multiple USB2 and USB3 ports, both direct to the motherboard and on powered hubs. But, all with the same result.
After powering up my base it no longer shows in the game device list. The Google Chrome popup says
FFB Board Bootloader detectedI've tried disconnecting USB and power at the base then reconnecting after a delay of around 30 seconds. Also, multiple USB2 and USB3 ports, both direct to the motherboard and on powered hubs. But, all with the same result.
RNo change after rebooting the PC.
Anti-cogging is working (gimble is smooth when emergency stop is out), no spring forces are present and the base does not show in the configuration app.
Anti-cogging is working (gimble is smooth when emergency stop is out), no spring forces are present and the base does not show in the configuration app.
WHey, that's strange - DM'd
RIssue resolved in double-quick time!
Thanks for your time @walmis , really appreciate everything you've done for the flight sim community with this project. Great work!
Thanks for your time @walmis , really appreciate everything you've done for the flight sim community with this project. Great work!
Aso i've noticed a general issue that happens sometimes, and I am not sure how to repro it, but basically it seems that at times the configuration app just loses the ability to get telemetry from the device, everything still appears to work fine, i can apply effects and all that, and games are fine, but in the configuration app i can't see the telemetry data, and i have to basically fully unplug the rhino
Aand plug it back in to get the telemetry data
Aby telemetry, i mean the output you see here:
WInteresting 
Does it happen often?
Does it happen often?WAnd as I understand correctly you can apply config and read it back?
AI’d say it happens a decent amount yeah, I think usually after using the emergency switch (I generally use that when I pause to go get up and do something)
AEverything appears to function normally though
WSo it's reproducible until you restart the controller, I mean restarting the GUI doesn't fix it.
AYeah, rebooting the config tool doesn’t fix
ASorry, shoulda said that
A(Feels like one of those annoying bugs you can never repro, but analyzing the the code you find it’s a possible state, but logically should never happen 
)
)Sare you connecting to a motherboard usb? is your cpu amd?
ANope, connected to a powered hub. And nope, Intel system. To be clear though, nothing else about the device isn’t working, it seems to just be a software/firmware bug between the device and the config app
Ais it bad for a motor to get up to 60c? Just after a play session I noticed temp_y at 60, and temp_x around 37
WIt's normal after intense load
Agtk! just wanted to make sure it was expected