This is a modified version of the original DuetLapse created by Danal Estes.
We should all remember him for his generous work

General Description

DuetLapse3 provides a highly configurable program for creating timelapse videos from printers using the Deut3D software.
It can be run as a one-of or continuously in the background.

It is also available as an SBC plugin.

A companion program startDuetLapse 3 provides administration capabilities and is especially useful if multiple instances of DuetLapse3 are running and connected to multiple printers. This is largely redundant due to continuous improvements in the DuetLapse3 UI and the ability to control DuetLapse3 with gcode instructions.

Details of DuetLapse3 are in this document:

DuetLapse3.md

In addition to a browser interface DuetLapse3 can be controlled directly from gcode.

Controlling with gcode.md

Useage examples are in this document:

DuetLapse3 Useage Examples.md

Version 5.0.0

[1] Completely revised UI
[2] Added display of last captured image to UI
[3] Added ability to specify a config file with -file option This avoids the need for long command lines. Options in command line over-write those in config file
[4] Added -maxvideo. Limits the maximum length of video by varying fps as needed
[5] Added ability to change -fps -minvideo and -maxvideo in the UI
[6] UI gives indication of video creation status
[7] Changed logfile name on startup
[8] Sequential jobs are numbered
[9] Misc bug fixes

Version 5.1.0

[1] Removed the use of M117 messages and replace with M291 messages as this gives much better control.
[2] Set new default, minimum values for -seconds (20) and -poll (10) along with some logic changes to avoid an occassional race condition.
[3] Fixed a code error associated with -extratime
[4] Some minor bug UI / Typo fixes

Version - 5.2.0

[1] Fixed snapshot when called from gcode
[2] Process all M291 messages without delay
[3] Refactored loop control to prevent thread blocking
[4] Prevent first layer capture if -pause yes
[5] Added -password option to support passwords
[6] Released as a plugin for SBC

Code / Detailed Instructions / Documentation are here:

Github

The readme.md file contains the full version history

Please post suggestions for improvement in this forum, not in the github. That way we get the wider, interested audience.

First of all, many thanks to @chrishamm @Falcounet @MintyTrebor and @T3P3Tony for all helping in progressing this plugin. Withouth their combined efforts it would still be where I left it late last year i.e. abandoned.

I'm very pleased to announce the pluging version of DuetLapse3.

The plugin uses the same source as the standalone version of DuetLapse3 but is easier to install than the standalone version. Other than that the standalone and plugin version have the same functionality.

https://github.com/stuartofmt/DuetLapse3/tree/main/plugin

The instructions for installing DuetLapse3 as a plugin are here:
https://github.com/stuartofmt/DuetLapse3/blob/main/plugin/plugin installation guide.md

DuetLapse3 plugin is now available for 3.5.0.beta.3.
This due to the generous assistance of @MintyTrebor

https://github.com/stuartofmt/DuetLapse3/tree/main/plugin

Note that the plugins are specific to the DWC version and are not interchangeable.

Version 2.0.0

Adds support for embedded cameras on the latest Raspberry Pi Release (Bullseye with Libcamera).

See here for full documentation:

https://github.com/stuartofmt/videostream

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.

Modes of operation
There are two modes of operation, depending on whether the archive option is used.

Files deleted from the source are deleted from the main branch (default)
The designated directories are compared to the files in the main branch. Files are either Added (new files), Updated (if changed), or Skipped (if not changed). Files that have been deleted from the designated directories are removed from the main branch. In this way, the main branch is a snapshot of the designated directories.

If you need to recover to the latest version - a simple download of the top level main branch is all that is needed.

Github history still provides access to previously deleted files.

Files are not deleted from the main branch
The behavior is the same as above, except that files which are deleted from the source are NOT deleted from the main branch. This makes recovery a little more involved.

Prerequisites:
SBC

V3.5.0-rc.1

Tested with Debian Bullseye

