Luna BBSHD Ludicrous V2 controller documentation

[AZguy]

I feel that pain more than you can imagine - more than half my business the last year or so has been redesigning products to utilize other parts we can actually get and even then it's most often only good for whatever can be bought at the time

[marcos]

Oh the only reason why we are not making more v2 controllers is the silicon shortage. The bbshd controller uses very high end parts, one of them has been impossible to source for a long time

[ncmired]

Hi Paxtana, thanks for the follow-up - apologies for the typo / confusion, I was thinking of the BBSHD V2 controller, not the M600 X2 bike.

[paxtana]

I do not see anywhere on the X2 page that says this needs staff approval. That is only for V2 ludicrous for BBSHD, which is a separate but related project from the X2 bike.

Assuming you are referring to V2, availability is ultimately Eric's call. It makes some sense to hold onto these for VIPs as a value add to reward those that choose to do a lot of business with Luna, especially in light of how difficult and expensive it is to make more; what limited supply there is would be wiped out immediately if it was made publicly available. That said, I would not be surprised if it is rolled into some kind of black friday combo deal or that sort of thing. It's not like we have any BBSHD bikes we still make with this as an option anymore anyway. But that is just speculation on my part.

[ncmired]

Here's a few comments and questions:

1. First and foremost, Marcos's software tames but doesn't neuter the V2 beast, permitting fine tuning before not possible, of what the bike drivetrain can handle and what the battery can put out. Before, in the beta state, the beast was nasty - ready to wreak havoc and bitemarks on the rider.
2. Now, the controller /BBSHD pair can be shipped out with a muzzle, totally controllable by the owner. I'd argue that this combination is safer than say, a Sur Ron. I'm wondering why purchasing the V2 controller still requires staff approval? Marcos has tamed the beast, perhaps now Luna will let availability rule the sale?
3. Correcting some, IMO misstatements on the V2 web page would help future purchasers - those being: "This controller is made available to trusted Luna VIPS on its initial offering" (well past that point now) and, "Retains all features of BBSHD" (no shift sensor and walk mode)
4. Jumping from 52 to 72 volts is mighty tempting with the V2, but the current 72 volt display options are, i think, limited to the Eggrider. A variation of the 750C display is available for the Cyclone and CYC motors - can the same display be altered or configured for use with the V2 controller?

Disclaimer: I'm the very happy owner of two V2 controllers and it's frankly none of my business how Luna runs its business -but I do wonder sometimes what Luna is up to.

[grahamgfr]

Dear All,

Just a quick update to my intial problem, long story short my display was faulty out the box (although highly frustrating I'm not finger pointing or playing the blame game here, these things do happen). Marcos was very much an excellent help in diagnosing this issue. Thank you.

I can confirm that the controller is AMAZING, it works with 72v no problem and with the latest EggRider firmware. It is far far better than any of the competion. I'm very pleased.

May I thank everyone who has been involved in providing me the Luna Ludicrous V2 here in the U.K.

All the best team,

Graham

[badrab]

Yup, that did it--changed the value in the Egg settings to 58.8, thanks again, Pete

[marcos]

yes, a fully charged wolf pack is 4.2V x 14 = 58.8V. The voltage at 0% depends on who you ask...

[badrab]

Thank you for the quick reply Marcos--checking the Egg settings, it's set battery 100% voltage 100% at 53.95V (Image 1). But the Egg itself is showing the present voltage as 56.8V (image 2), could that be the issue?

[marcos]

The battery % shown in the eggrider is not calculated by the motor controller, so it has to be something in the eggrider settings.
Probably the number of cells in series or the voltage, it could be set for a 48V battery for example

[badrab]

installed the V2 controller, and VESC using an Android. It's on a fat bike I built 5yrs ago, using the original BBSHD.10 miles of test riding over the past few days and all seems good, just one issue:

--VESC seems to be correctly reporting the battery %, which has dropped to about 89% over the course of the 10mi

--But the Egg is stuck at 100%. I'm using a 52V 17aH battery and the 52V Wolf profile, (because I don't know the other characteristics of the battery I have--not ideal I know)

--Maybe that's the problem: a discrepancy between the battery capacity VESC is assuming and the actual 17aH capacity of the battery?

--I went into the Egg settings and changed the battery capacity to 17 (I think it was at 11), but this seemed to have no effect

Any suggestions much appreciated! pete

[marcos]

lets move canbus discussion out of this thread, as the BBSHD doesn't have a CANbus display :)

[Ductapemaster]

Hey Marcos, yes I purchased an X2 with the Ludi V2 — my bike arrives Thursday! Happy to share any proof of purchase required. I really appreciate the offer, and the insight.

I assume the two protocols operate at different speeds, and that's what the mismatch is. Is that correct? I have been considering building a little DIY display/computer with some parts I have laying around, so any direction for compiling with the VESC protocol enabled would be lovely as well.

Thank you!!

[marcos]

If you purchased an X2 bike with the M600 ludi v2 controller I can send you the source code, otherwise you'll have to wait until the code is mergeable.
This is the BBSHD support thread, so I'm not sure if you got the BBSHD or M600 controller.

Having said so, the data on the CANbus is super limited, only the data used by the bafang display is on the bus. The bafang canbus protocol is limited, and the VESC canbus protocol is awesome to acquire all kind of log information, but bafang and vesc protocol can't work together on the same bus.
Cheers

[Ductapemaster]

Hey everyone, new here to the forums. Just purchased a X2 bike with the Ludicrous V2 controller last week for an engineering demonstration I'm building, and I'm very much looking forward to getting started.

I'm working to integrate an IoT module into the bike, and one of the major goals of my project is to integrate my module into the CAN bus to read out real-time information about a ride. After that, I would like to prototype some control functionality to set parameters remotely, for example a speed limit.

I see above that the code for the M600 variant of the controller hasn't yet been released, and I don't see it on a branch on Github. I'm hoping to save time reverse engineering the CAN protocol — is there any documentation available for what packets are being sent on the bus, or do I need to wait for the code to be merged?

I'm on a bit of a time crunch with the project and want to leverage as much existing work as possible so I can focus on the parts that matter! Any help is appreciated.