Hi folks, used my gt avalanch/ bbs02 for a couple of years now on trails in derbys /notts and really pleased with it , opened up a new world of 30 miles a day enjoyment , problem started with everything going dead last year end , good battery volts 48 v battery getting 54v so fitted a new controller from seller on e bay , the old controller smelt apalling when opend up so am sure it was a goner ,had to fit new wheel sensor and bike went like a rocket, then programed in my softer settings ie max 17amps and progressive assistance exactly same as last one as range more important than power and no go apart from if i peddle real fast motor kicks in oddly above the set speed limit.

just fitted new hall senser to no availl, no brake or gear sensors, any thoughts, cheers ian

When you pedal fast to make the motor go, does the speed show correctly in the LCD?

 

When you say you pedal fast, does the motor kick in at the same pedal speed in each gear or is it dependent on the bike speed?

 

Answering those questions will answer whether your pedal sensor or speed sensor are to blame.

 

It used to be quite common for the pedal sensors to break up after extended use.

Thanks for your promp reply, yes the speed seams to indicate right , never noticed till you asked but it changes depending what gear im in ie in low the motor kickes in at 7 mph but in high its getting on for 27 ish ,i have fitted a new internal hall senser i think its called to no effect,cheers

Thanks for your promp reply, yes the speed seams to indicate right , never noticed till you asked but it changes depending what gear im in ie in low the motor kickes in at 7 mph but in high its getting on for 27 ish ,i have fitted a new internal hall senser i think its called to no effect,cheers

There are three hall sensors for the motor timing and one to read the magnet disc for pedal speed. Which did you replace and why?

 

It's looking a lot like a broken magnet disc, but check the pedal sensor connector and wires first.

https://www.ebay.co.uk/itm/306701459523?var=0&mkevt=1&mkcid=1&mkrid=710-53481-19255-0&campid=5338268676&toolid=10044&_trkparms=ispr=1&amdata=enc:11IEwYuusSaq8s-o4cDxigw30&ff=11&gbraid=0AAAAADA7Q_I_x4zdOedtL8PIxqnakpP69&loc_physical_ms=1007151&adtype=pla&customid=Cj0KCQjwgr_NBhDFARIsAHiUWr7L6nd1yBXsIhaIMzsK-HwYh3jVVhcvmrs-5YAqE0Ks9-67wgVvLJYaArfWEALw_wcB&gclid=Cj0KCQjwgr_NBhDFARIsAHiUWr7L6nd1yBXsIhaIMzsK-HwYh3jVVhcvmrs-5YAqE0Ks9-67wgVvLJYaArfWEALw_wcB

oh i dident know that, i replaiced the magnetic disc and small electonic pickup that the wires go into black connector in controller ,pressume thats the one that reads magnetic disc ,

ill chech the wheel magnet and pickup again but it is blinking when wheel passes it and reading speed

yes see what you mean now theres a circuit buord inside the motor , could that be the culprit do you think and is it possible to replaice just that

ah , thats the one i changed thinking it was the only one ,do u think it could be the one inside the motor housing, thanks for your help by the way as had got to the end of the line with it, at least il know a fair bit about them when its done.

had to fit new wheel sensor and bike went like a rocket, then programed in my softer settings ie max 17amps and progressive assistance exactly same as last one as range more important than power and no go apart from if i peddle real fast motor kicks in oddly above the set speed limit.

 

I've got a BBS01B, therefore none of the following may be relevant but... is the wheel magnet as close to the speed sensor as possible? Also, why specifcally did you have to change the wheel speed sensor?

 

ill chech the wheel magnet and pickup again but it is blinking when wheel passes it and reading speed

 

Blinking isn't enough, it must be as close as possible to the sensor or you will get errors - I realised the wheel magnet wasn't close enough when going downhill unassisted at over 35kph - speed would rise to 35kph+, then fall to 0kph and go back up, over and over again in a loop. Speed calculation was ok at lower speeds. Moved the sensor closer the wheel magnet to resolve.

 

programed in my softer settings ie max 17amps and progressive assistance exactly same as last one as range more important than power and no go apart from if i peddle real fast motor kicks in oddly above the set speed limit.

 

Even though this strange problem seems unlikely to be caused by firmware configuration, I'd be interested to see your settings. Also, did you use the same configurator as originally? The reason why I ask, is because I noticed once, that the SPEEED app and Penoff's configurator set parameters differently under the hood for speed calculation - this only became apparent when I switched back to Penoff's, to see the SPEED app had used motor magnets to calculate speed, rather than the speed sensor, despite appearing to use the speed senor in the app view.

Edited March 12Mar 12 by guerney

i did spend some time on getting the magnet pretty close to the sensor.after i fitted new controler the display was giving me error code 21 and cutting drive ,did work ok after i changed sensor.