Python3

To use the plugin:

1- Create a new repository (Private is recomended) on Github. Include a Readme.md file. Take note of the name of the repository (including case) as well as the branch, which will usually be main.

2- Create a personal access token token. A classic token with "repo" authorization is sufficient. Instructions for creating a token can be found here:
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens

3- Create(using DWC) a file System/duetBackup/duetBackup.config details are in the file Config Notes.

4- Install the plugin using the plugin.zip file from here:
https://github.com/stuartofmt/duetBackup

5- To create an initial backup, set -days 0 and -hours 0. This will run duetBackup once. After that, set -days and -hrs to your prefered backup interval. Note that if there are no changes to any files, backup does nothing.

Versions

V1.0

• Initial release

V1.1

• Added messages, sent to DWC
• Displays time to next backup using local time (previously GMT)
• Added -duetPassword to support for printers that use a password
• Added -verbose to enable more detailed log messages.

V1.2

• Added -noDelete option
• Compares files to determine if an update is needed.
• Added date / time of last change to file (except initial save).

V1.3

• README.md file shows date and time of last backup
• README.md prevented from being deleted
• Added -ignore. Can specify files that are not to be backed up. This also causes these files to be deleted unless -noDelete is set.

This program allows monitoring of Duet status codes and display messages.

It runs in the background and periodically polls Duet looking for changes to the specified status values. It can also monitor changes in display messages.

When it detects a change - it sends an email. Changes are detected when entering AND leaving a status. In this way - you can monitor a single status and detect changes to that status. You can, of course, monitor multiple status.

DuetMonitor is designed to run continuously and can accept http commands to change settings. Typically, you would use a browser but curl or other means of sending http can be used.

emails are sent from your gmail account to any recipient with a legal email address. It is intended for short messages.

###Version 1.0.0

[1] Initial version

###Version 1.0.1

[1] Added monitoring of info messages

[2] Added additional Controls

[3] Provided additional information in browser UI

General Description
The main capabilities include:

Send emails using your gmail address.
Can send to any legitimate email recipient.
Is controllable via a browser (or other http) interface (e.g. curl)
Is dynamically configurable for the values that it monitors.
Reports if disconnected (for more than 2 polling intervals) from Duet and stops monitoring.
Because it can also monitor display messages - you can embed M117 Messages in your gcode and macros (e.g. at the start and end of printing, at key points in a calibration macro) and receive an email in a customizable manner.

DuetMonitor is intended to run constantly (if you wish) in the background.
From a http interface (e.g. browser) you can perform the following:

Start / Stop monitoring
Change the To: and Subject:
Change which values (status, display messages, info messages) are being monitored
Send an email independently of monitoring
The ability to just send an email (does not need to be monitoring) makes it useful in conjunction with other programs such as DueUI and BtnCmd and ....

I selected gmail as the delivery mechanism because:

1. It is widely used and reliable.
2. Is secure and avoids many possible miss-use situations.
3. You can easily get an account if you do not already have one (even if you only use it for DuetMonitor).
4. You can easily revoke and re-enable permission to send emails if you need to.
5. It is free - unless you want to send 1000's of emails per day

A full set of instructions for installing, creating credentials and initial setup are here:
https://github.com/stuartofmt/DuetMonitor

Note that this version was created for Dueui 3.0.2. Because of a change in the way DWC and hence Dueui now report the object model - this version is not compatible with later versions of Dueui.

I have an Ender 5 with Duet2 Wifi. I have a Raspberry Pi with 7" TFT mounted on the Printer.
I used it to serve up a camera and provide some local control with DWS in the browser on the Pi.
This was a fairly clumsy approach because of the small screen and the lack of touch precision. So I decided to give Dueui a go.

I was after a minimal set of control for the occasions when I was standing, mesmerized, in front of the printer.
DWS on my laptop is, of course, used for more complete control.
Other considerations included:
The Screen I am using is only 800 x 600 pixels.
I did not want to have to scroll up/down or left/right.
The browser (chromium) is used in full screen mode.

