MoTeC M1 User Manual
Printed documents are not controlled
While every effort has been taken to ensure correctness, MoTeC, its employees, contractors and
authorised representatives and agents take no responsibility, make no express or implied guarantees,
representations or warranties to any third party in relation to consequences arising from any inaccuracies
or omissions in this document.
This is a proprietary document and the property of MoTeC Pty. Ltd. All rights are reserved. No part of this
publication may be reproduced in any retrieval system, or transmitted in any form or by any means,
whether electronic, graphic, mechanical, photocopy, recorded or otherwise, without the prior express
written permission of MoTeC.
MoTeC reserves the right to make changes to this document without notice.
Copyright 2012
Published 1 June 2012
CONTENTS
User Manual
CONTENTS
1INTRODUCTION ................................................................................................................................... 5
2SYSTEM REQUIREMENTS .................................................................................................................. 7
3INSTALLING THE M1 TUNE APPLICATION ....................................................................................... 8
3.1CHECKING AND INSTALLING THE LATEST VERSION ............................................................... 8
4CONNECTING THE M1 ECU TO THE PC ............................................................................................ 9
4.1PIN-OUT INFORMATION FOR ECU COMMUNICATIONS ........................................................... 9
4.2ESTABLISHING ECU COMMUNICATIONS ................................................................................ 10
4.2.1
Resolving undiscovered ECU problems .................................................................... 10
5STARTING M1 TUNE ......................................................................................................................... 12
6OVERVIEW OF PACKAGES AND LAYOUTS .................................................................................... 13
6.1PACKAGE CONTENTS ................................................................................................................ 13
6.2LAYOUTS .................................................................................................................................... 14
6.2.1
Workspace ................................................................................................................... 14
6.2.2
Workbooks .................................................................................................................. 14
6.2.3
Worksheets ................................................................................................................. 15
6.2.4
Default Package Layout .............................................................................................. 15
7OPENING OFFLINE PACKAGES ........................................................................................................ 17
7.1ABOUT PACKAGE DETAILS ....................................................................................................... 18
7.2ABOUT THE PACKAGE FILTERING OPTIONS ........................................................................... 18
7.3ABOUT THE PACKAGE HISTORY .............................................................................................. 20
8COPYING, MOVING AND DELETING PACKAGES ........................................................................... 21
8.1ARCHIVE FILES ........................................................................................................................... 21
8.2EXPORTING PACKAGES ............................................................................................................ 21
8.3IMPORTING PACKAGES ............................................................................................................. 22
8.4DELETING PACKAGES ............................................................................................................... 22
9CREATING WORKBOOKS .................................................................................................................. 23
10WORKSHEET COMPONENTS ........................................................................................................... 24
10.1ACCESSING COMPONENT PROPERTIES ................................................................................. 25
10.2CALIBRATE COMPONENT ......................................................................................................... 26
10.2.1Calibrate List ............................................................................................................... 27
10.2.2Calibrate Component Properties ............................................................................... 28
10.2.3Changing Calibrate Display Options .......................................................................... 29
10.2.4About Calibrate Tables ............................................................................................... 31
10.2.5Table Axis .................................................................................................................... 31
10.3Table Interpolation ...................................................................................................................... 33
10.3.1Applying Interpolation ................................................................................................ 34
10.4Marking Sites as Tuned .............................................................................................................. 35
Printed documents are not controlled Page 2
User Manual
CONTENTS
10.5Unmarking Sites as Tuned ......................................................................................................... 35
10.6Entering Table Values ................................................................................................................. 36
10.7Importing and Exporting Tables ................................................................................................ 37
10.7.1Copying and Pasting Table Data ................................................................................ 37
10.8TABLE TARGET COMPONENT .................................................................................................. 38
10.9CHANNEL LIST COMPONENT ................................................................................................... 38
10.10TIME GRAPH COMPONENT ............................................................................................... 39
10.11SCATTER PLOT COMPONENT ........................................................................................... 40
10.12HISTOGRAM COMPONENT ............................................................................................... 41
10.13COLOUR GRAPH COMPONENT ......................................................................................... 42
10.14NOTES COMPONENT ......................................................................................................... 42
10.15GAUGES COMPONENT ...................................................................................................... 43
11USING M1 TUNE ................................................................................................................................ 44
11.1WHAT TYPE OF WORKSHEET TO USE ..................................................................................... 44
11.2USING SUPPLIED WORKSHEETS .............................................................................................. 45
11.2.1Initial Configuration Workbook .................................................................................. 45
11.2.2Setup Workbook ......................................................................................................... 45
11.2.3Tune Workbook ........................................................................................................... 45
11.3MANAGING DATA (CHANNEL) PROPERTIES ........................................................................... 46
11.3.1Accessing Data Properties ......................................................................................... 46
11.3.2Editing Channel Properties ........................................................................................ 47
11.3.3Setting Channel Display Limits .................................................................................. 48
11.4LIVE DATA CHANGES ................................................................................................................ 49
11.5SAVING CHANGES TO ECU DATA ............................................................................................ 49
11.6LIVE DATA CONTROL ................................................................................................................ 50
11.7Q CALIBRATE FUNCTIONS ........................................................................................................ 51
11.7.1Quick Lambda Function ............................................................................................. 52
11.7.2Dyno Tuning with M1 Tune ........................................................................................ 52
11.8W AND L FUEL TUNING ............................................................................................................. 53
11.9LAMBDA WAS ............................................................................................................................ 54
11.10VIEWING LIVE PIN VOLTAGE VALUES .............................................................................. 54
11.11VIEWING THE ECU PIN CONFIGURATION ........................................................................ 56
11.12ERROR MANAGEMENT AND STATUS LIST ..................................................................... 57
11.13INPUT VALIDATION AND INVALID ITEMS ........................................................................ 59
11.14MIGRATING DATA .............................................................................................................. 60
11.14.1Auto Migration ............................................................................................................ 60
12LOGGING ............................................................................................................................................ 62
12.1LOGGING FEATURES ................................................................................................................. 63
12.2LOGGING CONFIGURATION ...................................................................................................... 63
Printed documents are not controlled Page 3
User Manual
CONTENTS
13SECURITY ........................................................................................................................................... 64
13.1SECURITY LEVELS ...................................................................................................................... 64
13.1.1Advanced .................................................................................................................... 65
14HELP .................................................................................................................................................... 66
15GLOSSARY ......................................................................................................................................... 67
16KEYBOARD SHORTCUTS .................................................................................................................. 69
16.1M1 TUNE - GENERAL KEYBOARD SHORTCUTS ...................................................................... 70
16.2COMPONENTS - COMMON KEYBOARD SHORTCUTS ............................................................ 71
16.3TABLE COMPONENT - KEYBOARD SHORTCUTS .................................................................... 72
16.4PARAMETER LIST COMPONENT - KEYBOARD SHORTCUTS ................................................. 74
16.5TIME GRAPH COMPONENT - KEYBOARD SHORTCUTS ......................................................... 75
Printed documents are not controlled Page 4
User Manual
INTRODUCTION
1 INTRODUCTION
With over 25 years of automotive knowledge, MoTeC has developed its next generation of ECUs
with modern vehicles and controlled category racing at its core. Advances in technology have
increased the demands on a vehicle's components, especially the ECU. This demand has
reached a point where managing the intricate details of each installation become vital in
providing the ultimate in performance.
The M1 series was conceived to provide highly optimised targeted firmware for each unique
installation. M1 is a platform where operational efficiency, advanced features and flexibility are
its primary objectives. At its core, M1 provides the ability to develop a suite of flexible and
tailored solutions (packages), making it ideal for any application (however complex) and
category management.
This new approach to engine management systems introduces new concepts, terminology and
workflows - though much of this will be familiar to experienced Engine tuners. The M1 Tune
software is the link between an M1 Packages and an M1 ECU.
Some basic M1 concepts & terminology will help you get started:
• An M1 ECU is configured using a "Package"
• An M1 Package is a collection of data for M1 firmware that primarily consists of:
− A copy of the appropriate M1 firmware and help text
− Calibration (tuning) data for the version of firmware
− Data logging configuration
− Workbooks (screen layouts for M1 Tune).
• Each M1 Package is targeted to a specific M1 ECU model (M130, M150 etc.)
• Each M1 Package includes help specific to its intended application
• Packages can be upgraded to new versions of the firmware as they become available
• M1 Tune is generic and can be used with any M1 Package or M1 ECU model
M1 Tune has the same look and feel as MoTeC's i2 analysis software and is used for the
configuration, analysis and calibration of M1 firmware. The application allows creation of
customizable screen layouts that make engine calibration easier and faster. The ability to add
and configure individual components allows Worksheets to be customised for each application.
Printed documents are not controlled Page 5
User Manual
Example Worksheet window showing a number of components
INTRODUCTION
Printed documents are not controlled Page 6
User Manual
SYSTEM REQUIREMENTS
2 SYSTEM REQUIREMENTS
The system requirements for effective use of the M1 Tune application are listed here.
Operating system: Windows XP, Vista, Win7 (32 and 64 bit)
Minimum screen resolution: 1024 x 768
Recommended screen resolution: 1600 x 1200 or greater
The higher the resolution the greater the screen layout
options
Communications port: Ethernet port
Communication protocol: IPV6
Printed documents are not controlled Page 7
User Manual
INSTALLING THE M1 TUNE APPLICATION
3 INSTALLING THE M1 TUNE APPLICATION
Important: If during installation, you are prompted to allow the M1 software to make changes
to your PC, always allow; otherwise PC communications will not work.
The M1 Tune software is available as a download from the MoTeC website at
http://www.motec.com.au/software/latestreleases/
To install the software, the user must have a high enough level of access for the installation
software to be able to make the appropriate updates to the PC. This may require the software to
be installed by an administrator.
Once the software is installed, the M1 Tune icon is available from the desktop. Use this icon to
start the M1 Tune software.
3.1 CHECKING AND INSTALLING THE LATEST VERSION
M1 Tune is constantly evolving. It is recommended to keep the software up-to-date. Check and
update your version as follows.
1. Select Help »About and take note the version you are using.
2. Go to http://www.motec.com.au/software/latestreleases/
and check the latest release
version.
3. If a newer version is available, download and install the new version.
Printed documents are not controlled Page 8
User Manual
CONNECTING THE M1 ECU TO THE PC
4 CONNECTING THE M1 ECU TO THE PC
Important: If, during installation or application start-up, you are prompted to allow the M1
software to make changes to your PC, always allow; otherwise PC
communications will not work.
The MoTeC M1 ECU uses an Ethernet connection for communication between the ECU and M1
Tune. This ECU to PC connection uses a standard Ethernet cable, wiring and protocols.
When producing M1 wiring, all Ethernet communications cables must comply with Category 5
cable specifications. This includes wiring used to connect to the M1 ECU connector. MoTeC
have panel mount category 5 Ethernet cables available that are suitable for this application.
Note: It is recommended that Ethernet cables are wired as crossover from the ECU to
the loom side socket. By doing this, a standard (non crossover) Ethernet cable can
then be used for all communications between the ECU and the PC.
4.1 PIN-OUT INFORMATION FOR ECU COMMUNICATIONS
All M1 ECU to PC communications take place using the standard IPV6
communications protocol via an Ethernet cable.
The Ethernet connector pin-out is shown in the following table.
Pin Function
1 Ethernet RX +
2 Ethernet RX -
3 Ethernet TX +
6 Ethernet TX -
Printed documents are not controlled Page 9
User Manual
CONNECTING THE M1 ECU TO THE PC
4.2 ESTABLISHING ECU COMMUNICATIONS
The IPV6 protocol used by M1 Tune is the same method that is used in some internet
communications. Accordingly, some anti-virus and firewall applications will treat M1 PC
communications in the same way as other internet traffic. In most instances, this will have no
effect, but some anti-virus applications may block the M1 to PC communication.
To communicate from the PC to the ECU:
1. Power up the ECU.
2. Connect the Ethernet cable to the ECU and the PC.
3. Start M1 Tune. See STARTING M1 TUNE
.
►The connected ECU should display in the Quick Launch fly-out or the ECU Select window.
Example ECU Select window
Note: If M1 Tune does not discover the ECU, see Resolving undiscovered ECU
problems.
4. Select the required ECU from the list of available ECUs.
4.2.1 Resolving undiscovered ECU problems
When the ECU starts communicating, you will see it appear automatically in the list of connected
ECUs on the Quick Launch fly-out or the ECU Select window.
If your ECU does not appear in the list, follow the steps below to resolve the cause of the
communication problem.
Printed documents are not controlled Page 10
User Manual
CONNECTING THE M1 ECU TO THE PC
1. Ethernet ports normally include LED indicator lights. Check if they are lit (they normally
flicker, indicating data traffic on the cable) when the ECU is plugged in and powered ON. On
some PCs and notebooks, rather than individual LEDs, the Ethernet connector is lit at the PC
end.
Example Ethernet port lights on a PC
► If the ECU is powered ON and they stay OFF, it most likely indicates an Ethernet wiring
issue.
2. Where Ethernet wiring is confirmed as correct and there is still no communication:
a) Temporarily disable, turn off, or uninstall any anti-virus applications.
b) Close M1 Tune and ensure that the MoTeC Device Discovery service is also stopped. To
check if MoTeC Device Discovery is running, display the active services as shown in the
following image. If the MoTeC Device Discovery icon is shown (as circled below),
right-click on it and select Exit.
c) Restart M1 Tune and attempt to establish communications with the ECU.
Note: If turning off or uninstalling your anti-virus or firewall fixes the problem, then
your anti-virus or firewall application must be configured to allow the MoTeC
ECU to communicate normally.
If you have removed all anti-virus and firewall applications, and there is still no PC
communication with the ECU, continue with the following steps.
3. Ensure that the IPV6 communications protocol is installed on the PC (this is only an issue
with some Windows XP software).
a) Once any communication protocol issues are corrected, restart M1 Tune and attempt to
establish communications with the ECU, see ESTABLISHING ECU COMMUNICATIONS
.
4. If all the above are addressed and there is still no communication, contact MoTeC support –
http://www.motec.com.au/support/technicalsupportAU/
Printed documents are not controlled Page 11
User Manual
STARTING M1 TUNE
5 STARTING M1 TUNE
Important: If, during start-up, you are prompted to allow the M1 software to make changes to
your PC, always allow; otherwise PC communications will not work.
When the software is started, the Quick Launch window will fly out from the left hand side.
From Quick Launch you can connect to an ECU, or open a Package offline. The Quick Launch
images below provide examples “with” and “without” ECUs available for connection.
This example indicates that there are available
online ECUs for connection, as well as a
number of recent Packages that are available
to be opened offline.
This example indicates that there are no ECUs
that M1 Tune is able to connect to, but there
are a number of recent Package that are
available to be opened offline.
Other options available from Quick Launch provide the ability to retrieve logged data (an M1
ECU needs to be connected for this option to work), browse available ECUs, browse offline
Packages, or help on M1 Tune.
Printed documents are not controlled Page 12
User Manual
OVERVIEW OF PACKAGES AND LAYOUTS
6 OVERVIEW OF PACKAGES AND LAYOUTS
Within the M1 environment, a Package is the name used to describe the complete set of data for
an application.
Layouts refer to how data is laid and displayed in the M1 Tune graphical user interface.
Note: An M1 ECU can contain only one Package.
If a new Package is sent to the ECU, it completely replaces all content that might have been part
of a previous Package.
A Package on an ECU connected to M1 Tune can be worked on directly (online). Packages
stored on the PC are known as Offline Packages.
6.1 PACKAGE CONTENTS
A Package contains the following:
• System Firmware
• Tune Data (similar to an M800 Configuration)
• Security information
• A layout, that is, a Workspace containing base Workbooks and Worksheets, see LAYOUTS
Each M1 Tune Package contains three objects that are used for controlling the behaviour of
the ECU; they are Channels, Parameters and Tables.
Object Package Segment Definition
A Channel is a system variable which is updated in the ECU
Channels Firmware
firmware upon execution. Channels cannot be modified by
the user. An example of a channel is a sensor value, such
as throttle position.
A defined value which may be altered by the user in M1
Tune. These are the values that the end user modifies to
setup things such as re/sync mode, gear ratios, RPM limit
Etc.
Parameters
Firmware (for
definition) Tune
Data (for value)
.
Tables are a basic component of many control strategies
such as fuel and ignition delivery, and gearbox control. The
table is made up of a number of pre-configured axis types.
From within M1 Tune these axes can be turned on and off,
the axis sites changed, and the contents of tables modified.
This is one of the main ways to configure the M1 ECU. The
Tables
Firmware (for
definition) Tune
Data (for value)
number of axes and the number of set points are defined in
build, as are the input components and output units.
Printed documents are not controlled Page 13
User Manual
OVERVIEW OF PACKAGES AND LAYOUTS
6.2 LAYOUTS
A Package layout consists of:
• A Workspace
• Workbook(s)
• Worksheets
• Worksheet components
Using a book analogy a Workspace is the library, Workbooks are the book and Worksheets are
pages in the book. Worksheet components are the contents of a page.
6.2.1 Workspace
A Workspace is the name given to the entire collection of an M1 Tune layout, and is simply a file
that contains the layout elements defined for a particular Workspace.
Note: A Package can contain only one Workspace, see Default Package Layout. The
Workspace (layout) provided as part of the Package cannot be changed. However,
the data in the Package does not have to be displayed within the provided
Workspace. Any number of Workspaces can be created in M1 Tune and saved to
the PC. The Package data can be displayed in any Workspace selected by the user.
User created Workspaces are populated with user configured and customised Workbooks,
Worksheets and Worksheet components such as graphs, gauges, channel reports and alike.
Commonly, this customisation is made to suit a particular application.
Workspaces can be created, modified, exported and emailed from File »Workspaces
Example of the need for a different Workspace
A Package was created to work as a gearbox controller only, and not an engine management system. In
this instance the Workspace containing the Workbooks, Worksheets and settings would only show the
items to suit monitoring, setting up and calibrating a gearbox.
When that same PC was used with the M1 ECU as an engine management system, the workbook layout,
the worksheets, gauges and settings would need to be completely different. By creating a different
Workspace, work on each of these two applications is easier.
6.2.2 Workbooks
Once a user created Workspace is available, it is possible to create new Workbooks. Workbooks
can be used to separate different functions. An example of this would be to create a book called
"Fuel", one called "Ignition", one called "Dyno tuning" and another called "Traction Control". Any
number of these Workbooks can be created.
Note: Keeping functional areas separate is the recommended method for using M1
Tune. This allows easy identification of a functional area when work in that area of
the Package is needed.
Printed documents are not controlled Page 14
User Manual
OVERVIEW OF PACKAGES AND LAYOUTS
6.2.3 Worksheets
A Worksheet can be considered as a page of the Workbook. To realise the benefits of this
relationship, all Worksheets should be tightly related to the name of the Workbook.
For example, a Workbook called Fuel could have Worksheets related to fuel injector setup, fuel
pump control, fuel used calibration, fuel transient setup, fuel tuning, fuel pressure control, Etc. In
an ignition Workbook, appropriate Worksheets could relate to dwell, ignition timing, ignition
compensations, ignition cut, individual cylinder ignition compensations, Etc.
Example of Workbooks and Worksheets laid out in a structured fashion
6.2.4 Default Package Layout
A default layout is specifically designed to make using the Package as easy as possible.
When a Package is created, the developer of the Package has the option to create a default
layout. Once the layout is created, the whole Package can be saved so that this default layout is
immediately available in M1 Tune.
Printed documents are not controlled Page 15
User Manual
OVERVIEW OF PACKAGES AND LAYOUTS
Default layouts are distinguished from user created and customised layouts by the green
Worksheet tabs and window surround.
Example of default layouts
These default Worksheets are fixed in their layout and location and cannot be modified by the
end user.
In M1 Tune, the user can use the default layout provided with the Package or configure their own
layouts.
Printed documents are not controlled Page 16
User Manual
OPENING OFFLINE PACKAGES
7 OPENING OFFLINE PACKAGES
The Open Package window provides information and access to package details, filtering and
history. Packages saved on the PC can be opened as follows:
1. Select File »Open Package , or select Browse Pages from the Quick Launch fly-out.
► The Open Package window displays.
Example Open Package window
2. Identify and select the required Package using the Package details, filtering and history
information available from this window.
3. Select the Open button.
►The selected Package opens.
Printed documents are not controlled Page 17
User Manual
OPENING OFFLINE PACKAGES
7.1 ABOUT PACKAGE DETAILS
The Open Package window displays a list of offline Packages. The details about each of the
offline Packages is shown, these are defined in the following table. Also see, ABOUT THE
PACKAGE FILTERING OPTIONS and ABOUT THE PACKAGE HISTORY.
Details Definition
State Icons indicating ...
Vehicle ID
A unique identifier of the vehicle in which the package is used. The vehicle ID
is a useful way to find Package(s) for a particular vehicle.
The serial number field records the ECU number with which the package is
associated. Whenever a package is sent to an ECU, M1 Tune will attempt to
Serial #
send it to the matching ECU. If the package is to go into a different ECU, then
the serial number must be changed to the serial number of the receiving
ECU.
Comments are used to keep track of changes to the Package over time. This
Comment
is the recommended method to use for recording the sequence of changes
made to a Package. This field assists in selecting the correct Package.
Firmware The firmware property is the name of the firmware group.
Firmware
Version Name
Firmware
Version
Used to describe the specific version of the firmware.
An incrementing number that uniquely represents each unique build of the
package.
This field identifies for which M1 ECU model the package was built. Each M1
Hardware
Package is built to work with a particular M1 model. A package built for an
M170 will have a different pin allocation to a package for an M190.
Modified
Date/Time
Imported
Date/Time
This field records the last time that this particular package was modified.
This field records the date and time that the package was imported onto the
PC.
7.2 ABOUT THE PACKAGE FILTERING OPTIONS
The filtering options provided down the left hand side of the Open Package window can be very
useful in helping to find specific Packages.
Note: When working on a Package, update the Vehicle ID and the Description as you go
so that the most benefit can be realised when the filtering feature is later used.
This is important to make it easy to find and sort Package versions.
The result of using each of the filtering options is defined in the following table.
Printed documents are not controlled Page 18
Filter option Result
All Shows all packages on the PC (no filtering)
User Manual
OPENING OFFLINE PACKAGES
Recently imported
Recently Modified
By Firmware
By Hardware
By ECU
By Vehicle Id
Lists all packages grouped by imported date, sorted by the most
recently imported into Tune
Lists all packages grouped by Modified date, sorted by the most
recently modified from within Tune
Shows all packages grouped by firmware name, then sorted
alphabetically
Shows all packages, grouped by the M1 hardware model, then sorted
alphabetically
Shows all packages grouped by ECU type and ECU number, then sorted
alphabetically
Shows all packages grouped by the Package vehicle ID, then sorted
alphabetically
Printed documents are not controlled Page 19
User Manual
OPENING OFFLINE PACKAGES
7.3 ABOUT THE PACKAGE HISTORY
The Open Package window shows the history of each Package. This history is displayed using a
graphical State tree.
This State tree uses coloured boxes to denote the state of a Package, and connecting lines to
indicate the lineage of the Package.
Using these lines it is possible to determine from where a particular version of a Package
originated.
Displayed along the bottom of the Open Package window are the seven possible states.
The Package states as indicated by the coloured keys are defined as follows.
State Definition
Light Orange Unknown
Cyan - Auto
Saved
Blue - Tuned
Green - Matched
ECU
Dark Orange Migrated
M1 Tune cannot determine the source of this Package.
A modified Package that was never saved by the user,
M1 Tune auto saves Packages every minute.
A Package that has been changed offline but not sent
to an ECU.
A Package that matches exactly to a tune that has been
seen in an ECU.
A Package that has been changed based on another
Package.
This scenario occurs when there are multiple people
working on a single ECU. If two people are working in
different parts of the Package, but sending to the same
Purple - Merged
ECU, it means that changes have been applied "on top
of" (or merged) into a package that was different to the
original package (since one user updates the ECU
sometime between the other user opening the Package
and sending changes).
Example State
Tree
In some cases a full merge cannot fully succeed since
Red - Partial
Merge
Printed documents are not controlled Page 20
two users changed the same part of the package
(causing a conflict that cannot be automatically
resolved); but some of the data was merged.
User Manual
COPYING, MOVING AND DELETING PACKAGES
8 COPYING, MOVING AND DELETING PACKAGES
Moving M1 Package files via Windows Explorer is not recommended.
MoTeC M1 Packages are not intended to be copied, added, deleted or moved by use of the
standard Windows file system. It is recommended that when moving Package files the Import,
Export and Export Mail functions are used, these are available from the Open Package window,
see OPENING OFFLINE PACKAGES
Use the Import and Export functions when a package needs to be moved from one PC to
another.
8.1 ARCHIVE FILES
MoTeC has implemented a new method of adding and moving files within the M1 system. The
new file type is called an M1 Archive file. Its purpose is to remove the need for users to manually
find their way around the file system when moving or adding files.
.
The M1 Archive may contain multiple files and complete directory structures, it is similar to a
self extracting ZIP file. The locations are automatically determined when the file is extracted,
requiring no input from the user.
The archives used within M1 Tune are described in this table.
Archive file
extension
Purpose
.m1pkg-archive Files required to add a new package to M1
.m1prj-archive All files required for an entire M1 project
.m1lic-archive M1 licence file
.m1wsp-archive Files required to install a new workspace configuration in M1 Tune
8.2 EXPORTING PACKAGES
To export packages:
1. Open the Open Package window from the Quick Launch fly out, or the menu option File
»Open Package.
2. Using filters and searches as necessary, find and select the Package to copy.
3. Select the Export File button to export the archive to a USB stick or drive, or the Export Mail
button to attach the archive to an email.
►The file created has an extension of .m1pkg-archive. The filename is a combination of the
Firmware, Hardware, Vehicle ID fields.
4. Distribute the Package archive file as required.
Printed documents are not controlled Page 21
User Manual
COPYING, MOVING AND DELETING PACKAGES
8.3 IMPORTING PACKAGES
Once a Package archive is received, there are two options for installing (importing) the package;
using the Import function as described below, or by double-clicking on the archive filename.
Both methods result in the package being unpacked and files added to the correct locations so
that the Package becomes available in the Open Package window.
1. Open the Open Package window from the Quick Launch fly out, or by selecting menu
option File »Open Package.
2. Select the Import File button.
3. Browse to the location of the archive file, select it and click Open.
8.4 DELETING PACKAGES
To delete Packages:
1. Open the Open Package window from the Quick Launch fly out, or by selecting menu
option File »Open Package.
2. Select the Package to delete (Multiple Packages may also be selected) and right click on the
selection.
►The right-click menu displays.
3. From the right-click menu, select Delete.
Printed documents are not controlled Page 22
9 CREATING WORKBOOKS
To create Workbooks:
1. Select menu option Layout »New Workbook.
►A prompt to enter a Workbook name displays.
2. Name the new Workbook.
►A new empty Workbook is created.
3. Add Worksheets and components as required.
User Manual
CREATING WORKBOOKS
Printed documents are not controlled Page 23
Loading...