I'm pleased to give back to the community with the following script to add timelapse video when using a Duet3 and Raspberry Pi. I am unsure if this will work with a Duet2, but maybe..? if execonmcode works, then yes it will..

example video:
https://vimeo.com/468721949

This one does take some setup, but the payoff is well worth it. Note that this expects the files to be in the following folders as the default:

• timelapse.sh should be in a folder named /scripts located off of the root directory
• a folder named pix must be located in the /scripts folder
• a seed file named timelapse_counter, containing only a -1 must be located in the /scripts folder
• a folder located in the root directory named /timelapse for the output video

Also note that both mjpg_streamer and ffmpeg must be installed on your RPi.

First, here is the service code. I chose M5575.

[Unit]
Description=Duet API listener for Timelapse Video by oozeBot
After=duetcontrolserver.service
Requires=duetcontrolserver.service

[Service]
ExecStart=/usr/local/bin/execonmcode -mCode 5575 -command "./scripts/timelapse.sh %%A %%F"
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

Here is v1.0 of the bash script:

#!/bin/bash
# Timelapse Video by oozeBot (www.oozeBot.com) v1.0 - released 10/15/2020
# Usage: ./timelapse.sh Action FPS
# Example: ./timelapse.sh "Enable/Disable/Make/Remove" "1-30"
# gCode: M5575 A"Enable"     ;Enables timelapse and cleans up the image folder
# gCode: M5575 A"Capture"    ;if enabled, captures a snapshot from the video feed
# gCode: M5575 A"Disable"    ;Disables timelapse
# gCode: M5575 A"Make" F"12" ;Creates a video of the snapshots @ 12fps
# gCode: M5575 A"Remove"     ;Removes all images in the image folder

Action=`echo $1 | tr [a-z] [A-Z] | cut -c1-1`

CounterFile="/scripts/timelapse_counter"
ImageNum=`cat $CounterFile`

