Just released V1.4
It is available for both DWC3.5 and DWC3.6
Note that this plugin backs up its associated printer to Github (which retains versions). For backing up to a file system - take a look at
https://forum.duet3d.com/topic/10880/rfm-reprapfirmware-filemanager-duetbackup-successor
If there is sufficient interest - I can look at creating a non-plugin version that can backup a standalone printer (i.e. non SBC) from a remote computer.
Let me know.
This plugin provides periodic or instant backups of duet3d SBC files. Backups are made to a Github repository, thereby facilitating the ability to roll back to earlier file versions.
Instructions and plugins for V3.5 and V3.6 can be found here
https://github.com/stuartofmt/duetBackup
V1.0
V1.1
-duetPassword to support for printers that use a password-verbose to enable more detailed log messages.V1.2
-noDelete optionV1.3
README.md file shows date and time of last backupREADME.md prevented from being deleted-ignore. Can specify files that are not to be backed up. This also causes these files to be deleted unless -noDelete is set.V1.4
README.md file now shows a summary of the last backup i.e. files added, updated, deleted.Installation instructions and code can be found here:
https://github.com/stuartofmt/duetBackup
Version 1.2
Added a logfile (accessible from DWC) to make monitoring easier.
I also restructure the code for easier maintenance and updated the documentation.
@Tinchus said in raspberry camera on new firmware version:
@the_K Im not able to replicate the installation on another printer. The same as you it is happening to me: plugin just runs for 1 second. Looking at the logs I can see an error about a camera module, so I installed:
sudo apt -y install python3-picamera2
With this I can start the plugin and stays active. Still, I cant see the camera on DWC
I’ve always found it useful to prove a streamers settings with a browser before proceeding further. There are just sooo many variables …. Having said that, given a pi camera and the pi libraries - it should more-or-less just work (or at least log sensible errors)
I’ve stopped using pi cameras, so I stopped supporting my old pi streamer. However - you may ( or not ) find something useful in my old notes
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.
@chrishamm said in [3.6.0-beta.4] Inconsistent plugin state:
@stuartofmt Do you mean you'd rather like to see "stopped" instead of "installed" for third-party DWC plugins that are inactive?
Hi - I think the UI should behave consistently and avoid having to Ctrl+Shift+R if possible. Because of the different behavior - thought I may have been seeing a bug / problem.
For example with my DSF only plugins (no UI element)
(strikethrough --> greyed out):
1- Currently: [started] [Stop] [Uninstall]
2 - Press Stop
3 - UI displays [stopped [Start] [Uninstall]
4 - Press Start --> goes back to 1
Note that no refresh of the UI is needed
But for plugin that uses DWC (or DWC and DSF)
1- Currently: [started] [Stop] [Uninstall]
2 - Press Stop
3 - UI displays [deactivated] [Stop] [Uninstall]
4 - Ctrl+Shift+R
5 - UI displays [installed] [Start] [Uninstall]
4 - Press Start --> goes back to 1
@guywinslow
Ok - that's good news but a mystery as to why it did not work the first time, as I assume you, effectively, just reinstalled from github.
If you had used the version I posted yesterday - there would have been a duetBackup ONLY log created (along with additional debug information) that you could access directly using the DWC UI.
The version that I sent to you yesterday will be the version posted in github soon. I do not use github for "in progress" builds - just for version bumps, once they are tested.
While I have tested on my 3.6 beta build - It would be very helpful if you could validate it against your 3.5 build.
Can you do that for me? I.e. Try the version I posted yesterday.
P.S. The permissions dsf:dsf from the ls -l look correct - so there may have been some other issue.
@guywinslow
Very strange indeed ...
What version of Duet Software version are you using ? If it's 3.5.x try this. The plugin manager invokes plugins slightly differently than 3.6. The previous version was ambiguous ..
What SBC hardware ?
What OS version ?
At a console - what is the result of this command?
ls -l /opt/dsf/plugins
Can you try uninstall and then reinstall but before you reinstall run the following (just tails the plugin service logs) from the console to get any installation errors.
env SYSTEMD_LESS=RXMK /usr/bin/journalctl -u duetpluginservice -f
I've been meaning to add a log file to this plugin for some time.
The logfile is sys/duetBackup/duetBackup.log (i.e. same dir as the config file).
Other than the log file - I put in some code to report permissions. Can you please run this version (remove the .txt extension) of the plugin and use a config file like below (and then post duetBackup.log
-userName <your info>
-userToken <your info>
-rep <your info>
-dir sd/sys
-dir sd/macros
-days 0
-hours 0
-ignore *.log
-verbose
[plugin.zip]
V1.0.1
Exposure control is notoriously hit-and-miss. I changed the handling of exposure control to log the values at startup so that the user has a known point from which to research.
Essentially there are two options (used together). The first switches the camera to manual control and the second sets the exposure. All this, provided the camera supports exposure control. Just what the required values are is undefined.
Some cameras switch to manual when sent the value 0.25. Some require the value 1 to be sent, others ??
Exposure values are sometimes required to be between 0.0 and 1.0, sometimes negative numbers, sometime some other value (ms equivalent ?). It mainly depends on how the manufacturer set up the camera, the drivers used and even the OS.
In any case - if you need to adjust the exposure, there is going to be some trial and error.
For example, on one of my cameras, manual mode is set with 1 and usable exposure ranges are roughly in the range 75 to 200.
Good luck 
The internet if full of opinions ...
I have a plugin that correctly reported status and button changes in v3.5.4. By "correctly" I mean all plugins reported status and button changes in a consistent manner.
I recently re-built the plugin against 3.6.0-beta.4 and see an anomaly. This appears to be cosmetic only (or an error on my part)
The basics are:
[1] The plugin installs without error
[2] Start - the plugin works as expected and the state updates to "started" and the button changes to "Stop"
[3] Stop - the plugin stops but the state is reported as "deactivated"
[4]Ctl+Shift+R - state shows as "installed" with button changed to "Start"
Note that DSF only plugins (no ./src components) do not exhibit this behavior.
A new plugin with essentially the same vue code has the same behavior. As this is small, I have included the code below:
./plugin.json
{
"id": "httpViewer",
"name": "httpViewer",
"author": "Stuartofmt",
"version": "1.0.0",
"license": "GPL-2.0-or-later",
"homepage": "https://github.com/stuartofmt/usbStream",
"sbcRequired": false,
"dwcVersion": "3.6.0-beta.4",
"sbcOutputRedirected": false,
"sbcPermissions": ["commandExecution","networkAccess", "fileSystemAccess","objectModelReadWrite"]
}
./src/index.js
'use strict'
// import { registerRoute } from '../../routes'
import { registerRoute } from '@/routes'
//import Vue file;
import httpViewer from './httpViewer.vue'
// Register a route
registerRoute(httpViewer, {
Plugins: {
httpViewer: {
icon: 'mdi-transition',
caption: 'httpViewer',
path: '/httpViewer'
}
}
});
/src/httpViewer.vue
<comment>
Displays an iFrame that is linked to the DuetLapse3 html Display
Polls the status of the sbcPlugin and terminates the DWC plugin if the sbcPlugin is terminated
Thanks to @MintyTrebor for all the help in getting this working
</comment>
<style scoped>
.iframe-container {
position: relative;
background-color: transparent;
}
.iframe-container iframe {
position: absolute;
top: 0;
left: 0;
}
</style>
<template>
<div class="iframe_container">
<iframe id="myiframe" :src= "myurl" width="100%" :height="tmpHeight" frameborder="0">
<span>Your browser does not support iFrames</span>
</iframe>
</div>
</template>
<script>
import Path from '@/utils/path';
import store from "@/store";
import { DisconnectedError, OperationCancelledError } from "@/utils/errors";
// <!-- Do not change
const pluginName = 'httpViewer';
const configFile = pluginName + '/' + pluginName + '.config';
// -->
window.onmessage = function(event){
if (event.data == 'reply') {
console.log('Reply received!');
}
};
export default {
data() {
return{
myurl: '',
tmpHeight: "400px",
}
},
methods: {
//Modified file load from @mintyTrebor
async loadSettingsFromFile() {
try {
const setFileName = Path.combine(this.systemDirectory, configFile);
const response = await store.dispatch("machine/download", { filename: setFileName, type: 'text', showSuccess: false, showError: false});
this.fileContent = await response;
//get the ip address
//let pattern = /-duet.*(?:$|\n)/i;
let pattern = /-http.+/i;
let match = this.fileContent.match(pattern).toString();
this.myurl = match.replace('-http', '').trim();
// get the port
//pattern = /-port.*(?:$|\n)/i;
//pattern = /-port.+/i;
//match = this.fileContent.match(pattern).toString();
//this.myurl = this.topurl + ":" + match.replace('-port', '').trim();
console.log('url is ' + this.myurl);
} catch (e) {
if (!(e instanceof DisconnectedError) && !(e instanceof OperationCancelledError)) {
console.warn(e);
console.warn("File Does Not Exist");
}
}
},
// Set the screen height - from @MintyTrebor
getAvailScreenHeight(){
let tmpHeight = window.innerHeight - 90;
if(window.document.getElementById("global-container")){
tmpHeight = tmpHeight - window.document.getElementById("global-container").offsetHeight;
}
if(this.showBottomNavigation) {
tmpHeight = tmpHeight - 56;
}
return tmpHeight;
}
},
// use computed instead of methods cuz we only want it to run once
computed:{
systemDirectory() {
return store.state.machine.model.directories.system;
},
showBottomNavigation() {
return this.$vuetify.breakpoint.mobile && !this.$vuetify.breakpoint.xsOnly && this.$store.state.settings.bottomNavigation;
}
},
mounted() {
this.loadSettingsFromFile();
this.getAvailScreenHeight();
}
}
</script>
General Description
This is a simple plugin that displays the content of a web url.
It is useful if you want an embedded iFrame in DWC. For example - turn on / off your printer power supply with an ip enabled relay.
Capabilities
Just one - displays the web url. Like it says on the can 
Initial version - tested on Raspberry Pi 3B+ with Debian Bookworm
Documentation and Code can be found here:
https://github.com/stuartofmt/httpViewer
General Description
This is a simple video streamer for use with usb cameras. It streams video in jpg format from a url.
It is particularly useful when you want the same camera to be consumed by more than one application. For example a timelapse application (e.g. DuetLapse3) and to also monitor in real time.
usbStream is available as a DWC plugin and as a standalone application.
Capabilities
The main capabilities include:
Version 1.0.0
Initial version - tested on Raspberry Pi 3B+ with Debian Bookworm
Version 1.0.1
Made the use of exposure control more flexible
Version 1.2
Documentation and Code can be found here:
Your mental model is orthogonal to the intended use
Lets get something simple started and take it from there...
The usual approach is to start recording images at the start of the print. At the end of the print DuetLapse will create a video (you don't need to so so). You tell DuetLapse HOW you want images recorded with the options. These options are in the configuration file. At a broad level, images can be captured by layer, by time or even a combination.
What you were doing with your approach was asking DuetLapse the create a snapshot VIDEO on every layer change. It could not do that (not enough images) so it was spinning its wheels ...
I also suspect there may be other issues with your configuration (your reported delay between layers) but lets start off simply.
Why don't you try this config file - YOU DO NOT NEED TO PRINT . When you start the DuetLapse plugin you should see something like the screenshot below (after a few seconds). It will capture a new image every 10 seconds.
I'm assuming you are using a camera that streams via http. If that's not the case then tell my what you are doing.
-duet <your duet ip address>
-port <something other than 8080 e.g. 8084>
-basedir /opt/dsf/sd/DuetLapse3
-camera1 stream
-weburl1 <your camera stream source e.g. http://192.168.10.140:8090/stream>
-seconds 10
-dontwait
-keepfiles
-restart
-verbose
Make sure you have a working installation. Something like this after about 15 seconds.
Wait until you have over 51 images (Status tab keeps count) - this will take about 8 minutes. You can wave your hand in front of the camera or something to while away the time
Then:
[1] From the DWC interface send M3291 B"DuetLapse3.completed"
[2] Wait 15 seconds or so - video creation can take 10s of minutes with a large number of images.
[3] In DuetLapse UI -- Go to the Files tab - you should see a video has been created. You can click on it.
If there are issues with the above then before I can help - I will need a copy of the log file and configuration file.
You can click on the logfile from the Files Tab and it will download via your browser.
When you have this verified - come back here and I can give you a couple of changes to config and let you loose on a print job.
ALSO _ PLEASE USE THIS VERSION OF THE PLUGIN. I have been making some minor changes and introduced a bug. I am not sure what I had done / not done with the version I posted a few days ago.
Just a quick note: I am putting some finishing touched to a plugin that supports USB cameras. It should be ready in a few days . I've always found motion can be somewhat heavy in terms of CPU load (its got a lot built into it).
This plugin is fairly minimal: http endpoint, scaling(8 resolutions), rotate (90, 180, 270) and format choices (most will use the default MJPEG).
Its based on an earlier streamer I wrote so it should be pretty robust on day-one.
I'll post details when I'm done.
It won't be for everyone - but I think it has enough for many (and its a plugin )
My test platform is Bookworm and DWC 3.6.0-beta.4
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]
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.