https://github.com/raymondjstone/DUET3D_CNC_Probe

is the first stab at adding in the probe functions used by workbee owners that use the ooznest (ancient) version of the DUET UI. This is intended for 3.3 and above firmware versions it will not work below that.

https://github.com/raymondjstone/DUET3D_CNC_Probe

is the first stab at adding in the probe functions used by workbee owners that use the ooznest (ancient) version of the DUET UI. This is intended for 3.3 and above firmware versions it will not work below that.

With the lack of replies on this post here are some findings that do not seem to be well documented at the moment

1 If saving to machine settings you MUST use a real board or it will not work properly
2 If you use a real board to install the dev plugins you MUST uninstall them afterwards before switing to the real UI
3 you replace your dev entries in index.js with one in manifest.js (at the end) like this

export default [
new PluginManifest({
id: 'CNCProbe',
name: 'CNCProbe',
author: 'CNCProbe',
version: '0.6.20',
loadDwcResources: () => import(
/* webpackChunkName: "CNCProbe" */
'./CNCProbe/index.js'
)
}),
]

4 when you have your plugin files they go in a folder dwc/js/
5 The names in the plugin.json are case sensitive

I'm a bit stuck here.

I can run a plugin (CNC probing) in dev mode easily but when I build the project to get the files for the package they install fine but will not run since while machine specific they are trying to start as built in plugins.

So I removed the 'dev' entries from plugins/index.js which is fine, but they when I build the UI the new plugin is not picked up and built as part of it so no files to put into the plugin package.

Could someone help with whatever file it is that I am missing that would allow a machine specific plugin to be built while not treating it as a built in one?