rusefi.com

Re: Compatibility with Virtual Dyno - ticket #266

2022-10-25T03:07:20

Thank you! Just updated https://github.com/rusefi/rusefi/issues/272

We also have a https://github.com/rusefi/rusefi/issues/1987 dream without resources unfortunately.

Statistics: Posted by AndreyB — Tue Oct 25, 2022 3:07 am

Re: Compatibility with Virtual Dyno - ticket #266

2022-10-24T06:34:40

I got it to work by following these steps:

Open the RE log file in Mega Log Viewer

Export log as a CSV

Open CSV and delete the first row containing "#" so the new first row should be all the variable names e.g. RPMTimeTrigger Error CounterVehicle Speed

Save CSV and open in Virtual Dyno

Statistics: Posted by OSprey42 — Mon Oct 24, 2022 6:34 am

Re: Compatibility with Virtual Dyno - ticket #266

2017-10-16T16:19:34

I'll volunteer to contact Brad Barnhill, the lead developer behind Virtual Dyno to add a config for rusefi. I guess for that we'd need to decide what signature to use in TS.

Did this ever come through? I'm glad we have a solution for now, however.

Statistics: Posted by NBytevenom — Mon Oct 16, 2017 4:19 pm

Re: Compatibility with Virtual Dyno - ticket #266

2016-02-23T14:20:14

I'll volunteer to contact Brad Barnhill, the lead developer behind Virtual Dyno to add a config for rusefi. I guess for that we'd need to decide what signature to use in TS.

Statistics: Posted by stefanst — Tue Feb 23, 2016 2:20 pm

Re: Compatibility with Virtual Dyno - ticket #266

2016-02-23T13:43:21

Suggestion- change to:

signature = "MS3 Format 0523.15 "

Unfortunately I see a problem with that: once "MS3" is mentioned in rusEfi files I will get people wondering "why did you guys take MS3 stuff and call it your own?"

Statistics: Posted by AndreyB — Tue Feb 23, 2016 1:43 pm

Re: Compatibility with Virtual Dyno - ticket #266

2016-02-22T20:32:11

On the other hand, Virtual Dyno has a multitude of different log file definitions it's already using. So rather than using mimicry to pretend to be a different device, maybe we can get the developers of VD to include a specific rusefi log type. This would of course require the signature to be something more specific.
Suggestion: "rusefi x.xx"

Statistics: Posted by stefanst — Mon Feb 22, 2016 8:32 pm

Re: Compatibility with Virtual Dyno - ticket #266

2016-02-22T20:21:51

It certainly looks related. The version reporting in TS seems to come from line9 in file "Tunerstudio/rusefi.ini"

signature = "MShift v0.01"

Suggestion- change to:

signature = "MS3 Format 0523.15 "

Not sure why my MS3 has the at the end.

Statistics: Posted by stefanst — Mon Feb 22, 2016 8:21 pm

Re: Compatibility with Virtual Dyno - ticket #266

2016-02-22T16:00:40

Looks like this is really close to https://sourceforge.net/p/rusefi/tickets/265/ also and both should be pretty easy changes.

Statistics: Posted by AndreyB — Mon Feb 22, 2016 4:00 pm

Compatibility with Virtual Dyno - ticket #266

2016-02-21T04:44:51

Many users of Megasquirt and other efi systems use the virtual dyno software ( http://www.virtualdyno.net/ ) to obtain fairly good estiamtes of torque and horsepower. Virtual Dyno is a great tool for street tuning in addition to professional dyno tuning. It essentially looks at the rate of increase in rpm from an ECU log. The user adds in car specific parameters and from there VD estimates torque and hp.
Unfortunately the logs generated bu RUSEFI are currently not compatible with VD.
Suggestions: contact the people behind VD in order to make them implement the definition for RUSEFI logs, or change RUSEFI to use the same log format as other, already implemented, ECU software.

Required data columns for VD are: time, TPS and RPM.

It appears that simply changing the first line of the log from the current "MShift v0.01: Bowling & Grippo MS1 Base Code MShift v0.01" to "MS3 Format 0523.15 : MS3 1.4.0 release 20150709 19:51BST (c) JSM/KC ********" will have the desired effect.

Statistics: Posted by stefanst — Sun Feb 21, 2016 4:44 am