ASI bac 855 controller

jpc6000

100 W
Joined
Sep 3, 2017
Messages
130
Location
gent
I have received the controller, the cable and the software bacdoor 1

I want that the controller work with bafang bbs02/hd and m620

How to start? 24 pin jst to pc. Do I need an screen to connect?

What screen? I have a lot of bafang screens. Or ca screen also. Or better with eggrider?

I need Xml files for the motors. Have anyone them?

Do anyone bacdoor 3 software 🤔

I have bacdoor version 1, is there great difference between bacdoor 3 , these versions?

How to connect screens to bac controller 🤔

Are power supply, throttle and motor connected to controller?

Anybody manuals, information credentials for asi bac855?
 
Last edited:
Too bad programming of these controllers is not supported to end users.
I see lots of threads like this and nobody can provide answers for questions like these. So, good luck.

If you don't get help, consider getting a VESC or ebikes.ca controller because the programmability situation is the exact opposite, and it will even autodetect motors for you pretty well.. a lot less messing about to get up and running with both of these controllers.
 
How to start?
Sit down, read a lot about BLDC control, peripheral signal waveforms, serial and/or CAN communication .... :ROFLMAO:
You got warnings enough, that the ASI BACs are nothing for newbies ;)


Many of the articles in the ASI knowledge base are still available, but it's not easy to get access....
 
Last edited:
If you don't get help, consider getting a VESC or ebikes.ca controller because the programmability situation is the exact opposite, and it will even autodetect motors for you pretty well.. a lot less messing about to get up and running with both of these controllers.
TBF, even though the BaseRunner can auto detect a motor, tweaking MAY be needed.

In my case, with a Shengyi DGW22 rear hub motor, auto detect was fine. The wheel spun in the proper direction. Issue was adjusting the feedback bandwidth tuning. I didn’t know how much time would be involved to learn what the parameters do and how they interacted with each other. I thought “auto detect” would automagically get my motor running with no issue. Autodetect really only means that the controller will auto detect the phase wiring, kv/rpm, Rs, Ls, and wheel direction. There was a lot of jitter upon takeoff. Grin admitted that this was normal. I thought it was kind of dangerous, especially taking off at an incline. I’ve got a lot going on (not retired yet) and could only work on my bike for a couple of hours at a time. Not having a long continuous chunk of time created quite a disruption in the tuning process. I’ve got it running good now, but it’s taken months for me to get there. I contacted grin support and they responded quickly with good info. Saying I should try a default parameter similar to my motor (not sure why I didn’t do this earlier).

Don’t let me scare you off though, it’s my fault for being stubborn and wanting to learn and do it myself before contacting grin. On the plus side, I have a better understanding of the relationships between the different feedback bandwidth tuning parameters. Their support is a really great advantage from other controller options.
 
Yeah, with geared motors, the phaserunner/baserunner can be tricky to tune.
But i've seen people run BBSHD's on them, so information exists on how to tune them for that.

Did they include a prebuilt tune for the shengyi?
 
Did they include a prebuilt tune for the shengyi?
Only for the SX1/2. Not the DWG22.

I loaded the SX1/2 config when I was making changes and the motor stopped spinning at all. The different areas (directories?) that contain motor settings and controller settings are saved. Even though I reset the controller to factory, the motor settings never changed and I didn’t realize until it was suggested I run the preconfig for the SX1/2. Then (to my joyous surprise) the motor began to spin.
 
TBF, even though the BaseRunner can auto detect a motor, tweaking MAY be needed.

In my case, with a Shengyi DGW22 rear hub motor, auto detect was fine. The wheel spun in the proper direction. Issue was adjusting the feedback bandwidth tuning. I didn’t know how much time would be involved to learn what the parameters do and how they interacted with each other. I thought “auto detect” would automagically get my motor running with no issue. Autodetect really only means that the controller will auto detect the phase wiring, kv/rpm, Rs, Ls, and wheel direction. There was a lot of jitter upon takeoff. Grin admitted that this was normal. I thought it was kind of dangerous, especially taking off at an incline. I’ve got a lot going on (not retired yet) and could only work on my bike for a couple of hours at a time. Not having a long continuous chunk of time created quite a disruption in the tuning process. I’ve got it running good now, but it’s taken months for me to get there. I contacted grin support and they responded quickly with good info. Saying I should try a default parameter similar to my motor (not sure why I didn’t do this earlier).

