DuetLapse3

stuartofmt

@stuartofmt

https://i.postimg.cc/5tGyZb6j/duetlapse.png SBC installation doesnt work.

It's currently set to require R3.4.5 because that is the latest stable release and the release I tested on.

I'm not sure if it would even work on the 3.5 beta releases. I'll rebuild it (likely tonight) with a requirement of > 3.4.5 and make a note on the tested release.

I'll let you know when its done.

jay_s_uk

@stuartofmt I think things have changed a fair bit between 3.4.5 and 3.5. @MintyTrebor can probably comment more

MintyTrebor

@stuartofmt You will probably have to re-compile based on the 3.5 src at the very least - there were significant changes from 3.4.5 to 3.5. You may also have to make some changes to your code to make it 3.5 compatible, and it's likely the 3.5 version you make will not be backwards compatible with 3.4.5.

stuartofmt

@MintyTrebor said in DuetLapse3:

@stuartofmt You will probably have to re-compile based on the 3.5 src at the very least - there were significant changes from 3.4.5 to 3.5. You may also have to make some changes to your code to make it 3.5 compatible, and it's likely the 3.5 version you make will not be backwards compatible with 3.4.5.

Thanks - I'll leave the current verson as-is and upgrade to a beta version when I can.

@LuniLAB Its unlikely that I can get to this for a while. You can run DuetLapse3 independently i.e. not as a plugin if you like.

stuartofmt

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.

JonasBaleine

Hi, if I understand correctly, the plugin is only compatible with Duet board with SBC? Not the standalone boards?

stuartofmt

@JonasBaleine said in DuetLapse3:

Hi, if I understand correctly, the plugin is only compatible with Duet board with SBC? Not the standalone boards?

DuetLapse3 can be used either standalone or as a plugin. The code is common to both. The functionality is the same.

See the documentation here:
https://github.com/stuartofmt/DuetLapse3/blob/main/Documents/Getting Started.md

Standalone
DuetLapse3 can be installed (not as a plugin) on a linux or windows machine. DuetLapse uses python and its not possible / practical to run as a plugin on a standalone board.

I recently changed a few file locations for better identification of versions. I just noticed that I have not updated a couple of links in the documentation.

For standale on version 3.4.5 DuetLapse3 is here:
https://github.com/stuartofmt/DuetLapse3/tree/main/Release 3.4.5
For standalone on version 3.5.0-beta.4, DuetLapse3 is here:
https://github.com/stuartofmt/DuetLapse3/tree/main/plugin/3.5.0-beta.4/dsf

stuartofmt

@JonasBaleine

Also - if you are using the beta.4 version as standalone, you should copy this macro into your /sys folder

https://github.com/stuartofmt/DuetLapse3/tree/main/plugin/3.5.0-beta.4/sd/sys

JonasBaleine

@stuartofmt Hi, thanks for the reply. I saw that there are 2 versions, the plugin and standalone version. What I meant was: does the plugin version only works when using the duet board in SBC mode? That's what the documentation would lead me to believe. Just wanted to make sure I understood correctly.

stuartofmt

@JonasBaleine said in DuetLapse3:

does the plugin version only works when using the duet board in SBC mode?

The plugin version only works for SBC. The reason is that the "heavy lifting" of DuetLapse3 is all done with Python code. Its not possible / practical to run that code on a standalone board. For standalone, you need to install DuetLapse3 on some computer with network access to the printer. I used to run it this way when I had a Duet2 using a Pi to run DuetLapse3.

You can install not-as-a-plugin with either standalone or SBC. The main advantage of using the plugin (if you are running SBC) is that it simplifies the installation and integrates the UI with DWC. Otherwise the functionality is identical.

JonasBaleine

Hi, is there a plugin version for DSF version 3.4.6? I tried 3.4.5 and 3.5.0-beta.4 and both would not install with 3.4.6. Thanks.

stuartofmt

@JonasBaleine said in DuetLapse3:

Hi, is there a plugin version for DSF version 3.4.6? I tried 3.4.5 and 3.5.0-beta.4 and both would not install with 3.4.6. Thanks.

I have not created a specific version for 3.4.6, quite busy right now

I suspect it might "just work" if I edit the required version in the plugin.json file. There is a way to set a version range (I think) but figuring that out could take time.

Can you try this and let me know if it installs ok? (remove .txt extension)
~~[DuetLapse3-5.2.2.1-3.4.6.zip.txt]~~

P.S. 3.5.0-beta.4 definitely will not work.

JonasBaleine

@stuartofmt Hi, I will try it this weekend and come back to you. Do not worry, I understand being busy. Thanks for all you've done already.

JonasBaleine

@stuartofmt Hi, I installed the plugin and tried to run DuetLapse through terminal using this command:

python3 ./plugins/DuetLapse3/dsf/DuetLapse3.py  -file ./sd/DuetLapse3/DuetLapse3.config

from the /opt/dsf directory on my pi.

