DuetLapse available for Alpha testing

Danal

@zapta said in DuetLapse available for Alpha testing:

Edit: a feature idea, include automatically music in the generated video.

Probably going to let people do that in post-processing.

PaulHew

@Danal
It has stopped processing at image46 out of 200.
I had this issue with the other Timelapse, and dropped the resolution of the images.
Is there somewhere I can tweak the resolution?

I am not a Python Guru, my skills lie elsewhere.

Regards,
Paul.

PaulHew

@Danal
Following on, I added the -q 25 to the DuetLapse.py for the Raspistill

        cmd = 'raspistill -o -q 25 '+fn

I am getting some errors and it seems to be taking pictures whilst my bed leveling is happening

End of print will be sensed, and frames will be converted into video.
Capturing frame     0 at X25.00 Y25.00 Z117.31
Invalid command line option (25)
Capturing frame     1 at X25.00 Y25.00 Z121.31
Invalid command line option (25)
Capturing frame     2 at X-10.00 Y25.00 Z117.31
Invalid command line option (25)
Capturing frame     3 at X-10.00 Y25.00 Z121.31
Invalid command line option (25)
Capturing frame     4 at X-10.00 Y-8.00 Z117.31
Invalid command line option (25)
Capturing frame     5 at X150.00 Y150.00 Z122.31
Invalid command line option (25)

zapta

@Danal said in DuetLapse available for Alpha testing:

This is already implemented. Add -movehead 10 15 to flags that either detect or force pauses. The numbers are X and Y respectively.

Very nice! You are doing magic with network connections to the Duet.

zapta

@Danal said in DuetLapse available for Alpha testing:

Not a bad idea. I will add that to the "to do" list.

While you do it you can add other visual indicators such as Z height, and filament used.

Danal

@PaulHew said in DuetLapse available for Alpha testing:

@Danal
Following on, I added the -q 25 to the DuetLapse.py for the Raspistill
        cmd = 'raspistill -o -q 25 '+fn
I am getting some errors

Yes, those errors are from the flag you added. Don't add a flag between -o and the file name.

Also, the raspistill default is 35, so there is not much point in overriding to 25, that's not all that different.

and it seems to be taking pictures whilst my bed leveling is happening

If you have a bed leveling command in the print job, then yes, it will be capturing pictures, because the printer is running a job.

If you are manually initiating the bed leveling, do not start the script until after you bed level, but before you start the print job.

If there is some other situation, let me know.

Danal

@PaulHew said in DuetLapse available for Alpha testing:

@Danal
It has stopped processing at image46 out of 200.
I had this issue with the other Timelapse, and dropped the resolution of the images.
Is there somewhere I can tweak the resolution?

I am not a Python Guru, my skills lie elsewhere.

Regards,
Paul.

What camera? What command did you issue to start the script?

Danal

@zapta said in DuetLapse available for Alpha testing:

@Danal said in DuetLapse available for Alpha testing:

Not a bad idea. I will add that to the "to do" list.

While you do it you can add other visual indicators such as Z height, and filament used.

Keep the ideas coming!

PaulHew

@Danal said in DuetLapse available for Alpha testing:

What camera? What command did you issue to start the script?

Morning Danal
I used ./DuetLapse.py -camera pi -duet 192.168.0.7

PaulHew

Using -q 40 with the other TL program my filesizes are ...

This is the line it used.

raspistill -bm -q 40 -w 640 -h 480 -o $snapshot && curl -X POST http://localhost:8000/snapshot -d '{"name":"'$snapshot'"}'

These are the sizes of the files using DuetLapse

I was getting 'malloc' errors with the other program and it would fail when running the FFMPEG but when I dropped the filesize using the -q it worked. Do not know if the 640x480 had a part in it also.
I can try if it helps you.

As I previously mentioned, I am not a Linux / Python guru, just trying to help and fix things myself and also contribute.

Regards,
Paul

chas2706

@Danal

Absolutely brilliant. It works a treat.
Fantastic work!

Danal

