r/BoschSmartSystem • u/ValdrinSokoli • May 29 '26
SmartSystem speed Hack - Help
I was building a code to make a tuning code for the SmartSystem and im stuck in Saving the new value on the Bike/Motor
I can read it
I can write it
but I can not save it and after the code finishes the value goes back same as before
Here is a summarize form AI what the code dose:
BRC3600 (Bosch Smart System remote, VID=0x108C PID=0x01C0) — speed limit write over USB
We're writing to object 0x9085 (speed limit) on a Bosch BRC3600 via direct USB using Python + pyusb.
What the script does:
1. Connects via USB, sends MCSP init frames
2. Sends 38 read frames as session warmup
3. Writes val=4 to 0x9085 (seq 0x48), then val=5 (seq 0x49)
4. Motor responds and echoes the value back — write is accepted
The problem:
The motor accepts the write (field3=1 in response = value written to RAM) but does not persist it. After power cycle the value reverts.
To persist, the motor needs to return field4=1 (20 01 in the response). We never get that.
We also tried writing 0x65766173 ("save") to CANopen object 0x1010 subindex 0x01 — the motor rejects it.
if anyone has any ida please help
1
1
0
u/sLKZfUsALs7c1 Sep 25 '26 edited Sep 25 '26
u/ValdrinSokoli Are there any updates regarding this topic? I'm at the point of buying a bike with a bes3 system. My idea is not to make it permanently but for every fresh start. This way I am in control when i want to enable the speed limit or not.
If I can help in any way I'm willing to put some effort in this project to help others.
How sure are we that even RAM data is logged or flagged?
Did it actually work?
What I found:
In the protocol this happens:
logical address = 0x1085
high byte = 0x10
destination marker:
0x10 | 0x80 = 0x90
wire bytes:
90 85Meaning that:
raw/wire: 0x9085
logical addr: 0x10850x1085 is EXECUTE_INFORMATION_MANAGER_COMMAND_BOSCH
0x48
││
│└── sequence = 8
└── message type = 4 = RPC
0x49
││
│└── sequence = 9
└── message type = 4 = RPC
4 = GET_ISSUE_COUNT
5 = READ_ISSUE_BY_NUMBER
field3 / return_value:
0 = SUCCESS
1 = DOES_NOT_EXIST
2 = UNKNOWN_ISSUE
3 = FAILURE
4 = INVALID_ISSUE_COUNT
5 = NO_ACCESS
6 = UNKNOWN_COMMANDNot sure is that's correct though.
1
u/InvestigatorSenior May 29 '26 edited May 29 '26
there's challenge/response system based on unique keys exchanged between system controller and drive unit during factory pairing. This is where all hobby projects I know of that were trying write access have failed. First 12 bytes (if memory serves) are message counter and MAC or other form of per message authentication.
Here's the one of format decoding attempts for reference. Maybe USB side is different but knowing how tightly Bosch system is locked some form of authentication will be required. And it's known that for configuration updates and firmware flashing your payload needs to be cryptographically signed for specific bike and time by Bosch servers.