Metr Pro Updates

  • Use DieBieMS Tool and connect via BLE or
  • Disable CAN fwd in Metr app and run TCP bridge and use DieBieMS Tool to connect via TCP

Both ways you need to use DieBieMS Tool on your desktop

@Silverline no plans yet
@Murloc992 there should be some hint in the log file why the record stopped. Also, you are not “losing” rides, they just seem end too soon. I have an idea why. In the log file you sent me, you are

  1. Starting the record
  2. Changing mode
  3. Looks like then you just put your phone in the pocket and go

When on the Modes tab, there is no realtime data coming and the record stops after 60 secs. After you switch modes, you need to switch back to Realtime tab. I will think how to fix it, but for now don’t leave the app while on Modes tab

1 Like

Yup, this might be the case. Can it switch back to realtime automatically, please? For example when the phone gets locked. There’s no mode changes going on when it is locked for sure. Not sure if that’s detectable though. :slight_smile:

Even switching to realtime from anything after a lock sounds reasonable, especially when a record is ongoing. :slight_smile:

1 Like

@silverline, can´t you already see that in the real time data? I have two values displayed for current and temp. thought this are the different motors.
or you mean that it will also displayed later in the recording?

You see two split motor current values and graphs when you upload a record? I think they are combined atm.

that´s what i said. only in real time data you can see that indiviual motor

1 Like

Yeah, I understood that. SIlverline wants to see it in the graphs. I silently want too. It’s a good way to see if you have some friction in one side or something. Better to see it in the graphs, than to have bearings lock up or break the motors. :smiley:

Just wondering what functions people find most useful in using this over the vesc tool app? And this works with any vesc?

This idea is just great, thanks :slight_smile:

1 Like

what he said…

1 Like

I just updated the app, used my same settings and now my board is slow as crap… very little power. Was a raging beast mere moments ago. … the mosfet temp cutoffs look a little low 85/100, what should they be?

1 Like

A little low?? That’s like hot/blazing hot. Maybe your power got limited by a mode?

That °f not °C

Good to say from the start. :joy:

For example mine is:

85’C/185’F start
100’C/212’F cutoff

Maybe metr set metric values on this?

So the only FW working for me is 3.7.10 the other newer firmwares will not see my old metr module.
But its bad for me because I run FW 3.58 on my other metr pro board and this FW is not supported on the Version that I can use…

Any hints yet regarding the bluetooth issue ?
Thanks

probably there is an easy explanation for it, but I didn’t get how that could happen. I yesterday had different distances in the real time data and the recording

I was driving before that trip with an other board which has a metr modul as well, but even if to add up both distances it does not really fit to total distance displayed in the real time data.

Did you switch modes or settings during rides? If you are in that tab, the realtime data stops. I guess it’s being addressed atm.

1 Like

I didn´t switch, just switched the boards.
But even if, the real time data than should be lower than the recording. No?

Unsure, only @rpasichnyk will know.

1 Like

The distance in the record is zero when you start a new one. When you do, the distance should obviously be zero in every record that begins.

On the realtime screen the distance does not reset when you start records. It resets when you close the app. It should also reset when you switch boards, but maybe there is a bug, let me check :nerd_face:

Update: there is a bug with distance not resetting when switching boards, will be fixed soon :+1:

7 Likes

I noticed that the wh/mile in the real-time screen is very low. I have a unity and I think it might me displaying a per motor value rather than total. Wh/mile n the record log seems to be correct.