Good to know!
1 Like
And here I though that the ENNOID is expensive 
3 Likes
yet only one of those is available, which must be why Trampa feels like they can get away with charging 200 quid
2 Likes
Tempting to try it…but I don’t even know what I’d put it in.
I mean… Don’t forget, the others were expensive too, and none of them had vesc integration
1 Like
I think once the official firmware releases full BMS support, all CAN style BMSs will work with the VESC. Ennoid made some progress on that recently too.
4 Likes
I wonder if they’ll put it on “sale” then just permanently sell at a reduced price once 5.03 is released and other smart BMS will be able to communicate over CAN/UART
1 Like
Actually £240 (200 +vat @20%)
3 Likes
Looks good. Price is a bit higher than what I was expecting, but I can understand that almost all IC they are using for this BMS are B.O. or very expensive at the moment.
20ohns resistor is quite aggressive and will generate a lot of heat/stress for little gain IMO. (considering trampa’s actual targeted market, althought some might disagree with this statement)
I wish they would finalize their BMS firmware soon, because staying compatible with a moving target on my side is quite difficult.
8 Likes
There are one or a two (not sure which) internal MOSFETs in the balancing current path that add 10Ω or 20Ω to that though. Even then I agree that the balancing current is pretty high for esk8 use. But it could be okay for larger packs IMO and perhaps that’s what they are targeting?
LOL…hoping their firmware is finalized soon. I would find your situation incredibly frustrating!
4 Likes
By design™
10 Likes
Dammit…I just realized the BMS’ I’m working on are all rectangular.™️
17 Likes
Oh god Moocher, don’t start this train chugging. There’s no end
11 Likes
That’s ok, I will live with it. Just that I had to adapt DieBieMS to new VESC BMS commands and not the opposite. Some commands on the VESC for setting the allowed cell upper and lower voltage values are still missing afaik… So, VESC-BMS seems to be feature incomplete at the moment for a complete VESC & BMS integration despite what is claimed. I might be wrong, but I spent quite some time looking at both VESC & VESC-BMS firmware code in order to adapt my BMS firmware to works with VESC over CAN bus. I did as much as I could to integrate both, but I can’t decide on the implementation of those features on the VESC firmware…
2 Likes
Pretty much all VESC accessory developers seem to manage without too much trouble (or at least it appears that way )
I suppose it serves as incentive to make your FW update procedure user friendly and well documented?
I couldn’t find dimensions. I suppose you could get a rough idea by scaling a known component.
Or maybe @Trampa could elaborate.
2 Likes
Napkin guess here but to me it looks like its about 25mm wide, by about 70 ish long, and somewhere around 8mm thick
@Boardnamics think I’m close?
1 Like
I’m going to toss in a guess of 35mm x 135mm x 10mm, based on the LTC6813 case size of about 10.2mm.
1 Like
That seems extremely optimistic… i’m gonna take a punt at about 160x45x15