Luna BBSHD Ludicrous V2 controller documentation

[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.

[marcos]

I had to provide support around this just too many times. Happens when you switch phones or switch vesc apps. I'm hardcoding the pairing flag so the controller stays connectable at all times.

[grahamgfr]

Sure no problem..
Connected the controller via the micro usb port to my laptop.
Opened the Windows version of VESC Tool.
Connected
Read Firmware
Underneath the firmware version is a 24 digit number, make a note of this.
Open up the VESC Luna Gateway android app
Pair
Bottom left icon
Add from UUID
Copy the 24 digit number into the field
Now connect and it should work

[XikoPlavi]

So, what did you do to solve it?

[grahamgfr]

Can I check one more thing please, just had everything connected, latest EggRider firmware,connected VESC Luna App, uploaded the Luna firmware again and noticed one thing compared to a previous screenshot announcing your latest update. My firmware drop down menu simply says BBSHD_default.bin and at the bottom of the screen is shows HW : LUNA_BBSHD compared to VESC_BBSHD_52_DIRE_WOLF.bin and the same at the bottom of the screen too. I can see another screenshot duplicating this. I'm under the assumption that mine should be saying LUNA_BBSHD_72_POWER_WOLF. when correct. Would it be possible that I have downloaded the Luna app and the firmware is missing ? (I have re-installed a few times) Thank you.

[grahamgfr]

Solved !! Back on the app now !

[grahamgfr]

Just sat down to have another go at setting up and the VESC Luna phone app has presented me with this message. What's the best solution please ? Thank you

[grahamgfr]

Thank you for the confirmation.

[marcos]

I just checked the latest eggrider firmware with the latest bbshd firmware and seems to be working ok. Eggrider is displaying 84V here.

[grahamgfr]

Thank you again Marcos, let me get my work shifts out the way and I'll update you.

[marcos]

Okay, so here are the checks I'm running:
* Updated the eggrider firmware from within the eggrider andoid app. Firmware included in their app is v2.5.61
* Checked that PAS levels are set correctly. For that I use the desktop version and look at General->Current. I see that "Max Current Scale" field changes when changing PAS level in the display. On startup the last PAS level used is correctly acquired.
* With a lab supply providing 61V I see that the eggrider shows 61V, despite the controller is supplying the display with 12V. I need a second supply to bump this to 84V for proper coverage, will do it tomorrow.
* I checked that when the controller is configured for 72V battery the max voltage threshold is set to 86V.

So for now it looks like software wise is okay. If you have the app running could you make a brief datalogging so I can take a look? That way I can see dozens of variables at once, maybe there is one going off spec and makes it limit the torque.