I did set the settings exactly to what i used before but did use the speeed app,i also checked them with eggrider app but cant remember seeing motor magnets or speedsensor in the choices, however the fault developed after i re programed it so could be iv fouled it up somhow , il have a look tommorow

yes i set it to external motor meter, or thought i had ,is that correct please

Might be totally irrelevant to your problem but... Despite what the SPEED app said ie using wheel speed sensor, when I read my BBS01B firmware using Penoff's configurator (had to add COM ports to my Windows 7 PC), I discovered it had been programmed to use motor magnets to calculate speed, rather than the wheel speed sensor. Then my programming cable died, so it's a toss up as to whether the failing lead was causing the change or the SPEEED app. With a brand new programming cable, I used Penoff's configurator to use the wheel speed senor for speed calculation instead. Either way with my BBS01B, there was no discernable problem.

Edited March 12Mar 12 by guerney

I've got a BBS01B, therefore none of the following may be relevant but... is the wheel magnet as close to the speed sensor as possible? Also, why specifcally did you have to change the wheel speed sensor?

 

 

 

Blinking isn't enough, it must be as close as possible to the sensor or you will get errors - I realised the wheel magnet wasn't close enough when going downhill unassisted at over 35kph - speed would rise to 35kph+, then fall to 0kph and go back up, over and over again in a loop. Speed calculation was ok at lower speeds. Moved the sensor closer the wheel magnet to resolve.

 

 

 

Even though this strange problem seems unlikely to be caused by firmware configuration, I'd be interested to see your settings. Also, did you use the same configurator as originally? The reason why I ask, is because I noticed once, that the SPEEED app and Penoff's configurator set parameters differently under the hood for speed calculation - this only became apparent when I switched back to Penoff's, to see the SPEED app had used motor magnets to calculate speed, rather than the speed sensor, despite appearing to use the speed senor in the app view.

If it was his speed sensor, the problem would be independent of gear and pedal speed, but it isn't!

however the fault developed after i re programed it so could be iv fouled it up somhow , il have a look tommorow

I think it's unlikely your strange problem was caused by firmware configuration, but if you wanted to be sure, personally I'd use Penoff's configutator to set it back to default. Stock BBS02 settings are (or were in 2015)...

 

https://endless-sphere.com/sphere/threads/programming-the-bafang-middrive-bbs01-bbs02.58780/post-1065062

 

bike went like a rocket

 

...to see if it goes like a rocket again. If it does, set it to the configuration you used originally, using Penoff's. Here's an online configurator, if you can't run Penoff's:

 

http://devnotes.kymatica.com/BafangWebConfig/

 

Dying programming cables can write strange values. I've had two fail so far. I regard the freaking things as consumables at this point, it's good thing they're cheap. Thin cable wires break at the flex.

Edited March 13Mar 13 by guerney

I think it's unlikely your strange problem was caused by firmware configuration, but if you wanted to be sure, personally I'd use Penoff's configutator to set it back to default. Stock BBS02 settings are (or were in 2015)...

 

https://endless-sphere.com/sphere/threads/programming-the-bafang-middrive-bbs01-bbs02.58780/post-1065062

 

 

 

...to see if it goes like a rocket again. If it does, set it to the configuration you used originally, using Penoff's. Here's an online configurator, if you can't run Penoff's:

 

http://devnotes.kymatica.com/BafangWebConfig/

 

Dying programming cables can write strange values. I've had two fail so far. I regard the freaking things as consumables at this point, it's good thing they're cheap. Thin cable wires break at the flex.

 

On problems with editing configuration -

 

I could not get the penoff config to connect to the BBS01 when using my chromebook and I used the web page configurator that you sent me Guerney.

 

https://devnotes.kymatica.com/BafangWebConfig/BafangWebCfg.html

 

That connected and worked, but when I was making changes, I found it was more reliable to change one parameter at a time and then save, rather than changing a bunch of them and trying to do one save.

 

So change one thing and save setting, before proceeding if using that tool.

 

It worked faultlessly after that. I saved the web page on my machine locally in case the tool disappeared off the web in future.

thanks for that, went thro settings again today with eggrider app a nd nothing had changed ,ill have a look at penoffs settings with configeration tool and also double checked rear wheel magnet .

am now thinking could it be the electronics attached to inside of motor,looks like its better to get the complete motor and rotor unit to be on safe side .

I think it's worth bearing in mind that the firmware of your new BBS02 controller might not be exactly the same as the old. We've seen reports of some new BBSXX(X) controllers being current limit locked, for example. I don't know much about Eggriders, so I asked Google's AI what is causing your strange problem and it said the following, but they are prone to hallucination.

 

-------------------------

This issue usually happens because the motor’s

speed limit or pedal assist (PAS) parameters are misconfigured, causing the motor to think it should only provide power when you are already moving quickly.

 

 

1. Check the "Designated Assist" Setting

 

