Duetlapse3 "printer is not connected"

stuartofmt

Can you try this please.

Uninstall the existing plugin and install this version. Note that I have made the changes "blind" i.e. do not have access to my printer to test them.
There are two changes:

I added some defensive / debug code to the section that is checking the board version.
No matter what the results of above - I am forcing a valid version to be returned. This should (hopefully) mean that DuetLapse3 continues on its merry way

In either case - there should be more information in the logfile and I can try to determine what the root cause is. Please post the logfile when you are able.

Note: you will need to remove the .txt extension from the attached file.

DuetLapse3-5.3.0.zip.txt

Aurimas

@stuartofmt

Good news - we have progress
so now it is connected and it is even taking pictures.
the only problem is that it is taking images while the printer is idle (that was when the interval was set to 30s)
once I changed to layer detect it is still running but not taking images on its own.

also why do I have detect layer still enabled?
2023-07-21 09:01:12,302 - MainThread - -seconds = 30
2023-07-21 09:01:12,303 - MainThread - -detect = layer

even though it is not in the config.
-weburl1 http://192.168.1.128:8084/stream
-seconds 30
-verbose
startup.txt

DuetLapse3 Version 5.3.0
Connected to printer at: 192.168.1.128:8082

Process Id: 6407
Last Update: Friday - 08:53
Capture Status:= Waiting
DuetLapse3 State:= start
Duet Status:= idle
Images Captured:= 0
Current Layer:= None

stuartofmt

@Aurimas said in Duetlapse3 "printer is not connected":

@stuartofmt

Good news - we have progress
so now it is connected and it is even taking pictures.

Excellent - I now see where the problem lay and had fixed it but not promoted it to to the correct github folder (beta and non-beta variants are different). I'll do some tidy-up and (likely next week) create an updated version.

the only problem is that it is taking images while the printer is idle (that was when the interval was set to 30s)

This is expected with both -detect none and -seconds [some number] There is a message in the earlier log informing that this is equivalent to -dontwait.

once I changed to layer detect it is still running but not taking images on its own.

With no -second setting and -detect layer the first image will not be captured until after layer 1 of the print job (also the logfile name will be changed reflect the printjob name).

also why do I have detect layer still enabled?
2023-07-21 09:01:12,302 - MainThread - -seconds = 30
2023-07-21 09:01:12,303 - MainThread - -detect = layer
even though it is not in the config.

The default for -detect is layer
DuetLapse has expanded its capabilities over time and some values reflect previous defaults. The documentation is fairly comprehensive.

Enjoy! If there are any further issues, let me know.

Aurimas

@stuartofmt thank you.

few more issues maybe bugs

delete files buttons are not available until you restart the plugin
video continues to build up, rather than restarting with every job.

stuartofmt

@Aurimas
Whooops - looks like I recently introducted a bug. Thanks for pointing this out. I should be able to fix it quickly.

stuartofmt

@stuartofmt
I just did a quick check and it seems to be working ok BUT I'm not convinced as I have seen some strange behavior in the past. Mostly to do with video creation. Sometimes its difficult to trap errors ...

Do you have the logfile? How many images did / do you have ?

What version of ffmpeg are you using ?
ffmpeg -version

Also - was this a print job that completed normaly or did you use the UI terminate --> graceful terminate ?

stuartofmt

@Aurimas

I did introduce a bug last week. Payback for not being able to test changes with a printer !!! I dragged and dropped a ( to a different part of a logical expression (that I was not editing) and, of course, it was no longer logical. Had me scartching my head for quite a while

While I was investigating, I spotted a possible timing / race condition with large image counts. May or may not have occured in nature but best avoided. The main visual difference is that a graceful terminate from the UI no longer has a popup confirming the video was created.

Both of these would have caused the lack of delete buttons since the program thought it was still capturing the current print job.

The delete buttons now work as expected but note that it may take several minutes, while the video is being created, for them to appear.
This, especially if there are a lot of images to process.

I've run many hrs of test and all seems well. Version 5.3.2 for beta.4 is here:

https://github.com/stuartofmt/DuetLapse3/blob/main/plugin/3.5.0-beta.4/DuetLapse3-5.3.2-3.5.0-beta.4.zip

Aurimas

@stuartofmt

thank you. will test it now. if any issues I will let you know

Aurimas

@stuartofmt is there a setting to start new video with new print?
right now it keeps recording the images under the same folder

stuartofmt

@Aurimas said in Duetlapse3 "printer is not connected":

@stuartofmt is there a setting to start new video with new print?
right now it keeps recording the images under the same folder

It depends a lot on the settings you already have. The documentation is pretty comprehensive but there is a lot of it

Can you explain the sequence of events and the settings you have? I can then explain how it should work with those settings.

For example, if you have seconds > 0 and dontwait (explicit or logical) and are not in 'standby' then after the prior print: images will continue to be captured eveny 'n' seconds and placed in a folder. When you start the next print job, the folder (and logfile) will be renamed to the name of the print job (keeping the accumulated images). I suspect this is what you are seeing.

There are a couple of ways to change the behavior e.g. using -standby in the options will stop capture after the print job (no matter other settings). It does require a 'start' (from the UI or otherwise) at the start of the print job to allow.

If you are not using seconds and just using -detect layer and not using -standby then at the end of the print job, no images will be captured until the start of the next print job (and folders / logs get renamed with the jobname)

Another way is to send messages to DuetLapse3 to finely control the behavior using gcode. This is what I do

In 3.4.5 the M291 message command was used but recent changes in Duet3d firmware mean that does ot work as well as I would like. I'm finishing a custom alternative (likely today) and can walk you through it if yo like ?

Aurimas

@stuartofmt
for some reason when I click on the video now I get this message:
192.168.1.128 sent an invalid response.

stuartofmt

@Aurimas

Please start a new thread and include a logfile with -verbose set

Aurimas

@stuartofmt i think the issue might be with the length of the name. is there anyway to rename files?

stuartofmt

@Aurimas said in Duetlapse3 "printer is not connected":

@stuartofmt i think the issue might be with the length of the name. is there anyway to rename files?

@Aurimas

Please start a new thread. i.e. something other than "printer is not connected" (since this issue is solved).

Include a logfile with -verbose set together with a clear description of the problem and I'll take a look.

Aurimas

@stuartofmt so the plugin keeps crashing - starts fine then after a little while crashes.
sometimes it is possible to restart from plug in section and sometimes need to reboot Pi.
Log file is attached.
it happens fairly often

807_1_VEGA600_400-1581-01-A.txt

stuartofmt

@Aurimas
Please see my post above. Others cannot benefit when you add a new problem to an existing (solved) problem.

When you repost - I will try to assist.

Aurimas

@stuartofmt done