MoTeC M1 Development License V1.4.1

An M1 Development ECU is the same as any other M1 ECU, other than it has been loaded with an M1 Development Package Licence. One of these ECU's must be purchased for a developer to be able to build a package and test it. The M1 Development Package Licence prepares the M1 ECU to accept packages which have a correlating M1 Build Package Licence. For most users, the M1 Build Package Licence will be purchased, at the same time as an M1 Development ECU, and as such, all of the licences will match at the time of purchase.

One M1 Build Package Licence can be used to write firmware for many M1 Development ECU's. Therefore, when a developer purchases additional M1 Development ECU's, they will each get an M1 Development Package Licence which correlates with the developers M1 Build Package Licence. M1 Development ECU's can be used for in-house development, or sold as to as tailored ECUs to customers.

Using this model, a developer could buy additional M1 Development ECU's and sell them to customers. The developer could then write a packages for the customer and push the new code into customers ECU at any time.

If the end customer wanted to do their own development, then they would need their own M1 Build Package Licence, and M1 Development ECU.

M1 Development ECU's can be re-licensed at any time at no cost from one M1 Development Package Licence to another. This allows M1 Development ECU customers to move their firmware development around between different developers when required.

New feature/functionality

Feature #20597: DBC Import

Feature #20639 Update DBC file from root group

Feature #20571: Scheduled Function: add class method Period()

Feature #20692 Add file Version handling to project open

Feature #20691 Lock and increase project version when Project file upgraded

Feature #20524: Show code statistics on compile (ECU memory usage)

Feature #19808: Add "Location" and "Error Details" columns to messages tab

Feature #18445: help: add keyboard shortcuts for object and enumerator tags

Feature #19813: Single click within dropdowns to select items

Feature #19764: Add find matching key to security setup

Feature #21074: Add Activation to support activating Simulink Integration (requires Simulink license)

Feature #21124: Add "Show All" button in the Quantities panel

Increased performance

Feature #19077: shorten code compile time (build time)

Feature #20240: Faster project validation (validation time)

Feature #4990 Improve Property control performance (30% faster)


Bug #15538: Dialogue heading is truncated

Bug #18190: Check for Updates: Module name check is case sensitive

Bug #18828: Compare: Help marked as different but looks the same

Bug #18959: Space character entered as " " when entering text into help tab of the properties window

Bug #19479: validation doesn't pick up invalid characters in a script

Bug #19757: Tooltips on help editor missing

Bug #19780: Data logging systems 2-8 are not "Unused" (change the default names from "Unused x" to "System x")

Bug #19797: Application crashes when channel is dragged onto Object group

Bug #19807: Code references don't change colour from invalid if code was written before references were created

Bug #19812: 'Incorrect tag' validation error does not direct user to the error

Bug #19815: Event rates should not be sorted in the UI

Bug #19821: Help xml validation not listing correct offset

Bug #19902: M1Build treats math function as keyword

Bug #19908: Project validates but fails to compile (add validation at least one event, channel and parameter are present)

Bug #19951: help text editor doesn't support unicode

Bug #19979: Occasional crash when updating module

Bug #19983: Tuning Method Type Attribute is not saved.

Bug #20041: Invisible enum added when adding new enumerator while still editing another

Bug #20074: Active Configuration section on Settings tab doesn't scale height

Bug #20086: Resolving Data Type brings up Duplicate Data Type Error

Bug #20115: help editor "Italic" toolbar button doesn't tag selection correctly

Bug #20166: New lines in Help treated as changes

Bug #20168: Tags show a warning but project validates successfully

Bug #20170: Ctrl+shift+c shortcut to Close project crashes application

Bug #20194: Security key 'Select' and 'Create' do not always point to user key folder

Bug #12706 Property unlinking is broken in module projects

Bug #20425 Objects can be moved from a read only compare project to the main project

Bug #20620 Automatically saves after validate

Bug #20641 Invalid signal quantity not flagged

Bug #20660 Validation is very slow when there are warnings / errors

Bug #20687 When new dbc is added and not renamed immediately, the user is not prompted to select dbc file

Bug #20706 Error 1657 has incorrect description

Bug #20730 When scheduled Method scheduled in Dual event and period() is used, staging fails without error message

Bug #20772 Application crashes when delete a non-included object after validation

Bug #20784 DBC : Offset in FindMessage for compound message is incorrect for intel format

Bug #20975 Application crashes when selecting the help tab from the Argument Properties window

Bug #20982 DBC : when offset is a big number the precision is lost

Related Items