• Welcome to MX Bikes Official Forum. Please login or sign up.
 
March 28, 2024, 11:59:15 AM

News:

MX Bikes beta18j available! :)


MaxTM - A telemetry tool for GPB, MXB, WRS and KRP

Started by HornetMaX, December 31, 2014, 01:46:21 PM

Previous topic - Next topic

HornetMaX

December 31, 2014, 01:46:21 PM Last Edit: August 18, 2023, 10:25:12 PM by HornetMaX
MaxTM is a telemetry tool for GPB, MXB, WRS and KRP: it allows to display graphs of the telemetry data exposed by GPB/MXB/WRS/KRP. It has two main components:
  • A GPB/MXB/WRS/KRP plugin: in charge to generate the telemetry data files.
  • A viewer application: in charge of displaying graphically the telemetry files saved by the plugin.




DOWNLOAD v2.7:  <<-- THIS if for GPB beta21, WRS beta14, KRP rel13 and MXB beta18

Love this stuff and you want to show that ? Have too much money at hand and don't knowe what to do with it ? Donations are welcome  8)
PM me when donations are done, so that I can keep a donors list HERE.



INSTALLATION
  • Download the archive from the link above and extract it somewhere. Inside the main folder you should have 4 extra folders: one for the plugin(s), one for the viewer and 2 folders with sample data.
  • Take the viewer folder (MaxTM_Viewer-vX.Y) and the 2 sample foders and put them somewhere (Desktop, Documents, wherever you have write rights). DON'T PUT THEM IN Program Files OR SIMILAR. The viewer is a portable app: it does not write anything in the registry, it requires no installation (in the Windows sense) and it won't ask you if you want to install a stupid toolbar.
  • Now run the viewer application (MaxTM_Viewer.exe and check it starts without issues. If it complains for missing dlls, you may need to install:
  • If you want to generate telemetry data from GPB/MXB/WRS/KRP you have to install the plugin: in the plugin folder (MaxTM_Plugin-vX.Y) you have 4 .dlo files (one each for GPB/MXB/WRS/KRP) and a folder named MaXTM_data. Just copy the appropriate .dlo and the MaXTM_data to the GPB/MXB/WRS/KRP plugins folder.
  • Restarting GPB/MXB/WRS/KRP and going to the track you should hear a heartbeat sound each time you start a run: this confirm that the telemetry logging is active.
  • You can also press 'Z' to see is if logging is currently ON or OFF, and CTRL+Z to toggle it ON/OFF. You can change the key in the .ini file of the plugin (MaxTM.ini, in the GPB/MXB/WRS/KRP data folder).
  • Telemetry log data will be saved (2 files per run) in folder MaxTM under GPB/MXB/WRS/KRP data directory (e.g. C:\Users\MaX\Documents\PiBoSo\GP Bikes).

IMPORTANT:
  • The telemetry file can be relatively big if you ride a lot. Remember to clean-up the MaxTM folder from time to time.
  • If you want to disable the plugin (for whichever reason), you simply rename it from .dlo to .dlo.off (or to .pizza) or edit the .ini file of the plugin (MaxTM.ini, in the GPB/MXB/WRS/KRP data folder) and set 'active' to false.

USAGE:
I'll briefly describe the main features here: there is no user manual yet (and maybe there will never be one), but the viewer is not too complicate.
  • The main areas of the main window have tooltips (i.e. little text explanations that appear when you leave the mouse still on them for a while): READ THEM.
  • The main areas of the main window have tooltips (i.e. little text explanations that appear when you leave the mouse still on them for a while): READ THEM (intentional repetition)
  • Seriously, read the tooltips: in particular the ones of the graphs and track map, as they explain how to interact with the graphs using the mouse. I could resume the thing here, but if I do it then you won't read the freakin' tooltips, so I won't do it  :P
  • On most areas a context menu is available: just right-click with the mouse.
  • The worst thing you could do with the viewer is delete some telemetry file: it's not a dangerous app, don't be afraid to try things around.
  • The general idea is:
    • You can open an arbitrary number of telemetry files at the same time. Each telemetry file will appear as a Run containing some Laps.
    • On the left you have the Runs/Laps as seen via the telemetry data, along with their lap times (as seen by the telemetry).
    • On the right (in the panel named Timings you have the same Runs and more or less the same Laps, with more or less the same lap times (as seen by GPB/MXB/WRS/KRP) and their split times.
    • Telemetry lap times come in two flavours: column "Lap Time" is based on GPB/MXB/WRS/KRP timing, column "Lap Time (w)" is based on an external timer which turns out to be more precise (I think it's some sort of bug, but I have no feedback on it from Piboso).
    • The telemetry lap times should more or less match the "official" lap times (the one in the Timings panel). Small errors are normal (up to 0.1-0.2 sec I'd say), larger ones are not.
    • The number of laps between the Runs/Laps panel and the Timings panel may not be identical: typically due to not completed laps, out of pits laps and so on. It's not too hard to see which lap in Runs/Laps corresponds to which lap in Timings.
    • In Runs/Laps you can select up to 4 laps (each one has a specific color): the 1st lap you you select will be the reference lap.
    • On the right you have (by default) one Graphs panel: here you can have the telemetry data plotted. You can have multiple graphs panels.
  • In each graphs panel, using the context menu (right-click), you can:
    • customize the number of graphs (as an N by M grid) and their appearance (axis labels, tick labels).
    • customize the each individual graph: delta plot (see later on), join/mark data points, show/position the legend etc.
    • customize what to plot on each graph on the X and Y axes (the variable on the X axis is the same for all the graphs in the panel)
    • Save the current layout of the graphs panel, so that you can reload it next time.
  • Delta graphs: a delta graph is simply a graph where instead of plotting (let's say) the speed against the position on the track (centerline) of the selected laps, you plot the difference in speed between the 1st selected lap (the reference lap) and the other selected laps. So if you have 4 selecte dlaps, on a normal plot you'll have 4 lines while on a delta plot you'll have 3 lines, each of them being the speed difference between selected lap 1 and selected laps 2, 3 and 4.
  • The viewer app comes with 2 themes: the default "bright" one (almost white background) and a darker one I find very handy at night (did I told you I average 4-5hrs of sleep per day ?).

I'll open another topic to gather your feedback on this: please try to keep this topic clean (just for new versions etc).

MaX.

HornetMaX

v1.10 out:

  • Updated for KRP beta12 (no changes for others).

MaX.

arnzzz

What do you use to make this Max? C++, C#, Java etc ?

HornetMaX

Quote from: arnzzz on January 05, 2015, 08:59:48 AM
What do you use to make this Max? C++, C#, Java etc ?
C++ with Qt (http://qt-project.org/).

Qt is a bit daunting when you start but after the initial struggle I do like it.
As said by others, it "gets in the way of C++" (it kind of extends the language) but other than this, I find it pretty good.

For the plots I use a great library (that extends Qt basic plot capabilities) named QCustomPlot (http://qcustomplot.com/).
I actually decided to use Qt because of the existence of QCustomPlot.

MaX.

HornetMaX

v1.11 out:

  • Updated for GPB beta7, WRS beta7b, MXB beta3, KRP beta14.
  • IMPORTANT: telemetry files saved with older versions of MaxTM are not supported. You won't be able to open them.

arnzzz

this looks great Max. Im very impressed. How long have you worked on this for?

HornetMaX

Quote from: arnzzz on February 10, 2016, 06:39:58 AM
this looks great Max. Im very impressed. How long have you worked on this for?
I didn't count, I just did it for fun. But it took a decent while: I had plenty of time when I did it (I was on a sabbatical leave).

I wasn't very effective when I started because it was the very 1st time I used Qt.
Not sure I'm very effective even right now: I've once been a developer (professionally I mean) but I moved to something else a long ago, so I'd say I'm kind of a "spare time developer" :)

HornetMaX

v1.12 out:

HornetMaX


Bj Slice

May 29, 2017, 08:48:09 AM #9 Last Edit: May 29, 2017, 08:50:04 AM by Bj Slice
Does this work with beta6? I tried this app but it didn't work. This is a great tool. I use telemetry in iracing to tune my setup and it worked great for me.
"Practice not until you get it right. But practice until you can never get it wrong, and make it a routine"


HornetMaX

Quote from: Bj Slice on May 29, 2017, 08:48:09 AM
Does this work with beta6? I tried this app but it didn't work. This is a great tool. I use telemetry in iracing to tune my setup and it worked great for me.
No it doesn't. I need to update it to the latest plugin interface.

HornetMaX

v1.16 (2017/06/19) out:

  • Updatetd for GPB beta11, MXB beta6, KRP beta16 and WRS beta11.
  • Fix a bug in timings panel (happening "only" for MXB, KRP and WRS).

HornetMaX

v1.17 (2018/01/23) out:

  • Updatetd for GPB beta13 (no changes for MXB, KRP and WRS).
  • TC, EB and AW signals from ECU are now logged.

mmtroop616


HornetMaX

Quote from: mmtroop616 on July 04, 2018, 04:06:48 PM
does this work with beta 8?

Not yet. I'll probably update it when the next GPB release is out too.