![]() ![]() Users have reported Bluetooth connection issues using this adapter with GoldenCheetah v3.6 on Windows 10, there is not known solution for this problem, except for switching to alternative adapters. ![]() ![]() Intel Dual Band Wireless AC8260 (Bluetooth) New in v3.6 is a contributed patch allowing control of TACX trainers using these sticks, if you are on v3.5 it may worth a try. There is no workaround for this, other than to use another ANT+ Stick (Garmin, Suunto and Elite ANT+ sticks are known to work, for example), or to switch to BTLE for supported sensors. Cycplus/Anself ANT+ StickĪccording to several users reports Cycplus/Anself ANT+ Sticks don’t work with GC Train mode and confirmation from the manufacturer has been relayed to users forum, usually they are detected but no sensors are found or the trainer cannot be controlled or speed and cadence sensors drop data, even when it can work with other applications. A workaround is to copy Qt5Bluetooth.dll from version 3.5, that would allow GC to run without BTLE support. V3.6-DEV Users on Windows 7 and 8 are reporting failures indicating that Qt5Bluetooth.dll version only works with win10, likely because it depends on features not present in these OS versions. GoldenCheetah v3.5 was built using Qt5.9 which doesn't support Bluetooth On Windows, but includes a dummy backend to allow the application to run anyway and BTLE functions are disabled.įor v3.6-DEV we are building with Qt5.14.2, which supports BTLE on Windows 10, and including that backend in the distribution, so Windows 10 users should have the same BTLE support previously available on Linux and macOS. Sudo setcap cap_net_admin+eip GoldenCheetah_v3.5_amd64_Linux.AppImage BTLE on Windows Some Linux distributions require the cap_net_admin capability for GoldenCheetah to be able to discover and use BTLE sensors, this error is reported on goldencheetah.log when the BTLE device is started in Train mode and can be fixed with the following command: WIFI Routers can also be a source of interference for ANT+ connections, see Solving WiFi Interference for details.īTLE tends to be a more robust protocol than ANT+ interference wise, if available it may worth the change. Your trainer manual should have a detailed list, otherwise this one from Wahoo is generally useful: SIGNAL INTERFERENCE WITH WAHOO SMART TRAINERS To avoid this an extensor cable to put the receiver close to the trainer may be necessary.Ĭheck for the presence of nearby transmitting electronic devices which can be interference sources. In more general terms, signal interference can also provoke unexpected fluctuations, drop to zero and spikes. No need to select Power and Speed as your trainer already sends this data on the FE-C channel for GoldenCheetah to read. When connecting your smart trainer to GC you should only connect the FE-C channel. # Garmin ANT+ - USB1ĪTTRS="1009", MODE="0666"įor the Tacx USB Ant+ Antenna the file name and it's content can be as described above, there's no need rename Garmin into Tacx, add anything to the file, or remove the Garmin specific wording for the Tacx Antenna to work. Garmin stick/Tacx Antenna to be accessable from GoldenCheetah when run as a normal (not root) user. On UBUNTU and other Debian based distros this is achieved by writing a rules file and placing it in /etc/udev/rules.d.Ĭreate a file containing the text below called les and copy it into /etc/udev/rules.d for the To change the way permissions are granted you need to configure udev with a rules file. When using Garmin USB2 stick/Tacx Antenna on Linux the udev rules that control access to the USB devices tend to mount the Garmin stick/Tacx Antenna with permissions that restrict access to normal users. The Garmin USB stick and the Tacx USB Ant+ Antenna (a.k.a T2028) use the same hardware (and thus have the same idVendor and idProduct), so the info below applies for both devices. Accessing the Garmin USB2 stick & Tacx USB Ant+ Antenna (T2028) on Linux To ensure there is no conflict, turn bluetooth on your device off entirely when training. NOTE: The trainer may not appear under the list of connected Bluetooth devices on your phone or tablet, but the connection may still be interfering. your phone connected to the trainer via bluetooth will stop the trainer from connecting via ANT+ to GC. If you TacX trainer FE-C is not working as expected trying turning off bluetooth on your phone/ipad/other controller device. Troubleshooting TacX Device FE-C connection ![]()
0 Comments
Leave a Reply. |