DuetLapse available for Alpha testing
-
@Adrian52 said in DuetLapse available for Alpha testing:
@Danal I used . /DuetLapse -duet 192.168.1.16 -camera pi -pause yes If I leave out the pause it works fine. Not sure why I said bed.g of course I meant pause.g, which contains a z as well as x and y moves.
Actually.... that form of pause is not yet coded, not working. Let me make a minor change so that the script itself will issue a message to that effect.
And, "coming soon", in terms of when it will work.
Sorry for any confusion.
-
Is there a step by step guide for setting this up to work from a PC, rather than Pi?
I'm a little confused as to where to put the IP addresses for the printer and Webcam in the Duetlapse.py file, etc.
I have a Duet 2 Maestro, BTW.
I'm using an old iPhone as an IPCam. I can see the vid on the DWC.
I'm a total noob when it comes to this kind of thing.
-
It is only supported (by me) on Pi. If you want to adapt to a PC, it will probably run there, maybe even unchanged, but I choose not to get into all the extreme variations of PC stuff. I will answer specific questions.
You don't modify the script to specify addresses. Run it with -h and it will tell you usage. The only required parameter is -duet which specifies the IP or name of the printer.
./DuetLapse.py -duet 192.168.7.101or similar. Full usage:
./DuetLapse.py -h usage: DuetLapse.py [-h] -duet DUET [-camera {usb,pi,web,dslr}] [-seconds SECONDS] [-detect {layer,pause,none}] [-pause {yes,no}] [-movehead MOVEHEAD MOVEHEAD] [-weburl WEBURL] [-dontwait] {camparms,vidparms} ... Program to create time lapse video from camera pointed at Duet3D based printer. optional arguments: -h, --help show this help message and exit -duet DUET Name or IP address of Duet printer. -camera {usb,pi,web,dslr} -seconds SECONDS -detect {layer,pause,none} -pause {yes,no} -movehead MOVEHEAD MOVEHEAD -weburl WEBURL -dontwait Capture images immediately. subcommands: {camparms,vidparms} DuetLapse camparms -h or vidparms -h for more helpSo if your old phone has a URL that, when fetched, returns a still image, then something like:
./DuetLapse.py -duet 192.168.7.101 -camera web -weburl "http://oldphoneurl" -
I moved my old laptop running DuetLapse and a C920 USB cam to Ubuntu 20.04 and I'm having this problem now;
baen@baen-W110ER:~/DuetLapse$ ./DuetLapse.py -camera usb - detect layer -pause no -duet 192.168.1.212 camparms -r 1920x1080 ./DuetLapse.py: line 7: syntax error near unexpected token `newline' ./DuetLapse.py: line 7: `<!DOCTYPE html>' ffmpeg:
baen-W110ER:~/DuetLapse$ ffmpeg -version ffmpeg version 4.2.2-1ubuntu1 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 9 (Ubuntu 9.3.0-3ubuntu1) configuration: --prefix=/usr --extra-version=1ubuntu1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-nvenc --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared libavutil 56. 31.100 / 56. 31.100 libavcodec 58. 54.100 / 58. 54.100 libavformat 58. 29.100 / 58. 29.100 libavdevice 58. 8.100 / 58. 8.100 libavfilter 7. 57.100 / 7. 57.100 libavresample 4. 0. 0 / 4. 0. 0 libswscale 5. 5.100 / 5. 5.100 libswresample 3. 5.100 / 3. 5.100 libpostproc 55. 5.100 / 55. 5.100 Python3:
baen@baen-W110ER:~/DuetLapse$ python3 --version Python 3.8.2 fswebcam is installed but I can't figure out how to pull a version number off it.
-
@THP Done. On Github. Obviously, you have to repull both scripts. Let me know.
-
@Baenwort said in DuetLapse available for Alpha testing:
baen@baen-W110ER:~/DuetLapse$ ./DuetLapse.py -camera usb - detect layer -pause no -duet 192.168.1.212 camparms -r 1920x1080 ./DuetLapse.py: line 7: syntax error near unexpected token `newline' ./DuetLapse.py: line 7: `<!DOCTYPE html>' That `<!DOCTYPE html>' tells me that the contents of file "DuetLapse.py" is not the script, it is a webpage. That almost always means somebody right clicked and said "save as" on the filename on Github. That does not work... that link leads to a page that shows the script, not the script itself.
How did you fetch it from github? I just checked the "readme" install instructions, and they are correct.
mkdir DuetLapse cd DuetLapse wget https://raw.githubusercontent.com/DanalEstes/DuetLapse/master/DuetLapse.py chmod 744 DuetLapse.py wget https://raw.githubusercontent.com/DanalEstes/DuetWebAPI/master/DuetWebAPI.py -
@Danal You found the problem.
Used wget this time and it works now. Must have just right clicked in the rush of setting things back up with the new install../DuetLapse.py -camera usb -detect layer -pause no -duet 192.168.1.212 camparms -parms -r 1920x1080functions fine
-
Hey guys,
Thanks for the help yesterday!
Ok, so I have installed python (latest) and ran script. I did not get any errors, so I am assuming that it is running (even though I didn't get any text to confirm this...possible addition?).
Now, the only question I have is...where are the images going? Do I have to edit either file to tell it where to save the pics and also where it need to look for the conversion to the time lapse?
I'm on PC btw..not Pi.
-
Duet lapse is very verbose. If you are getting no output, it is not working. If you are not seeing lots of output, it hung attempting something; press Ctrl-C to terminate it. Here's an example of the first part of a run:
Command issued:
./DuetLapse.py -camera web -weburl http://192.168.7.96/cgi-bin/currentpic.cgi -duet localhostOutput:
Attempting to connect to printer at localhost Connected to a Duet V3 printer at http://localhost ################################## # Options in force for this run: # # camera = web # # printer = localhost # # seconds = 0 # # detect = layer # # pause = no # # camparms = # # vidparms = # # movehead = 0.00 0.00 # # dontwait = False # ################################## Waiting for print to start on printer localhost Will take pictures when printing starts, and make video when printing ends. Or, press Ctrl+C one time to move directly to conversion step. Print start sensed. End of print will be sensed, and frames will be converted into video. Or, press Ctrl+C one time to move directly to conversion step. Capturing frame 0 at X-3.87 Y375.83 Z9.80 Layer 0 2020-04-26 18:04:28 URL:http://192.168.7.96/cgi-bin/currentpic.cgi [182012/182012] -> "/tmp/DuetLapse/IMG00000001.jpeg" [1] Capturing frame 1 at X136.41 Y107.90 Z0.30 Layer 1 2020-04-26 18:06:11 URL:http://192.168.7.96/cgi-bin/currentpic.cgi [184934/184934] -> "/tmp/DuetLapse/IMG00000002.jpeg" [1] Capturing frame 2 at X151.73 Y184.54 Z0.45 Layer 2 2020-04-26 18:17:43 URL:http://192.168.7.96/cgi-bin/currentpic.cgi [186458/186458] -> "/tmp/DuetLapse/IMG00000003.jpeg" [1] Capturing frame 3 at X99.61 Y178.44 Z0.60 Layer 3 2020-04-26 18:31:45 URL:http://192.168.7.96/cgi-bin/currentpic.cgi [190931/190931] -> "/tmp/DuetLapse/IMG00000004.jpeg" [1] Capturing frame 4 at X166.89 Y184.79 Z0.75 Layer 4 2020-04-26 18:33:08 URL:http://192.168.7.96/cgi-bin/currentpic.cgi [186529/186529] -> "/tmp/DuetLapse/IMG00000005.jpeg" [1] Capturing frame 5 at X178.56 Y131.07 Z0.90 Layer 5 2020-04-26 18:34:32 URL:http://192.168.7.96/cgi-bin/currentpic.cgi [185255/185255] -> "/tmp/DuetLapse/IMG00000006.jpeg" [1] Capturing frame 6 at X164.44 Y179.88 Z1.05 Layer 6 2020-04-26 18:35:57 URL:http://192.168.7.96/cgi-bin/currentpic.cgi [187514/187514] -> "/tmp/DuetLapse/IMG00000007.jpeg" [1] Capturing frame 7 at X119.43 Y124.66 Z1.20 Layer 7 2020-04-26 18:37:26 URL:http://192.168.7.96/cgi-bin/currentpic.cgi [185951/185951] -> "/tmp/DuetLapse/IMG00000008.jpeg" [1] Capturing frame 8 at X143.62 Y172.98 Z1.35 Layer 8 2020-04-26 18:38:55 URL:http://192.168.7.96/cgi-bin/currentpic.cgi [189934/189934] -> "/tmp/DuetLapse/IMG00000009.jpeg" [1] Capturing frame 9 at X160.05 Y182.59 Z1.50 Layer 9 2020-04-26 18:40:26 URL:http://192.168.7.96/cgi-bin/currentpic.cgi [184134/184134] -> "/tmp/DuetLapse/IMG00000010.jpeg" [1]``` -
Do I still need to use the "./DuetLapse.py -duet 192.168.7.101 script first? (obviously changing to my printers IP.
-
I'm not sure what you mean by "first"?
DuetLapse.py is the script that runs from before the print job starts, throughout the entire capture, and makes the video at the end.
So, yes, you need to run it.
-
I'll be more specific, hopefully it helps.
Here is the details of my setup:
IP Address of printer: 192.168.3.72
***Note: Priner is running 2.0.7 Firmware on a Duet 2 Maestro
IP Address of IPCam: 192.168.3.2
***Note: When I navigate to the IP address of the cam it shows a page with links to show different options of displaying.Here is the page:
The following are what shows up the the address bar for each:
Web Browser Links
~ JPEG Video: http://192.168.3.2/video.html
~ MJPEG Video: http://192.168.3.2/av.htmlRaw Video Links
~ JPEG Image: http://192.168.3.2/image.jpg
~MJEPG Video: http://192.168.3.2/video.mjpgHere is the command that I put in:
"DuetLapse.py -camera web -weburl http://192.168.3.2/image.jpg -duet 192.168.3.72" (Of Course, without quotes)I'm running V3.8 Python
When I run above, it asks what program to use and I select Python. It then jumps to the next line on the cmd prompt with no feedback.
There is one thing that I'm not sure if it matters. One your guide it says to "chmod 744 Duetlapse.py" When I do that in cmd is says its not a valid command...is that ok?
Hopefully you can find the solution in all of the above?
. -
I can tell that the script is not running... and I have no clue as to how to get a python script to run in your environment.
I can tell you that chmod is a unix only command, and the purpose is to mark the "DuetLapse.py" file executable (on Unix). There is no windows equivalent. Windows picks things as 'executable' based on having an .exe or .bat or .cmd or similar file extension. Windows itself will not (and, AFAIK cannot be configured to) consider a .py file as an executable.
So the script doesn't even start.
You MAY need to enter:
python3 DuetLapse.pyOr similar. Is there a "demo" or "run this first" example for the Python you installed? How would that command be issued?
-
Not that I know of... I think I'm going to have to try a different option. It seems that I don't have enough experience to make this work on PC.
You would think it would be rather easy, seeing as I can see the live stream from the DWC. I would have thought there would be a rather easy way to even do a screenshot of that feed every time the layer changes on the DWC?
Oh well...I guess I'll have to order a Pi.
Thank you for your help, all the same!
-
I have a windows PC with Python 3.8 installed on it. I copied DuetLapse.py over (and the API script) and ran it. It immediately blew up on a Unix only command... and that's followed by several others.
It is just not going to run on Windows.
It was designed to run under Raspbian Linux (Unix) on a Pi. It MIGHT also run under other flavors of Linux on a Pi. It even MIGHT MIGHT run on a Linux laptop or desktop.
It is really never going to run on Windows.
-
@Damien said in DuetLapse available for Alpha testing:
Oh well...I guess I'll have to order a Pi.
3B+ or 4B+ is preferred. 2G or 4G ram, either should work.
Zero will not work. I'm unsure about a 2 (and I don't think those are really available anyway).
-
I have it working under Ubuntu 19.10 and 20.04 now that I remembered not to right click.
You have to install Python3-numpy and ensure you are using a recent version of ffmpeg and python3 (both should be installed normally by a Desktop linux distro)As for a Windows PC it may be possible to get it working under Windows Subsystem for Linux: https://docs.microsoft.com/en-us/windows/wsl/install-win10
I haven't tried as all my old laptops and non-pi stuff do not have Windows 10 Licenses.
If @Danal wants a linux install guide I can write up what it took to get running on Ubuntu and it should be readily transferable to other Distros.
-
Despite having written this, I don't actually do timelapse all that often. As a result, I've tested DuetLapse in pieces, but I have never actually run it, with a camera, on a print. Therefore, just for fun, when running a test print yesterday, I set up a web cam and executed:
./DuetLapse.py -camera web -weburl http://192.168.7.96/cgi-bin/currentpic.cgi -duet localhostThe print ended up running for 17 hours 40 minutes. DuetLapse captured 1046 images, and produced a video that runs for 1:43.
Amusingly enough, the camera was double-stick-taped to a tripod, and it fell off about four hours before the print end. It is sort of comical that the printer is moving around in this image where the background is rock solid... and then you see the background start to 'ooze' (really, the camera just beginning to fall off the tape). It takes several seconds in lapse time, so probably 30 min or more of real time from the first detectable move to the fall. Then, bam, between one frame and the next, a nice view of the corner of the room from floor level.
It is just really funny to watch it ooze, accelerating as it bends its way off the tape, and knowing that motion would have been imperceptible in the real world, until the final fall.
Anyway, that was literally my first run of DuetLapse.
(Cool Story Bro)
-
@Danal ....Can I see the video?
-
Sure,
http://danalspub.com/wp-content/uploads/2020/04/DuetLapse0427201124.mp4
Also, note it is at a horrible angle to show a print... the head blocks it. Camera power cord was very short, and I didn't really care about the content of the vid, just did the script work or not.
