In the video you can see that he’s drawing 30A before the notification pops up. So I think the voltage sag is expected; he should probably limit his battery current to 20A per side.
Strange that his consumption is so high on the bench though, I wonder if something is causing drag
The bench part is confusing me too. I’ll check it out more today just to be safe.
tight belt is usually main cause
It was on two ebike batteries of different brands. I bypassed the BMS on them. They are definitely not built for high amps.
The nickel tabs did feel pretty thin. I’ve never built a pack myself before but I thought pictures of packs here had a lot thicker tabs.
The rest of the pack looked decent to my eye.
The 2x 14awg is great, but the nickel looks like 4x0.15x7mm? So probably ~60A there but hard to know without measuring
I run Linux VESCTool on my Chromebook, it doesn’t have USB access though so I use it with BT and TCP
Edit: using crouton, not crostini
I appreciate the feedback!
Maybe running as root / adding your user to the correct permission groups would allow it to?
Also, can’t chromebooks run android apps? Maybe the mobile vesc tool app works
So would Spintend be considered the top pick in terms of ESC?
For higher voltages, yes. 14s is considered HV, so you need something like a ubox.
the mobile version works fine, but the mobile version ONLY lets you connect over BT and not USB/TCP or anything else, plus I just hate the mobile UI and prefer desktop VT.
I was so pleasantly surprised to find the full apk runs the desktop UI on my chromebook, but still isn’t able to access USB
Add: I have also never, even after 3.01 ever been able to make metr work as a BT for the VT app
Ensure your phone is connected to the same wifi router as your computer.
If your phone is on the mobile network, it won’t work.
Yeah everything is on my home WiFi, tried restarting BT service on both devices in various orders, tried the classic restarts and reboots and all.
Metr just doesn’t connect to VT directly no matter what. The only way I’ve found is via TCP
Oh, I was referring to using TCP. 
Has anyone used flipsky motors with 18s? I’m thinking to make the switch, but the motors are officially rated to 12s.
metr’s TCP works fine for me as a bridge to the VESC tool.
The android VESC tool also connects fine to the metr dongle, but the metr app has to be force closed for it to work.
I’ve tried it with a force-closed metr app and I still can’t get it to connect, what are you doing differently?
For me TCP works fine and is the only way I can connect currently, have you been able to successfully upload new FW over TCP through the metr? FW is the only limitation I’ve found.
Were you the one who said they removed the external antenna on the metr without soldering the jumper? Maybe that’s the issue…
that was an entirely different metr device, I did that on the metr.pro, I’m currently using a metr.unity with the pins replaced with a UART cable (4 connections)
sigh… I have a test ride to get to today, if another unrelated issue turns out to be a HW connection issue I’ll have to open up the enclosure anyway, might as well get at the USB while I’m in there.
I truly yearn for the day when I can do all config and settings functions wirelessly and without hacky workarounds like using my phone for TCP to BT ad-hoc connecting