if [ "$Action" = "E" ];then
 #Enables timelapse by setting the counter to 0 and removes all images in the image folder
 ImageNum=0
 rm -rf /scripts/pix/*
 echo $ImageNum > $CounterFile
elif [ "$Action" = "D" ] && [ $ImageNum -gt 0 ];then
 #If enabled, disables timelapse by setting the counter to -1
 ImageNum=-1
 echo $ImageNum > $CounterFile
elif [ "$Action" = "M" ] && [ $ImageNum -lt 0 ];then
 #Creates timelapse video at the specified FPS, else defaults to 24
 #This will return an error if no images exist and only works when disabled
 fps=$2
 if ! [[ $2 =~ ^[0-9]+$ ]];then
  fps="24"
 fi
 ffmpeg -framerate $fps -start_number 1 -i "/scripts/pix/%d.jpg" -s:v 1920x1080 -vcodec libx264 -qp 0 -preset veryslow /timelapse/$(date +"%Y_%m_%d_%I_%M_%S_%p").mp4
elif [ "$Action" = "R" ] && [ $ImageNum -lt 0 ];then
 #If disabled, removes all images within the image folder (optional as all images will be removed after restart)
 rm -rf /scripts/pix/*
elif [ "$Action" = "C" ] && [ $ImageNum -ge 0 ];then
 #Increments counter and captures snapshot
 ImageNum=$((ImageNum+1))
 wget http://localhost:8080/?action=snapshot -O '/scripts/pix/'$ImageNum'.jpg'
 echo $ImageNum > $CounterFile
fi

Note all M5575 commands should be preceded by an M400 if you want the extruder to stand still

I put examples in the script of all usage through gCode. For the example video above, in the starting script of my slicer, I've added M5575 A"Enable" to enable timelapse. In my layer change script, I've added M5575 A"Capture". And finally, in the ending script, I've added M5575 A"Disable" to disable.

Why did I do it this way? Because I wanted to process the video outside of the control of the job's gCode - however, you could include the following in the bottom of your ending script to both make the video and clean up the photos: M5575 A"Make" F"12" (whatever FPS you want) followed by M5575 A"Remove". Just be prepared to wait before the job actually completes as it holds in process until the video is done.

I also did it this way so I could adjust the framerate by just running the command with various FPS from DWC..

This was also designed to be added to your daemon.g file using M5575 A"Capture" followed by a G40 S10 (or whatever second delay you want) to make a different type of timelapse. It will only save photos while the timelapse has been enabled using M5575 A"Enable".. so it's safe to just leave in there if you so choose. However, it currently supports layer change or X seconds - not both at the same time. If there was demand, I could add that..

And if there are an ffmpeg experts out there, please feel free to correct my usage of it. What I've used might be overkill or not perfect, but it's working well..

Here's a quick pic of our latest prototype in the enclosure I just finished..

Sneak peak at the enclosure I’ve been throwing together in my spare time for our latest prototype.. am getting excited to wrap this up!

I spent some time on this earlier and thought I'd share my first success with it. This script is something we used with our printers prior to moving to Duet. It is a script I wrote (based off of a bit of info scraped off the internet of Wemo's undocumented API). It interfaces with local Wemo switches, plugs, and dimmers locally without the Cloud. The only caveat is that you have to know all the IPs for your wemos.. we just made dhcp reservations for all of ours.

The script primarily turns Wemos on and off; toggles; and can set dimmer brightness. It can also return the current values as well. However, for this post, I'm going to focus on the gCode implementation I just completed.

Note this service code originally gave me trouble as it turned out "%" had to be escaped as "%%". That may be beneficial for others wanting to implement similar scripts with parameter inputs.

I chose M5555. It has 3 inputs - I, C, & B. I is the IP address of the Wemo (or potentially hostname). C is the command. B is the brightness value for setting a dimmer.

Example usage

M5555 I"192.168.0.123" C"ON"               ; turns on the Wemo
M5555 I"192.168.0.123" C"OFF"              ; turns off the Wemo
M5555 I"192.168.0.123" C"TOGGLE"           ; toggles the Wemo (if off, turn on | if on, turn off)
M5555 I"192.168.0.123" C"SETDIMMER" B"50"  ; sets dimmer to 50%

M5555.service code

[Unit]
Description=Duet API listener for Wemo control
After=duetcontrolserver.service
Requires=duetcontrolserver.service

[Service]
ExecStart=/usr/local/bin/execonmcode -mCode 5555 -command "./scripts/wemo.sh %%I %%C %%B"
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

wemo.sh

#!/bin/sh
# Wemo Control
# Usage: ./wemo_control IP Command
# Example: ./wemo_control 192.168.0.1 ON
# ON/OFF/STATE/PORT/SIGNAL/GETDIMMER/SETDIMMER

IP=$1
COMMAND=$2
BRIGHT=$3
PORT=49152

if [ $IP = "" ];then
 echo "Invalid Command"
else
 PORTTEST=$(curl -s $IP:$PORT | grep "404")
 if [ "$PORTTEST" = "" ];then
  PORT=49153
 fi
 if [ $PORT = 49153 ];then
  PORTTEST=$(curl -s $IP:$PORT | grep "404")
  if [ "$PORTTEST" = "" ];then
   PORT=49154
  fi
 fi
 if [ $PORT = 49154 ];then
  PORTTEST=$(curl -s $IP:$PORT | grep "404")
  if [ "$PORTTEST" = "" ];then
   PORT=49155
  fi
 fi
 if [ $PORT = 49155 ];then
  PORTTEST=$(curl -s $IP:$PORT | grep "404")
  if [ "$PORTTEST" = "" ];then
   PORT=0
  fi
 fi
 if [ $PORT = 0 ];then
  echo "Wemo Unavailable on IP $IP"
 else
  if [ "$COMMAND" = "STATE" ];then
   curl -0 -A '' -X POST -H 'Accept: ' -H 'Content-type: text/xml; charset="utf-8"' -H "SOAPACTION: \"urn:Belkin:service:basicevent:1#GetBinaryState\"" --data '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:GetBinaryState xmlns:u="urn:Belkin:service:basicevent:1"><BinaryState>1</BinaryState></u:GetBinaryState></s:Body></s:Envelope>' -s http://$IP:$PORT/upnp/control/basicevent1 |
   grep "<BinaryState"  | cut -d ">" -f2 | cut -d "<" -f1 | sed 's/0/OFF/g' | sed 's/1/ON/g'
  elif [ "$COMMAND" = "ON" ];then
   curl -0 -A '' -X POST -H 'Accept: ' -H 'Content-type: text/xml; charset="utf-8"' -H "SOAPACTION: \"urn:Belkin:service:basicevent:1#GetBinaryState\"" --data '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:GetBinaryState xmlns:u="urn:Belkin:service:basicevent:1"><BinaryState>1</BinaryState></u:GetBinaryState></s:Body></s:Envelope>' -s http://$IP:$PORT/upnp/control/basicevent1 |
   if [ "$( grep "<BinaryState"  | cut -d ">" -f2 | cut -d "<" -f1 )" = "0" ];then
    curl -0 -A '' -X POST -H 'Accept: ' -H 'Content-type: text/xml; charset="utf-8"' -H "SOAPACTION: \"urn:Belkin:service:basicevent:1#SetBinaryState\"" --data '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:SetBinaryState xmlns:u="urn:Belkin:service:basicevent:1"><BinaryState>1</BinaryState></u:SetBinaryState></s:Body></s:Envelope>' -s http://$IP:$PORT/upnp/control/basicevent1 |
	grep "<BinaryState" | cut -d ">" -f2 | cut -d "<" -f1 | sed 's/0/OFF/g' | sed 's/1/ON/g'
   else
    echo "ON" #Already On
   fi
  elif [ "$COMMAND" = "OFF" ];then
   curl -0 -A '' -X POST -H 'Accept: ' -H 'Content-type: text/xml; charset="utf-8"' -H "SOAPACTION: \"urn:Belkin:service:basicevent:1#GetBinaryState\"" --data '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:GetBinaryState xmlns:u="urn:Belkin:service:basicevent:1"><BinaryState>1</BinaryState></u:GetBinaryState></s:Body></s:Envelope>' -s http://$IP:$PORT/upnp/control/basicevent1 |
   if [ "$( grep "<BinaryState"  | cut -d ">" -f2 | cut -d "<" -f1 )" = "1" ];then
    curl -0 -A '' -X POST -H 'Accept: ' -H 'Content-type: text/xml; charset="utf-8"' -H "SOAPACTION: \"urn:Belkin:service:basicevent:1#SetBinaryState\"" --data '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:SetBinaryState xmlns:u="urn:Belkin:service:basicevent:1"><BinaryState>0</BinaryState></u:SetBinaryState></s:Body></s:Envelope>' -s http://$IP:$PORT/upnp/control/basicevent1 |
    grep "<BinaryState" | cut -d ">" -f2 | cut -d "<" -f1 | sed 's/0/OFF/g' | sed 's/1/ON/g'
   else
    echo "OFF" #Already Off
   fi
  elif [ "$COMMAND" = "SETDIMMER" ];then
   curl -0 -A '' -X POST -H 'Accept: ' -H 'Content-type: text/xml; charset="utf-8"' -H "SOAPACTION: \"urn:Belkin:service:basicevent:1#SetBinaryState\"" --data '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:SetBinaryState xmlns:u="urn:Belkin:service:basicevent:1"><brightness>'$BRIGHT'</brightness></u:SetBinaryState></s:Body></s:Envelope>' -s http://$IP:$PORT/upnp/control/basicevent1 |
   grep "<brightness"  | cut -d ">" -f2 | cut -d "<" -f1 
  elif [ "$COMMAND" = "GETDIMMER" ];then
   curl -0 -A '' -X POST -H 'Accept: ' -H 'Content-type: text/xml; charset="utf-8"' -H "SOAPACTION: \"urn:Belkin:service:basicevent:1#GetBinaryState\"" --data '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:GetBinaryState xmlns:u="urn:Belkin:service:basicevent:1"><BinaryState>1</BinaryState></u:GetBinaryState></s:Body></s:Envelope>' -s http://$IP:$PORT/upnp/control/basicevent1 |
   grep "<brightness"  | cut -d ">" -f2 | cut -d "<" -f1
  elif [ "$COMMAND" = "TOGGLE" ];then
   curl -0 -A '' -X POST -H 'Accept: ' -H 'Content-type: text/xml; charset="utf-8"' -H "SOAPACTION: \"urn:Belkin:service:basicevent:1#GetBinaryState\"" --data '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:GetBinaryState xmlns:u="urn:Belkin:service:basicevent:1"><BinaryState>1</BinaryState></u:GetBinaryState></s:Body></s:Envelope>' -s http://$IP:$PORT/upnp/control/basicevent1 |
   if [ "$( grep "<BinaryState"  | cut -d ">" -f2 | cut -d "<" -f1 )" = "1" ];then
    curl -0 -A '' -X POST -H 'Accept: ' -H 'Content-type: text/xml; charset="utf-8"' -H "SOAPACTION: \"urn:Belkin:service:basicevent:1#SetBinaryState\"" --data '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:SetBinaryState xmlns:u="urn:Belkin:service:basicevent:1"><BinaryState>0</BinaryState></u:SetBinaryState></s:Body></s:Envelope>' -s http://$IP:$PORT/upnp/control/basicevent1 |
    grep "<BinaryState" | cut -d ">" -f2 | cut -d "<" -f1 | sed 's/0/OFF/g' | sed 's/1/ON/g' | sed 's/Error/OFF/g'
   else
    curl -0 -A '' -X POST -H 'Accept: ' -H 'Content-type: text/xml; charset="utf-8"' -H "SOAPACTION: \"urn:Belkin:service:basicevent:1#SetBinaryState\"" --data '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:SetBinaryState xmlns:u="urn:Belkin:service:basicevent:1"><BinaryState>1</BinaryState></u:SetBinaryState></s:Body></s:Envelope>' -s http://$IP:$PORT/upnp/control/basicevent1 |
    grep "<BinaryState" | cut -d ">" -f2 | cut -d "<" -f1 | sed 's/0/OFF/g' | sed 's/1/ON/g' | sed 's/Error/ON/g'
   fi
  elif [ "$COMMAND" = "SIGNAL" ];then
   curl -0 -A '' -X POST -H 'Accept: ' -H 'Content-type: text/xml; charset="utf-8"' -H "SOAPACTION: \"urn:Belkin:service:basicevent:1#GetSignalStrength\"" --data '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:GetSignalStrength xmlns:u="urn:Belkin:service:basicevent:1"><GetSignalStrength>0</GetSignalStrength></u:GetSignalStrength></s:Body></s:Envelope>' -s http://$IP:$PORT/upnp/control/basicevent1 |
   grep "<SignalStrength" | cut -d ">" -f2 | cut -d "<" -f1
  elif [ "$COMMAND" = "PORT" ];then
   echo "$PORT"
  else
   echo $COMMAND
  fi
 fi
fi

Hi all, we are excited to finally show off the near final design of our machine. It is powered by a Duet3 and a toolboard mounted to the extruder. A video of it running at 400mm/s in all axes is posted below at our Instagram.

We have so much to learn about the Duet framework as our past experience has always been with Marlin, but we are ramping up fast..!

https://www.instagram.com/p/B-klDdcD_ld/?igshid=96tmsc5zuvkp

I decided to create a post where we can show our progress as we finalize the design and testing of our first open-source commercially available printer - the oozeBot ele^gant (short for elevating gantry). For starters, here is the current custom boot logo for the PanelDue. We are also posting progress photos and videos on our instagram at instagram.com/oozebot

Feedback is welcome and appreciated, even critical!

After thinking about this since I posted it, maybe this isn't necessary.. If there are variances front to rear on either side, they should be static and mesh bed compensation would resolve it. My current M671 is set as follows to check each motor directly in the middle of the z-belt loops..

M671 X-82:424 Y-175:-175 S5

I'd still appreciate feedback though. Thanks

I posted a response a few minutes ago, but deleted it after I finally realized my mistake..

One note on this that's worth mentioning is the % in the service file has to be escaped like %%. Here is an example file:

[Unit]
Description=Duet API listener Test
After=duetcontrolserver.service
Requires=duetcontrolserver.service

[Service]
ExecStart=/usr/local/bin/execonmcode -mCode 4567 -command "./test.sh %%A %%B %%C"
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

So.. the idea of running macros from the local SD card is compelling - it's not ideal, but it would be very workable. I took a clean SD card and put a few sample macros into a folder named "macros" off the root. It works! They all show up like expected and run! I'm pleased.. it's not perfect, but that's a big step forward.

@Phaedrux - Yes, the XY belt layout is to both get around the smooth rods and Z-belt as well as for tensioning - it works great!

The version in the video is using a single Igus 12mm bushing on each smooth rod. An updated version should be ready in the next few days that uses two bushings each.. we'll see if it is necessary or not.

Here are some photos of the z-belt connections. The piece that fits against the teeth is ribbed to properly seat itself into the belt and the holes are over-sized to allow it to properly fit in the front (more on that in a second).

rear connection:

front connection:

The rear is where the ends of the belt come together. After it is tightened (with the front connection removed), proper belt tension is applied. Then, the XY mechanism (still working on a good name) is leveled. Once leveled, the front connections are tightened onto the belt. The belt is now locked in place and the XY mechanism has no ability to lose alignment.

Yes, the bed itself is adjustable for fine tuning.

Thoughts?

@dc42 said in Duet 2: using:

To reduce the risk of damage to the drivers on the Duet, use the M918 command to execute M18 when a power loss is detected, to turn the motors off.

David, can you elaborate on this? I've reviewed the M918 command and can't decipher how that can be used in connection with the M18?

Digging up this older thread to report in.. we've recently tested multiple chamber heaters and have settled on a target temp of 70c for our enclosures. What we've picked as our recommendation is the Stego 028119-01. It is a 250w PTC with built in fan. Along with the build plate at 110c, it can heat our chamber to 70c in less than 30 minutes.

First, here is a photo of our enclosure:

And the Stego heater:

And the PanelDue after the chamber temperature has stabilized:

Thank you both for the assistance! I was not aware these coordinates were in a specific order.. but that does make sense. However, I now know how this was introduced as this is the machine I recently rewired to put in the enclosure I've posted photos of.

Changing:

M671 X-85:424 Y132.4:132.4 S2

to:

M671 X424:-85 Y132.4:132.4 S2

Corrected the issue!

For those following along or find this later down the road, I decided to fix this by flipping the order of the z-motors in my config's M584 instead of flipping the order in the M671 as shown above.

@Veti @dc42 thanks! I'll try this right now.. I pray it's just my ignorance! SO MUCH TO LEARN.. but we are getting there!

Here is what it's doing. FIrst is running the macro after running homez.g to square the machine; second is after running the macro again (no homing z); and third is after running it again.. it is doubling the offset each time

I would love to be corrected on some simple mistake here, but I can't find one. I may roll back to 3.1.1 on this machine if there isn't a simple solution.

@dc42 No - that doesn't correct it. I just tried several times up to 1 second but it still does not enable unless I run a second command.

I'm putting this in the beta category, but I'm really not sure if it's related to the beta.

Note our Z is belt driven and has been calculated to X-85 and X424 and since it lifts both front and rear, we've defined Y and center to the build plate.

I need some help here. I had this working perfectly - or at least I thought I did - and it's recently become completely inaccurate. I've isolated a routine into a macro that shows the issue.

M558 K0 P9 C"20.io0.in" H3 F100 T12000 A5 R0.1 S0.01
M671 X-85:424 Y132.4:132.4 S2

G1 X132.4 Y132.4 F24000	 ; aligns BLTouch in center of build plate

M561
G30 Z-99999

G30 P0 X0 Z-99999
G30 P1 X260 Z-99999 S2

M557 X14.5:265.5 Y14.5:265.5 S115.5

G29 S0

These are the relevant lines that are involved. If I run homez.g, the routine lifts the gantry to the top of the machine, levels it, and then everything is back square. However, running this macro multiple times in a row, without homing z, results in the following:

What am I doing wrong? Or is this an issue with the beta? By the 3rd time I ran it, I could physically see the gantry out of square to the bed.. Thanks

@wilriker I was wrong about needing a following M400 (as it's "in process" - duh!). I changed it in my original post. Thanks for letting me know I can edit earlier posts - not sure how I missed that!

@wilriker That's great! I'll be eager to test that when you have time to work on it..

We are using Duet3/RPI and currently running 3.2b1. I have the following in my config:

M150 X1 F3000000
M150 R0 U85 B255 P64 S57
M150 R0 U85 B255 P64 S57

Note the two lines with the same command - if I send it once (in the config or through the console), it never works the first time, I have to send it a second to get them to start working.

This feels wrong, but again, it could be I don't know what I'm doing. Thanks