Here is the log that was produced startup.txt , saying "The printer at (IP address) needs to be at version 3.4.5".

Let me know if you need more information. Thanks!

Edit:

I changed the duet3DVersion to '3.4.6' in DuetLapse3.py and when I run the same command, I get the following startup.txt

In the DWC, I get partially started as Status when I press the start:

If I run the command above in the terminal, I get this in the DWC, but still only partially started:

stuartofmt

This post is deleted!

stuartofmt

@JonasBaleine

Before we get too far along - I've rebuilt the blugin against the 3.4.6 release (attached at end).
In theory there should not have been a difference between 3.4.5 and 3.4.6 from a plugin perspective but ...

Regarding the version numbers. In the beta / rc versions I require a complete match because there can be some sensitivity. I was not thinking when I set the version number in 3.4.5. It should have been 3.4 which will match any release in that series. I've corrected this in the version above (The only change to DuetLapse3 I made).

Regarding the start issue. The fact that it shows as only partially started when you run it from the terminal is, I think, to be expected based on the underlying plugin framework. What we should focus on is what happens when installed as a plugin and run as a plugin.

From the logfile I see
-duet = c3po.local . The connection to the printer is successful, so that part is good.

For -weburl1 = http://c3po.local:8081/0/stream its hard to tell because its likely not tried to capture any images.

If the problem persistes with the above build .....

From a browser on the pi does http://c3po.local:8081/0/stream display your video feed?
The logfile is only partial - can you run it with -verbose as that will capture most errors seen by the program.
In a console: run the following command before trying to start the plugin and monitor for errors. sudo SYSTEMD_LESS=RXMK /usr/bin/journalctl -f

~~[DuetLapse3-3.4.6--5.2.2.1.zip.txt~~]

JonasBaleine

@stuartofmt Hi, I downloaded the new version you provided and installed it. When I start it, it says "started" for a few seconds, then "partially started".

To answer your questions:

Yes, http://c3po.local:8081/0/stream display my video feed, on the pi, on my pc, in the Webcam tab of the DWC.
-verbose is already in my DuetLapse3.config.txt file. Starting the plugin does not seem to create a startup.log file.
When I run the command in the terminal and start the plugin, I get this result: Errors.txt saying PermissionError: [Errno 13] Permission denied: '/opt/dsf/sd/DuetLapse3/C3PO/c3po-local/startup.log'

I tried stopping Motion Webcam Server, but it did not solve the issue.
I tried adding my Raspberry Pi password to the config file with -password, but it did not solve the issue.

Thanks again, I appreciate the help.

stuartofmt

@JonasBaleine said in DuetLapse3:

Thanks for the quick turnaround. This is looking like a permissions issue as opposed to a code issue. Lets see ...

@stuartofmt Hi, I downloaded the new version you provided and installed it. When I start it, it says "started" for a few seconds, then "partially started".

This makes sense given the problems below.

-verbose is already in my DuetLapse3.config.txt file. Starting the plugin does not seem to create a startup.log file.

That seems wierd - the location for the config file should be /opt/dsf/sd/sys/DuetLapse3/DuetLapse3.config. Using DWC - Did you create a folder off your sys directory called DuetLapse3 and place your config file there ?
This is set by -basedir = /opt/dsf/sd/DuetLapse3. If you have those folders/files set up - this error is possibly related to the permission issue described below.

When I run the command in the terminal and start the plugin, I get this result: Errors.txt saying PermissionError: [Errno 13] Permission denied: '/opt/dsf/sd/DuetLapse3/C3PO/c3po-local/startup.log'

This looks to be a a permissions error. I dont know where the /assets/ ... path comes into it. Its certainly not in the DuetLapse3 code. The /assets folder does not even exist in my setup. It could be a temp folder and we are seeing it because of the error.

All the files under /opt/dsf should be owned by dsf:dsf. I've seen several times now where the strange permissions were set when installing SBC using these instructions. https://docs.duet3d.com/User_manual/Machine_configuration/DSF_Other

Take a look in /opt/dsf and confirm all the files / folders have the correct permissions.

I've had to fix it by uninstalling the plugin, running the following, then reinstalling the plugin

cd /opt/dsf
sudo chown -R dsf:dsf *

I've reported it and hopefully its something that can be fixed.

I tried adding my Raspberry Pi password to the config file with -password,

The config file only requires a -password if you have set a password for your printer and is only used for connecting with the printer. Its not used for the file / folder structure.

JonasBaleine

@stuartofmt Hi, thanks for the quick reply. Yes, I did create a folder in System and then created the config file inside it.

By trying a few things, I realised that my Pi failed to fetch updates with sudo apt update, so I reflashed the Pi, following the steps https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup again. Now it works when I start the plugin.
Thanks for all your help, I really appreciate it.

JonasBaleine

Hi @stuartofmt, its me again. I have everything working properly now, but I am wondering if there is a way that DuetLapse3 would not automatically resume a print if I manually paused it or paused by a filament sensor? Thanks!