Throttle not working after new controller install

penserv

1 mW
Joined
Jan 29, 2024
Messages
10
Location
Calgary
I have a GMAC 10T and CA3 (3.2B3 firmware). My V4 controller developed an intermittent short, so over the winter I replaced it with a new V6 Baserunner controller. When I put everything back together and adjusted the settings in both the Phaserunner suite and CA3 setup utility everything worked fine except the throttle from a standing start. At full stop, if you press the throttle lever, the wheel weakly lurches forward in small increments of about 1/8th of a turn. If you rotate the pedals to get the power to come on, the throttle will work fine and increase the rpm quite noticeably, but from a standing start, nothing.

When I set up the electronic freewheeling in the phaserunner software, the wheel spins freely at about 1.37 amps. In the Phaserunner suite, there is a button called Autotune, so naturally, like wet paint, I had to touch it. It takes you into 2 tests. In the first test the motor makes a humming sound. The second test is called a spin test, but for me, the wheel did not "spin", rather it moved forward in small increments of about 1/8th of a revolution. In the phaserunner software there are no faults being highlighted and the Hall Sensors flash blue green and yellow in sequence, which is about normal.

I can live without a throttle, most of the time, but it sure comes in handy when you need it and not being able to go from a standing stop is a big disadvantage.

Anyone have any ideas about a throttle? The input voltage is set to 1.0v and the output is set to 4v. When you press the throttle lever, you get the specified voltages, just no power, unless you have engaged the boost assist first from pedalling.
 
Here's something to rule out.

Are you in sensorless mode or a mode that allows fallback to sensorless mode? if so, turn the fallback off and try sensored only mode.

If the motor doesn't start in hall only mode... you have bad halls and it's reverting to sensorless.

What kind of phase amps / battery amps are you running as well?
 
Here's something to rule out.

Are you in sensorless mode or a mode that allows fallback to sensorless mode? if so, turn the fallback off and try sensored only mode.

If the motor doesn't start in hall only mode... you have bad halls and it's reverting to sensorless.

What kind of phase amps / battery amps are you running as well?
That's an interesting comment. I noticed that it was in sensorless mode and when I turned it to hall sensor, it reverted back to sensorless. I don't think I saw an Apply button for the program to remember my changes. That's not too unusual, though. It's been like that for a while, since at least a year, as I noticed it last year about this time when I was setting up the bike in the spring of 2024. Tomorrow morning, I'll hook up my laptop again and check the phase amps. The battery is 52v 20 amps, but I think you're referring to something that's shown in the phaserunner screens.
 
If it's always reverting to sensorless, it usually means one or more of the sensors is returning values that can't be right for the test it's doing. You can look at the numbers it provides for the tests and see what the issue is, or post screenshots of your results of the autotune tests.

I have a GMAC that had a catastrophic self-disassembly that damaged the PCB inside, forcing it to be run in sensorless mode on the PRv6. But I did not have the issue you're having.

On my system the CAv3 is doing all the PAS and throttle monitoring and sending it's throttle to the PR.

Is your system wired for this, or are you using the PAS and throttle directly to the PR?

If the former, you can check the CA's diag screen (one left button push from main screen) for any capitalized letters in the group on the left lower area, which means a limit is being hit and so the CA will reduce throttle output until the limit isn't being hit anymore, and then the flag will go lowercase again.
 
^-- look at this king, he actually knows what he's talking about
 
Not sure about that ;) but here's the start of my GMAC PRv6 saga The SB Cruiser : Amberwolf's 2WD Heavy Cargo Trike & Dog Carrier and somewhere there's a thread trying to troubleshoot the issue discussed later in those posts about the fault that happened whenever I went over a certain spot on the way home (pretty sure I know what causes it at the root but never found a useful solution and ended up going to different motors instead).
 
I've heard very few success stories with the Phaserunner and a MAC.
The MAC spins a little too fast tor the controller to catch up.

A VESC would probably be great at driving one because it can handle waaaaaaaaaaay higher high electrical RPM since it's designed to drive RC motors 'n such.
 
If it's always reverting to sensorless, it usually means one or more of the sensors is returning values that can't be right for the test it's doing. You can look at the numbers it provides for the tests and see what the issue is, or post screenshots of your results of the autotune tests.

