@Phaedrux

Do you have plugin.json in the root?

Yup still there

It looks like the zip is created during the build process for the plugin. So unzipping, modifying, and re-zipping it doesn't seem possible. You may need to modify the source and rebuild.

Ahh, that would explain it

@chrishamm Okay thanks for all the pointers ! I switched all my machines to 3.5.3 and made the changes with the connections that you suggested, and it solves most of my problems.

For the problem that I mentionned due to the machine being shifter along the Z axis after executing a macro from the plugin, I found something that might have caused the issue:

When intercepting a command inside the plugin, I was always starting by sending G90 and M83 to the machine to make sure that whatever mode it is in, I can always perform moves and extrusions in absolute and relative mode, respectively. I suspect that those two commands might have caused the machine to shift position along Z due to synchronization issues because I removed them and the issue never happened again...

Updated to V1.3.3 for DWC 3.5.3

Updated to 01.03.05 for DWC 3.5.3 compatability.
No functional changes.

@MintyTrebor
I'm very sorry! It was my fault...
The graph was not showing the same value as the numeric panel!
Whats the difference between requestedValue and actualValue? Is the actualValue the "real" PWM inside the min and max settings?

EDIT: Now i need a RRF3.5.3 version...
It's funny... first, one layout was not working because the missing retraction parameters in OM (RRF5.3.2). Now, with 3.5.3 the plugin itself is not working anymore..🙃

@madeinta1wan Can you figure out what files are taking up the most space? If you have an old DuetPi version installed, make sure rsyslog isn't installed (sudo apt purge rsyslog), because that used to log a lot of stuff without ever purging the log files, which gradually filled up the SD card.

@chrishamm

I took the liberty of adding some additional checks / logging to build-plugin.js. Warns if the plugin src/index.js file is missing. Hopefully helpful:

build-plugin.js

ExecOnMcode v0.6 has been released.
This version now supports DWC 3.5

@achrn Your first approach is fine. Instead of a simple code you can send a regular DSF G-code as well. SetObjectModel is reserved for the DuetPiManagementPlugin and for non-SPI mode (which I haven't tested in a while), so don't use that.

@chrishamm Thanks a lot, that was the problem ! I was looking at an old documentation page that didn't show that this permission was possible... Thank you !

This (above) does work with dsf-python 3.5.1rc1 (as announced in https://forum.duet3d.com/post/338777).

However, I've got a slightly refined set of installation instructions for the pre-requisites:

To install dsf-python it's not necessary to download the source etc. you can just sudo pip3 install --break-system-packages --pre dsf-python (and this is better). It will moan about how you should be using a virtual environment instead, but should work. I haven't done any testing with virtual environments. (pip is deprecated, but setup.py is even more deprecated.)

For hx711py it's not set up to use pip, but if you use sudo python3 setup.py install --record files.txt it will at least write the files it installs into files.txt, which will help if you want to uninstall it in future.

Otherwise, same instructions as above.

@marvineer Version 3.5.1 is available now, see https://github.com/Duet3D/MotionWebcamServerPlugin/releases/tag/v3.5.1. It is compatible with v3.5 and Debian Buster and Bookworm.

I've tried converting the custom_http_endpoint.py example into a plugin and that goes 'partially started' too.

I've disabled apparmor in /opt/dsf/conf/plugins.json, just so it can't interfere - my goal would be to put it back on when I've figured out what's going on.

I've set up a 'test_plugin' that comprises only the custom_http_endpoint.py in folder dsf, and a plugin.json:

{ "id": "TestPlugin", "name": "Test Plugin", "author": "achrn", "version": "1.0.1", "license": "MIT", "dwcVersion": "3", "sbcDsfVersion": "3", "sbcRequired": true, "sbcExecutable": "custom_http_endpoint.py", "sbcExecutableArguments": null, "sbcOutputRedirected": false, "sbcPermissions": ["fileSystemAccess","launchProcesses","registerHttpEndpoints"] }

If I install that plugin it seems to go in OK, in that it appears as an external plugin in the web page, but if I start it, it goes to status 'partially started', and if I then try to access the endpoint (using wget) I get a zero length response. If I try and access the endpoint when the plugin is stopped (ie not even partially started) I get a 500 internal server error.

/run/dsf/custom/getIt-GET.sock does exist, dsf:dsf and permissions srwxrwxr-x

So I'm still flummoxed.

@PDBeal sudo apt install duetpimanagementplugin via SSH/Linux console

@Exerqtor It looks like it's not there. I'll see if I can add it in the next release....There may be a reason I did not add it in the begining, but that was too long ago to remember, or I just missed it the first place. Who knows!😊

@chrishamm Thanks, I will ignore it than. There are enough more urgent thinks on my table.

Cheers, Chriss