Duetlapse3 "printer is not connected"
-
@Aurimas
Whooops - looks like I recently introducted a bug. Thanks for pointing this out. I should be able to fix it quickly. -
@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 -versionAlso - was this a print job that completed normaly or did you use the UI terminate --> graceful terminate ?
-
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:
-
thank you. will test it now. if any issues I will let you know
-
@stuartofmt is there a setting to start new video with new print?
right now it keeps recording the images under the same folder -
@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 folderIt 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 > 0anddontwait(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
-standbyin 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
secondsand just using-detect layerand not using-standbythen 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 ?
-
@stuartofmt
for some reason when I click on the video now I get this message:
192.168.1.128 sent an invalid response. -
Please start a new thread and include a logfile with -verbose set
-
@stuartofmt i think the issue might be with the length of the name. is there anyway to rename files?
-
@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?
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.
-
@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 -
@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.
-
@stuartofmt done
