v5.2.0

Release v.5.2.0

This release updates to the latest godsfapi version and uses the new filters option on InterceptConnection to only receive those M-Codes the user is interested in.

This version requires DSF 3.2 or later.

Release v5.1.2

This release adds a new flag -returnOutput to be able to send the collected output of a successful run back to DCS. Prior this was only the case if the execution of the command failed.
Note that this cannot be combined with -execAsync.

v5.1.1

This release introduces three new features:

• New parameter -execAsync. This will execute all commands asynchronously returning control immediately back to DCS. This flag is active for all captured M-Codes per execonmcode instance, i.e. if some commands should be performed asynchronously and others synchronously start two execonmcode instances.
• New parameters -interceptionMode to select between Pre (default), Post and Exectuted
• New parameter -noFlush. This will prevent flushing the code channel prior to executing the attached command. This is useful if the command can be executed once it is read from disk. As with -execAsync this applies to all commands of an instance of execonmcode.

v5.1

This makes execonmcode compatible with Duet Software Framework 2.2.0 and later.

v5.0

This release updates godsfapi to v2 and thus is only compatible with Duet Software Framework 2.1.0 and later.

New Features

• A new command-line paramter -version to output the version and exit

Bug fixes

• After a handled code is intercepted and before the assigned command is executed Flush will be called to make sure we are in sync with the machine

v4.0

This version works with DuetSoftwareFramework 1.3.0 and later. Unfortunately due to breaking changes in the API of DSF this is NOT backwards-compatible with older versions of DuetSoftwareFramework.

This release also has a new parameter -trace that will enable output of the underlying requests/responses to/from DuetControlServer.

v3.0

This release adds the possibility to provide an arbitrary amount of -mCode + -command tuples. This way it is possible to have a single instance of execonmcode handle all the custom commands.

Note that as part of this change there is no longer a default value for -mCode.

Fix #3

This is just a bugfix release to fix #3.

Added parameter substitution

This release supports parameter substitution requested in #2.

Please see README.md for details on how to use it.

Reworked to arbitrary commands

This new release allows the user to specify which command will be run and has thus renamed to project to execonmcode. ;-)