I have a GMAC that had a catastrophic self-disassembly that damaged the PCB inside, forcing it to be run in sensorless mode on the PRv6. But I did not have the issue you're having.

On my system the CAv3 is doing all the PAS and throttle monitoring and sending it's throttle to the PR.

Is your system wired for this, or are you using the PAS and throttle directly to the PR?

If the former, you can check the CA's diag screen (one left button push from main screen) for any capitalized letters in the group on the left lower area, which means a limit is being hit and so the CA will reduce throttle output until the limit isn't being hit anymore, and then the flag will go lowercase again.
I have the T-17 Erider BB torque sensor and it is hooked into the CA3. There are no flags displayed on the CA3 Diagnostic screen. Everything is lower case "awsvt". Once the system is going and the bike is just idling along in electronic freewheeling, the throttle works fine and the speed goes up to max on the dashboard screen. The throttle just won't do anything from a dead stop. Attached is the readout from the spin test. The values don't mean much to me.

I went in to Basic Setup in the Phaserunner software and unchecked Fallback to Sensorless and set the Sensor Type to 0 - Hall Sensor. Voila! It's magic! All of a sudden, my throttle works from a dead stop. Still no warning flags, no faults, no error messages, battery and hub motor are cool to touch - I think I'm ready to ride. I'll have to wait till Monday afternoon when the temp gets up to 14C. Today at 0C is too cold for my old bones.

Thanks for your help Amberwolf.
 

Attachments

  • SpinTestValues.png
    SpinTestValues.png
    50.3 KB · Views: 3
Oh, and one other thing. After I changed the setting to Hall Sensor from Sensorless, I had to increase the current from 1.37 to 1.56 amps to maintain the electronic freewheeling. I have no idea why that should be, but I'm sure someone more knowledgeable than me can explain it. I'm just happy that it works.

Also you asked earlier about my battery and phase currents. I've attached the Basic Setup screen for your perusal.
 

Attachments

  • BasicSetup.png
    BasicSetup.png
    146.2 KB · Views: 4
Oh, and one other thing. After I changed the setting to Hall Sensor from Sensorless, I had to increase the current from 1.37 to 1.56 amps to maintain the electronic freewheeling. I have no idea why that should be, but I'm sure someone more knowledgeable than me can explain it. I'm just happy that it works.
I'd guess that the timing is different with the halls vs without, which changes the current angles in the phases to do the same job, which changes the amount of current used to do it.

Attached is the readout from the spin test. The values don't mean much to me.
I don't know what those mean either, but if you look at what the hall test results are, it may tell you what the BR actually sees and that might tell you why it's dropping to sensorless.




I went in to Basic Setup in the Phaserunner software and unchecked Fallback to Sensorless and set the Sensor Type to 0 - Hall Sensor. Voila! It's magic! All of a sudden, my throttle works from a dead stop. Still no warning flags, no faults, no error messages, battery and hub motor are cool to touch - I think I'm ready to ride.
That's good--it means the halls are actually working, just that there's something in the PR autotune that is not seeing them as correct so it then ignores them and switches to sensorless. (it's probably related to how the GMAC itself is designed or works, but I don't have a completely intact one to experiment on that with; anything I test on it has to deal with the original damaged PCB / hall replacement / etc induced issues it may have).

With no flags in the CA, it's doing exactly what it should do and sending the throttle as specfiied in it's settings to the PR. So if you have the CA set for the same output range as your BR is set for input throttle range, you'll get full control over the system via throttle or PAS.


I'll have to wait till Monday afternoon when the temp gets up to 14C. Today at 0C is too cold for my old bones.

Doesn't get that cold here very often--maybe once every couple years for a few hours at night. :) (but I'd rather the cold than the heat (can be over 120F at the hottest in the summer)...you can only take off so much clothing before you have to start taking off skin :oops: ).



