As promised, here are the results of my modifications -
This was sent as Feedback to Bikee by 'bedesign' after 60 Km
------------------------------------------------------------
When the issues described below are managed,
I would recommend the set.
Edit: bending = manual shaping
At the beginning of the shaping of the rear chain guide rod to
~45°, it broke like brittle porclaine.
This could be prevented by heating the piece with a heat gun
to 200°C - and not more.
WARNING! never use a gas burner - it will ignite, which is impossible
to extinguish.
The metal is possibly magnesium with a low content of alloy.
I manufactured a replacement from silicon-aluminium.
Edit:
I now tested a 2 mm piece of my replaced rear chain guide rod for
the risk of ignition while heating it to a bright red color,
Well, it didn't burn at all !
So I lower the warning to no or low risk.
The crank arm outer threads are not
parallel with the square hole
-----------------------------
I corrected the wobble to within 0.5mm by manually grinding the square
hole surfaces on only the offending areas to 50% of their axial depths,
just until the eloxation layer was removed at the inner and outer and
top and bottom opposite sides.
- (but this is not for the average customer)
The pinion is not totally stable
--------------------------------
The depth of the grove on the axle for the segger is not very deep,
and may allow the pinion to force the segger out of its
position.
I'm trying a modification that might eliminate the segger
by adding a total of 4.0mm spacers behind the pinion,
and a 1 to 2mm spacer at the front.
Then I added a thread locker and adjusted the screw until a
slight friction was noticed when the pinion is fully
pushed seated.
After a some tenths of Km runs, it's still totally stable,
but should be tested for longer.
Edit:
I had to change the 42T chain wheel to 36T because the chain kept
swinging down on top of it, despite there was clearence with
the chain stretched under load.
(I plan to later add the installation of another pulley to keep
the chain from swinging low and going back to 42T)
This resulted in the chain being too long now, and combined
with a bad, abrupt high gear change under load, it derailed
from the pinion and pulley and put a brutal sideway force
on them.
This resulted in a hard, unwanted test of stability -
but, there was still not the slightest trace of a wiggle.
So I think this simple modification can be relied on.
I needed your support for updating the display
before I found an odd fix, see further below.
--------------------------------------------
My mobile Android version is 13
and the display is not actively BT-bonded
to the phone, only listed as available -
as advised.
The App version is 94
original motor controller fw rev. 072
original display fw rev. 026
The update begins, but then the Bluetooth indicator on the display
turns off and resets with an error message in the App:
DFU Device Disconnected
Error type: 0
Error: 4096
Edit:
By using the Nordic nRF Connect App for monitoring while updating,
the connection was kept and not reset?
And the update to ver. 053 was sucsessful!
Though let's see for future occasions if that's still needed.
Edit:
Just received a morning surprise, an almost auto update (no QR code required)
of the motor controller took ~14 minutes to rev.127.0!
nRF Connect, 2024-06-09
DfuTarg (E8:19:F3:4E:AE:9D)
D 18:54:29.128 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
D 18:54:29.145 gatt.close()
D 18:54:29.148 wait(200)
V 18:54:29.349 Connecting to E8:19:F3:4E:AE:9D...
D 18:54:29.350 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D 18:54:29.361 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I 18:54:29.361 Connected to E8:19:F3:4E:AE:9D
V 18:54:29.383 Discovering services...
D 18:54:29.383 gatt.discoverServices()
I 18:54:29.561 Connection parameters updated (interval: 22.5ms, latency: 0, timeout: 4000ms)
I 18:54:29.725 Connection parameters updated (interval: 7.5ms, latency: 0, timeout: 5000ms)
D 18:54:29.925 [Callback] Services discovered with status: 0
I 18:54:29.925 Services discovered
V 18:54:29.931 Generic Access (0x1800)
- Device Name [R W] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
Generic Attribute (0x1801)
- Service Changed (0x2A05)
Client Characteristic Configuration (0x2902)
Device Firmware Update Service (00001530-1212-efde-1523-785feabcd123)
- DFU Packet [WNR] (00001532-1212-efde-1523-785feabcd123)
- DFU Control Point [N W] (00001531-1212-efde-1523-785feabcd123)
Client Characteristic Configuration (0x2902)
- DFU Version [R] (00001534-1212-efde-1523-785feabcd123)
D 18:54:29.932 gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
I 18:54:29.986 Connection parameters updated (interval: 22.5ms, latency: 0, timeout: 4000ms)
I 18:54:30.391 Connection parameters updated (interval: 22.5ms, latency: 0, timeout: 4000ms)
D 18:55:22.486 [Callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)
I 18:55:22.486 Disconnected
D 18:55:22.503 [Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED
It's very difficult to moderate the speed by the
throttle, especially with a 6 Km/h limit set
----------------------------------------
I think instead of a current control,
a PID speed algorithm would be better.
The torque sensor pulley position
---------------------------------
May make the chain grind against the sensor bar with
a chain width of 7.45 or more (with gears less than 9),
if no extra spacers are installed.