Cycle Analyst V3 preview and first beta release

Are you asking for the feature to be added, or asking if it's already there?

In either case:

There's no feature like that in there at present.

AFAIK from what Justin_LE has said over the years, no features can be added (without taking something else) as there's just no more code space in the MCU.


So...you'd probably have to create a little Nano or similar MCU device that either has it's own speedo to accumulate ODO data, or uses the serial data stream from the CA to accumulate ODO data from, to then provide these alerts.
 
It would be a nice feature to have on a mid drive that needs regular chain stretch check/ maintenance etc
 
I just setup a bike with an AllAxle v3 rear hub and am experimenting with regen for the first time. My setup: AllAxle rear, PhaseRunner v6, CAv3 with v3.2b3 firmware. I'm currently using a Sempu BB for torque/PAS (but my AllAxle has the torque sensor so I can switch if that would help).

I'm running into an issue and want to see if it is common. When I use backpedal regen the system often doesn't switch back into assist mode when I start again. A common example would be using backpedal regen to come to a stop, then a fraction of a second pedaling away from the stop. When I do that assist doesn't trigger for a few seconds (or sometimes I blip the throttle and that seems to get it going). This is making me turn off backpedal regen because I need torque assist to come up within one crank rotation to be useful.

I made a suggestion to Justin on YouTube to support backpedal regen only when the e-brake switch is on. For me this would be the best of both worlds: you get the intuitive usage of back-pedal to set regen amount (vs throttle), but the controller instantly knows if you are trying to brake or accelerate. He said they'll consider it, but it would be nice to get some more support if others like the idea.
 
I just setup a bike with an AllAxle v3 rear hub and am experimenting with regen for the first time. My setup: AllAxle rear, PhaseRunner v6, CAv3 with v3.2b3 firmware. I'm currently using a Sempu BB for torque/PAS (but my AllAxle has the torque sensor so I can switch if that would help).

I'm running into an issue and want to see if it is common. When I use backpedal regen the system often doesn't switch back into assist mode when I start again. A common example would be using backpedal regen to come to a stop, then a fraction of a second pedaling away from the stop. When I do that assist doesn't trigger for a few seconds (or sometimes I blip the throttle and that seems to get it going). This is making me turn off backpedal regen because I need torque assist to come up within one crank rotation to be useful.

I made a suggestion to Justin on YouTube to support backpedal regen only when the e-brake switch is on. For me this would be the best of both worlds: you get the intuitive usage of back-pedal to set regen amount (vs throttle), but the controller instantly knows if you are trying to brake or accelerate. He said they'll consider it, but it would be nice to get some more support if others like the idea.
Glad to see an All Axle V3 in the wild. Mine came in this week and I'm hoping to knock out my build this weekend. I'll be using the Superharness so no backpedal regen for me. My big ask right now is for analog/proportional hydraulic disc brake levers.
 
I'm running into an issue and want to see if it is common. When I use backpedal regen the system often doesn't switch back into assist mode when I start again. A common example would be using backpedal regen to come to a stop, then a fraction of a second pedaling away from the stop. When I do that assist doesn't trigger for a few seconds (or sometimes I blip the throttle and that seems to get it going). This is making me turn off backpedal regen because I need torque assist to come up within one crank rotation to be useful.
This is probably related to the stuff on the previous page, where BPregen doesn't actually let you come to a complete stop, it ceases at a certain speed, specifically so that the system doesn't have the problem you describe.

This post
has the notes about this feature, showing that it should cease the regen the instant forward crank motion is detected. Does your crank sensor have a direction indication line, so that the CA can tell which way you're pedalling? (I don't see how it could do BP regen at all if it didn't, but just making sure).


This thread
discusses the feature, if it helps any. Maybe the feature has changed since that release back in 2022, to remove the limit.



I don't know for sure, but it sounds like you have a firmware version where this limit isn't present, so that it does allow BPregen down to a stop, and so the system can't tell what's going on for some reason. (don't know if it's a bug or just a limitation of how the software reads the sensors, or design flaw in the software).
 
My back-pedal regen firwmare (3.2b3) does have that feature. I was actually glad to find that part of the thread this morning because I couldn't understand why the braking stopped just before the bike came to a complete stop. It seems like my bike still has trouble knowing when to go again.

The Sempu BB does have quadrature encoding.
 
