Just back from a day and a half at the coast and the a night away for NYE, but…
Yes, the ‘LudiV2’ controller is released. The controllers designer has been working with VESC since 2015 or so on various projects, and there’s a thread on a predecessor on emtb forums.
A nearly identical controller was released for the BBHSD in early 2021 by Luna, and there’s a looong thread on Lunas kb/forum on that, with several quite happ users.
The variant for the M600 is essentially the same controller, with different firmware to account for, for example, the torque sensor. You can technically flash the same controller with either firmware, although I cant think of why you’d want to..
The M600 controller document is online and linked to here:
https://electricbike.com/forum/foru...na-m600-ludicrous-v2-controller-documentation
The code is open source, although the M600 code base has not yet been merged back to the main VESC branch…the BBHSD code has been and I know its in process.
The mobile app is effectively a ‘simple and safe’ version of the vesc full desktop app. At the moment, given ‘v1’ was for the BBHSD the exposed settings are more throttle focused, along with typical things like max power, max current, etc. in configurable ‘profiles’ for Street Legal, Trail, and Ludicrous modes. These values operate in conjunction with the display set PAS levels, e.g. if set to 750W max power, and display is set to 9 levels, each level is ~11% added power from the previous.
The mobile app also has a typical dashboard including temp gauge, ability to set battery cutoff limits, wheel size, speed limits - many of the things not user-set table on an OE M600. It can also datalog a ton of things including gps position, altitude, power, watt-hours consumed, etc.
What the mobile app does not have right now is a simple way to adjust the ‘ramp’ or sensitivity directly. I believe this can be done via the full app, but have submitted as an enhancement request - I usually am in lvl 2 of 9 a majority of my riding time, and might slow down the initial power ramp time, but it’s not ‘needed’ as much as I’d like to do some fine-tuning. Power is there within very few degrees of pedal pressure, so was surprised to see claims of Hydra/Archon not kicking in for 1/3rd to 1/2 crank revolution, as I’d expect the torque sensors to be quite similar across the M600 and Ultra, so am sure it’s just a config setting for Archon vs any hw limitations.
I swapped bikes for a bit with my wife (Bosch), and other than power from a complete standstill (Ludi come on faster), once moving, the feel is very comparable. L2 of 9 in Trail profile is probably a little more power than Bosch eco mode.
(PS - if there is a valid Archon/Innotrace manual anywhere, or if anyone can just post the actual user-configurable options, I’d appreciate it..)
Neither the Archon nor Ludi seem to provide 1:1 direct settings vs the UART config settings and from what I’ve seen and read, I expect both to continue to evolve, hopefully in the direction of improved out-of-box configurations (although other than slightly toning down ramp-up from a standstill, I don’t have a huge list - feels very nice.), but also in which specific settings are made available for intuitive change by users. The full desktop app for VESC does allow more configuration, but also can smoke a motor in the wrong hands/wrong settings.
I’m sure some things not user-exposed are hard-coded within the firmware itself, but even if so, they could become exposed over time, or in the case of Ludi…source code is available.
M600 vs M620/Ultra
AHicks and others covered most. I think the motors came out at around the same time, even if Ultra complete bikes started coming out slightly later.
The M500(eu spec 250W nominal) and M600 share the same mounting, not sure on internals, while the Ultra is a fair amount heavier and bigger. Part of the weight and size is in the motor stator and windings, and the M620 can dissipate heat better than the M600 and as such, can run at higher sustained power output > 1kW for longer without going into thermal cutoff.
A way I like to look at it is this - anyone expecting to be heavy on the throttle or has a huge concern on top speed, just buy the Ultra. It was designed for cargo bikes but can sustain both higher output than the M600, and sustain it for longer.
Bafang pricing is, well - stupid, or distributors are taking advantage. M500, M600 and M620s all cost pretty much the same, which doesn’t do any of us any favors really…
Meanwhile, the only non-science-project or plug-and-play programmable options are UART Ultra while they last, Innotrace if outside the US (and Canada, I think?), WW who AFAIK wont sell the controller or controller/motor separately at the moment, or the LudiV2, also not purchaseable at the moment other than with a bike.
Note - there is little reason the LudiV2 couldn’t be sold for Ultras - possible a board layout change, but not insurmountable, and same applies to Archon/Innotrace for M600.
With the relatively non-existent price difference in motors, once a reliable, able-to-be-delivered-in-reasonable-time controller option happens for the Ultra, I’d probably choose whichever motor has better parts supply chain reliability. As mentioned, given a competent controller or just ability to set max amps, you can turn the Ultra into a 500W or 750W nominal motor if you’d like… Yes, it’s a few lbs heavier and probably overkill for anyone actually wanting to pedal/get a workout, and I’d never intentionally add significant weight to a bike/motorcycle/car, but - does the few lbs really matter for most?
I realized even on my BBHSD I’d be at low PAS levels and sometimes ride that fat pig (>80# with bat) unassisted for a bit), so personally I don’t really even ‘need’ the 1500-2kW ma output of the LudiV2 M600), but everyone’s situation is different.