Please compare these two log files and try to identify the profile names and correct assistance levels.
Copilot said:
I can identify the profile names directly from the log payloads and infer the assistance-level mapping from the changing configuration values.

Profiles found
Log 1: 4modes_L5sensor_SWEN600_84B_2026-07-21-14-23-14.log
The sensor reports two profile names:

4modesL5 (34 6d 6f 64 65 73 4c 35)
sharepoint
9modesL5 (39 6d 6f 64 65 73 4c 35)
sharepoint


Log 2: 15modesL5sensor_SWEN600_84B_2026-07-21-14-41-53.log
The sensor reports:

15modesL5 (31 35 6d 6f 64 65 73 4c 35)
sharepoint
9modesL5 (39 6d 6f 64 65 73 4c 35)
sharepoint
Assistance levels observed
The changing byte in records beginning with 02 looks like the active assistance level:

Level byte	Decimal
0x11	17
0x12	18
0x13	19
0x14	20
...	...
0x1F	31
The corresponding 03 ... 02 xx 00 xx 00 xx 00 record carries the assistance value repeated three times.
sharepoint
+1

4modesL5 profile
From the first log:

Mode	Assistance value (hex)	Decimal
Level 0 (0x00)	BD	189
Level 17 (0x11)	BD	189
Level 18 (0x12)	57	87
Level 19 (0x13)	40	64
Level 20 (0x14)	34	52
So the effective 4-mode profile appears to be:

Off (0x00)
High = 189
Medium = 87
Low = 64
Lowest = 52
15modesL5 profile
From the second log:

Level	Value
0x11	231
0x12	189
0x13	175
0x14	114
0x15	105
0x16	87
0x17	84
0x18	77
0x19	71
0x1A	64
0x1B	60
0x1C	58
0x1D	54
0x1E	52
0x1F	49

sharepoint

This looks like a custom 15-step assistance ladder from maximum (231) down to minimum (49).

Relationship between the profiles
The 4-mode profile appears to use values that also exist inside the 15-mode profile:

4modesL5	Matching 15modesL5 level
189	Level 0x12
87	Level 0x16
64	Level 0x1A
52	Level 0x1E

sharepoint
+1

Most likely interpretation
15modesL5 = full 15-level tuning profile.
4modesL5 = a simplified profile selecting four discrete assistance levels from the same scale.
9modesL5 is present in both logs but was not actively stepped through during the recordings, so its individual assistance levels are not visible in the captured data.
sharepoint
+1
If you want, I can also decode the 01 ... status packets and determine exactly which byte corresponds to the on-bike displayed assist level versus the internal assist setting.



You said:
Can you identify how many levels of assistance are present in the first file and the second file, and what they have in common?
Copilot said:
Yes. Looking at the 02 xx level identifier packets and the corresponding 03 ... 02 yy 00 yy 00 yy 00 assistance-value packets, we can determine the number of distinct assist levels actually configured in each profile.
sharepoint
+1

First file: 4modesL5
Profile name reported:

4modesL5
sharepoint
Observed assistance levels:

Internal Level	Assist Value
0x11	189
0x12	87
0x13	64
0x14	52
So the profile contains 4 riding assistance levels:

189
87
64
52
Plus an "off" state (0x00) visible elsewhere in the log.
sharepoint

Second file: 15modesL5
Profile name reported:

15modesL5
sharepoint
Observed assistance levels:

Internal Level	Assist Value
0x11	231
0x12	189
0x13	175
0x14	114
0x15	105
0x16	87
0x17	84
0x18	77
0x19	71
0x1A	64
0x1B	60
0x1C	58
0x1D	54
0x1E	52
0x1F	49
So this profile contains 15 riding assistance levels.
sharepoint

What do they have in common?
The interesting part is that every level in the 4-mode profile exists inside the 15-mode profile.
sharepoint
+1

4modesL5 value	Matching 15modesL5 value
189	189
87	87
64	64
52	52
In fact, the 4-mode profile appears to be a subset of the 15-mode profile:




Plain Text
15modesL5:
231, 189, 175, 114, 105, 87, 84, 77, 71, 64, 60, 58, 54, 52, 49

4modesL5:
189, 87, 64, 52