Luna BBSHD Ludicrous V2 controller documentation

[marcos]

That's basically the email that Ludi v2 users received :)

Keep the feedback coming!

Cheers

[paxtana]

Maybe try downloading it on windows and transferring it to your phone after? Download works for me.. I could mirror it if you want

[BUD WHITE]

Hello
I used my Android phone, but once I try to download your link, the phone says app not installed. I don't know if this makes any difference or not, but I do not have any of the 3 batteries listed on your screenshot.

[paxtana]

(update notification copy for reference)




Good news, your drive unit is getting even better!



Here at Luna we keep working on the Ludi V2 day and night, and after coding, testing and gathering user feedback we have some improvements to share in this new firmware release. It also comes with small tweaks into the VESC Tool app to improve the user experience.


FIRMWARE CHANGELOG


5.02 STABLE-3:

• Pre-configured battery settings:
  • Soft cutoffs
  • Overvoltage trip
  • Undervoltage trip
  • Cell count
  • Capacity
  • Current limit
• Tuned temperature limits
• More linear power level increments from the display
• Fixed App "Profiles"
• Faster boot to catch the Eggrider last level setting
• PAS keeps the motor spinning at minimum current to prevent chain slapping
• Tighter 12V rail monitoring
• New terminal command to read and store the default power level for display-less applications

VESC TOOL CHANGELOG

• Embed Luna BBSHD Ludi firmwares into the app for easier updating
• Add Motor Temperature gauge to the realtime page. Motor temp is the main limiting factor and it's good to keep it in check
• Fix FilePicker dialog used for datalogging that didn't work on some devices.
• Remove unused IMU realtime page that crashed on some devices

UPDATING THE FIRMWARE

Download the app installer here

Go to the FIRMWARE tab, select the correct firmware for your system depending on your battery type:

	52V Wolf	52V Dire Wolf	72V
Type	14s4p	14s6p	20s3p
Capacity	12Ah	21Ah	9Ah
Batt current	70A	105A	60A

Keep your Android device close to the controller and don't shut down your BBSHD while updating the custom firmware.


REQUIRED TOOLS

• BBSHD Ludicrous V2
• Android device

Have fun!






--
Luna Team

[marcos]

No problem, been using that new screen firmware for a while and its also required for 72V setups as the new eggrider firmware can print correct voltage information

[StvMan]

Is there any conflict with the Ludi V2 and installing the new firmware from EggRider (V2.5)

[BUD WHITE]

Thank you again for answering all of my questions Marcos. I am off for a long ride on the beach. Have a great day. Cheers.

[marcos]

I have finally dialed this wonderful V2 controller to my liking and just came here to say that this is by far the most fun I have had on any of my PEV's, including my upgraded ASI BAC 4000 Sur Ron X. This enabled my fat bike build to be 3 different ebikes by a simple few pushes of some buttons to change one of my custom profiles

I'm happy to hear the experience is on par with a modded Sur-Ron! Can't overstate how big of a deal that is.

I have 2 questions for the future. 1. Is there any plans to create a torque sensing pedal assist option to a BBSHD in the future?

I think its not viable to retrofit a torque sensor into a BBSHD. Firmware can read torque sensors but mechanically its just too involved. There is an M600 ludi on the works with the same software platform you know and love, which does have torque assist, but the motor is much smaller so its not in the same league as a BBSHD.

And... 2. Is there a way to make my Ludicrous V1 controller bluetooth enabled at some point? Thanks again for inventing this controller. Cheers.

Nope. V1 is a modded bafang controller which means we can't introduce any firmware or hardware improvements like that, only bafang can do that, and they don't. An uart to bluetooth adapter could be installed, but the bafang protocol is so poor that there isn't much to gain there and can't be made compatible with the vesc app. VESC datalogging is super rich, to the point I can log 25,000 samples per second to analyze faults, or log a full week of dyno operation.

[BUD WHITE]

I have finally dialed this wonderful V2 controller to my liking and just came here to say that this is by far the most fun I have had on any of my PEV's, including my upgraded ASI BAC 4000 Sur Ron X. This enabled my fat bike build to be 3 different ebikes by a simple few pushes of some buttons to change one of my custom profiles. I have 2 questions for the future. 1. Is there any plans to create a torque sensing pedal assist option to a BBSHD in the future? And... 2. Is there a way to make my Ludicrous V1 controller bluetooth enabled at some point? Thanks again for inventing this controller. Cheers.

[StvMan]

Understood....Thanks.

[marcos]

Are there any special precautions and /or advantages in tying in a Cycle Analyst V3 into the Ludi V2 controller?

Special precautions:
* It was never attempted
* It was not designed to be compatible with the CA

Advantages:
I don't see any, I think out of the box the ludi software is already outperforming the CA, not sure why would anyone want to add all that wiring for features that are built into this controller.

One thing it lacks is cadence logging and cadence stats, but instead of spending time and $ on a CA I would encourage people to help the vesc community to implement it. That way (and this is valid for any new feature) the new open source code becomes available for anyone who would like to use it or learn form it.

[StvMan]

Are there any special precautions and /or advantages in tying in a Cycle Analyst V3 into the Ludi V2 controller?

[marcos]

Oh. Yes, the controller increases the top speed by about 25%, unlocked by an algorithm I contributed a while ago, so yes pedals move faster. 72V setups also spin faster.

As you stated, a motor running low RPMs is not very efficient. To produce the same amount of watts it has to flow more current through the windings, and on these small motors I²R losses are pretty dominant.

[ncmired]

Hi Marcus;

Apologies, I phrased my question poorly - I meant the top pedal axle RPM via the throttle, motor unloaded. Does V2 controller increase the RPM? I'd guess not by much (over the max 150 RPM I've seen referenced often).

What I have been doing with the intent of or hope when riding for maximum range efficiency, is to match the bike gear to the terrain, so that the motor is spinning flat out, and just being (for the most part) very lightly loaded. Think locked-on throttle and a "keep the motor spinning" mindset. On level ground, for my wind load, weight load, and bike drag, for most of my bikes this returns approx. 20mph, and a 300watts guesstimate draw (hard to visually average the jumping display indicator and pay attention to the road). And, at a pedal cadence I can't possibly match.

I've always been a stomper, or relatively low pedal cadence rider - a bad match for how fast I've been lead to believe the BBSHD wants to turn.

[marcos]

Cadence question - does the motor still peak out at the (I believe) 150 top pedal RPM or cadence unloaded, or is it even higher with the V2 controller?

Does this value show up in the data stream - I'm guessing no, as I don't know of any sensor for it?

The pedal RPM is configurable from the GUI, here:

In this screenshot, at 10 pedal RPM you would have 0% assist, and at 120 pedal RPM (and beyond) you would have maximum assist. In this case max assist current is 8% of 150 phase Amps. These parameters are user-editable so you could set the RPM end at 800rpm and you'll have to pedal like crazy to get it to max out. Does this answer your question?

I haven't thought about including pedal RPM into the real time data plots, its a good idea. I need to check if its too difficult to merge into vesc as it reduces bandwidth for all those who don't have PAS.