Topics created by MintyTrebor

@MintyTrebor Thanks, I've changed registerCategory in the 3.5 branch to wait for the DOM update.

@MintyTrebor thanks. It's strange that I don't see any malformed packets on either of my machines, and the ones you see don't appear to be triggered by a packet received by the Duet.

OK. Figured it out... It is indeed down to OpenSSL 3.0 - Posting resolution in case anyone else comes accross this issue:

Edit the openssl.cnf file and enable the legacy provider options. eg:

# Uncomment the sections that start with ## below to enable the legacy provider. # Loading the legacy provider enables support for the following algorithms: # Hashing Algorithms / Message Digests: MD2, MD4, MDC2, WHIRLPOOL, RIPEMD160 # Symmetric Ciphers: Blowfish, CAST, DES, IDEA, RC2, RC4,RC5, SEED # Key Derivation Function (KDF): PBKDF1 # In general it is not recommended to use the above mentioned algorithms for # security critical operations, as they are cryptographically weak or vulnerable # to side-channel attacks and as such have been deprecated. [provider_sect] default = default_sect legacy = legacy_sect [default_sect] activate = 1 [legacy_sect] activate = 1

Save and reboot.
npm run serve should now work

Note: On Fedora 36 openssl.cnf file is located in /etc/pki/tls - it may vary per distro.

Updated to V1.3.3 for DWC 3.5.3

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

@chrishamm Another user experience the same issue described above (you can read about it here https://forum.duet3d.com/post/227680), so @jay_s_uk and I put our heads together and tried to narrow down the failure circumstances and find a consistent fix (simply uploading a new DWC*SD.zip does not always work).

What we have discovered is that if the current install/SD card has gone through a number of release upgrades (eg 3.1 through to 3.3b3) it is likely that this Z-Index issue will arise after installing the plugin. Under this scenario I have also experienced complete plugin installation failures.

The resolution is to remove the SD card, wipe the WWW folder (& dwc-settings.json for completeness), and manually replace the WWW folder with a fresh copy extracted from the DWCSD.zip release file. Then once back up and running, re-install the plugin. Simply re-installing DWC by uploading a new DWCSD.zip will not resolve the issue.

This leads us to theorise the following:

There are redundant/left over files in WWW from previous upgrades which are contributing to, or causing this issue. If (for whatever reason) a plugin install fails, it does not always fail gracefully, and can corrupts or leaves files in a non working state.

I appreciate this is somewhat speculative (correlation is not causation and all that jazz), but it may help you with the continuing development of the plugin system.

@chrishamm you can get the plugin here https://github.com/MintyTrebor/BtnCmd/releases

I'm creating separate versions for 3.2 & 3.3 - they are both available in the releases.

I think the plugin is almost ready to go - I'm just resolving some dynamic layout issues. So it should functionally work OK.

Thanks for looking at the issue.

@DIY-O-Sphere said in NodeDSF : Interface nodes for Node-Red (V1.1.11 - 06-10-23).:

And it's a bit strange that the latest image contains such old versions of node.js....

Yep - a user of my nodes for klipper (moonnode) hit the same problem (v18 nodes on v16 docker image), he raised the issue with the docker image maintainers and there response was something like "we wont update the node version until the next major release" - which is not ideal

Thanks for the info. I did not include in the readme all the nodes used in the "example" dashboard, just the nodes in the "Universal" dashboard. I have made it clearer in the readme.

Node-red-contrib-looptimer2 is a node available in palette manager and was used in the "universal" dashboard.

I have also updated the notes to reflect the changes required to use the updated API object model used in the recent beta firmware(s). Its just a simple path change, nothing major.

Edit: I have updated the Duet Dashboard Universal Flow:
Updated to show how to get all three types of status updates from API V1.
Included example of how to process Remaining Job Time
Added alternative Object Model API Paths for Firmwares V3.1+