MoTeC Global Forum

MoTeC is making available to dealers and M1 users Beta versions of our latest M1 Tune and GP Packages. These updates do not incur any additional cost, but the GP Packages are only available to existing GP Package users.

Customers can go to MoTeC Online to download the M1 Tune Beta version.

For access to the July 2015 Beta Packages and Licences, please email dispatch@motec.com.au with a request for access to the Beta, along with your ECU and Package details.

Dispatch will reply with the new Licence for that ECU as well as the latest Package for the requested ECU.

Migration
This update to the GP Packages includes a number of new and updated features, as can be seen in the migration documents. Hence there is a requirement for careful migration of configurations for existing GP users. Links to the migration documents are shown below; we recommend they are closely followed to fully understand the process.

http://www.motec.com.au/filedownload.ph ... docid=4851

http://www.motec.com.au/filedownload.ph ... docid=4852


Features
The new features are listed in the Migration documents

Availability
These Beta versions are available now.

The release documentation for Version 1.4.0.0021 Beta contains the following line:
"Feature #13435: Add information to distinguish extrapolating tables"

Can you detail what form this information takes? The tables that I have reviewed show no change when viewed in M1 Tune 01.03.03.0194 or the beta.

Thank you

hnatho wrote:The release documentation for Version 1.4.0.0021 Beta contains the following line:
"Feature #13435: Add information to distinguish extrapolating tables"

Can you detail what form this information takes? The tables that I have reviewed show no change when viewed in M1 Tune 01.03.03.0194 or the beta.

Thank you

The information regarding extrapolation is presented in the axis setup dialogue box and the help for the table. See a Sensor Translation table in the June 2015 GPR beta package for an example.

If there is no information regarding extrapolation presented for a table then the table is clamped to the end of the axis - this is the default behaviour from earlier versions.

Had a play, looks like another step forward, well done.


One stupid question - Can the the UDIG inputs be used as analogue inputs?

Thanks in advance.

denis bassom wrote:Can the the UDIG inputs be used as analogue inputs?

Yes, UDIG (and INJ_PH, IGN_LS, etc) can be used as analogue inputs but only for simple voltage measurements as they don't have the required resolution and accuracy for sensors. Precision measurements (ie sensors) are supported by AV, AT and KNOCK inputs.

Thanks

one thing I did notice is if you select udig 2 for crank sync then udig2 a and b are still listed as being available for other sensors. Just a bit inconsistent rather than a problem.

denis bassom wrote:one thing I did notice is if you select udig 2 for crank sync then udig2 a and b are still listed as being available for other sensors. Just a bit inconsistent rather than a problem.

Tune just lists potentially available resources, ie it excludes resources that are used. We don't have a mechanism to exclude resources that are not applicable such UDIG 2 A and B.

Does the July 2015 release need a new license?

Thanks

Yes, it does.

This can be organised through your dealer.

Thanks, have done so.

One observation....having to get new licences for every GP* version upgrade is creating a lot of extra work for you hard working dealer network.