random Duet3 + SBC questions...

A Former User

@garyd9 said in random Duet3 + SBC questions...:

I currently use a script from @resam for webcam timelapse videos. That script relies on being able to open a telnet port to the duet to see layer change notifications (via "M118 P4 S"..." gcodes inserted by the slicer.) This won't work with the Duet3/SBC combination due to the lack of telnet support. As an alternative, is there any hook in DSF to watch for gcodes, M118 messages, etc? (Is there any documentation available for hooking into DSF?)

lots of ways the simplest may be one of the ones offered here https://forum.duet3d.com/topic/13566/socat-the-guide-to-remote-serial-paneldue-and-telnet-ish
but mind you i found the reliability of socat + codeconsole to be lacking, pending further investigation

i suspect Danal will come up with a more involved, but cleaner and more reliable option

garyd9

@Danal

The original thread is here: https://forum.duet3d.com/topic/6058/timelapse-pictures-videos-with-duet-and-webcam-on-layer-change

The gcode inserted by the slicer is: M118 P4 S"LAYER CHANGE"

Here's a link to the python script hosted on github by the author: https://github.com/Kriechi/DuetRRF-timelapse/blob/master/timelapse.py

It basically just opens a telnet port to the duet and waits for the string "LAYER CHANGE". On seeing that, it saves a snapshot from the PiCam.

I could easily reproduce this in another language (including C#/.Net.) What I'd like to avoid, however, is having to parse EVERY gcode command in a .g file while it's being sent to the Duet3. (The impression I got from reading the DSF docs is that I can't filter that stream...)

dc42

@garyd9 said in random Duet3 + SBC questions...:

I could easily reproduce this in another language (including C#/.Net.) What I'd like to avoid, however, is having to parse EVERY gcode command in a .g file while it's being sent to the Duet3. (The impression I got from reading the DSF docs is that I can't filter that stream...)

The command has already been parsed for you when you intercept it. All you need to do is check whether the command letter and command number are a combination that interests you. If not, just pass it on.

Danal

I believe there is an easier way. Take the script that currently connects to telnet, strip all the telnet socket stuff out, and make it read stdin. Then, run it on the SBC with: sudo journalctl -fu duetcontrolserver | timelapse.py (which could itself be a one line shell script)

There is one other small change required: The M118 P4 that currently get embedded need to be M118 P0 to hit the log that the above command is scanning.

Does that make sense? And/or do you need me to make that version of the scripts?

garyd9

@Danal said in random Duet3 + SBC questions...:

I believe there is an easier way. Take the script that currently connects to telnet, strip all the telnet socket stuff out, and make it read stdin. Then, run it on the SBC with: sudo journalctl -fu duetcontrolserver | timelapse.py (which could itself be a one line shell script)

There is one other small change required: The M118 P4 that currently get embedded need to be M118 P0 to hit the log that the above command is scanning.

Does that make sense? And/or do you need me to make that version of the scripts?

It does make sense. I'm wondering what the "M118 P0" will do in DWC, though...

A Former User

@Danal said in random Duet3 + SBC questions...:

The M118 P4 that currently get embedded need to be M118 P0 to hit the log that the above command is scanning.

does this have a version requirement? haven't updated in a while, but M118 did not show up in journalctl regardless of P

A Former User

@garyd9 said in random Duet3 + SBC questions...:

I'm wondering what the "M118 P0" will do in DWC, though...

seems to vary. if executed in dwc console it shows in dwc, if executed elsewhere it does not. (at least on the version i tried)

Danal

Within a running job, it logs to the correct log on the SBC for the commands I was proposing.

It also logs to DWC, log and popup.

Danal

@bearer said in random Duet3 + SBC questions...:

@Danal said in random Duet3 + SBC questions...:

The M118 P4 that currently get embedded need to be M118 P0 to hit the log that the above command is scanning.

does this have a version requirement? haven't updated in a while, but M118 did not show up in journalctl regardless of P

Maybe. I am on:

DSF Version: 1.2.3.1

Wally

@Danal
Not being super python savvy, I think it would be very handy if you could provide the modified version of timelapse.py and a bit of instructions on how to setup for others with a Duet3 + SBC. I would be willing to help test/verify/report on my setup. If it helps, I already have MJPG-streamer and FFMPEG setup and running on my SBC (Pi 3).

Danal

I will take a look!

Wally

Just to help complete anyone that come back through this thread:
Danal has a Time Lapse Python script posted here for the Duet 3: https://github.com/DanalEstes/DuetLapse
Also, I have one published for the Duet 3 here: https://github.com/JimsJump/Duet_3_6HC_Time_Lapse
Danal's is more polished for multiple systems where my is more customized to my setup.

Danal

@Wally said in random Duet3 + SBC questions...:

@Danal
Not being super python savvy, I think it would be very handy if you could provide the modified version of timelapse.py and a bit of instructions on how to setup for others with a Duet3 + SBC. I would be willing to help test/verify/report on my setup. If it helps, I already have MJPG-streamer and FFMPEG setup and running on my SBC (Pi 3).

I may have misread this when I replied back on the 18th.

DuetLapse can run on any Pi. Personally, I wouldn't run it on a Pi zero, but it will probably work (very slowly). The Pi on which DuetLapse runs only needs to be able to reach the printer that it is going to monitor or control via the network, and the camera it is told to use. If a command or library is missing, it will tell you how to get it.

To say this same thing phrased another way:

DuetLapse can be run on the Pi in a Duet 6HC + Pi configuration. With no modifications.
DuetLapse does not require running on a Duet 6HC + Pi. It runs on any Pi that has network connectivity to the printer.

Therefore, the instructions are:

Install per https://github.com/DanalEstes/DuetLapse#installation
Perhaps take a look at ./DuetLapse.py -h.
Run.
Enjoy.