El mar., 17 mar. 2020 a las 14:11, Ale Martinez (Please don't email or
cc me) (<
amtri...@gmail.com>) escribió:
>
> El lunes, 16 de marzo de 2020, 13:04:06 (UTC-3), José Luis García Pallero escribió:
>>
>> El lun., 16 mar. 2020 a las 15:44, Ale Martinez (Please don't email or
>> cc me) (<
amtri...@gmail.com>) escribió:
>> >
>> > El domingo, 15 de marzo de 2020, 11:43:02 (UTC-3), José Luis García Pallero escribió:
>> >>
>> >> El domingo, 15 de marzo de 2020, 13:30:31 (UTC+1), Ale Martinez (Please don't email or cc me) escribió:
>> >>>
>> >>> Yes, via ANT+ on Windows or ANT+/BTLE on macOS/Linux
>> >>
>> >>
>> >> Mmm, I'm trying to connect the Assiomas but I can't connect to GC. I use Debian and a Lenovo workstation with integrated bluetooth. Both pedals are detected and connented. Then, in the GC Train window I select the Add device -> Bluetooth 4.0 option. Then the Add devive wizard opens (I attach a figure). It contains three buttons (Heartrate, Speed+Cadence and Power), although the drop down list does not show any device. Anyway I click on the Next option. I can see another window (figure attached) where I can introduce a name for the device. I left with "None" the option virtual, as all possible values are trainer devices. Also I left the default values for wheel size and stride length (what means this value?). Below I select "Power". Then I select finish and I can see the screen attached as train-window.png. But when I pedaling with the bike any power value is shown on the screen (I connect the device in the "Intensity adjustments and Workout Control" panel. Maybe I'm doing something wrong...
>> >
>> >
>> > You need to press the red button on the bottom toolbar to start the device(s) selected on the left sidebar, it will turn to green and the search for BTLE sensors will start, if it doesn't work goldencheetah.log may give some clue.
>>
>> Yes, I press the red button prior to pedaling. The contents of my
>> goldencheetah.log are:
>>
>> First of all, at the time of GC starting this line is written:
>>
>> "Debug: Missing CAP_NET_ADMIN permission. Cannot determine whether a
>> found address is of random or public type."
>
>
> You could sudo or use setcap to add the cap_net_admin to GoldenCheetah to see if this is the origin of the problem
Thank you for the tip. I've added as root the net capability (can not
be added this feature at compilation time?) as
setcap cap_net_admin+ep /opt/GoldenCheetah/GoldenCheetah_v3.5_amd64_Linux
and then I've checked the result:
getcap /opt/GoldenCheetah/GoldenCheetah_v3.5_amd64_Linux
/opt/GoldenCheetah/GoldenCheetah_v3.5_amd64_Linux = cap_net_admin+ep
When I start GC, the warning about CAP_NET_ADMIN is still present in
the goldencheetah.log as
Debug: Missing CAP_NET_ADMIN permission. Cannot determine whether a
found address is of random or public type.
but now I've seen power values in train mode, but with intermitent
interruptions. I've discovered that when I press the red button in the
Intensity Adjustments panel the bluetooth connection to the pedals
start to interrupt, disconnect, connect again, again disconnect...
This is reflected in the goldencheetah.log file as
Debug: Connected to device "ASSIOMA31119L"
Debug: Service scan done for device "ASSIOMA31119L"
Debug: Discovering details for service
"{00001818-0000-1000-8000-00805f9b34fb}" for device "ASSIOMA31119L"
Debug:
Debug: service state changed
QLowEnergyService::ServiceState(DiscoveringServices) for device
"ASSIOMA31119L"
Debug: Ignoring the CSC service for device "ASSIOMA31119L"
Debug: service state changed
QLowEnergyService::ServiceState(ServiceDiscovered) for device
"ASSIOMA31119L"
Debug: service state changed
QLowEnergyService::ServiceState(InvalidService) for device
"ASSIOMA31119L"
Debug: Lost connection to "ASSIOMA31119L"
Debug: Connecting to device "ASSIOMA31119L"
etc., etc.
Thanks
>
>>
>> Then, when I try to use the power meter the messages are:
>>
>> "
>> Debug: Connected to device "ASSIOMA31119L"
>> Debug: Service scan done for device "ASSIOMA31119L"
>> Debug: Discovering details for service
>> "{00001818-0000-1000-8000-00805f9b34fb}" for device "ASSIOMA31119L"
>> Debug:
>> Debug: Ignoring the CSC service for device "ASSIOMA31119L"
>> Debug: service state changed
>> QLowEnergyService::ServiceState(ServiceDiscovered) for device
>> "ASSIOMA31119L"
>> Debug: service state changed
>> QLowEnergyService::ServiceState(InvalidService) for device
>> "ASSIOMA31119L"
>> Debug: Lost connection to "ASSIOMA31119L"
>> "
>>
>> And again the Debug: Connected to device "ASSIOMA31119L" line
>>
>>
>> > --
>> > _______________________________________________
>> > Golden-Cheetah-Users mailing list
>> >
golden-che...@googlegroups.com
>> >
http://groups.google.com/group/golden-cheetah-users?hl=en
>> > ---
>> > You received this message because you are subscribed to the Google Groups "golden-cheetah-users" group.
>> > To unsubscribe from this group and stop receiving emails from it, send an email to
golden-cheetah-u...@googlegroups.com.
> To unsubscribe from this group and stop receiving emails from it, send an email to
golden-cheetah-u...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/golden-cheetah-users/fcfbb119-f1f9-438a-9cc6-e0b08d0b7025%40googlegroups.com.