Attached is the first version of my configuration.json together with some macro's that I use.
*EDIT - A better version is posted as V3. I have removed the prior versions. *
To get everything working - I had to modify two of the javascript files supplied by @gtj0 who will update those files in due course - I am including the modified dueui.js and dueui_widget.js files as well
I am very happy with the results so far and look forward to improving as I go.
I will explain a little about each of the panes below.

General
The theme I chose is "Darkly" - other themes may affect the layout.
I trimmed the menu bar at the top to make it fit better.
I placed the log / status just above the menu tabs.
Most everything else fits in between.
In V3 - I added output for M117 Messages (not shown in the screen shots) because I liberally sprinkle messages in my macros and gcode.

Printer
This is a really just intended for basic monitoring, stop / start etc.
Because I like to see Nozzle and Bed Temperature that is included.
Babysteps are small i.e. assumed the printer is more-or-less calibrated.

Calibration
The intent here is to provide simple calibration control and monitoring.
I use a Z-Probe (BLTouch) so bed calibration is automagic. The "Calibrate" button calls a macro () that does all the work.
Since I often change hotends - the Z axis offset can change so I have included a capability to measure the offset.
The "Z Adjust Start" button calls a macro () to setup for adjustment using one of the standard techniques.
It first homes all - so after that has happened you can go ahead and adjust the nozzle to the bed to "paper thickness".
When done - pressing the "Done" button performs a single probe (and another home all just because).
The Z offset is reported in the log / status bar and can then be used to adjust your G31 settings.

Heightmap
No changes here - just copied from the sample config file.

Control
Edit - Made some changes so as not to need keyboard and posted as V2. Removed the need for a keyboard
I mainly use this for filament changes and such. Heat up the nozzle etc.
I personally do not use standby and such. In any case, wanted to "unclutter' the UI for this screen.
The config file comments out a second row of nozzle temps and Fan 0 these can be added back in easily if you want.
There is also a control to reposition the bed (Z axis) to specific positions (useful for getting access to the bed).

Console
More or less the same as the sample config file.

NOTE THE FILENAMES GET CHANGED DURING DOWNLOAD SO YOU WILL NEED TO RENAME THEM BACK TO THE ORIGINAL

Config File

config_pi_panel_sofmt_V3.json

Remove the .txt from these two files before using

dueui.js.txt

dueui_widget.js.txt

Macros

AutoProbeCalibration.g

Z-AdjustStart.g

Z-AdjustStop.g

Videostream is a simple, lightweight video streamer for USB cameras, integrated Pi cameras and likely others.

I have noticed that some of us (me too) end up wresting with various software in order to successfully setup video streaming. As well some of the software has a large footprint and in some cases ends up consuming excessive amounts of CPU and other system resources.

Videostream addresses many of these issues by attempting a "goldilocks" solution - not too big/small not too complex - "just right".

It is particularly useful when you want to same video feed to be consumed by more than one application. For example you want to use a timelapse recording recording program and at the same time monitor in real time.

Videostream is designed to run continuously and can accept a http command to terminate the program. Typically, you would use a browser but curl or other means can be used.

It runs on Linux and Windows10 and WSL

###Version 1.0.0

Initial Version

###Version 1.1.0

[1] Improved the detection of size and formats

[2] Can now select a preferred format

[3] Improved the fallback to a lower size if the selected size is not available.

[4] If the preferred format is not available an available format will be used.

###Version 2.0.0

[1] Adds support for embedded cameras on the latest Raspberry Pi Release (Bullseye with Libcamera).

[2] Some internal restructuring to improve performance.

[3] Updated documentation

The main capabilities include:

