@MintyTrebor perfect, now it starts. Thanks a lot!

V1.5 released

updated python packages to allow newer versions fixed a non-critical error in shutdown enforced mandatory options fixed error when -ignore was not provided fixed issue handling multiple -ignore

@stuartofmt
Great, thanks for the reply. I might wait for the release since I had some weirdness when I tried 3.6.0 rc2. I was messing with several things at the time so maybe it was unrelated. In the meantime I have been manually checking my config into github. 🙂

Thanks again and I look forward to trying this out.

@achrn have you considered releasing this as a plugin via plugins.duet3d.com

Updated for 3.6 (tested on 3.6.0rc1): PyDaemon.zip.txt (as usual you will need to take the .txt off the end of this file - I'm circumventing the forum restrictions).

The only change is to renumber it to a 3.6 version and set the requisites to 3.6.

Installation

The 3.6.0RC1 package repository does not have 3.6.0 DSF (at time of writing), and the 3.5.1 DSF one does not work with 3.6.0, so you need to add DSF manually. The 3.6.0 RC1 version is on pypi: https://pypi.org/project/dsf-python/3.6.0rc1/ so sudo pip3 install --break-system-packages dsf-python==3.6.0rc1 should install it.

python3-dsf-python (3.6.0~rc1-1) is in the repository now so can just sudo apt install python3-dsf-python (or apt upgrade) it.

Otherwise it's install in the usual manner for plugins - drop the zip onto the 'Install Plugin' button in Plugins in DWC and click the Start button (after checking the code is not going to do you harm). Refer to the first post in this thread for discussion of what goes in your daemon.py file.

@chrishamm

I understand the refresh - that was a secondary thing. I'm not too fussed, now that I know its not a bug / issue.
Cosmetically - I think it would benefit from consistent language.

@MintyTrebor

Hi,

I have been using it for some time.

It is the greatest thing since sliced bread!

I'm very glad you have been keeping it up-to-date as new versions of Duet firmware come out.

Do you have a "tip jar"?

Frederick

@droftarts
@chrishamm

OWA TAGU SIAM

My apologies - rebuild at each release level (even minor ones) ... 😊 😊 😊

All is well in the world of plugin installs.

@chrishamm
Understood, as it relates to DWC. I may just use "sbcDsfVersion": "3" for the DSF only plugins.

@stuartofmt Thanks. I ran into the venv elsewhere so that makes sense. I will move to 3.6.

OK, I may have inadvertently resolved it.

I found how to remove the desktop and boot to terminal using raspi-config. I wanted to understand the RAM cost. I have an RPi4b with 2GB RAM.

FYI:
in terminal mode after boot I have 1.5 GB free.
In desktop gui with DWC running at 1280x900 I have 960 KB free.

Anyway, after switching back to GUI mode everything boots as expected and DWC starts. So I suspect my config was whacked somehow (I touched nothing!) and running the rasp-config corrected the situation.

Sorry for all the bother.

@Notepad Thank you very much, unfortunately I only have the option to install the plugin...perhaps the other options are no longer available in version 3.5.4?

@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

@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