baserunner programming - necessary?

[dtbh]

Hey experts - I bought a CA3 and baserunner to see if I could get a g020.350 motor up and running as an experiment for my old bike. I took a functional test ride but about 10 minutes in, started getting motor cutout - a second or so of power then it would cut out. rebooting the CA would allow another second of power before it would cut again. Once it cut, it would not power back up unless there was a reboot. Unplugging the motor and plugging it back in would not reset it, so my suspicion is the controller. The diag screen was flipping a capital W and S right before cutout, but the spwwed and wattage were nowhere near any limits (I left the limits at max actually). Since then, By lowering the watt output I was able to get it to drive the motor again in a bench test but I'm not taking it to the streets til I figure this all out.

Long story short, the baserunner arrived with no instructions, no programming cable, no information whatsoever. Before connecting everything, I read through the entire CA manual and set everything up as necessary before sending power to the motor, but until I had this issue after a test ride and started digging around online there was no indication that the controller would need to be programmed.

So my questions include: do I need to get the programming cable for the baserunner? is it possible it needs its default settings changed in order to get things running? What happens if I don't? Is it possible I damaged anything by using it "out of the box"? What could have caused it to work fine for a while and then after a short time start exhibiting this now chronically repeatable issue?

Thanks in advance!

 

[neptronix]

The baserunner is a modified phaserunner, so you can refer to the phaserunner manual for instructions ( this is in the product details tab on ebikes.ca's site )

https://ebikes.ca/amfile/file/download/file/117/product/939/

 

[amberwolf]

Also, test with the CA in "throttle bypass mode" so that the CA cannot do any limiting. This will ensure that any problems you are having are not caused by a setting in the CA. Once the system works completely without the CA interfering, *then* set the CA's throttle output to whatever you want to use, and tune the settings from there.

https://ebikes.ca/product-info/grin-products/cycle-analyst-3.html#SetupThrotIn

Bypass: This mode is the equivalent of connecting the throttle directly to the controller to completely eliminate the CA from motor/controller behavior. This differs from PassThru mode in that ThrIN is sent directly to ThrOUT with no processing whatsoever: no min/max range adjustments, no ramping, no limiting, and no autocruise or PAS support.

IMPORTANT: This is only a diagnostic mode and is not intended for normal ebike use. All normal CA protections are inoperative (e.g. low voltage, max current).

 

[dtbh]

Thanks, ya I saw the direction from baserunner to phaserunner and followed the path to some programming info that way, which is why I'm here... So it sounds like the programming is a necessity and I'll have to get a cable. Or presumably I can just build a serial cable that connects to an old school 9 pin serial port of I can find the pin mapping?

I don't have a throttle, I'm running strictly via pas. After a cut-out the diag screen shows that it's putting a throttle signal out, bit the motor does not respond unless I cycle the power.

 

[amberwolf]

Thanks, ya I saw the direction from baserunner to phaserunner and followed the path to some programming info that way, which is why I'm here... So it sounds like the programming is a necessity and I'll have to get a cable. Or presumably I can just build a serial cable that connects to an old school 9 pin serial port of I can find the pin mapping?

Yeah, the PR/BR are not plug-and-play controllers; they must be setup for each motor they're used with. Kinda of a PITA but they run better that way than a generic "works with most everything" controller.

The 3.5mm phono plug connector pinout is on the Grin site and probably in the BR instructions. It's the same cable and pinout that all their stuff uses, AFAIK. So if you already have a serial-USB cable, you can just make an adapter for the serial end of it that goes to the connector on your BR. The PR/BR software suite is on Grin's site, and there is also an android app on the play store, though you still have to use the USB-serial cable (with an OTG thing for your particular android device).

I don't have a throttle, I'm running strictly via pas. After a cut-out the diag screen shows that it's putting a throttle signal out, bit the motor does not respond unless I cycle the power.

If the CA is still putting out the expected throttle value from your PAS input, then it's not the CA, but the controller.

 

[dtbh]

Alright so I'm on the right track. I have a cable now and will get cracking on this tomorrow. Thanks for the tips!

 

[dtbh]

Well I programmed it to match the motor. What I am finding is that if I use PAS power mode, I get the cut out problem. If I use the ThO mode I can run the motor consistently. So it seems like the controller is misinterpreting the power output somehow. I think my next step is to connect my computer while I'm riding it and record diagnostics. but I'm not sure what to look for to be honest...

 

[HrKlev]

If it runs on throttle but not with PAS your problem is probably cycle analyst setup og PAS sensor. Does the little figures below the P and D in the PAS setup menu move consistently if you pay attension in a full revolution of the cranks? What does the RPM menu say when you ride the bike? Any limiters blinking in the diagnostic menu while riding the bike?

Whar kind of PAS and speed sensor do you have?

 

[amberwolf]

Well I programmed it to match the motor. What I am finding is that if I use PAS power mode, I get the cut out problem. If I use the ThO mode I can run the motor consistently. So it seems like the controller is misinterpreting the power output somehow.

If you are using a cycle analyst v3 to measure a pas sensor, and also have a throttle on the ca throttle input, but only the throttle works as desired, it just means teh pas isnt' setup quite right in the ca, to make its output the same response range / smoothness as the throttle input.


What exact equipment do you have, and how is it hooked up, specifically?

What are your settings in the CA itself, for all of the throttle and pas menus?

 

[E-HP]

Well I programmed it to match the motor. What I am finding is that if I use PAS power mode, I get the cut out problem. If I use the ThO mode I can run the motor consistently. So it seems like the controller is misinterpreting the power output somehow. I think my next step is to connect my computer while I'm riding it and record diagnostics. but I'm not sure what to look for to be honest...

1. What is your scaling set to (Scale Fctr) for Basic (Pwr) and ThO modes?

2. Check your PAS wiring. You may have an intermittent short.

3. Maybe there's something wrong with your battery and the BMS is tripping. I'm not clear by what you refer to as "rebooting", but if that's cycling the battery switch, them maybe the issue is the battery, or a combination of issues.

 

[dtbh]

Hi everyone, thanks for your help on this thread! I'm just coming back for a long overdue report to say that I have been using the system without any issues since I changed the pas from power mode to th0 - but I don't think this is the most ideal set up. But it does work.

I think I wasn't clear enough about my problem. When the CA3 was set up based on power, it seemed to be misinterpreting the wattage and it would spike and cut out. I do not have a throttle, I have a basic pole driven PAS with no torque sensing.

I can't remember now where I left this off for troubleshooting but I'll probably get back into it now that the busy season is over.

I wanted to make sure I wasn't completely ghosting on y'all!

 

[amberwolf]

What exact equipment do you have, and how is it hooked up, specifically?

What are your settings in the CA itself, for all of the throttle and pas menus?