1. Automatically scans for available cameras and determines the resolutions it / they support.
2. Supports USB cameras (most should work).
3. Supports integrated Pi Camera and likely other integrated cameras (e.g. from a laptop).
4. Is light in its use of system resources
5. Allows camera selection if more than one camera is available.
6. Allows video size selections.
7. Allows video rotation.
8. Allows video format selection

The full instructions for downloading / setup are found here:
https://github.com/stuartofmt/videostream

Its been a while -- I've made updates to both DuetLapse3 and startDuetLapse3.
Included in the documentation are instructions on using DuetLapse3 with the Pi camera on Buster.

Version 3.5.0

Remember to keep DuetLapse3 and startDuetLapse3 at the same release levels

Changes to DuelLApse3

• [1] Changed some system calls to allow for better error handling.
• [2] Fixed an issue with sending gcodes to SBC
• [3] Improved the handling of -pause yes and - movehead
• [4] Added an optional argument -rest that delays image capture after a pause. This is because the camera feed can be delayed with respect to the actual head position.
• [5] Updated documentation with additional notes
• [6] Deprecated the use of -camera pi due to changes in Raspberry Pi (see notes in the section on -camera).
• [7] Added a new argument -nolog and deprecated -logtype. Logging will always use the console unless the program is running in the background.
• [8] If -verbose is used, much more detail is created. Should usually only be used for debugging.
• [9] Added new argument -fps. Sets the default frames-per-seconds
• [10] Added the ability to change the default frames-per-second (fps) from the main menu.
• [11] Added a new argument -hidebuttons. Hides menu buttons that are currently invalid. Otherwise, invalid buttons are greyed out.
• [12] General UI improvements.
• [13] After Snapshot, returns to the previous logical state either 'start' or 'pause'

Changes to startDuetLapse3

• [1] Changed some system calls to allow for better error handling
• [2] Updated documentation with additional notes
• [3] Added a default logfile (startDuetLapse3.log)
• [4] Added a new argument -nolog. Logging will always use the console unless the program is running in the background.
• [5] Added a new argument -verbose. Creates detailed debugging information.
• [6] Failure to start DuetLapse3 (from the UI) is reported with reasons. Successful starts are reported after 30 seconds.
• [7] Shutdown, from the UI, requires confirmation.
• [8] The use of http option nohup=yes is deprecated.
• [9] Added new argument -fps. Sets the default frames-per-seconds
• [10] Added the ability to change the default frames-per-second (fps) when creating a video from the files menu.
• [11] General UI improvements.

First of all, many thanks to @chrishamm @Falcounet @MintyTrebor and @T3P3Tony for all helping in progressing this plugin. Withouth their combined efforts it would still be where I left it late last year i.e. abandoned.

I'm very pleased to announce the pluging version of DuetLapse3.

The plugin uses the same source as the standalone version of DuetLapse3 but is easier to install than the standalone version. Other than that the standalone and plugin version have the same functionality.

https://github.com/stuartofmt/DuetLapse3/tree/main/plugin

The instructions for installing DuetLapse3 as a plugin are here:
https://github.com/stuartofmt/DuetLapse3/blob/main/plugin/plugin installation guide.md

@oliof said in Create a virtual temp. sensor based on average of multiple?:

another option would be to wire the sensors in parallel and adjust the reference resistance accordingly (halving it if my memory of Ohm slaw is correct).

If you want to go that route - then maybe 4 thermistors. Two in series and then wire those two in parallel. That way the nominal resistance would be the same as just one.

I do have to ask though: what is your objective (in real day-to-day terms)?

With reasonable stable conditions (i.e. no breeze across the bed) you'd expect the bed to reach a steady-state and more-or-less have a consistent distribution of temperature.

Is the complexity you are considering providing an advantage compared with (say): Manually take the temperature at different parts of the bed and compare to the desired temperature - create a simple lookup table. Use that knowledge (moving forward) to infer the average temperature from the reported temp given by a single sensor.

@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

@chrishamm