Don’t let me scare you off though, it’s my fault for being stubborn and wanting to learn and do it myself before contacting grin. On the plus side, I have a better understanding of the relationships between the different feedback bandwidth tuning parameters. Their support is a really great advantage from other controller options.

I think Justin hates me. 😆
He doesn't help me, already bought for more than 10.000$
You know why, he hates me, I find mid motors better.
And I wrote it to him. 😅
Never burn, spin more, in the mid of the bike, easy to replace.
Easier to work on ....
Or You are maybe from Canada 🤣

He hate the mid motors from Bafang, also🙃

Already also burned 2 phaserunners at 30A 60V
The power xt 60 connector or something inside burned, didn’t get even connector lose was burned 🔥.

Justin, wrote me to open the lips at some time, and lose cable to it, then cables hanging, but I think also water comes in. I saw that also others wrote about that problem.

Better the cable like asi.
Use an other connector xt90 and these short cables of the phaserunner and different colors, different versions, different colors, gives me already a lot of work and headaches.

I told JUSTIN to use xt90 connector. V6 and still xt60. Or cables.
Send him burned phaserunner controller, payed the transportation
Get an phaserunner v1 in return and didn't work, maybe 20h work.
And no response more on mine mails. And payed also these transportation to Belgium 🇧🇪.

Maybe it also an hubmotor 😁 they helped you.

I have phaserunners got that worked good,
Now I placed a new bbs02 motor and new phaserunner used the same parameters
Motor does nothing, I thought it was the wiring.
After 3 days it seems the parameter, but now the motor is working terrible. Jitter 🥴

Want to by, for 10.000 grin material, 😁 Justin answer.

Mail later, I have the problem with shake and vibrate bbs02 BAFANG😉 motor, no answering 😑

He wants give me 20% discount, than 10 after lots of mails, no answer.
Then 10% and the nothing, so give up and want other controller 🙄.
And the same with grin eu. No answering, no help and no discount for reseller.

ASI I think cheaper and better, Justin has made it a little more user-friendly.
But asi even more worse service.
Compact, good cable, cheaper, better connectivity
But no bacdoor 3, find parameters for the motors and I can use asi bac855.
 
Last edited:
Sit down, read a lot about BLDC control, peripheral signal waveforms, serial and/or CAN communication .... :ROFLMAO:
You got warnings enough, that the ASI BACs are nothing for newbies ;)


Many of the articles in the ASI knowledge base are still available, but it's not easy to get access....
It's like to solve the war in Oekraïne, Israel, Sudan, Trump and many other places. 😊 not easy.

If you have a lot of of money like stupid Tesla boss, Elon Musk, it's easier in this world.

I have bought two asi controllers 855, cable and bacdoor software v1.

Should I Try to work it, or send them back.

Or Buy vesc controllers.
Or work with phaserunner, and child Justin.
Like with Trump, playing with stupidity 🙄.

Or find someone who can solve problems with asi, grin or vesc.
Who knows about it, electronic engineer?


How to fine tune it, work with parameters.
Can place bike on rolls 🤔.

Different software, different screens, it's a puzzle 👌.
Where to start. I make progress.

The asi at 180$ and bafang color screens, and wheel of fortune.
Maybe someone can make manual 🤔.
 
Last edited:
Motor jitter and shake and vibrate is a good sign. Just having the motor rotate in the proper direction is the first step. Now to correct the jitter. It’s a process and the settings can have impact on other settings so time to use your patience. It will take time.

You’ll have to adjust the Feedback Bandwidth Tuning parameters to correct the jitter.
Refer to Current Regulation Control Loop and PLL Regulation Control Loop.

For example, adjusting the Current Regulation will impact the jitter, the PLL Regulation may intensify the jitter. Adjust the Current Regulation (use increments of 1000 first, then 100) until the jitter is gone or as minimal as it can be. Then adjust the PLL Regulation (adjust in increments of 100, then 10) (and also PLL Damping, I found adjusting in increments of 5, then 2 works well) to further decrease the jitter. Don’t worry if the motor spins “weak” or “slow”. You can use throttle ramping to have a quicker motor response.
 
Back
Top