Does the CA always correctly show which direction the cranks are spinning when you quickly change directions? (if nowhere else, this is visible in the Setup PAS Device screen)

Maybe something in the sensor or the CA isn't cooperating and detecting this in all situations?
 
I just setup a bike with an AllAxle v3 rear hub and am experimenting with regen for the first time. My setup: AllAxle rear, PhaseRunner v6, CAv3 with v3.2b3 firmware. I'm currently using a Sempu BB for torque/PAS (but my AllAxle has the torque sensor so I can switch if that would help).

I'm running into an issue and want to see if it is common. When I use backpedal regen the system often doesn't switch back into assist mode when I start again. A common example would be using backpedal regen to come to a stop, then a fraction of a second pedaling away from the stop. When I do that assist doesn't trigger for a few seconds (or sometimes I blip the throttle and that seems to get it going). This is making me turn off backpedal regen because I need torque assist to come up within one crank rotation to be useful.

I made a suggestion to Justin on YouTube to support backpedal regen only when the e-brake switch is on. For me this would be the best of both worlds: you get the intuitive usage of back-pedal to set regen amount (vs throttle), but the controller instantly knows if you are trying to brake or accelerate. He said they'll consider it, but it would be nice to get some more support if others like the idea.
Thanks for bringing it up with Grin; I'd run into the same issue/feature of the position-backpedal-regen taking a long time to "unwind" from a user perspective, and recently watched Justin's video about the feature, where he calls that particular behavior out.
 
What does it mean when the cycle analyst input on the screen flashes under load and power is cut? Is this some type of limit cutting in? Or does it signify the throttle input is down? . Or is the throttle input from the controller dropping first ? I don't think I have cav3 power limit set but it recently started behaving like it is! But not sure if it's a bad connection or battery BMS cutting out under full load ? So just trying to decipher what that indication on the main cav3 screen is for throttle input
 
On the diagnosis screen now of the limits awsvt went capital when this happens.. so their is no limit in CA but the vin flashes to zero when this happens? No power was cut to CA screen. What does it mean if Vin flashes and goes to zero?
 
Actually I think I was mistaken I sometimes see a capital A flag hence current limit is in play and is the maximum of the cav3 only 99amps? I cannot put it any higher?
 
I tried to disable the 99amp limit by setting Alim very low number like 2 to have slow response but it still cuts out.. is their anyway to disable the current limit ?
 
I tried to disable the 99amp limit by setting Alim very low number like 2 to have slow response but it still cuts out.. is their anyway to disable the current limit ?
You should probably figure out why that's triggering -- but in the meantime, if you change the throttle mode, the CA will stop interfering with the output entirely. I believe you would want 'bypass'.
 
You should probably figure out why that's triggering -- but in the meantime, if you change the throttle mode, the CA will stop interfering with the output entirely. I believe you would want 'bypass'.
Its hitting the 99amps on hard acceleration hence the capital A limit.. I can try the bypass to confirm bypass fixes it the issue is the main reason I use the cycle analyst is for thermal rollback... So I cannot just bypass it as that would disable thermal rollback also
 
The Unofficial User Guide for B22(final) is posted here.

Firmware B22 Prelim3 became B22 so there are actually no feature changes to the previous Prelim3 Guide. This version upgrades images, expands/clarifies existing content, and adds details for using LM35 temperature sensors (cell_man MACs). The sections on throttle ramping and power oscillations have been reorganized and new material on tuning the Speed Throttle has been added. The Speed Throttle stuff is incomplete (continuing bad weather for testing) but hopefully it will be finished up in the B23 UUG version. :D

Enjoy!
Sorry if I dig up an old post, but this was the only mention of the UUG B22 I could find, and since this document mentions a possible version B23 and Procedures to tune Speed control settings in Appendix B, I actually came looking for that..

can anyone confirm the B23 does exist and possibly point the UUG B23 Link?
 
Since Teklektik actively removed all but the most current versions of his work and documentations everywhere, and aggressively acted against anyone posting copies of any versions of them, I doubt there is anything out there other than whatever the most recent version was. (beyond what individuals saved to their local drives and did not mention they had in his "presence")

There may not even be that, since the UUG was supposed to have evolved into the actual official CA documentation available on ebikes.ca's CA info page, and if so then Teklektik would have removed all actual UUG versions.

