MoTeC Global Forum

Hello MoTeC enthusiasts and professionals,

I'm looking for potential options for engine dyno recording + analysis solutions for a customer and therefore I'm curious if someone ever used i2+telemetry to feed live data into i2 for dyno purpose, or at least T2 users who know the workflow and can rate the potential of such setup?

My question is NOT related to controlling the load/brake of the dyno itself but instead mainly for recording/plotting/analysis live during the run and after the fact (live data of torque and power would be transmitted via CAN from engine dyno controller "YourDyno").

So I'm specifically interested in ease of use during situations of repeated dyno runs, plotting them live, saving run after run or having multiple runs within a live stream and extracting/overlaying multiple runs on top of each other. Is it a matter of setting some conditions which act like lap triggers, so to create multiple runs, which then can be compared like individual laps?

To give some background and goals/ideas:
Customer has a waterbrake engine dyno with a "YourDyno" controller. The controller (+related gui software) will do it's thing properly, but other than plotting the data and showing numeric values the graphical and analysis capabilities obviously are less powerful compared to a professional data analysis software.
With a big amount of CAN signals (from dyno, ecu, whatever expansion modules,...) and an array of hardwired sensors then for proper analysis something like i2+T2 came to mind, so to have all the data in one place. I imagine just logging and analysis of some runs after the fact would be a no brainer, but I'm specifically curious whether i2+T2 might work out well during daily use as the main analysis tool, run after run, so to "organize" the data in a quick and intuitive way?

The solution in mind might be a C185 +I/O +ProAnalysis +T2 +Advanced functions with live telemetry in a "hardwired" permanent install with whatever fits T2 most for a permanent setup (is use of LAN possible when using T2 or only serial output from C185 for that purpose).

Thanks!
Mike

In your proposed setup, the C185 serial telemetry output would be hardwires to a rs232 to usb connection (or direct to the serial port if the pc motherboard has one)

The input source in T2 is set to serial port - this is how we do telemetry bench testing. There are no other direct interface options available.

Your idea of beacons would work the best for quickly overlaying data. You would use an internally generated beacon for this.