@walmis Which grub screw do you use with the motor pulleys? M4?
@walmis Which grub screw do you use with the motor pulleys? M4?
WM4x3
TWhen connecting the motors to MOT1 and MOT2 on the controller board, which one is Roll and which is Pitch?
Wdoesn't matter
RI've noticed a significantly reduced damper effect on my X-axis (roll). Pull-and-release on the Y-axis results in a well damped return to center, while the same on the X-axis results in a springy overshoot and return, which gradually settles out to center.
Adjusting the effect percentage on the axis doesn't seem to make a noticeable difference. Disabling the effect results in the expected very bouncy return to center.
Intial effect levels are the same for both axis and the gain maps are 1:1. Using current firmware and app versions.
Adjusting the effect percentage on the axis doesn't seem to make a noticeable difference. Disabling the effect results in the expected very bouncy return to center.
Intial effect levels are the same for both axis and the gain maps are 1:1. Using current firmware and app versions.
WCan you show us your settings?
R@walmis
R
RNo looseness and the bounce is more pronounced with friction and inertia disabled.
R@walmis
WMy guess is that the the X axis has reduced calibrated range
WTry increasing spring bandwidth to 15Hz
Rno change
Rre calibration, I'm using the printed limiter set at 13 degrees y-axis, 10 degrees x-axis with axis calibrated after fitting.
Wwhat happens if you set both axis the same range - 1512 <> 2925
RMax reported deflection on the y-axis occurs at ~75% physical deflection, as expected. But, still bouncing on the x-axis.
WInteresting, how's the belt tension?
Raround 5mm displacement from the centreline on both axis. I don't recall what it was like when first received though.
RActually, quick comparison of the calibrated ranges vs setting both axis to 1512<>2925 and the y-axis now also has very reduced damping. Not quite as bouncy as the x-axis, but it's close.
R... if I pull the y-axis to its max physical deflection before releasing it.
Rscratch that, it's the same whether it's full physical or just to the reported max in relation to the reduction in damping.
AIs there a reason for the red color of the center value?
WYeah, your physical center is ambiguous on startup, you need to install the belts so that the motor center is in the middle (~2000)
N@walmis any chance you can drop the stl file for the USB jack mount somewhere? My USB jack came lose again and in the process of trying to fix it, I managed to break the mount :D... I could re-create it, but figured I'd ask.
SI have an interesting problem with the SA342. I calibrated the Rhino and assigned the pitch and roll axes. The controls indicator at maximum stick excursion looks like this:
S
SAs you can see, the only direction which registers a full deflection is down (moving the cyclic forward) . All the others are only about halfway. I have no curves or saturation modifications in DCS. This is a newly calibrated Rhino and the settings were cleaered before assigning the axes. For comparison, I hooked up my old virpil stick and it registers full excursions in all directions.
S
SThese are my VPconfig settings:
S
KI'm assuming you've tried with hi-res mode unchecked?
KWhat does the windows joystick configurator show for stick deflection?
SYes, I unchecked hi res and the same behavior persists. Anyway, the excursion limitation in DCS is asymmetric. In the VP config app, the excusion is full and goes to the edge of the box in the direction the cyclic is moved
SAlso, the windows USB game control panel shows full excursion of the cyclic.
KThose numbers look good from a VPForce configurator perspective. If windows is reporting full deflection, it's got to be a DCS issue. Does it do this on other DCS modules?
SThe huey shows full excursion. However, they seem to have builtin some inertia in the huey controls. Moving the stick shows lag in movement of the controls indicator
SThe apache shows about 2/3 excursion of the indicator with full movement of the stick. And there is no lag.
NThese numbers should not be 0.... Default for Rhino should be X=190 and Y=100...
N
SThat does not fix the problem.
SThis aberration persists even when I turn the gain of the spring down to zero and there is no force feedback
AWhen you can’t reach full deflection, is it because there’s lots of resistance on the stick?
SAlso, it seems that polychop has built in some curves even when the dcs axis assignment has no curve or stauration change. Near the zero point the indicator does not move much. However as the stick excursion moves away from the zero point, the indicator moves more from the same relative deflection. I guess they did that in recognition that their flight model was too twitchy. Before the SA342 flight model update, you couldnt fly this helicopter unles you added a generous amount of curve.
S@amadeus It is the indicator that does not go to the edge of the box even WITH full stick deflection.
SDoes anyone else here fly helicopters?
ASorry — I know that — but I asked poorly
AAre there strong forces on the stick when reaching full physical deflection, but show up as not full deflection in the game?
Sno forces are present on the stick. i have turned spring gain to zero to eliminate that variable
AKk
AThen yeah, not sure what is going on. In that post that Number481 posted above, the default force compensation values were not nearly good enough to account for the belt flex at high resistance for me and required tuning, but if you have all forces turned down and not fighting any physical force at max physical deflection then it must be something else