Pot#1 function disabled, shouldn’t that cause the issue?
Pot#1 function disabled, shouldn’t that cause the issue?
NNo. Only if you had a pot assigned to an effect setting and it was turned all the way down.
Si never used the effect tab
NScreenshot it. If you set the spring gain up and apply and it doesn’t take, the spring setting in the effects tab could be the culprit.
S
SSBecause oh the weight it does not stay in position at one axies. At other axis it stays
NThis is your problem. Spring is disabled.
Sstill the same problem
Sokay i think it was a false alarm....Because previous time i tested it without any weight on it and now it has a lot of weight
WWell due to the weight it behaves as expected as the whole motor is riding at the bottom.
WI'll think about how to compensate this use case, since ideally it should stay put wherever you put the stick
Swell i am triming the helicopter in dcs {T} and it does not want to trim it
Wdoes the blue circle jumps to the trim position ?
Sin Vp FOrce? no it does not
WDo you have FFB enabled in DCS settings?
Syes
S
S
Wcheck also the MISC tab
S
SIf i put heuy at default trimmer mode it works
WYeah, Stick without springs and ffb means there is no springs AND no FFB, the wording is a bit confusing
WSo set those special options to instant trim (default)
Aall the requirements are already satisfied
PNoob question, is there anything to amply the shake in F14? I notice it slightly, have gain up pretty high using default rhino config
JShould work somehow. I have a profile for the F-14 and think it's giving enough feedback, fiddled some time to get it right.
KWow, this was super helpful. I just ran into this same issue on a board I spun for a custom joystick. Thank you for diagnosing it and saving me a TON of head scratching.
KFor those of you with a single axis system: Is there a trick to using the VPForce board with only 1 motor? I can only get the software to show motion when I have 2 motors connected. The software says the motor is detected but never shows motion. If I attach a second motor, both motors work perfectly?
WYou need to disable the unused axis
KThat never even occurred to me. Thanks. I’ll do that.
PI may have been a little stupid when I made my order, I recall ticking the box for the Virpil adapter - I could be making that up tho 
My Virpil Constellation arrived today and the connections don't suit the adapter piece I got with the Rhino ? Not a big deal - obviously I have ordered the wrong part or done something else equally stupid.... what do I need to make this right now ? thx
My Virpil Constellation arrived today and the connections don't suit the adapter piece I got with the Rhino ? Not a big deal - obviously I have ordered the wrong part or done something else equally stupid.... what do I need to make this right now ? thx
BDoes it even need an adapter ?
Thought it was native for TM and virpil grips?
Thought it was native for TM and virpil grips?
WThat's the winwing adapter in the pic, Virpil mounts directly to the Rhino.
RIs this something we should all do? Also what is the breakout force effect for and will it be fixed anything soon. I assume it means you must meet the force demand before it will move from center?
RLooking to make the center stay more within its trimmed blue circle without messing with the linear feel of movement
PAhh that would explain it, I got that so I had all the options - just in case, I will try and plug it in again then, I just didn't want to force it 
HJust thought I’d pop in and give an update. I’ve had a bunch going on so I had to put my friend’s Rhino FFB board on the back burner. Had a chance to look at it today and after pulling the 3v3 regulator off the board I still had a short between the 3v3 line and ground. So next I pulled the processor off and sure enough there is an internal short between VDD and VSS
HI’m going to order a new chip tonight to throw on there and see if it works
KA new STM32F103? That will have to be programmed with the VPForce proprietary firmware. Better to just get a new board since you don’t even know if that’s the extent of the damage.
HIt’s actually a Geehy apm32f103cbt6
HAnd hopefully they are willing to support their products enough to provide the firmware necessary to fix the board
HLooks like there’s already a way to flash the firmware to these boards. I’ll have to read some documentation since I’m not familiar with these apm chips, but I’m willing to bet all I need to do is get it (newly installed chip) into DFU mode and use this firmware flashing tool: https://vpforcecontrols.com/usb/rhino/
H@walmis I see that these chips are reprogrammed through UART1. What is the process for flashing a new chip?
HAnd it looks like I can get an actual STM32F103 for less 
HLooks like Boot0 needs to be pulled high with Boot1 pulled low to enter Bootloader, cool.
KThe Geehy is an STM clone that gained popularity during the chip shortage. Not sure why you’d make a distinction.
HBecause that’s what’s physically on this board, clone or not. Not interested in semantics arguments though so take that somewhere else
K
KK.
TAre you trying to fix a broken controller board, that came with the Rhino? Why not just send it in to Walmis for repair?