(speaking from the experience of being reamed out by him for attempting to help others by preserving any of his documenation).


Unfortunately he's no longer alive to ask anything of, though, so unless someone happens to have copies of the UUG, whatever you can locate online is all that is available.
 
Ah, too bad. That was really handy last time I needed it. Mine copy is really ancient, though:
document version 3.0-e
2016.02.16
 

Attachments

  • CaV3_UUG_3-0e.pdf
    3.5 MB · Views: 14
It's been awhile since I've had my ca hooked up so wanna get it running on my newer bike. The firmware that is currently on it is 3.14. that was the stable version awhile back. Should I stay on 3.14 or is there a newer stable version that I should be using? Thanks
 
It's been awhile since I've had my ca hooked up so wanna get it running on my newer bike. The firmware that is currently on it is 3.14. that was the stable version awhile back. Should I stay on 3.14 or is there a newer stable version that I should be using? Thanks

I'm running 3.15. I believe that is the latest stable version, but I'm not certain. It is certainly working fine for me though. But if you run the Grin software, that should tell you for certain.

The Grin page says 3.14. But that page hasn't been updated since March of 2023. So I think it is out of date.
 
I'm running 3.15. I believe that is the latest stable version, but I'm not certain. It is certainly working fine for me though. But if you run the Grin software, that should tell you for certain.

The Grin page says 3.14. But that page hasn't been updated since March of 2023. So I think it is out of date.
Thx for the reply..I wonder if there is any big difference between the two. 3.14 to 3.15
If it's worth updating
 
AFAIK , it's not software controlled at all (not connected to the MCU); you'd have to open it up and change the resistance to the LED itself, to change the current and thus it's brightness. You could add a potentiometer if you want it adjustable on the fly, or you could put a switch that shorts out one of two series resistors to get two brightness levels

BTW, in context of fhis, (since it received a reaction today and brought my attention back to it):

It has now been a few years since I looked into it, but in at least some, perhaps all, of the CA's, the power regulation from battery votlage down to logic voltage includes the LEDs and their droppping resistor(s) in the circuit, so modifying the brightness may also affect the voltage regulation.

If the circuit of the CA anyone is considering this modificaiton for does have the LEDs / resistors in that circuit, I'd recommend removing the LEDs/rsistors from the circuit, and adding separate components that duplicate their functions in their places.

Then the LEDs/resistors can be driven from a separate lighting power supply, either derived from the CA itself or from a separate DC-DC powered by the battery voltage that comes into the CA casing (before it reaches the CA board).

Somwhere in one of the CA repair threads, or this one, is a part of the circuit diagram for a version of the CA (don't recall which one) that shows the regulation section, and should help anyone doing this trace out the actual circuti in thier CA to be sure which way will work for them.
 
Hey random semi related bit of info....I now run a ~30W ~48V LED light bar and power a DC-DC running a front/rear dash cam which probably draws another 5-10W. It's right at the limits of what the CA can handle and if I power them on separately in the wrong order it will trip the CA resettable fuse. Powering both on with the bike works fine normally though.

Anyway, just thought I would share that the CA can supply quite a bit of power when called for. :D

Cheers
 
Keep in mind that the CA isn't really supplying that power--it's just passing it on via the internal wiring from the battery input, thru the auotmatically-resettable fuse (I think all versions that have the lighting plug have that), to the lighting connector.

Just to clarify for other readers, I don't think the LEDs and their resistors are in series of that portion; they're just in the low-voltage regulation section (of at least some CA versions).
 
I forgot to add when I posted previously that recently I had the need to ride a distance in a dark area, and without my own lights on due to some...unsavory...people I wished to avoid contact with, and had a hard time seeing because of the bright white CA backlight, which I had to put my hand over so I could clearly see where I was going (easy enough with dark-adapted eyes, but impossible with that shining in them).

It's a very rare circumstance, but I have thought about a way to disable the CA backlight for the duration whenever it comes up.

The last time it was just that it was a very nice night and I was on the unlit canal path, and I wanted to see the stars and moon and the surroundings in their "natural" light.

That time I put black electrical tape (which I always have with me anyway) over the screen...but I didnt have time to do that this time around, and getting the sticky gunk it leaves behind off the screen is a chore.

So...if I ever remember to do it i'll post a diagram of the bypass and/or brightness control circuit here. :oops:
 
Back
Top