Hi, I am trying to ascertain who is having issues with Impulse II motors on Kalkhoff or Focus e-bikes (both made by Derby Cycles). Personally, I had a first motor replacement after 900 miles (4 months, loud clacking/clicking noise), and then another failure at around 900 miles (7 months, very weak assistance, some loud clacking once). I have found the following people reporting issues too on this forum (usually on fairly new pedelec bikes and low mileage/kilometers): Username/Model/Age/Mileage reggie_electric - Agattu - 6 months - 800km nemesis - Focus Jarifa - 4 months - ??? Jean-christophe Saville - S11 Alfine - 14 months - 2800 miles Lothlean - ??? - 10 months - ?? Will Tinker - Pro Connect 9 - 5 months - 500 miles Oriteroom - Focus Aventura Impulse S10 - 10 months - 3000 miles (3rd motor) Roger R - ??? - 6 months - 1000 miles nightrider - Endeavour S10 - ?? - ?? bernharvey - Agattu - ?? - 400 miles Reseg - Focus Aventura - 10 months - ?? (3rd Motor) lowranger - Impulse 10 - ?? - 2300 miles Biscitt - Agattu - ?? - 350 miles Biscitt - Tasman - ?? - 100 miles Tomtomato - Pro Connect 10 - 7 months 900 miles (2nd fault) Please reply to this thread if you had a motor issue. It seems quite clear to me that there is a design/quality issue with the Impulse 2 crank-driven motors, and that those should be able to last a lot longer (given the high prices of the bikes), without requiring some expensive replacements (£600, once out of warranty). Kalkhoff are not willing to provide a warranty beyond 2 years on those motors, and have made people pay for replacement out of warranty, even when low mileage was done. After first saying that there were no issues, they confirmed that Kalkhoff knew about the issue, and it had been sorted. A software update can apparently prevent some clacking issues leading to failure. However, I am not aware of a recall to do so by Kalkhoff (are they just waiting for bikes to fail?). The 2015 motor replacement I had (supposedly the new reliable version) failed again after a small mileage, so I am not sure the issue is really sorted. Thanks, T.