I've heard very few success stories with the Phaserunner and a MAC.
The MAC spins a little too fast tor the controller to catch up.
THe PR drives my GMAC "just fine" in sensorless mode (I assume that the inability to do sensored has to do with the damage to the PCB such that even though I see good hall signals, the controller doesn't)*** even at the higher RPM of a 20" wheel at max of 20MPH, with the exceptions that:

--if the motor is being driven and it skips off the ground (like dropping off a 1" expansion joint going up the bridge over the canal near here), it spins up rapidly and then when it is suddenly decelerated the RPM change is so great because of the gearing that it causes a fault (phase overcurrent, IIRC). This error does not happen with a DD hubmotor (the ultramotor) in the identical conditions.

--if the system is left powered off long enough (a few minutes?) then there is always a power-on fault. Re-cycling the power clears this. This error does not happen with the ultramotor, and I suspect it is *also* caused by the PCB damage from the motor's prior self-disassembly.

***the DD Ultramotor works fine sensored, so the PR itself isn't the cause of the GMAC hall / sensored issues.

The GMAC also does *great* regen braking (better than the DD UM because of the gearing in the GMAC).

But I've certainly seen that the GMAC *doesn't* work with typical "generic" controllers; from my SB Cruiser thread:
The GMAC simply doesn't work with the generic 15FET; above 4.5-5mph it just starts to do wierd stuff, loaded or not. Autolearn always works normally, but that's only for phases since the hall wires on this controller are just for show and have never worked with any motor, so it really only sets the direction of spin.
 
Last edited:
Also you asked earlier about my battery and phase currents. I've attached the Basic Setup screen for your perusal.


BTW, I notice you have max regen voltages set to almost three times your battery low voltage. Was that deliberate?

Just asking because it seems like one of those "has" to be wrong, wiht LVC at 19-19.5V, and max regen 59.5-60V.

Unless you're just setting LVC so low so it can never shutdown from LVC, but are still using a regen voltage appropriate for your battery voltage.... :?


1742697623398.png
 
BTW, I notice you have max regen voltages set to almost three times your battery low voltage. Was that deliberate?

Just asking because it seems like one of those "has" to be wrong, wiht LVC at 19-19.5V, and max regen 59.5-60V.

Unless you're just setting LVC so low so it can never shutdown from LVC, but are still using a regen voltage appropriate for your battery voltage.... :?
The only thing I use in the Phaserunner software is the ability to set the electronic freewheeling. I've never looked at any of the other settings, so I can only assume they are Grin default values. AFAIK, those values have been there for the past 6 years. I have had problems with regen in the past when I tried to set them to speed limits to start regen at 42km/hr. I like to think of regen as a safety feature. You'll take off less skin going 42km/hr or slower on a downhill run than you will at 65km/hr or higher on a hill, though 65 is infinitely more exciting. Maybe the problems I've had with regen are related to the regen voltage settings. I'll run it by Grin support next week.
 
I have had problems with regen in the past when I tried to set them to speed limits to start regen at 42km/hr. I like to think of regen as a safety feature. You'll take off less skin going 42km/hr or slower on a downhill run than you will at 65km/hr or higher on a hill, though 65 is infinitely more exciting.
;) Some long years back, on a regular bicycle going down Cave Creek from the top of the hill there (it's labelled as a mountain, but....) I got to speeds I don't even know how fast but it was more than I could control it at.... :( Luckily the excitement ended without serious injury.


Maybe the problems I've had with regen are related to the regen voltage settings. I'll run it by Grin support next week.
What were the specific problems?

There are a range of different issues that can happen when using regen for slowing down on slopes especially from speeds higher than the motor could attain on it's own.
 
;) Some long years back, on a regular bicycle going down Cave Creek from the top of the hill there (it's labelled as a mountain, but....) I got to speeds I don't even know how fast but it was more than I could control it at.... :( Luckily the excitement ended without serious injury.



What were the specific problems?

There are a range of different issues that can happen when using regen for slowing down on slopes especially from speeds higher than the motor could attain on it's own.
For a while last year, regen worked just fine on speed limits. I set the power assist at1.5 or 2 x up to 25km/hr and between 25 and 42 I'm the engine. Sometimes I would go fast enough on the flats to engage regen. But then, sometimes regen would kick in on a downhill run as expected and at the bottom I would start pedaling and on the way up, when I was only going 10 or 12km/hr, regen would kick in again and would revert to the throttle, so the more I pushed down the throttle, the slower I went. I would have to stop on the hill, cycle the power off and on to clear the regen and then the throttle would work normally. I would go back home and check all my settings and indeed, regen was disabled on pedal position as well as throttle. Things would go along fine for a while and then it would happen again. Finally, I just gave up on regen completely, did away with the speed limits and just used the power assist at a lower setting (1x or 1.25x). Grin never did come up with an explanation other than to suggest it might be an intermittent error in the controller, which was a v4 unit. So this winter I purchased a new V6 controller and tomorrow when it's warm enough to ride, I'll try it out and hope the folks at Grin were clairvoyant geniuses. When the speed limits were working though, I was able to get 150 km out of a single charge on the battery and only be down to 48V. Without the speed limits, with no regen, I was back down to 120 km range and less than 46V, which was extremely disconcerting, because I live at the top of a hill and this bike, even though it's carbon frame, is still 50 lbs and it's a beast to push. My last build in aluminum was 65 lbs, but having to push any bike home sucks, especially when all the neighbors are watching.
 
For a while last year, regen worked just fine on speed limits. I set the power assist at1.5 or 2 x up to 25km/hr and between 25 and 42 I'm the engine. Sometimes I would go fast enough on the flats to engage regen. But then, sometimes regen would kick in on a downhill run as expected and at the bottom I would start pedaling and on the way up, when I was only going 10 or 12km/hr, regen would kick in again and would revert to the throttle, so the more I pushed down the throttle, the slower I went. I would have to stop on the hill, cycle the power off and on to clear the regen and then the throttle would work normally. I would go back home and check all my settings and indeed, regen was disabled on pedal position as well as throttle. Things would go along fine for a while and then it would happen again. Finally, I just gave up on regen completely, did away with the speed limits and just used the power assist at a lower setting (1x or 1.25x). Grin never did come up with an explanation other than to suggest it might be an intermittent error in the controller, which was a v4 unit. So this winter I purchased a new V6 controller and tomorrow when it's warm enough to ride, I'll try it out and hope the folks at Grin were clairvoyant geniuses.

I can't think of much off the top of my head that could cause any of that, other than a bug in the controller firmware, or a fault in the system elsewhere that sends a signal causing it to happen, or a set of interactions between settings (many of which are not accessible to the user via the PRsetup program normally; only thru ediring specific parameters that you have to dig into it to find, and which have little documentation available outside of ASI's private documentation) and circumstances (which should result in consistent repeatable behavior if the circumstances can be repeated closely enough).


It sounds as if you have disabled this, but it's not clear if that's in the CA, the PR, or both: Do you have any form of regen control setup in the CA? Just to eliminate it as a possible source of the issue--if it is setup to output a throttle value below 0.8v for any braking events, and if the PR is setup to respond to below 0.8v by braking, then any condition or fault in the CA that causes it to force throttle below the PR's trigger level will cause regen braking to occur.

For instance, you can setup the CA so that using the ebrake lever turns the throttle into a variable brake control. When the brkae lever is pulled the throttle now varies the CA output between 0.8v and 0.0v (in that direction, opposite of the usual direction when it's making a normal throttle signal). The PR can be setup to do this (might be the default, can't remmeber; the old Grinfineons did this built-in). So any issue wiht brake lever switches or wiring that can accidentally trigger it on can accidentally trigger regen.





When the speed limits were working though, I was able to get 150 km out of a single charge on the battery and only be down to 48V. Without the speed limits, with no regen, I was back down to 120 km range and less than 46V, which was extremely disconcerting, because I live at the top of a hill and this bike, even though it's carbon frame, is still 50 lbs and it's a beast to push. My last build in aluminum was 65 lbs, but having to push any bike home sucks, especially when all the neighbors are watching.
At least it's not like my SB Cruiser trike. Even if I was healthy and non-arthritic, I couldn't push it far on the flats, and as I am, can barely push it up the short slope of my *driveway* which is hardly classifiable as shallow, much less steep!
 
It sounds as if you have disabled this, but it's not clear if that's in the CA, the PR, or both: Do you have any form of regen control setup in the CA? Just to eliminate it as a possible source of the issue--if it is setup to output a throttle value below 0.8v for any braking events, and if the PR is setup to respond to below 0.8v by braking, then any condition or fault in the CA that causes it to force throttle below the PR's trigger level will cause regen braking to occur.
I expect it was a bug in the controller. The CA is only a year old. Last spring, as soon as I put in the T-17 BB torque sensor, the speed display on the CA went crazy, jumping all over the place. Grin said to install a mechanical speedometer and they have a nice little video showing how to do it. Problem for me is that the board shakes so badly, the tip of the soldering iron, the solder and the contact never intersect long enough to melt the solder. I managed to do it though and I thought I had done a good job, but the first time I rode the bike, I noticed that I still didn't have a speed display and the CA was getting really hot, really fast. I had to turn off the power and cycle home with no power assist, all uphill. That little incident prompted the need for a new CA3, but this time I discovered the joy of solder sleeves and I've had no issues with speedometers ever since.
For instance, you can setup the CA so that using the ebrake lever turns the throttle into a variable brake control. When the brkae lever is pulled the throttle now varies the CA output between 0.8v and 0.0v (in that direction, opposite of the usual direction when it's making a normal throttle signal). The PR can be setup to do this (might be the default, can't remmeber; the old Grinfineons did this built-in). So any issue wiht brake lever switches or wiring that can accidentally trigger it on can accidentally trigger regen.
Towards the end of summer, when I abandoned regen completely and set up the bike for power assist only, any unexpected regen problems disappeared. I just don't like riding that way. I like the idea of speed limits for power assist and regen and apparently the V6 controller can handle that better than the V4 controller. So, I'll try it out this year and report back on my progress. Personally, I don't like the path that Grin has taken with regen by modulating it on a throttle or a brake lever. I find that it's counter intuitive. I only want to remember that pulling the brake lever stops the bike and depressing the throttle makes it go faster.
 
Last spring, as soon as I put in the T-17 BB torque sensor, the speed display on the CA went crazy, jumping all over the place. Grin said to install a mechanical speedometer and they have a nice little video showing how to do it.

That's a wierd problem. It sounds like the torque sensor might have a ground that touches the frame of the bike so that it creates either a ground loop, or picks up noise (probably motor noise) on the ground line and feeds that into the CA. I don't understand why that would affect the speed sensor, though, unless it also affects motor operation (because the speed sensor would be one of the motor halls, so anything that causes erroneous output of that sensor that causes wrong speed readings would also cause the motor controller to get wrong position signals).

Or perhaps there's a wiring fault in that CA's wiring / PCB / etc that shorts the torque sensor's cadence (or torque signal) sensor to the speedometer input signal. (perhaps if the pins are next to each other on the MCU, or routed next to each other somewhere on the PCB, there's a solder bridge?)

Anyhow, it would have to be some interaction between the T-17's design and the motor signal hall that's used for speedometer, *or* the PR's output of that signal.


Problem for me is that the board shakes so badly, the tip of the soldering iron, the solder and the contact never intersect long enough to melt the solder. I managed to do it though and I thought I had done a good job, but the first time I rode the bike, I noticed that I still didn't have a speed display and the CA was getting really hot, really fast. I had to turn off the power and cycle home with no power assist, all uphill. That little incident prompted the need for a new CA3, but this time I discovered the joy of solder sleeves and I've had no issues with speedometers ever since.

I have had to build a little workstation for small repair work that has a magnifier and all the tools to hold stuff for me (the pics don't show everything that's there now, and some stuff has changed)
Camera-magnifier electronics workstation




Towards the end of summer, when I abandoned regen completely and set up the bike for power assist only, any unexpected regen problems disappeared. I just don't like riding that way. I like the idea of speed limits for power assist and regen and apparently the V6 controller can handle that better than the V4 controller. So, I'll try it out this year and report back on my progress.

By "abandoned regen completely" what specificaly do you mean? Disconnected controls or wires for it? Changed settings for it (from what, to what)? Etc?

Figuring out the problem also requires knowing whether you were doing the controlling within the CA, the PR, or both, and what the specific settings were for each, and what experiments were tried (and their results) to fix the issues.




Personally, I don't like the path that Grin has taken with regen by modulating it on a throttle or a brake lever. I find that it's counter intuitive. I only want to remember that pulling the brake lever stops the bike and depressing the throttle makes it go faster.
I happen to agree--no matter how well you train yourself to use the system as it is, the reaction time will be longer to do it this way than to just pull the lever. And for anyone already trained over years to use a brake lever normally the reaction time will be even longer than anyone that never rode any bike of any kind and has never used a brake lever. And in a "panic stop", your brain will revert to the control method it learned first / has used longest / most, most of the time. Since braking reaction time is often critical, then this could be an issue in some situations. (if the switching brake lever still controls a well-set-up mechanical brake, it won't matter, but there are numerous bike builds that use *just regen* on the wheel that lever controls (including my SB Cruiser trike) so that there is no braking occuring until the regen engages at the appropriate strength).

AFAIK they did that because they didn't have a second analog input available, so the only option then was to do what they did (technically they could have given the choice between a torque sensor and variable regen, and used that input for it, but it would have probably been an even less popular choice).


There are a few ways around the design. One is documented here:

It's even easier now, because Xiaomi and others make variable-output brake levers, so all you'd need do to use it with the CA is to add a switch to the brake lever (if it doesn't have one) to trip a relay that switches the CA throttle input between your actual throttle and the variable lever output.

If you prefer, you can setup the PR itself to accept the variable lever input directly on a second analog input, and not run that lever to the CA. On older versions than v6 it would be easier because you just separate the throttle and brake wires, and setup the appropriate voltage ranges in the setup software for each to respond to the independent throttles. In v6 you have to change a setting to enable separate inputs first; I think this is on page 20? of the PR manual.

I haven't done this as my source-switching setup works and these days I prefer to not break working things to do experiments, at least on my daily ride. ;) (am building a new one slowly that will be a new testbed)
 
By "abandoned regen completely" what specificaly do you mean? Disconnected controls or wires for it? Changed settings for it (from what, to what)? Etc?

Figuring out the problem also requires knowing whether you were doing the controlling within the CA, the PR, or both, and what the specific settings were for each, and what experiments were tried (and their results) to fix the issues.
I reprogrammed regen out of my profile last year. This year, with a new controller, I've put it back in. Today was my first test ride and it went reasonably well. I had set the speed limits for regen down to 35km/hr and it kicked in just when it should. The power assist levels were fine. The only problem is the throttle. If I press the throttle lever during a ride, it shuts off the power assist, so you end up pedaling a 50lb dead weight. I have to stop, cycle the battery off and on to clear the settings and then it's ready to go again. I didn't try the throttle from a dead stop after a power cycle. It may work then. If not, I may have to just remove the throttle entirely and remember fondly how it used to be.
 
The only problem is the throttle. If I press the throttle lever during a ride, it shuts off the power assist, so you end up pedaling a 50lb dead weight. I have to stop, cycle the battery off and on to clear the settings and then it's ready to go again. I didn't try the throttle from a dead stop after a power cycle.
Is the throttle fed into the CA? Or into the PR? (same for PAS--which does it feed?) Below will assume the CA itself is being fed by the throttle and PAS sensors, and sending a throttle signal to the PR.

If into the CA, what voltage range is it set to output, for what range of input? What is the PR set to expect for throttle input voltage range?

And what voltage does the CA *actually* output when the throttle is used, vs the PAS? If the PAS works but the throttle doesn't, then the CA is outputting a correct throttle to the PR for PAS, but not for throttle.

If PAS works as expected, but the throttle isn't allowing any operation, it means either the throttle itself is causing an input that it shouldn't, the CA is set to expect the wrong input values, or the throttle is connected to the wrong input on the CA, etc.

If the CA is set to expect wrong input values, perhaps the throttle is causing a limit flag to trigger--if so, knowing what that is in the diag screen one button press to the left could help you narrow down the issue. If no limit flag happens when trying the throttle and cuts off the motor, then it's likely the CA is either ceasing to output a valid throttle (no longer within the range the PR expects) or it's outputting a throttle voltage equivalent to the PR's braking range (if it's set to accept braking command on the throttle input).
 
Back
Top