I have to check later but yes i supose I have to test the trim because I had the old config
I have to check later but yes i supose I have to test the trim because I had the old config
Swell, is working in flight
Sbut now the aileron in flight its weird almost like loose
NWait.. you were trying the autopilot on the ground before?
NIf you want to increase the spring strength of the axes, change these values in the aircraft config...
Syes
Sand i should work because its a so old system that it dont know if its on the air or groun.. it the same
Sbut the rhino dont comply
NThe rhino doesnt comply because it cant comply.. This is a simulation and we do the best we can to emulate real life behavior.
On the ground, your controls are limp. In Rhino speak, that means we have zero spring force applied to the stick.
With no spring force on the stick, we can't move the center point of said spring force to make the joystick follow the virtual control.
Might work if you configure the aircraft as "center sprung".. which will set a minimum spring force that will be applied to the axes, even when the aircraft is idle on the ground...
On the ground, your controls are limp. In Rhino speak, that means we have zero spring force applied to the stick.
With no spring force on the stick, we can't move the center point of said spring force to make the joystick follow the virtual control.
Might work if you configure the aircraft as "center sprung".. which will set a minimum spring force that will be applied to the axes, even when the aircraft is idle on the ground...
Swell... it simulates the weight of the elevator..
Nelevator droop is just a "constant" force. Constant forces are simply "an amount of force in a given direction"....
Sundervolt error.
Well, I was gettting away with an old 12v 5a laptop brick, so I replaced it with a 20v brick. I know someone mentioned the psu I list was weak...they were right.
Instructions updated
Well, I was gettting away with an old 12v 5a laptop brick, so I replaced it with a 20v brick. I know someone mentioned the psu I list was weak...they were right.
Instructions updated
SThanks
AAh dang it lol I’ll order another one that 5a is suppose to be here tomorrow lol
WYeah, 12Vx5A = 60W which is pretty low compared to included Rhino PSU of 180W
Sthat actually happended to me, with the new telemFFB and the lastest firmware
Sthe long beep and shutdown of one motor
AWhat’s average lead time on a motor set?
JMine shipped out almost immediately.
AIs it possible to adjust the frequency of the vibration effects TelemFFB creates?
AThis should work yeah? SHNITPWR Universal Power Supply DC 24V 12V 5V 6V 9V 14V 19V Adjustable AC/DC Adapter 100V~240V AC to DC Variable Power Converter Multi-Voltage 3.5V ~ 24V 6A 144W Power Adapter 14 Tips LCD Display https://a.co/d/iIdf1Qk
SHNITPWR Universal Power Supply DC 24V 12V 5V 6V 9V 14V 19V Adjustable AC/DC Adapter 100V~240V AC to DC Variable Power Converter Multi-Voltage 3.5V ~ 24V 6A 144W Power Adapter 14 Tips LCD Display
Ndepends on the effect you are talking about. Some are fixed frequency, some are based on real-time telemetry, and some are configurable indirectly by adjusting parameters is the config.
Whttps://www.amazon.com/LRS-350-24-Switching-Supply-350-4W-115Vac/dp/B07RF38JXK this one is a great bang for the buck
350.4W 24V 14.6A Single Output Switchable Power Supply 24 Volts @ 14.6 Amps
SYea the 180w unit I have now is perfect. Thanks again.
I updated docs so no other diy makes the same mistake
I updated docs so no other diy makes the same mistake
HOut of curiosity, could a stronger PSU allow higher motor currents in the rhino without any additional issues?
Aheat is already a thing so at least that would become a limiting factor fairly early on
Sits just me or the x axis is having a big tendency to keep temperature than the y?
SIs it possible that A2A comanche has some FFB implementation that makes some problems with telemFFB? I got a lot of vibration and a long beep and after that the roll comes nimble and the vibration ceases and pitch. it happens more when above terrain over water its gets more smooth.
WThis could be general instability, not necesarily telemFFB. Can you show your VPconf settings?
S
S
SI did nothing but update to the latest telemFFB
Ntry lowering friction (or set it to zero to test).. I still find that any amount of friction will often cause oscillations.
Also, have you modified your spring gain map?
Also, have you modified your spring gain map?
SI did not, because that not so relevant to me.. I was just testing it.
SI'll try the friction and report back
Scan I edit efects in TelemFFB live or I need to reboot the app?
Nmost things you can edit/save the config or the user config live (keeping in mind that userconfig will override primary config)
BI did not know that!
NYessir.... the only things you cant modify on the fly are the system variables (like enabled sims, etc).
Also, you can't add a new aircraft section while live either. That will require a restart (of telemFFB).
Also, you can't add a new aircraft section while live either. That will require a restart (of telemFFB).
Ai would say in general, avoid using friction, use damper instead
Ai.e. jack damper back up to 100%, (probably worth doing the same with inertia as well), and maybe keep friction in the Settings tab at 10% or lower, and also yeet it from the effects tab and instead add some damper to give it that mechanical feeling
Sthe thing is that I had friction all 100 with no issues prior the last update from TelemFFB
Sshould I remove Friction in the effects tab too?
Swhat is this? often it happens and I have to restart TelemFFB.
STraceback (most recent call last):
File "main.py", line 449, in process_data
File "aircrafts_msfs.py", line 712, in on_telemetry
File "aircrafts_msfs.py", line 680, in on_telemetry
File "aircrafts_msfs.py", line 571, in _update_flight_controls
File "simconnect\sc.py", line 197, in send_event
File "simconnect\datadef.py", line 137, in map_event_id
File "simconnect\sc.py", line 66, in _callable
File "_ctypes/callproc.c", line 993, in GetResult
OSError: [WinError -1073741648] Windows Error 0xc00000b0
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 488, in run
File "main.py", line 453, 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'
File "main.py", line 449, in process_data
File "aircrafts_msfs.py", line 712, in on_telemetry
File "aircrafts_msfs.py", line 680, in on_telemetry
File "aircrafts_msfs.py", line 571, in _update_flight_controls
File "simconnect\sc.py", line 197, in send_event
File "simconnect\datadef.py", line 137, in map_event_id
File "simconnect\sc.py", line 66, in _callable
File "_ctypes/callproc.c", line 993, in GetResult
OSError: [WinError -1073741648] Windows Error 0xc00000b0
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 488, in run
File "main.py", line 453, 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'
NIf you have friction enabled, and your hand is the only thing moving the stick, the oscillations might not occur. However, s soon as the trim/AP following in latest TelemFFB is moving the stick by itself without your hand on it to stop the oscillations from beginning to amplify.. that can absolutely start the oscillations.
Also... while your friction slider is %100.. you are limiting it to %20 in the effects tab.. important to understand how the two tabs work together.
Also... while your friction slider is %100.. you are limiting it to %20 in the effects tab.. important to understand how the two tabs work together.
NCan't say for sure. I've not seen that myself nor had any other reports of similar errors...
It looks like an issue with the simconnect code sending the axis position to MSFS.
How is the stability of your USB connection to the Rhino? Does it ever momentarily disconnect/reconnect by itself?
It looks like an issue with the simconnect code sending the axis position to MSFS.
How is the stability of your USB connection to the Rhino? Does it ever momentarily disconnect/reconnect by itself?
Sno, just happens in the sim
W0xC00000B0 is a Windows kernel "disconnected pipe" error. Simconnect should recover automatically and probably would be a good idea to put the
send_eventeasy enough!
Sglad to help 