Figured it out. I omitted src/index.js for the plugin (possibly during a copy / paste) . The build thought it had suceeded but it failed silently.

@chrishamm

I'm cannot figure out what's actually going on ...
This call .run("build", {}, ["build"]) (near the start of the build-plugin.js script) does not create files for the plugin in the dist/css/ or dist/js/ directory. This, obviously causes a downstream failure, specifically no zip file being created.

The script goes through the "Building for production" dance BUT does not report any errors.

Anyway to modify the script so that it reports errors ?

When I try to build a plugin with 3.5-dev, I get an error ' ERROR No Webpack chunks have be added to the ZIP archive.`. Any idea why? I can build in 3.4.6 OK.
This is on Win11.

There is no zip file is created.

When I first build the dev environment, npm run serve runs without errors.

After trying to build the plugin: If I try npm run serve again, I get the following error. It seems that the act of trying to build a plugin changes something ...

C:\Users\stuar\Github\DWCv3.5-dev>npm run serve

> duetwebcontrol@3.5.2-rc.1 serve
> vue-cli-service serve

 INFO  Starting development server...
 ERROR  AssertionError [ERR_ASSERTION]: Missing entry point (index.js, index.ts, dwc-src/index.js, dwc-src/index.ts, src/index.js, src/index.ts) in plugin DuetLapse3
AssertionError [ERR_ASSERTION]: Missing entry point (index.js, index.ts, dwc-src/index.js, dwc-src/index.ts, src/index.js, src/index.ts) in plugin DuetLapse3
    at C:\Users\stuar\Github\DWCv3.5-dev\webpack\lib\auto-imports-plugin.js:54:17
    at Hook.eval [as call] (eval at create (C:\Users\stuar\Github\DWCv3.5-dev\node_modules\webpack\node_modules\tapable\lib\HookCodeFactory.js:19:10), <anonymous>:9:1)
    at Hook.CALL_DELEGATE [as _call] (C:\Users\stuar\Github\DWCv3.5-dev\node_modules\webpack\node_modules\tapable\lib\Hook.js:14:14)
    at createCompiler (C:\Users\stuar\Github\DWCv3.5-dev\node_modules\webpack\lib\webpack.js:86:28)
    at create (C:\Users\stuar\Github\DWCv3.5-dev\node_modules\webpack\lib\webpack.js:145:16)
    at webpack (C:\Users\stuar\Github\DWCv3.5-dev\node_modules\webpack\lib\webpack.js:173:32)
    at f (C:\Users\stuar\Github\DWCv3.5-dev\node_modules\webpack\lib\index.js:73:16)
    at serve (C:\Users\stuar\Github\DWCv3.5-dev\node_modules\@vue\cli-service\lib\commands\serve.js:185:22)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Full output from plugin build attempt below

C:\Users\stuar\Github\DWCv3.5-dev>cmd.exe /c npm run build-plugin "../DuetLapse3/pluginv3.5-dev"

> duetwebcontrol@3.5.2-rc.1 build-plugin
> node scripts/build-plugin.js ../DuetLapse3/pluginv3.5-dev

All browser targets in the browserslist configuration have supported ES module.
Therefore we don't build two separate bundles for differential loading.


