Most people generally have success using a 22-in-1 universal flight simulator dongle or similar. Don't know if it works with the Radiolink AT9 though. If it has a standard 3.5mm trainer port you could try to use that one as described in the manual.
As for the AT9 - most people generally have success using a 22-in-1 universal flight simulator dongle or similar when connecting the radios. Don't know if it works with the Radiolink AT9 though. If it has a standard 3.5mm trainer port you could try to use that one as described in the manual
It's very hard though since every single controller/transmitter/radio gives different output, along with all the different dongles/cables etc. and operating system that there is. So often it is unavoidable to do some manual setting up on the radio itself anyway.
I have some old 4 channel controller connected via (again, old) ATMega64-based USB \"dongle\" (really, it is embedded into controller case, so not exactly dongle). It shows at Windows as standard joystick (without any 3rd party drivers), but with unusual channel mapping (I don't know why): Throttle (left hand, vertical) is \"X Axis\", Yaw (left hand, horizontal) is \"Rudder\", Pitch (right hand, vertical) is \"Y Axis\" and Roll (right hand, horizontal) is \"Throttle\" according to windows standard \"Game controller properties / Test\".
I just got the Orange DRX transmitter from hobbyking with the simulator dongle package, and cannot get it to work/recognize it for free rider. I am running the latest Mac OSX as well. Just wondering if anyone knows if it is possible to use this with fpv freerider and if not, other simulators that would work!
I have just spent a day on this problem with my pi. I had changed nothing but moved the box physically. My pi has a wifi connection through a WIFI dongle Realtek RTL8188CUS.Yes i have already fixed the dropout issues with some kernel module parameters, mainly \"options 8192cu rtw_power_mgnt=0 rtw_enusbss=1 rtw_ips_mode=1\" in a file /etc/modprobe.d/8192cu.conf But the pi still occasionaly used to drop out. Now i moved it seems cannot connect with a static IP 192.168.1.60. So what was problemFor me the \"RTNETLINK file exists\" is an issue set by me at sometime in my wireless router. I put a DNS entry in the router for 192.168.1.60 but with a low TTL value by mistake. Rather than TTL=1200 i had TTL=12.I removed the bad entry in the router and WIFI then connected after reboot.So if you are playing with static routes with Pi and the router at the same time beware you may have set something bad in the router.Its not always the PI network fault.
I had this problem when I got my new Wi-Fi dongle and have seen a few people with the same issue. Basically when I have one interface configured and want to swap to the other one, it throws up this error: 1e1e36bf2d