Update Metr Pro firmware again to v3.68
Ok i will try
It seems to work now. Had the app freeze when using modes but after i restarted the app it worked again
Just ordered a Metr Pro, canāt wait to add it to my build
I got mine today, canāt wait to put it on.
@rpasichnyk, is it going to be a lot of work to have more/configurable fields in the log? Say I want watts, or watthr/km. I can definitely open the log in Matlab or python and plot it myself, but would be nice to have it integrated into the existing setup.
Can we not use ackās firmware with this new update. No data here since the update?
I have the older modules in my boards.
TCP bridge seems to not work correctly after I updated to the latest version of the app and Metr.Pro firmware. Iām getting a TCP timeout error 30 seconds after I attempt to connect on Vesc Tool.
Can someone walk me through hooking up the Metr pro to the Unity and a DieBieMS. I will be running this setup and just want to make sure I understand how everything is going to be hooked together. Thanks guys sorry if this is a noob question.
@SeanHacker Yes you can! The fix for the older modules just arrived to Google Play v3.5.18, you will get it in a bit
@NullReference could not see your problem with my setup. Can you send logs to [email protected]?
Leave the diebiems CAN ID=10. For wirig check the diebiems thread, has been asked recently. Other than that default settings I think
Is it actually possible to export the recorded data? I havenāt found the option for that and I looked really hard.
Did you already upload to the Play Store? Havenāt got the update yet.
@bevilacqua used them for his masterās project. I just got my metr pro module. Havenāt had a chance to explore it.
@SeanHacker I did upload it but forget to press Release button
@janpom it is possible, using file manager and getting json app data from the phone, or by adding ?format=json
to the record url in the browser
Hey @rpasichnyk, I know you are really busy fixing issues after the lastest vesc firmware update, but was wondering if you could talk about how hard it easy is it going to be to make logs configurable, when you are a bit free. To add extra fields etc.
It is already possible to calculate watts or watts/km using the data present in the record. What you are probably after is to display it in the browser, right? I will look at it
Nice! I like the format. Very concise and comprehensible. I did quick parsing in Python. Hereās a dump of one of my logs with the array data restricted to 10 points (taken from somewhere in the middle of the log) in case anyone else is interested in what kind of info is available.
ah: 2.34
ahRegen: 0.06
altitude: [196.2, 196.2, 196.2, 196.4, 196.4, 196.4, 196.4, 196.4, 196.7, 196.7]
appver: 3.5.4
consumption: [6.6, 6.8, 7, 7, 7.4, 7.5, 7.6, 7.6, 6.5, 7.6]
current: [5.3, 6.23, 6.12, 5.99, 5.38, 5.5, 5.52, 5.71, 5.48, 5.57]
distance: 17648.38
duty: [66.6, 67.1, 67.6, 66.3, 67.5, 68.9, 69.9, 69.1, 67.8, 68.3]
elapsed: [618623, 618806, 619065, 619339, 619567, 619772, 619954, 620158, 620389, 620635]
elapsedAh: [0.29, 0.29, 0.29, 0.29, 0.29, 0.29, 0.29, 0.29, 0.29, 0.29]
elapsedAhRegen: [0.02, 0.02, 0.02, 0.02, 0.02, 0.02, 0.02, 0.02, 0.02, 0.02]
elapsedDistance: [2730.8, 2730.8, 2730.8, 2730.8, 2739.3, 2739.3, 2739.3, 2739.3, 2739.3, 2746.8]
elapsedWh: [11.6, 11.6, 11.6, 11.6, 11.6, 11.7, 11.7, 11.7, 11.7, 11.7]
elapsedWhRegen: [0.8, 0.8, 0.8, 0.8, 0.8, 0.8, 0.8, 0.8, 0.8, 0.8]
end: 1550854003844
escCount: 1
faultCode: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
faultsCount: 2
fw: 3.40 410
latitude: [49.17688, 49.17688, 49.17688, 49.17682, 49.17682, 49.17682, 49.17682, 49.17682, 49.17676, 49.17676]
longitude: [16.61679, 16.61679, 16.61679, 16.61687, 16.61687, 16.61687, 16.61687, 16.61687, 16.61692, 16.61692]
motorCurrent: [9.36, 10.81, 10.73, 10.6, 9.44, 9.42, 9.4, 9.75, 9.51, 9.59]
motorTemperature: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
os: iOS 11.4
rpm: [29597, 29920, 29824, 29460, 29806, 30508, 30944, 30693, 30296, 30427]
speed: [26.78, 26.78, 26.78, 30.67, 30.67, 30.67, 30.67, 30.67, 29.81, 29.81]
start: 1550850465825
temperature: [27.6, 27.6, 27.6, 27.6, 27.6, 27.6, 27.6, 27.6, 27.6, 27.6]
version: 10
voltage: [39.6, 39.7, 39.7, 39.8, 39.7, 39.8, 39.7, 39.8, 39.6, 39.6]
wh: 88.77
whRegen: 2.44
@rpasichnyk Whatās consumption
? The version
is the version of the json format?
@janpom consumption
is Wh per km value at the given moment. I do not display it yet on the web chart, but it is possible. Yes, version
is a version of record format. Version 1 only had a few things, version 10 (current) has a lot more. This is one of the first records made on 29 October 2016 https://metr.at/r/NcF4o and it still displays fine because I have versioning in place
@mishrasubhransu I added Power (Watts) to the chart, enjoy
Thanks Roman. Youāll probably hate me for this, but wh/km is probably a better indicator if we are trying to be efficient. The reason I was requesting for that to be added to the chart is because, I want to learn my sweet spot in riding efficiency.