/  Building for production...[BABEL] Note: The code generator has deoptimised the styling of C:\Users\stuar\Github\DWCv3.5-dev\node_modules\vuetify\dist\vuetify.js as it exceeds the max of 500KB.
-  Building for production...

 DONE  Compiled successfully in 236835ms                                                                      1:56:47 PM
  File                                        Size                                Gzipped

  dist\js\monaco-editor.54de9d18.js           4748.92 KiB                         1058.10 KiB
  dist\js\app.fc942cc4.js                     3764.19 KiB                         816.44 KiB
  dist\js\GCodeViewer.2c2d2e4a.js             2699.53 KiB                         590.23 KiB
  dist\js\HeightMap.0a7868ce.js               1464.97 KiB                         316.40 KiB
  dist\js\OnScreenKeyboard.08821710.js        106.99 KiB                          33.03 KiB
  dist\js\InputShaping.3edf6046.js            81.09 KiB                           17.29 KiB
  dist\js\ObjectModelBrowser.b7c78d60.js      25.50 KiB                           6.78 KiB
  dist\workbox-6567b62a.js                    14.11 KiB                           4.93 KiB
  dist\js\monaco-json-worker.1cd76b1b.js      2.80 KiB                            1.01 KiB
  dist\js\monaco-worker.6d781179.js           2.79 KiB                            1.00 KiB
  dist\service-worker.js                      2.16 KiB                            1.01 KiB
  dist\css\app.1e72278e.css                   768.96 KiB                          107.11 KiB
  dist\css\monaco-editor.bda37737.css         112.91 KiB                          18.12 KiB
  dist\css\GCodeViewer.5c28e225.css           14.26 KiB                           2.96 KiB
  dist\css\ObjectModelBrowser.562feac3.css    6.60 KiB                            1.24 KiB
  dist\css\OnScreenKeyboard.425af7fa.css      3.53 KiB                            1.13 KiB
  dist\css\HeightMap.6241cfd5.css             0.49 KiB                            0.24 KiB
  dist\css\InputShaping.bd3578ab.css          0.44 KiB                            0.24 KiB

  Images and other types of assets omitted.
  Build at: 2024-06-10T19:56:48.845Z - Hash: 030dae31db75d394 - Time: 236835ms

 DONE  Build complete. The dist directory is ready to be deployed.
 INFO  Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html

 ERROR  No Webpack chunks have be added to the ZIP archive. Make sure it is imported by src/plugins/index.ts

@droftarts said in manual/Tuning/Tool_changing:

@stuartofmt from the 3.5 release notes https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x :

• When RRF needs to deploy a Z probe ...

Ian

I'll take another look as soon as I get the chance. This was not the behavior in one of the 3.5 rc's - hence the workaround. I've not checked for a while - will report back as soon as I can.

@droftarts @luca-Massimiliano

If you are using a common (i.e. same for each tool) BLTouch or similar: it might be worth checking to see if you also need to add deployprobeN.g and retractprobeN.g

I'm not entirely sure if its fixed / working as intended and may depend on the firmware version you are using.
I had to add them even though they only call deployprobe.g and retractprobe.g

@chrishamm @Falcounet

@chrishamm @Falcounet

It looks like I have some work to do. I've not dug deeply into it yet but it seems Bookworm does not like pip3 and would prefer / needs to use pipx.
I can check versions of Debian and make the appropriate differences transparent to the install program. I just need a few days to carve out some spare time and then it will mostly be testing.

EDIT: Looks like using apt is the prefered way ...

If I'm missing something obvious here, that you have already encountered / resolved, please let me know.

I've created a chatroom to take any implementation discussion off-line. I'm progressing on the basis of providing each python plugin with its own virtual environment.

@chrishamm @Falcounet

It looks like I have some work to do. I've not dug deeply into it yet but it seems Bookworm does not like pip3 and would prefer / needs to use pipx.
I can check versions of Debian and make the appropriate differences transparent to the install program. I just need a few days to carve out some spare time and then it will mostly be testing.

EDIT: Looks like using apt is the prefered way ...

If I'm missing something obvious here, that you have already encountered / resolved, please let me know.

@Ant1 @chrishamm @Falcounet

Sorry - for some reason I have not been getting notifications about this thread until today.

I will take a look at the installation script to see if it can be improved but ...

Please note that it's all a bit "vague". By that I mean there is no sure-fire way to check versions across all libraries. It depends too much on how the author chose to identify (or not) versions.

Regarding the use of exec. I was being a bit lazy but at the same time its limited to calling version. I'll take a closer look.