The most common cause is the EggRider Pedal Settings being set to a fixed high value rather than following the display's commands.

 

• Fix: In the EggRider app, go to Bafang Pedal settings and ensure Designated Assist is set to "Display Command".
  
• Why: If this is set to a specific number (like 9), the motor may ignore lower assist levels and only kick in when you reach the high speed threshold associated with that level.
  
• 
  

 

2. Adjust "Keep Current" and "Current Decay"

 

If the motor only helps at high cadences (pedalling fast), your PAS decay settings might be inverted or too restrictive.

 

• Keep Current (%): Should typically be set between 60% and 100%. If it’s too low, the motor will cut power as soon as you start pedalling at a normal speed.
  
• Current Decay (1-8): This determines how early the power drops off as your pedalling speed increases. Set this to 8 (the highest) to ensure the motor continues to assist even at higher cadences.
  
• 
  

 

3. Verify Speed Limit Sync

 

Sometimes the EggRider Road/Off-Road modes have conflicting speed limits that confuse the controller.

 

• Speed Limit Setting: In Bafang Basic settings, ensure the Speed Limit is set to "Display Command".
  
• Max Speed: Check that your "Max Speed Road" and "Max Speed Off-Road" in the app's display settings are not set lower than you intended.
  
• 
  

 

4. "Startup Degree" (Signal No)

 

If there is a massive delay before the motor starts, your Startup Degree may be set too high.

 

• Fix: Set this to 4 or 8. If it is set to 20 or 24, you have to complete almost a full pedal rotation before the motor activates.
  
• 
  

Which assist level (0-9) are you using when this happens, and is the motor completely silent until you hit that high speed?

Edited March 13Mar 13 by guerney

more noticable in higher settings , definatly need read a few times and print off also good idea to reset to factory settings , i have the programing tool but not got a laptop so not able to set using computor , will give it a go in the morning cheers

Unless your phone or tablet is very old, you should be able to configure firmware using your programming cable connected to an OTG lead via an online configurator using Chrome. Should also work with Edge. As mentioned [mention=45963]Tony1951[/mention] used this one:

 

https://devnotes.kymatica.com/BafangWebConfig/BafangWebCfg.html

 

OTG adapters without cables tend to work better for data transfer. The ones with thin cables often don't carry data, in my experience. Test using a USB thumbdrive if unsure.

 

https://www.ebay.co.uk/itm/286395873984

have just put on my tablet so will give it a go shortly ,im not exactly technical so am sweating already , a lot happy er with mechanical stuff

Here are guides about what the settings do.

 

https://edrivenet.com/bafang-programming/

 

https://www.bafangers.com/en/bafang-central-motor-programming-guide/

 

It'd be good to rule out firmware misconfiguration, or the Eggrider's inability to change settings of newer BBS02 firmware, or an interrupted bluetooth connection while writing via the app, or configuration parameter mismatch/conflict between the Eggrider and new controller, as the cause of your strange problem - cheaper than buying more parts. You can screenshot the settings and upload, or export the config file then edit copy/paste the config file contents into a post. Changing and writing one parameter at a time does tend to work better as [mention=45963]Tony1951[/mention] has said, particularly the current limit. Let's hope it reverts to rocket mode when you set it back to factory defaults.

Edited March 14Mar 14 by guerney

can get on tablet but wont connect to a port,possibly not available on tablet, looks a nice interface though , any way returned settings to factory and double checked to no availe, just kicks in with more power above set speed,checked all the settings now with speeed and eggrider and nothing not set properly , might see if missis will lend her laptop but not keen ,

What happens if you pedal with a very low speed cutoff?

 

Changing settings on your new controller using something other than the Eggrider might help, might not. Sometimes enabling OTG connection is as simple as searching for "OTG" in Android settings and toggling it on, other times you need to dig slightly deeper. If you can't get Penoff's configurator working on the laptop, you can try via an online configurator using Chrome or Edge browsers.

 

 

have just put on my tablet so will give it a go shortly ,im not exactly technical so am sweating already , a lot happy er with mechanical stuff

 

Did you try this one?

 

https://devnotes.kymatica.com/BafangWebConfig/BafangWebCfg.html

 

• Connect
  
• Load your settings
  
• Read your settings and see what you want to change
  
• Before making any changes save the original settings to a backup file name - that way you can revert if you need to.
  
• Make single parameter changes and save each single change to the controller before changing any other parameter.
  

 

Good luck. Worked well for me with a chromebook - likely will do with an android tablet too.

If you can read a USB drive via OTG, but can't connect to the controller using the online configurator via Chrome or Edge browsers, and have no laptop or PC available, you could try the SPEEED app. However, it's been removed from the Play store for some reason. You could download and install the APK, although doing so can be risky, because APKs could contain malware. Installed and connected fine using my Lenovo tablet.

 

https://speeed-bafang-bbs0102-bbshd.en.softonic.com/android