@PaulHew You can add the -q 25 (or whatever you wish to try), just put it before the -o. Or, more correctly, not between the -o and the filename.

At this moment, none of my Pi cameras can reach to see a printer. Ribbon too short. I have some longer ribbon, and an Arducam, on the way. Amazon keeps moving the date (which I totally understand). I'll be able to fine tune this more when I receive that stuff.

Meanwhile, keep the specifics coming! (And, you are a lot more of a Guru than you think)

gtj0

Just about to try it but noticed that it seems to be opening and closing the unix socket twice a second. Not usually an issue except I run the DCS with debug logging so it's kinda distracting. Any chance of just keeping the socket open or better yet, just getting the model updates as they happen?

gtj0

Getting

# python3 ./DuetLapse.py -camera usb -duet 127.0.0.1 -seconds 5 -detect none
Attempting to connect to printer at 127.0.0.1
Connected to a Duet V3 printer at http://127.0.0.1

##################################
# Options in force for this run: #
# camera   = usb                 #
# printer  = 127.0.0.1           #
# seconds  = 5.0                 #
# detect   = none                #
# pause    = no                  #
# movehead =   0.00   0.00       #
##################################

Waiting for print to start on printer 127.0.0.1
Print start sensed.
End of print will be sensed, and frames will be converted into video.
Capturing frame     0 after 1586032541.73 seconds elapsed.
Unable to find a compatible palette format.
Capturing frame     1 after 5.01 seconds elapsed.
Unable to find a compatible palette format.

Nothing written to /tmp/DuetLapse.

Any ideas?

Danal

Which USB camera?

Danal

@gtj0 said in DuetLapse available for Alpha testing:

Just about to try it but noticed that it seems to be opening and closing the unix socket twice a second. Not usually an issue except I run the DCS with debug logging so it's kinda distracting. Any chance of just keeping the socket open or better yet, just getting the model updates as they happen?

It doesn't touch the unix socket. It is opening and closing a websocket connection, and not persisting it. This was a design choice in startup to not track state. I will look into persisting that connection.

zapta

@Danal said in DuetLapse available for Alpha testing:

Keep the ideas coming!

Danal, here is an idea, not necessary specific for this timelapse app, but since you know how to monitor the duet during printing and generate visualization, would be interesting to have something that plot the different time left estimations that the Duet provides.

Think of an x/y graph. X is print time from 0 to total print time T. Y is the time left for completion. The ideal reporting is a straight line from (0,T) to (T,0). And then you can sample the duet and plot the time left graphs by the various methods the Duet uses.

The output can be an actual graph or a csv file that can be plotted with a spreadsheet and the likes.

gtj0

@Danal said in DuetLapse available for Alpha testing:

Which USB camera?

Teslong USB "Endoscope". It only supports MJPEG as a palette and I just noticed that you've got YUYV hard coded on the fswebcam command line. Maybe don't specify '-p' and let it default?

@Danal said in DuetLapse available for Alpha testing:

@gtj0 said in DuetLapse available for Alpha testing:

Just about to try it but noticed that it seems to be opening and closing the unix socket twice a second. Not usually an issue except I run the DCS with debug logging so it's kinda distracting. Any chance of just keeping the socket open or better yet, just getting the model updates as they happen?

It doesn't touch the unix socket. It is opening and closing a websocket connection, and not persisting it. This was a design choice in startup to not track state. I will look into persisting that connection.

Ah yeah, the websocket will result in the same messages. It's not critical so don't spend all that much time on it.

Danal

@gtj0 said in DuetLapse available for Alpha testing:

Teslong USB "Endoscope". It only supports MJPEG as a palette and I just noticed that you've got YUYV hard coded on the fswebcam command line. Maybe don't specify '-p' and let it default?

I think I did that and it required it for some reason. I will try a couple of different things to get it as automatic as possible.

kingfisher

Thanks for sharing I. I'll try installing this in whilst in lockdown.
I had an idea to use a pi remotely to control RGB LEDs based on the printer status. (eg red = heating, white = printing, green = finished)
I might try and learn how to do this based on your code/logic