-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elite Trainer code #4
Comments
Dear Filippo, I look forward to the results! Beste Wishes, |
Dear Jörgen! of course I'm serious ;-) After the nRF check, i modified the ino file "Test_FE-C_over_BLE" Next step to change the UUID on the main program and let's see how SimCline responds and also SimCline companion App Regards |
I tried to change Tacx's UUID with Elite in main program.. unfortunately it not works (not read page 51). |
Dear Filippo,
I tried to change Tacx's UUID with Elite in main program..
Did you monitor the Serial Output of the Simcline code? Does it look like
the output of "Test_FE-C_over_BLE" ?
unfortunately it not works (not read page 51).
Do you mean that you do not get a response (from Elite trainer) when the
code sends "request for data page 51". The previous sample output (test
program) did not show a response on the page 51 request...
Any suggestions or can I close the issue?
If they do not have implemented the full FE-C protocol, what about other
(open source) protocols that Elite has implemented? How has Elite
implemented the communication with their Rizer product?
Best wishes,
Jörgen
Op za 8 okt. 2022 om 11:58 schreef cherryphilip ***@***.***>:
… I tried to change Tacx's UUID with Elite in main program.. unfortunately
it not works (not read page 51).
Any suggestions or can I close the issue?
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANS5LSRAOJP42J6EQ6VX5I3WCFASXANCNFSM6AAAAAAQVE2M7Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I am curious about your answer and the present status! |
After some thought: I suggest that you try the following setup:
Possibly you tested previously only connecting the Direto over BLE with Zwift. Connecting over ANT+ with Zwift might change the way the Direto code handles and stores information... Testing is knowing! |
Hi, |
Dear Filippo, |
Thanks for the very helpful info! |
Hi Jorgen!
I understand and it's not easy to implement soon. I did see the DC RAINMAKER post you shared with me and also looked at this related trend on FE-C over ANT+.
laberning/openrowingmonitor#71
Thank you that you will keep me in case of help and / or further specific information on Elite Direto XR!
Best Regards
Filippo
Sent: Tuesday, October 18, 2022 at 11:34 AM
From: "Jörgen van den Berg" ***@***.***>
To: "Berg0162/simcline" ***@***.***>
Cc: "cherryphilip" ***@***.***>, "Author" ***@***.***>
Subject: Re: [Berg0162/simcline] Elite Trainer code (Issue #4)
Thanks for the very helpful info!
Do not spend any time (anymore) on FE-C over BLE! All Elite trainers support FE-C over ANT+ only (!) and FE-C over BLE is definitely not supported by Elite on any of their trainer products. FE-C over BLE (conforming ANT+) is exclusively supported by TACX. See for a list of supported protocols: https://www.dcrainmaker.com/2020/11/smart-cycle-trainer-recommendations-guide-winter.html
My strategy now is to code a MITM for (open standard) FTMS and use the eavesdropped Grade info, that a trainer app (like Zwift) is sending, to drive the Simcline device up and down. That strategy worked well before with the Wahoo Kickr proprietary protocol.....
It will take an undetermined amount of time, patience and no garanties are given!
I will contact you when I need help and/or additional Elite Direto XR specific info!
Beste wishes,
Jörgen.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Dear Filippo, |
Dear Filippo, |
Hi Jörgen,I'm sorry for my answer delay. I will check within this Wednesday.At the moment I'm mission for wor and i come back home tomorrow night.Best RegardsFilippo Sent from Android deviceIl 14 nov 2022 10:25, Jörgen van den Berg ***@***.***> ha scritto:
Dear Filippo,
Hopefully you received the previous post.....
I very much would appreciate that you test the FTMS_Client_v01 code with your Elite Direto trainer and supply me with the Serial Monitor output during the first minutes....
Beste wishes,
Jörgen.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hi Jörgen! Here below the serial monitor output and a simple screenshot of the Zwift app during a workout. I used the Test_FTMS_Client_plus_CPS_CSC_v01.ino 18:48:35.266 -> Feather nRF52 Client/Central: FTMS, CPS and CSC Best Regards |
Hi Jörgen! Here below the serial monitor output. I used the FTMS_Client_v01.ino 19:02:48.407 -> Feather nRF52 Client/Central: FTMS, CPS and CSC Best REgards |
Hi Jörgen! After pairing with Zwif, my avatar is moving with more effort in the Zwift world controlled by the nRF52 Feather. 19:16:56.992 -> Feather nRF52 Server/Peripheral: FTMS, CPS and CSC The serial monitor output show only few rows, no futher informatios from it. Best Regards |
Dear Filippo, With respect to the FTMS_Server it is very clear that FTMS_Server did NOT connect to Zwift... The fact that you had resistance on the trainer tells the story: the Elite trainer was connected instead of FTMS_Server..... Next time do not power on the trainer, just connect manually FTMS_server to Zwift. You can easily recognize its device name being very different from your Elite trainer when pairing with Zwift. |
Dear Filippo, Please handle in the indicated order:
Good luck, |
Dear Jörgen.! Here my feedback 1. Upload and Run this code on the Feather nRF52 11. Hop on the bike: make your avatar move and feel resistance change with the road Best Regards |
Dear Filippo, |
Hi Jörgen. The night brings good ideas and so it was!!! I uploaded the new version of FTMS_Client_v012. Below you find the serial monitor data without the first part of bluetooth connection side the trainer. So we have: - nRF52 has been paired with Elite trainer by Bluetooth. - Zwift app connected to trainer by ANT+ - I started ride with the serial monitor output window visible on top of the Zwift window - Avatar moved and I felt resistance change with the road - Speed, Cadence and Power shown on serial monitor were been matches with Zwift app, but distance is misaligned. I waiting the next step. Have a nice weekend Best Regards |
Dear Filippo, |
Dear Jörgen!
Thanks for your reply. I will can try tomorrow afternoon.
Meanwhile I've downloaded all three *.ino files and I hope to do a fast check this afternoon later.
Best Regards
Filippo
Da: Jörgen van den Berg ***@***.***>
Inviato: domenica 27 novembre 2022 14:31
A: Berg0162/simcline ***@***.***>
Cc: cherryphilip ***@***.***>; Author ***@***.***>
Oggetto: Re: [Berg0162/simcline] Elite Trainer code (Issue #4)
Dear Filippo,
It took some time but now I have uploaded version 02 of the test codes!
See: https://github.com/Berg0162/simcline/tree/master/FTMS%20Enabled
You are invited to give all 3 a try and report the different screen outputs.
Notice that FTMS Client should now only connect to a FTMS enabled trainer and not to an extra power meter!
Furthermore MITM needs the Mac Addresses of your trainer and Laptop/PC (with Zwift) to be able to run!
I am particularly interested in how you experience its presence between trainer and Zwift. Afterall it should be transparent so you have to feel (the resistance) with any change in road grade like you would normally experience during indoor cycling!
If the code is doing well we came a lot closer to our final goal...
Thanks in advance and best wishes,
Jörgen.
—
Reply to this email directly, view it on GitHub <#4 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEVV6QSRKFQ7ULYMVTAP2B3WKNO7ZANCNFSM6AAAAAAQVE2M7Q> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AEVV6QSC5TB5ZGDCBBJTLFLWKNO7ZA5CNFSM6AAAAAAQVE2M7SWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSPFNY72.gif> Message ID: ***@***.*** ***@***.***> >
|
Hi Jörgen, File 1 Output from serial monitor. 19:08:09.902 -> Feather nRF52 Client/Central: CPS, CSC and FTMS File 2 utput from serial monitor. After pairing, I saw power value and rmp speed changing on "paired devices window" Same results with the avatar Here output from serial monitor. 19:20:04.519 -> Feather nRF52 Server/Peripheral: CPS, CSC and FTMS File 3 Output from serial monitor. Avatar moved according to trainer, but no feedback from serial monitor 19:54:18.845 -> Feather nRF52840 MITM supporting: CPS, CSC and FTMS Best Regards |
Dear Filippo, WARNING grade data btw serial monitor and zwift monitor discrepancy Best wishes, |
Hi Jörgen,!
I think that client receive info from trainer, but nRF52 is not able to manage the trainer. 10:07:43.146 -> Feather nRF52 Client/Central: CPS, CSC and FTMS 2) Feedback from FTMS_Zwift_Bridge_v02 serial monitor: 19:49:03.382 -> Feather nRF52840 MITM supporting: CPS, CSC and FTMS Let me know the next step Best Regards |
Dear Filippo, 19:49:03.382 -> Feather nRF52840 MITM supporting: CPS, CSC and FTMS Please check the Mac Addresses of Trainer and Laptop --> did you make a typo when entering these in the program code ??? |
Daar Filippo,
All signs are green but the data exchange does not start after Zwift sends
a "request for machine control"...
Please retry and run the Bridge again with Zwift. You can easily see in the
ouput when the exchange succesfully starts!
In addition you can run it with Rouvy for testing, that should work as
well...
Success!
Jörgen.
Op za 3 dec. 2022 17:53 schreef cherryphilip ***@***.***>:
… Dear Jörgen!
*my fault, I* put a *wrong MAC address* (last two codes).
Here the serial monitor output data.
No resistance when the road grade changes
I used Zwift and Rouvy apps for this test.
In Zwift i found *DIRETO XR S57*
In Rouvy I found *DIRETO XR Sim*
[image: image]
<https://user-images.githubusercontent.com/19619650/205452085-30b629a1-4eee-463f-acad-d3029a5c451b.png>
17:38:15.675 -> Feather nRF52840 MITM supporting: CPS, CSC and FTMS
17:38:15.675 -> ------------------ Version 02 ---------------------
17:38:15.957 -> FTM Service and Chars are 'initialized'
17:38:15.957 -> CP Service and Chars are 'initialized'
17:38:15.957 -> CSC Service and Chars are 'initialized'
17:38:15.957 -> Generic Access Service and Chars are 'initialized'
17:38:15.957 -> Device Information Service and Chars are 'initialized'
17:38:15.957 -> Start Client-side Scanning for CPS, CSC and FTMS!
17:38:16.096 -> Peripheral device (Trainer) found that has FTMS [1826]
enabled!
17:38:16.096 -> Advertising Peripheral with FTMS, CPS and CSC is found!
See Raw data packet:
17:38:16.096 -> Timestamp Addr Rssi Data
17:38:16.096 -> 000000424 EE:18:4B:1F:9F:3E -67
03-19-85-04-02-01-06-05-02-26-18-18-18-06-16-26-18-01-20-00-0A-09-44-49-52-45-54-4F-20-58-52
17:38:16.190 -> Feather nRF52 (Central) connected to Trainer (Peripheral)
device: [DIRETO XR] MAC Address: EE:18:4B:1F:9F:3E
17:38:16.190 -> Now checking all mandatory Client Services and
Characteristics!
17:38:16.190 -> Discovering Client Cycling Power (CP) Service ... Found
it! CPS Max Payload: 20 Data Length: 27
17:38:16.237 -> Discovering Client CP Measurement characteristic ... Found
it!
17:38:16.331 -> Discovering Client CP Control Point characteristic ...
Found it!
17:38:16.517 -> Discovering Client CP Feature characteristic ... Found it!
17:38:16.658 -> -> Client Reads Raw CP Feature bytes: [4] [ 0D 02 00 00 ]
17:38:16.658 -> Pedal power balance supported
17:38:16.658 -> Wheel revolution data supported
17:38:16.658 -> Crank revolution data supported
17:38:16.658 -> Offset compensation supported
17:38:16.658 -> Discovering Client CP Sensor Location characteristic ...
Found it!
17:38:16.705 -> -> Client Reads CP Location Sensor: Loc#: 0 Other
17:38:16.705 -> Discovering Cycling Speed and Cadence (CSC) Service ...
Found it! CSCS Max Payload: 20 Data Length: 27
17:38:16.800 -> Discovering Client CSC Measurement CHR ... Found it!
17:38:16.891 -> Discovering Client CSC Location CHR ... Found it!
17:38:16.985 -> -> Client Reads CSC Location Sensor: Loc#: 0 Other
17:38:16.985 -> Discovering Client CSC Feature CHR ... Found it!
17:38:17.079 -> -> Client Reads Raw CSC Feature bytes: [2] [ 03 00 ]
17:38:17.079 -> Wheel rev supported
17:38:17.079 -> Crank rev supported
17:38:17.125 -> Found Client Generic Access
17:38:17.218 -> Found Device Name: [DIRETO XR]
17:38:17.310 -> Found Appearance: [1157]
17:38:17.357 -> Found Client Device Information:
17:38:17.499 -> Client Manufacturer: Elite
17:38:17.781 -> Client Serial Number: 52687
17:38:17.781 -> Discovering Client Fitness Machine (FTM) Service ... Found
it! FTMS Max Payload: 20 Data Length: 27
17:38:17.829 -> Discovering Client FTM Feature Characteristic ... Found it!
17:38:17.922 -> -> Client Reads Raw FTM Feature bytes: [8] [ 86 50 00 00
0C E0 00 00 ]
17:38:17.922 -> Discovering Client FTM Training Status Characteristic ...
Found it!
17:38:18.017 -> Discovering Client FTM Supported Resistance Level Range
Characteristic ... Found it!
17:38:18.157 -> -> Client Reads Raw FTM Supported Resistance Level Range
bytes: [6] [ 00 00 C8 00 01 00 ]
17:38:18.157 -> Discovering Client FTM Supported Power Range
Characteristic ... Found it!
17:38:18.295 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [
00 00 A0 0F 01 00 ]
17:38:18.295 -> Discovering Client FTM Indoor Bike Data Characteristic ...
Found it!
17:38:18.389 -> Discovering Client FTM Control Point Characteristic ...
Configuring the Server Device Information Service
17:38:18.576 -> Configuring the Server Cycle Power Service
17:38:18.576 -> Configuring the Server Cadence and Speed Service
17:38:18.576 -> Configuring the Server Fitness Machine Service
17:38:18.623 -> Configuring the Server NUS ServiceFound it!
17:38:18.623 -> Discovering Client FTM Status Characteristic ...
17:38:18.623 -> Setting up the Server-side advertising payload(s)
17:38:18.623 -> Setting Server Device Name to: [DIRETO XR Sim]
17:38:18.623 -> Setting Server Appearance to: [1157]
17:38:18.623 -> Server-side is CPS, CSC and FTMS advertising!
17:38:18.810 -> Found it!
17:39:40.266 -> Feather nRF52 (Peripheral) connected to Central device:
[DESK-CHERRYPHIL] MAC Address: 40:23:43:A5:FE:78
17:39:40.266 -> Enabled 'Notify' for Client CP Measurement values
17:39:40.266 -> Enabled 'Indicate' for Client CP ControlPoint Responses
17:39:40.266 -> Enabled 'Notify' for Client CSC Measurement values
17:39:40.313 -> Enabled 'Notify' for Client FTM TrainingStatus values
17:39:40.313 -> Enabled 'Notify' for Client FTM IndoorBikeData values
17:39:40.361 -> Enabled 'Indicate' for Client FTM ControlPoint Response
Messages
17:39:40.407 -> Enabled 'Notify' for Client FTM Status values
17:39:40.407 -> Waiting for Central (Zwift) to set CCCD Notify/Indicate
(enable) and start....
17:39:42.649 -> Client- and Server-side are Up and Running!
17:39:43.026 -> Central Device Updated CCCD to: [1] --> Server CP:
Measurement 'Notify' enabled
17:39:43.120 -> Central Device Updated CCCD to: [2] --> Server CP:
ControlPoint 'Indicate' enabled
17:39:43.294 -> Central Device Updated CCCD to: [1] --> Server CSC:
Measurement 'Notify' enabled
17:39:43.520 -> Central Device Updated CCCD to: [1] --> Server FTM:
IndoorBikeData 'Notify' enabled
17:39:43.660 -> Central Device Updated CCCD to: [1] --> Server FTM: Status
'Notify' enabled
17:40:17.369 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:17.369 -> Request Control of Machine!
17:40:20.373 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:20.373 -> Request Control of Machine!
17:40:23.447 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:23.447 -> Request Control of Machine!
17:40:26.473 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:26.473 -> Request Control of Machine!
17:40:29.472 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:29.472 -> Request Control of Machine!
17:40:32.455 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:32.455 -> Request Control of Machine!
17:40:39.893 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:39.893 -> Request Control of Machine!
17:40:42.883 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:42.883 -> Request Control of Machine!
17:40:46.010 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:46.010 -> Request Control of Machine!
17:40:46.290 -> -> Client Rec'd Raw FTM Training Status Data: [2] [ 00 00 ]
17:40:48.920 -> -> Client Rec'd Raw FTM Training Status Data: [2] [ 00 09 ]
17:40:48.968 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:48.968 -> Request Control of Machine!
17:40:49.719 -> -> Client Rec'd Raw FTM Training Status Data: [2] [ 00 00 ]
17:40:51.964 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:51.964 -> Request Control of Machine!
17:40:54.963 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:54.963 -> Request Control of Machine!
17:40:57.950 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:40:57.950 -> Request Control of Machine!
17:41:00.990 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:00.990 -> Request Control of Machine!
17:41:04.014 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:04.014 -> Request Control of Machine!
17:41:07.006 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:07.006 -> Request Control of Machine!
17:41:10.088 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:10.088 -> Request Control of Machine!
17:41:13.077 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:13.077 -> Request Control of Machine!
17:41:16.066 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:16.066 -> Request Control of Machine!
17:41:19.053 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:19.053 -> Request Control of Machine!
17:41:22.136 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:22.136 -> Request Control of Machine!
17:41:25.120 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:25.120 -> Request Control of Machine!
17:41:28.116 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:28.116 -> Request Control of Machine!
17:41:31.145 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:31.145 -> Request Control of Machine!
17:41:34.138 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:34.138 -> Request Control of Machine!
17:41:37.181 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:37.181 -> Request Control of Machine!
17:41:40.178 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:40.178 -> Request Control of Machine!
17:41:43.176 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:43.176 -> Request Control of Machine!
17:41:46.264 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:46.264 -> Request Control of Machine!
17:41:49.251 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:49.251 -> Request Control of Machine!
17:41:52.231 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:52.231 -> Request Control of Machine!
17:41:55.265 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:55.265 -> Request Control of Machine!
17:41:58.308 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:41:58.308 -> Request Control of Machine!
17:42:01.356 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:01.356 -> Request Control of Machine!
17:42:04.302 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:04.302 -> Request Control of Machine!
17:42:07.303 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:07.303 -> Request Control of Machine!
17:42:10.302 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:10.302 -> Request Control of Machine!
17:42:10.820 -> -> Client Rec'd Raw FTM Training Status Data: [2] [ 00 09 ]
17:42:13.290 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:13.290 -> Request Control of Machine!
17:42:16.375 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:16.375 -> Request Control of Machine!
17:42:19.364 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:19.364 -> Request Control of Machine!
17:42:22.349 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:22.349 -> Request Control of Machine!
17:42:25.380 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:25.380 -> Request Control of Machine!
17:42:28.417 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:28.417 -> Request Control of Machine!
17:42:31.452 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:31.452 -> Request Control of Machine!
17:42:34.447 -> -> Server Rec'd Raw FTM Control Point Data [len: 1]
[OpCode: 00] [Values: 00 ]
17:42:34.447 -> Request Control of Machine!
17:42:41.790 -> Central Device Updated CCCD to: [0] --> Server CP:
Measurement 'Notify' disabled
17:42:41.930 -> Central Device Updated CCCD to: [0] --> Server CP:
ControlPoint 'Indicate' disabled
17:42:42.070 -> Central Device Updated CCCD to: [0] --> Server CSC:
Measurement 'Notify' disabled
17:42:42.163 -> Central Device Updated CCCD to: [0] --> Server FTM:
IndoorBikeData 'Notify' disabled
17:42:42.305 -> Central Device Updated CCCD to: [0] --> Server FTM: Status
'Notify' disabled
17:42:45.579 -> Server disconnected from Central (Laptop):
[DESK-CHERRYPHIL], reason: [13]
Sorry again for my wrong mac address informations
Best Regards
Filippo
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANS5LSUPOJQFBCX2CTYXKBDWLN3HLANCNFSM6AAAAAAQVE2M7Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Dear Filippo, |
Dear Jörgen! starting for this I will send other two reports one for each ino file.
In bold highlighted when resistance changed 18:13:14.949 -> Feather nRF52 Client/Central: CPS, CSC and FTMS 18:13:35.815 -> -> Client Rec'd Raw FTM Training Status Data: [2] [ 00 09 ] Next report; FTMS_SERVER_V022 Best Regards |
Dear Jörgen! Second report. >>>>>>>>>>>>>>FTMS_SERVER_V022 <<<<<<<<<<<<< 18:42:44.131 -> Feather nRF52 Server/Peripheral: CPS, CSC and FTMS Next report; FTMS_ZWIFT_BRIDGE_V022 Best Regards |
Dear Jörgen! third and last report. >>>>>>>>>>>>>>FTMS_ZWIFT_BRIDGE_V022 <<<<<<<<<<<<< I felt resistance change as I pedaled. Max slope reached is 6%, but this value not found on serial monitor 18:53:43.671 -> Feather nRF52840 MITM supporting: CPS, CSC and FTMS I hope that these data are hopefully for you Best Regards |
Ciao Filippo, |
Migrate to Testing Simcline with FTMS v01 |
Dear Jörgen!
I came back here, but today not for an issue regarding the my SimCline simulator (it works fine!).
Recentelly I bought a new Elite Direto XR-T trainer for my new SCOTT ADDICT RC bike and i saw that SimCline now is availble also Wahoo trainer and of couse TACX too.
So, I would like to contribute to the development of SimCline for ELITE if you plan to do it, so that SimCline can communicate with the best trainers on the market and to be a reference for us.
Let me know how I can be useful
Best Regards
Filippo (cherryphilip)
The text was updated successfully, but these errors were encountered: