ok, just to make sure its clear, at 0.15 I don't have the problem.. just at 0.2 and wilco.
ok, just to make sure its clear, at 0.15 I don't have the problem.. just at 0.2 and wilco.
Nagreed, but this also changes the amount of power the Rhino is pulling when generating the effects... reducing the slider in vpconf will have the same net effect
Seffects slider at %25 I cant reproduce the problem and after that I set it again to 50 and started right away with it! I managed to put it at %0 the effects slider and rhino continued to shake and then stopped it with debug - reset motors.
Sso, looks like its not TelemFFB..
WI'm starting wondering if the rumble is the result of self-oscillation.
@snooperoldschool can you use the snipping tool to grab a screenshot of both effects and settings tabs
@snooperoldschool can you use the snipping tool to grab a screenshot of both effects and settings tabs
Sbut the Periodic effects LPF from 20 to 15 helped to take more time till it shows
Sok
S
S
Scould be inertia?
WYeah, it adds instability
WTry disabling it
WOr set inertia LPF to 3Hz
Si'll go first to 3hz
Stried it engine_rumble_lowrpm_intensity = 0.25 and did not showed the issue
N@walmis - before I get too deep in how to add FF, does the circuit/software require there to be x and y axis inputs? I’m thinking for my purposes that I might use cables to transmit forces to my existing stick and keep using the stick for control inputs while the motors add the forces. I was thinking the motors themselves have encoders that the control circuit and software uses or do they need the axes inputs to function?
WNot really sure what's the question, but yeah, the motors are the axis sensors
NThe question is if the motor connections are all that’s necessary to get FF and it sounds like that’s true. The analog axis inputs are optional and to duplicate the function of a regular stick is what it sounds like. I’m having to work around some physical constraints and can’t go with the standard box for a stick base. Mine is kind of a kludge if it is to work without some major sim rework.
AJust hooked up the 86BFL04 for the first time. The motor is recognized by the configurator tool, but no Axis output is displayed. Does the kill switch have to be installed for this to work? (Couldn’t see it on the wiring diagram) or do i have to change something in the configuration for it to work?
WIf a single motor is attached disable the unused axis in the configurator
P@snooperoldschool @walmis FWIW - I too had engine effects just continue after Telem and MSFS were terminated. had to unplug stick to get the engine vibes to stop.
AThanks. Will try when i get back home on Saturday.
PI haven't set my Rhino fully up yet because I'm still working on my mounting solution. I do however notice that the belt that controls the pitch squeaks in one small specific part of its travel (the roll belt is totally silent and smooth). Does that mean the pitch belt is too tight? Or something else?
PIf I put my finger on where it's squeaking, it does feel like it has a bit of extra tension during the squeak
PLooking closer at the belt, I see some orange on the belt near the squeak point, but also near the top of the belt so I'm not sure if it's related. Is that normal, or is the belt slightly compromised?
PVideo of the sound
POther belt (totally smooth and quiet)
Wmaybe it rubs a bit with the small pulley's outside wall. You can try a.) Pushing the belt a bit deeper on both pulleys b.) apply some silicone spray c) remove the belt and put it back in a different orientation
POkay, I will try those steps
PPushing the belt closer into the pulley made it much quieter 
I will experiment further as needed using your advice.
I will experiment further as needed using your advice.Swhoopsy:
Exception in thread Thread-2:
Traceback (most recent call last):
File "main.py", line 450, in process_data
File "aircrafts_msfs.py", line 694, in on_telemetry
File "aircrafts_msfs.py", line 438, in _update_flight_controls
File "aircrafts_msfs.py", line 350, in _update_fbw_flight_controls
AttributeError: 'NoneType' object has no attribute 'setCondition'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "traceback_with_variables\print.py", line 67, in printing_exc
File "traceback_with_variables\print.py", line 98, in wrapper
File "main.py", line 489, in run
File "main.py", line 454, in process_data
File "traceback_with_variables\print.py", line 39, in print_exc
AttributeError: 'NoneType' object has no attribute 'write'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "threading.py", line 1009, in _bootstrap_inner
File "traceback_with_variables\print.py", line 92, in wrapper
File "contextlib.py", line 153, in exit
File "traceback_with_variables\print.py", line 70, in printing_exc
File "traceback_with_variables\print.py", line 39, in print_exc
AttributeError: 'NoneType' object has no attribute 'write'
Exception in thread Thread-2:
Traceback (most recent call last):
File "main.py", line 450, in process_data
File "aircrafts_msfs.py", line 694, in on_telemetry
File "aircrafts_msfs.py", line 438, in _update_flight_controls
File "aircrafts_msfs.py", line 350, in _update_fbw_flight_controls
AttributeError: 'NoneType' object has no attribute 'setCondition'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "traceback_with_variables\print.py", line 67, in printing_exc
File "traceback_with_variables\print.py", line 98, in wrapper
File "main.py", line 489, in run
File "main.py", line 454, in process_data
File "traceback_with_variables\print.py", line 39, in print_exc
AttributeError: 'NoneType' object has no attribute 'write'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "threading.py", line 1009, in _bootstrap_inner
File "traceback_with_variables\print.py", line 92, in wrapper
File "contextlib.py", line 153, in exit
File "traceback_with_variables\print.py", line 70, in printing_exc
File "traceback_with_variables\print.py", line 39, in print_exc
AttributeError: 'NoneType' object has no attribute 'write'
Sflying with the C310S
Nmilviz/blackbird?
MAny plans, or is it possible, to have a 1/2 deflection stop in the y axis forward when flying the dcs F-15E? There's a new setting that mimics the real jet's reduced forward range, but the rhino will push through it in to a large zone of no input
Smilviz
Nseems to work fine for me.. best advice I can give s to startup without your userconfig (aircraft will just be detected as "generic aircraft)... if that works, look at your userconfig for syntax errors ( duplicate
[setion names] or missing [ ] or duplicate line items in a given section.NWhat conditions did the error occur under? Starup of TelemFFB? Loading the Aircraft with TelemFFB already running? Mid-flight?
RHello, has anyone had an issue with a "clicky" sound when passing through the X axis?
RIt occurs when unpowered, powered, and also occurs if I hold the stick back and to the right when under load:
RR
SI never "tampered" with the userconfig, just use the maste, but with the new update tje only change I made was making msfs active and activating the axis in TelemFFB. prehaps some setting in my vpforce config? Number481, could you share you VPForce settings to check if fix it?
Sits kinda random, but happened on the ground. I took off and noticed I had no controls.... 
Nare you running ec8185c5 or dd8b0022 ?
Sc5
Sand I left off the trim follows and recent implementation to make sure.
SI think its something from VPForce config
Nunless the motors are going into fault state, I doubt its in vpconf. If its happening mid-flight and things are working fine up until then, it's not your config either.
Next time it happens. Grab the entire log from TelemFFB (log folder) and post it here or DM it to me
Next time it happens. Grab the entire log from TelemFFB (log folder) and post it here or DM it to me
Sill do
Sbut if thats the case, after TelemFFB "crashes" I still have all axis so proprably as you say not VPForce Conf fault(or mine, messing with it), but i'll do, thanks for your time wih it!
Sand patience