@lidocaineus If you want to try to only replace the screen, I recommend that you make sure you can still BLE-connect to the Megan to make sure it’s alive.
1 Like
I noticed that in logs battery voltage isn’t split out for each ESC like currents, temperatures, duty cycle etc.
On Ankle Wreacher I have 4 VESCs wired individually, and was/am curious if I’m getting voltage drop across the wires between my G300s.
- Would it be possible to record individual voltages from each ESC?
- My Megan is connected over CAN. It is an average of all 4 reported voltages, or from a single vesc? Which one? (lowest CAN id or something?)
2 Likes
I have found that vesc voltage readings are not completely accurate compared to the actual battery voltage and it makes me wonder if they would be accurate enough at all to calculate voltage drop?
I found they have like a ±0.5V gain error and I have voltage drops of easily 10V+ on the battery so it’s definitely good enough to record overall sag, but most of sag is in the batteries and internal connections, not in the output cables so I don’t think measuring multiple vescs really help anything here.
That said the voltage data is in the CAN packets if anyone wants to make a logger that records it.
2 Likes
There’re also settings in Metr to smooth out battery voltage readings and margin. Not sure if that matters or not.
Megan does actually log the voltage for all ESCs. However, when we process the uploaded file, we only keep the voltage data from the first ESC – the first would be the one with the lowest CAN ID, yes. The reason for this is that for most people, all ESCs are connected to the same battery and thus the voltage is the same for all.
Your particular setup is special and I understand that for you specifically it would make sense to retain all voltage values.
This is a tough call to make. It’s not a difficult update to make if we just keep all voltages for everyone. But then we need to store all those redundant values that almost nobody will ever use. Or we can create a config option but then it’s not a simple update anymore.
Let me discuss this with Roman. No promises at this point.
2 Likes
So how did that turn out anyway? Is there a integration with race chrono?
Unfortunately not. This was too low prio.
1 Like
Id record voltages with a different dedicated device. Vesc suuuucks at tracking voltage
Thanks for the reply
Live long an prosper 
So @janpom, I looked into this more with TITS, where I can log stuff.
Here’s a chart of the voltage from a couple minutes of racing.
@Dinnye is totally right. My 4x G300s read up to 1.1v different at rest.
Subtracting out this static offset, all voltages remain within 0.1v of eachother, even when pulling 100’s of battery amps. Considering this is the resolution of the data in the CAN packet, literally couldn’t be closer.
TLDR; there’s no appreciable difference in the voltage at the 4 vescs
Pending an even weirder setup then mine, I now think individual voltage logging is entirely unnecessary 
would likely only cause confusion to users (from the static offsets). Thanks for humoring me 
4 Likes
I wonder if it is hardware dependent. Like my mp2 escs have the most reliable motor detection values and my flipsky the least reliable. For motor detection battery voltage plays a role, so i guess mp2 is more accurate
My m6d hobby charges have a (hidden) calibration menu, and they weren’t all calibrated the same when I got 'em. i make a large assumption from that that anything else measuring voltage needs calibrating, and can therefore vary device to device.
@janpom @rpasichnyk
I’m missing the open menu icon at the bottom left of the screen. I can still access it if I tap all the way near the bottom. But when the menu opens I’m missing the setting tab, I could still access it if I tap all the way near the bottom. I’ve reinstalled Metr app and updated the firmware.
1 Like
Hello, I’m using a Samsung Galaxy S25 Ultra (SM-S938N). My Android version is 16 One UI version 8.0. The metr app seemed to be working fine until last week, but when I launched it today, it just shows a white background and isn’t responding. Do I need to wait for an app update? Voyage Connect is working fine.
1 Like
Just had this issue last week. Reinstalled the app made it worked again for me but I lost the menu icon at the bottom left of the screen, the interface still seems to be there cause I can still open the settings menu. It seems be to be doing some weird stuff.
1 Like
Sorry about that, I accidentally released an update that targets new Android SDK 35 and this issue is not easy to fix. The old releases did not have this problem but I can’t upload any of the older releases anymore, because those were targeting SDK 34 and Google does not allow that for new releases 
Please use this APK as temporary workaround Sign in to your account
4 Likes
What’s the difference between Metr and Voyage Connect app?
Voyage Connect
- Pros
- Clean UI
- Easy to use
- Good Voyage Cloud integration
- Cons
- Doesn’t support Metr Pro devices
- Can’t be used for changing VESC settings
2 Likes
FYI for anyone dealing with tariff issues, a Minnie will fall under the US Harmonized Tariff Schedule heading of 8524.31.00, suffix 25 for a 32-bit microcontroller (specifically an ESP32-S3). This is 100% tariff free (see column 1, column 2 is if you’re importing it from a very few number of countries you would never import from, like North Korea.)
Section 8542.39.00 would also include the GPS and probably WiFi aspects, though I doubt it’ll come to that (this is also tariff free).
If you import a Megan, that would also include the display, which would fall under 8524.11.10 (actually 8524.91.10 – 8524.11.10 excludes a hardware driver for the display, but neither heading has a fee, and I doubt someone looking at the unit will be able to assess the difference). This is ALSO tariff free:
@janpom Might want to either somehow figure out how to include this in your export documents to US customers, or let buyers be aware of the 10 digit heading numbers, which people will need to dispute their assessed tariffs. As a perfect example, my Minnie arrived with a $200 tariff because it was classified as basically a block of aluminum from Russia (wtf?) and the moron-in-chief has slapped a 200% tariff on that partciular line item. They also slapped a 4% sports equipment part tariff, but at this point I’ll pay the $4.24 if the $212 gets erased. Check it out:
That was under tariff item 9903.85.68, and quoting from the schedule:
Derivative aluminum articles that are products of Russia, or where any amount of primary aluminum used in the manufacture of the derivative articles is smelted in Russia, or where the derivative aluminum articles are cast in Russia, when such derivative articles are provided for in the headings or subheadings enumerated in note 19(a)(iii) to this subchapter, or notes 19(i), 19(j) or 19(k) to this subchapter, as applicable per the date of entry for consumption or withdrawal from warehouse for consumption, except any exclusions that may be determined and announced by the Department of Commerce
The schedule is available here:https://hts.usitc.gov You can download each individual section (warning, it’s gigantic - 99 chapters), but there is a rudimentary search engine that can help you narrow it down.
So yeah. If anyone gets slapped with charges from UPS, FedEx, DHL, USPS, or whatever, throw those 10 digit headings this in their face.
10 Likes