Metr.at or Flipsky Bluetooth module?

Hi Everyone

I am trying to decide, which recording system I should go for - Metr.at or Flipsky nrf51_vesc bluetooth module. I have a Flipsky 200A VESC and would like to record and review the data mainly after the ride, but if possible also during riding (This is not a must).

As far as I can tell, Metr.at is the easiest way to get good solid GPS based info, with an overlay on Google Maps. This should also be possible with the VESC android app and the bluetooth module, but not as easy - am I wrong.

Other than the price difference, Metr (52 EUR) and Flipsky BT module (12 EUR), what is the cons and pros between these options?

Metr.at module is more expensive and has excellent plotting abilities. The proceeds do not go to the person who put an uncountable number of hours into the VESC firmware and hardware. The Flipsky module allows you to use the Vesc Tool android app for datalogging. This is less expensive and $2 for the app supports the guy who made your speed controller possible. I am working on a project now called vesc_tool_plotter. It will plot the log files from the Vesc Tool app similar to metr.at. The goal for vesc_tool_plotter is for efoil.builders to upload their log files to their account, select which build the log was from and make the data publicly accessible for all builders. Kind of like a central repository for efoil data.

1 Like

Many of us use metr.at
This module is really great. Works all the time and the App is superbe. Easy to customize, it records everything you need.
It is also possible to export the data online and view the result on your screen computer.
For me metr.At is a must if you want data recording.

I do agree it is the best solution currently (opinion formed from viewing logs, reading reviews but not owning the module). It is just such a shame that instead of using the protocol VESC to talk to the app. The module encodes the data before sending over BT to the app. The module uses the VESC library to talk to the VESC before inserting an unnecessary layer of proprietary encoding. The sole purpose of this encoding step is so metr.at can sell its own modules and people can’t use the regular bluetooth ones. Not in the spirit of open source if you ask me. The VESC hardware and software are open and free to implement as you see fit.

I Think I Will try the metr module, but will make to make a donation to Vedder for his exceptional work with the VESC. Thank you for your inputs!

Great choice. Metr.at did a great job with their plotting software and integrating it into efoil.builders forum for inline display is a suburb plus. I hope I didn’t make you feel bad going for a metr.at! Metr.at should be compensated for their great graphing software. If only metr.at could make their graphing software open source and accept compensation in the form of being able to use the open source VESC libraries. At the end of the day metr.at is running a business and not violating the open source licenses on the VESC. Perhaps going to school out in California has gotten to me.

No no, not at all. I fully understand your point. I had allready purchased the VESC tool for android, thought it would work with a cheap BLE HM-10 module, but it didn’t.

I think im gonna be very pleased with the metr functionality, including the ability to change settings in VESC.

1 Like