I don't see the V2 mentioned as being a bit thicker. Luna included a chain ring spacer, thank you very much. I have only one bike where this will be a problem.
The Rolhoff is sold for a 190mm dropout, but it is really a 170 with spacers. Therefor the chainline is already fat bike challenged. I fear there is not enough wiggle room.
The V2 is bolted up to the Uzzi now, so I added to the build report:
https://electricbike.com/forum/forum...th-bbshd/page3
Announcement
Collapse
No announcement yet.
Luna BBSHD Ludicrous V2 controller documentation
Collapse
This is a sticky topic.
X
X
-
Back at you... wrapping up other obligations so just looking for some time to mess with one. I'm cozy with code so I want to get "under the hood". Summer is coming so riding is going to get limited a bit. Still super nice now though except a little bit hot in the afternoons... still gotta get out your way!
I throttle and pedal when I'm doing stuff that's changing a lot so the throttle gives me that fine control instead of just letting PAS do it's thing... I like PAS for cruising tho. I almost never throttle only. I do want to be able to grab throttle when I need it and when I set the BBSHD to follow PAS level didn't like that at all!
-
Hey buddy, long time. For my first tests, having the throttle tied to the level has been helpful (didn't break at 7, let us try 8). However I do worry about the long run. Already I grabbed throttle after a bunch of tests at 2, but not realizing I was on 9 created a yikes moment. Throttle tied to PAS might be very useful for those of us who throttle and peddle at the same time, get one and test with us!
-
Yes - throttle behavior ideally should be consistent and unchanging
This is especially important managing higher powers IMO
My BBSHD was one of those that had the "PAS-override" issue where you couldn't use the throttle while pedaling and we came up with a parameter set that effectively overrode the PAS altogether and I set it up with three levels of maximum throttle (~750W, 1000W & 1500W) and after a bit I just always left it alone. In that mode I'd have to use the throttle 100% of the time and really didn't like it changing even though the differences weren't all that great and not that high.
I did an electrical mod at least a couple of years ago to address the "PAS-override" - best thing I could have done, didn't realize how much that bothered me until I fixed it
I tried tying the throttle to the PAS levels and even at those lower powers thought what a really bad idea. The worst part was that you couldn't command more power than the PAS level... but having it be different was also really bad, especially since the difference between PAS 1 and 9 is almost 20:1 in my setup...
-
Marcos/Azguy, Would I be correct in saying that AZguy’s config preferences would be met by choking back the PAS% while leaving the MAX motor current at 150A (or in the profile settings MaX watts). While you wouldn’t reach max in PAS, you would always have much more (if not max) using throttle for those critical moments.....correct?Last edited by StvMan; 05-19-2021, 06:18 PM.
- Likes 1
-
Think I hit a firmware bug. Wanna discuss here or offline?
- Likes 1
Leave a comment:
-
I noticed that in the latest firmware update there was this feature "PAS keeps the motor spinning at minimum current to prevent chain slapping". How is this implemented as I have not noticed this behavior, Thanks
- Likes 1
Leave a comment:
-
Cool Marcos - I figured it would be easy to address in code
My background is decades, more than a million miles, plenty of track time and desert racing motos and so I may have a different perspective on the throttle. For me it really needs to be consistent and I'm likely ok with full throttle being full power although I'd likely limit full power on this controller for both PAS and throttle... throttle needs to be consistent and exceed the power of the lower PAS levels which I would likely set a lot lower than most people - e.g. the maximum current in PAS1 on my BBSHD is just 1.8A (<~100W).
-
Thanks Marcos. Slower was the correct guess. Thanks. I’ll play with that.
- Likes 1
Leave a comment:
-
We discussed this and it was done that way to avoid users getting injured with the default 150A setting.
Eventually it this be configurable from the app, but if its a hard requirement NOW you can change the code, its very few lines of code. I rode it your way for quite some time until we agreed to tie throttle to the levels.
- Likes 1
-
Hi Adam, I think you need to define "softer". I'm not sure if you want a slower response (heavy filtered PAS input) or just lower torque like ncmired pointed out.
If you want your throttle to react slower, you go to Apps->ADC->General->Positive Ramping time
If you want your PAS to react slower, you go to Apps->PAS->Positive Ramping time
These two settings introduce a delay. if you set it to 1.0, it will take 1.0 seconds to reach 100%
If you just want to reduce the torque you can do that using profiles.
Personally I just keep my motor current limit maxed out (150A at the throttle) and just play with App->PAS->PAS Max Current for lower PAS torque
- Likes 1
-
I definitely don't want the throttle to change *ever* aside from diddling the parameters - it should behave the same always so we can get our muscle memory working with it proper
If max so be it although I'd be happy with it less - I've had motos where max throttle can dump you on your butt or break the rear wheel loose so I'm cozy that I can get used to anything as long as it's "enough"... but that's the point isn't it? I need to get used to it and if it changes that's much, much less practical... deal killer really...
I suppose since it's open source it's likely easy enough to address even if just hard coding a maximum but I'm not sure why a throttle that behaves differently depending on *any* other setting would ever be a good idea in my not so humble opinion... particularly in a higher power vehicle... a wrist will learn whatever it is but if it's not enough for the times we need a lot of power right at the moment and it's different at different times it's pointless... this seems like a serious and potentially dangerous flaw to me...
Leave a comment: