Luna BBSHD Ludicrous V2 controller documentation

[Bengy22]

Thanks for getting back with me, understandable that 72v is the max supported. I have another question, currently as temperatures are a big concern of mine does the eggrider display them? I know the eggrider can display them when being used with other controllers so I would be very disappointed to hear this isn't implemented. I couldn't find any one that said it was though, if its not I would love to see it be in the future, checking your phone can be hard when its buried in a pocket and you are wearing gloves. Maybe you can put the word in? I hardly think I would be the only one that would appreciate it, thanks!

[fattiejack]

I recently upgraded my BBSHD with the Ludi V2 and am using the latest Luna Vesca app. I am not able to find this screen with all of these great adjustments that can be made. Can you say why that is, Marcos? Thanks!

[fattiejack]

I just installed my Ludi V2 and Vesc app and it seems to be doing fine. However, Marcos referenced a page on the app "Apps->ADC->General->Positive Ramping time" and "Apps->PAS->Positive Ramping time" which I am unable to locate on my Vesc app. Is it no longer available in the latest update?

[intramorph]

72V is the highest you can go with this controller.

[Bengy22]

Hi! I got my Ludi almost a month ago and I've been very happy and pleased with it. I've been using it with a 52v battery I had previously which has been great and fine but I'm looking to move to a higher voltage battery so I can get more rpms and less heat (motor sure does heat up fast when you go above 30mph haha). I figure this will lower temps because of less amps more volts for the same watts and less FW needed. I got wondering though as I plan to build my own battery, is 72v the max voltage? My thoughts are its a lot easier to fit 6 more cells (20s3p to 22s 3p) than to get another 20 cells for another parallel group. And this would give me just a little more watt hours and also a slight rpm boost as well. I know the controller has 100v parts so even a full 22s charge would be under that at 92.4v. But in the vesc app the max I can put is 20s and 86v which would cause issues. And also the eggrider I'm sure would also be through off (although I don't use the % I like volts better). Is higher voltages something that could be implemented? And while we are talking features I would love if on my 860c display I could make the "range" show the motor temp instead. I would find this way more helpful so I can know exactly when I need to start backing off (yes I know it will for me but I still like to know haha).

I hope to hear back,
~Ben

[Dan Bet]

Hi Marcos! Im Daniel and have a v2 controller. I tried to update the firmware via the VESC app i downloaded from the Luna update site. I was able to see the controller and hit update. Went through 100% updating it; however, a few seconds afterwards, my display displays error 30. Communication error. The vesc app cannot connect either. I think somehow the update bricked my controller. Is there anyway of getting it back to a default point?

Thanks, -Dan.

[stts]

waste of time

[Jungle]

Hi. Is there something I have to do to turn on the Bluetooth. My app doesn't pick up when it scans. Thanks

[Floid]

A couple configuration questions. I skimmed through the posts but don't see good explanation of these. I don't see much of an explanation in the manual. Let me know if there is a better place to look. I have the X2 bike with 54 v battery.

RPM - is there any advantage of a lower RPM setting? I mostly run street legal settings - any reason not to increase RPM to the max or near the max? Seems like this would be the most efficient setting for the motor and heat regulation?

Power vs PAS Amps - what is the relationship between these? For example, if I set power to 500 watts, does the max amps equal 500 watts / 54v = ~9 amps? As long as PAS amps exceeds this then it should not limit the assist level? However, in messing around, I can tell a difference between 25 and 35 PAS amps for a given assist level, and I see motor amps up to 20 amps on the ride display. At 20 amps wouldn't the motor be putting out about 1000 watts? I'm having a hard time connecting the dots.

PAS Amps vs Throttle Amps - I notice that increasing PAS Amps automatically adjusts Throttle Ams down, but then I can increase Throttle Amps again. Is there a relationship between these two? Do they need to stay under the max configured battery amps?

Thanks!

[marcos]

in that case, the overvoltage is real and the reason is the battery being far away from the controller and having field weakening enabled. Generally its not a problem to have long motor phase wires, an airplane could have the motor 100ft away from the controller... but it is important to keep the DC side of the controller close to the battery. When the controller is far away from the DC source you'll often see a bigger bank of capacitors at the controller to avoid current spikes in the DC wires.

Fortunately all v2 controllers use 100V rated parts and its safe to increase the input voltage limit to 84V. Its there just to make it obvious to a user that the settings are for a 14s battery, in case you keep jumping from 52V 100A and 72V 60A (you may not want to draw 100A from your 72V batt). If those faults keep happening with a standard bbshd+luna battery pack I can increase the limit a bit, I just haven't seen them.

For those running a 72V battery: short, tight DC wires for the win

[ncmired]

I've two BBSHD V2 controllers, and both have shown a tendency to throw an overvoltage error while running on the bike stand and/or with no load on the rear wheel. The behavior symptom is repeatable:

1. while the system is "on", hit the throttle (motor runs)
2. let off very briefly and hit the throttle again (the motor does not run, nor does PAS work)
3. wait for a few seconds (roughly the chain spindown time) and either hit the throttle again or spin the pedals - the motor again runs

No errors show on the display, and I got the same symptoms when all motor inhibitors and related sensors were unplugged. The first controller exhibited the issue early on, and the second one did today after extending the power-related wiring to install a second battery.

Thanks to Marcos's excellent software, I could catch the overvoltage error reported briefly by the controller. I only run 52-volt batteries, and the overvoltage was set (IIRC) in the sixties - I reset it to the high limit of approx. 84 volts, as I did a long time ago on the first controller.

My guess is that there's an inductive kick - perhaps too much for a capacitor to suppress and/or being picked up by an overzealous sensor circuit.

[marcos]

If the batteries are exactly the same and both can supply 40A, then you could increase the controller battery current limit to 80A. That would dump about 4kW into the motor.
However, keep in mind no two batteries are exactly the same, one of them will have lower internal resistance, or higher voltage or better cells, so it will tend to flow more amps than the other. I don't know what batteries do you have, and even if I knew I don't know what would be an adequate derating to accommodate for this. If I had to swing it I'd go for 60 battery Amps max and see how it goes.
It kind of sucks when one of the paralleled BMS's trips as the other one has to take the full load, and gets discharged. If their voltage gets too different you can't re-arm the tripped BMS because it will send a ton of Amps from the charged battery to the discharged one, tripping the BMS again.

[stts]

waste of time

[Wamedrano]

Hi I guess I asked this question in a different topic incorrectly….


I own a Ludi controller and want to use two 20AH in parallel. (I have been doing this for a while safely and correctly) they both have a 40A continuous bms.

since in the Ludi controller you can select amp limit for batteries should I select 40A or 80A since it draws from both. My understanding is that if your motor draws 40A it will draw technically draw 20a from each (hence why voltage slag is very small when in parallel ex 1-2 v)

im not sure what amp setting to use.

[marcos]

Hi Rob, do you remember exactly what you did to end up like this? This has happened before and I don't understand how you can brick it with a firmware update if the app only allows you to upload the correct firmware