Posts made by stuartofmt

@jltx

Hi - attached is a version of DuetLapse3 for 3.6.0-beta.4
If you want to try it be sure to remove the .txt extension

DuetLapse3-5.3.7.zip.txt

@droftarts
@chrishamm

OWA TAGU SIAM

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

All is well in the world of plugin installs.

@droftarts
@chrishamm
Please hold off looking at this. I may have made a rookie mistake in that I forgot to rebuild for 3.6.0-beta.4 because of the simplicity of the vue involved (basically just invoking an iFrame).

I'll do so then report back.

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

In plugin.json dwcVersion and sbcDsfVersion are defined to have single values.
It does not seem possible to, for example, indicate that a plugin is compatible with 3.5.x and 3.6.x.
Is this the case , or is there a way? It would be useful for plugin developers and users to not have to, unnecessarily, target specific plugin versions.

I have tried e.g. >=3.5 and also tried an array ["3.5","3.6"] however neither are supported. The latter, BTW, fails silently.

I am trying to test my duetLapse3 plugin on 3.6.0-beta.4. It works correctly on 3.5.4.

I changed plugin.json to reflect the target version and the installation completes reporting success. When starting the plugin - it reports `partially started' . It does not do this in 3.5.4.
I can access the program from a browser, using the direct url - so that part is working correctly. However - there is no UI element, for the plugin, created in DWC This is the specific problem.

Any and all help would be appreciated.

The journal reports two warnings, which I suspect are the root of the problem.

Feb 17 10:31:59 srsender DuetPluginService[48396]: [info] Plugin DuetLapse3: Installing files
Feb 17 10:31:59 srsender DuetPluginService[48396]: [warn] Plugin DuetLapse3: Skipping installation of file src/DuetLapse3.vue
Feb 17 10:31:59 srsender DuetPluginService[48396]: [warn] Plugin DuetLapse3: Skipping installation of file src/index.js

Below are the relevant files.
The index.js file (and src/DuetLapse3.vue) are unchanged from the 3.5.4 version:

'use strict'

import { registerRoute } from '../../routes'
// import { registerRoute } from '@/routes'

//import Vue from 'vue';
import DuetLapse3 from './DuetLapse3.vue'


// Register a route via Plugins -> DuetLapse3
registerRoute(DuetLapse3, {
	Plugins: {
		DuetLapse3: {
			icon: 'mdi-transition',
			caption: 'DuetLapse3',
			path: '/DuetLapse3'
		}
	}
});

plugin.json

{
    "id": "DuetLapse3",
    "name": "DuetLapse3",
    "author": "Stuartofmt",
    "version": "5.3.3",
    "license": "GPL-2.0-or-later",
    "homepage": "https://github.com/stuartofmt/DuetLapse3",
	"sbcRequired": true,
	"dwcVersion": "3.6",
    "sbcDsfVersion": "3.6",
	"sbcExecutable": "DuetLapse3.py",
	"sbcExecutableArguments": "-file /opt/dsf/sd/sys/DuetLapse3/DuetLapse3.config",
	"sbcOutputRedirected": false,
	"sbcPermissions": ["commandExecution", "objectModelReadWrite", "objectModelRead","networkAccess", "webcamAccess", "readSystem", "writeSystem", "fileSystemAccess","launchProcesses", "managePlugins"],
	"sbcPythonDependencies": ["requests","psutil"]
 }
 

DuetLapse3.vue

@jltx

As I indicated above - the 3.6 version is not yet available. It looks like there was a change or two to the plugin framework since 3.5 - so I have to track that down.
The 3.5 version will not install on a 3.6.0-beta.4 release. If you think it has installed - then something is wrong or you are not using the plugin installation method from DWC.

The documentation has several cautions about the use of the pause capability. It has the ability to set delays and can also interact poorly with the default pause capability.
I strongly recommend you get a basic config working first.

When you report back - with the config file and logfile info I requested above. That way we can see what is going on.

@jltx
Lets have a look at your config file.
Also - to be clear, you are running 3.5.4 SBC on Bookworm? Buster?
Also - since there are no images being collected - there is something wrong - so please include a log file that was created with -verbose.

The images are not created in that directory. See the info tab for the directory location. You should also be able to see them in the files tab.

Its best to get basic operation working correctly before adding pauses and such.

@jltx

@jltx
I have been "offline" for about 6 months and am just now restarting having rebuilt my system.

For SBC the 3.5 version in github is the one you should be using. I'll push out a 3.6 version shortly (I don't think there will be any changes - but ...)

There was one broken link in the documentation which I just fixed. This is likely the main info you are missing
https://github.com/stuartofmt/DuetLapse3/blob/main/Documents/plugin installation guide.md

The software grew in capability over time - so its important to start of simply and not be overwhelmed by too many options. See the examples here (they are for standalone but the config file examples are the same for the plugin version)
https://github.com/stuartofmt/DuetLapse3/blob/main/Documents/DuetLapse3 Useage Examples.md

The example and the fixed link should get you started. When testing - make sure you include -verbose so that errors and warnings can be seen.

Once you have it basically configured and can use the plugin UI - you can then start tweaking configurations and doing "fancy stuff" with gcodes.

Let me know if you get stuck.

Reposting this as I inadvertently posted it in the firmware area ...

I tend to use the webcam iFrame for another purpose.
In my case I link the webcam UI to a url that controls an IP relay which turns on / off the mains to the printer power supply.
I use SBC with a Pi that is always powered on - so I have DWC always available.
This way I can switch on / off the printer from DWC versus the terribly onerous task of opening another tab in the browser. So lazy am I that I also use the *Physical Printer' tab in Prusa Slicer ... but it does give a nice, all-in-one, feel.

Since the webcam UI is more-or-less generic, it would be nice (and nice only) to be able to label it as other than Webcam Surveillance in the display and as Webcam under the Jobs menu.

@dc42 said in [3.6] A very minor, cosmetic, DWC UI suggestion:

@stuartofmt that's one for @chrishamm.

Sorry - at the time of posting I conflated everything 3.6.0-beta in my mind. I'll repost in the DWC forum

@jltx

TLDR; You need to be using Duet V3.6.0+ (or not use Bookworm)

Bookworm introduced some new requirements for installing python programs and modules. They need to be installed in a virtual environment. In practice, this means a virtual environment for each plugin (so they don't stomp on each other).
The plugin manager in V3.6 uses an installer that takes care of this, version 3.5 does not.

Unless installing deliberately into the system environment - you should not be using apt for python packages. I suspect there are other safeguards in place as well.

On my system (SBC, Bookworm, Duet 3.6.0 - beta.4) - trying to install into the system environment, using pip, I get the expected warning

pi@srsender:~ $ python -m pip install "PyGithub=="
error: externally-managed-environment

This environment is externally managed
    To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.
    
    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.
    
    For more information visit http://rptl.io/venv

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

The required version of pyGithub is however available:

pi@srsender:~ $ python -m pip index versions PyGithub
WARNING: pip index is currently an experimental command. It may be removed/changed in a future release without prior warning.
PyGithub (2.5.0)
Available versions: 2.5.0, 2.4.0, 2.3.0, 2.2.0, 2.1.1, 2.1.0.post0, 1.59.1, 1.59.0, 1.58.2, 1.58.1, 1.58.0, 1.57, 1.56, 1.55, 1.54.1, 1.54.0.1, 1.54, 1.53, 1.52, 1.51, 1.50, 1.47, 1.46, 1.45, 1.44.1, 1.44, 1.43.8, 1.43.7, 1.43.6, 1.43.5, 1.43.4, 1.43.3, 1.43.2, 1.43.1, 1.43, 1.40, 1.39, 1.38, 1.37, 1.36, 1.35, 1.34, 1.33, 1.32, 1.31, 1.30, 1.29, 1.28, 1.27.1, 1.26.0, 1.25.2, 1.25.1, 1.25.0, 1.24.1, 1.24.0, 1.23.0, 1.22.0, 1.21.0, 1.20.0, 1.19.0, 1.18.0, 1.17.0, 1.16.0, 1.15.0, 1.14.2, 1.14.1, 1.14.0, 1.13.1, 1.13.0, 1.12.2, 1.12.1, 1.11.1, 1.11.0, 1.10.0, 1.9.1, 1.9.0, 1.8.1, 1.8.0, 1.7, 1.6, 1.5, 1.4, 1.3, 1.2, 1.1, 1.0, 0.7, 0.6, 0.5, 0.4, 0.3, 0.2, 0.1, 0.0.0

@jltx

I've just recently recreated by printer and SBC from the Duet3D bookworm full image and have a clean (and working) system. So a couple of these may help:

Regarding DWC auto starting:

pi@srsender:~ $ cat  ~/.config/wayfire.ini
[autostart]
dwc=launch-dwc

pi@srsender:~ $ cat  ~/.config/labwc/autostart
# Start DWC on boot
launch-dwc &

regarding permissions, I've never seen rwe permissions needing to be changed, but I have seen ownership issues (with a "hand build")

pi@srsender:/home $ ls -l /opt
total 12
drwxr-xr-x 7 1001  127 4096 Nov 27 13:21 dsf
drwxr-xr-x 3 root root 4096 Nov 27 13:15 pigpio
drwxr-xr-x 4 root root 4096 Nov 27 13:26 WidevineCdm

pi@srsender:/home $ ls -l /opt/dsf
total 96
drwxr-xr-x 2 1001 127 77824 Feb 11 15:24 bin
drwxrwxr-x 2 dsf  dsf  4096 Feb 11 15:25 conf
drwxr-xr-x 6 dsf  dsf  4096 Feb 11 15:24 dwc
drwxr-xr-x 4 dsf  dsf  4096 Feb 11 15:24 plugins
drwxrwxr-x 9 dsf  dsf  4096 Jan 18 14:27 sd

The (rather) odd ones out are /opt/dsf and /opt/dsf/bin (I'd somehow expect them to be dsf:dsf too but that's not the case)

I'd make sure all the second level subdirectories are recursively set to the same ownership as the parent using

sudo chown -R [user]:[group] /opt/dsf/[subdir]

or just reinstall from the Duet3D bookworm image

For anyone stumbling across this ...

Looks like the correct file to edit is ~/.config/labwc/autostart
Just comment out the line with launch-dwc &

# Start DWC on boot
# launch-dwc &

@chrishamm @T3P3Tony
I just tested with 3.6.0-beta.4. I can no longer trigger the behavior.

Looks good!

I tend to use the webcam iFrame for another purpose.
In my case I link the webcam UI to a url that controls an IP relay which turns on / off the mains to the printer power supply.
I use SBC with a Pi that is always powered on - so I have DWC always available.
This way I can switch on / off the printer from DWC versus the terribly onerous task of opening another tab in the browser. So lazy am I that I also use the *Physical Printer' tab in Prusa Slicer ... but it does give a nice, all-in-one, feel.

Since the webcam UI is more-or-less generic, it would be nice (and nice only) to be able to label it as other than Webcam Surveillance in the display and as Webcam under the Jobs menu.

@T3P3Tony
No need to be sorry - I had to figure out what else was in the boxes anyway

And thank you Christian. I though I was seeing things at first

@tfranssen
Have you solved the issue (if so how) or is this still a problem?

@T3P3Tony
Well, that was fun ... I've moved countries and eventually found the external antenna in a box of bits. It was only then that I realized the Mini5+ is ethernet and said antenna was for something else. The house is wifi only. Getting the printer, safely, to the router in the loft (for an ethernet connection), is a faff too far