Duetlapse3 "printer is not connected"

stuartofmt

@Aurimas said in Duetlapse3 "printer is not connected":

2023-07-11 10:29:41,395 - MainThread - !!!!! Could not get SBC firmware version !!!!!

The problem looks to be that the firmware version could not be resolved. I'm guessing you are using 3.5.0.beta.4 ? There was a change in the object model (or I misinterpreted it) between earlier beta and beta 4. DuetLapse3 V5.2.4 was not tested against beta4.

In any case, I saw the same error when I recently upgraded to beta4. I have fixed the issue in V5.3.0 but not yet posted it to Github. Let me know if it resolves the problem.

Note that it's normal for DuetLapse3 to attempt to connect first in standalone mode. If it detects emulation mode or cannot connect in standalone then it tries to connect in SBC mode.

DuetLapse3.py

stuartofmt

Also, It looks like you are using SBC mode but you specify a port number for the printer. I would have though that, normally, there was no need to use a port number in SBC mode? At least, I have not needed to do so.

Aurimas

@stuartofmt thanks for the info - just tried without the port number and the page is not found. So I assume it is needed.
could you please share 5.3.0 version? maybe you can email direct?

stuartofmt

@Aurimas said in Duetlapse3 "printer is not connected":

could you please share 5.3.0 version? maybe you can email direct?

I shared it several posts above. If you are using the plugin, let me know and I can share that as well.

Aurimas

@stuartofmt I am using plugin in SBC mode.
All I can find is the Beta 3. can you please share the latest version?
thank you

stuartofmt

@Aurimas

Try this:

https://github.com/stuartofmt/DuetLapse3/blob/main/plugin/3.5.0.beta.4/DuetLapse3-5.3.0.beta.4.zip

Aurimas

@stuartofmt same

DuetLapse3 Version 5.3.0
Connected to printer at: 192.168.1.128:8082

Process Id: 1724
Last Update: Wednesday - 12:20
Capture Status:= Waiting
DuetLapse3 State:= start
Duet Status:= Printer is not connected
Images Captured:= 0
Current Layer:= None

stuartofmt

@Aurimas said in Duetlapse3 "printer is not connected":

@stuartofmt same

DuetLapse3 Version 5.3.0
Connected to printer at: 192.168.1.128:8082

Hi - I’m away from my printer for a couple of weeks but we should be able to resolve this.
Can you restart duetlapse3 plugin after setting the config file to include ‘-verbose’ and post the log file?

The error likely occurs when attempting to resolve the version number of the printer. I’m wondering if the port number is confounding something. Is there a special reason why you have set the port number for the printer? Can you try it without the port number being set (I.e. no port number set for the printer and no port number set for DuetLapse3). When I switched to SBC, I must admit, I did not test with a port number set on the printer as I did not see an advantage to doing so. Is there one ?

I’m assuming with this question that the SBC is not trying to serve up another web interface that uses port 80.

Aurimas

@stuartofmt thanks a lot
it says connected but in emulation mode.
what could be the reason for that?
i didn't change standard settings on DSF

i tried to go to:
http://192.168.1.128/rr_connect?password=reprap

and got this output
{"apiLevel":1,"err":0,"isEmulated":true,"sessionTimeout":8000,"boardType":"duet5lcunknown"}

2023-07-14 09:11:12,255 - MainThread - DuetLapse3 Version --- 5.3.0
2023-07-14 09:11:12,256 - MainThread - Process Id  ---  1655
2023-07-14 09:11:12,257 - MainThread - -------------------------------------------------------------------------------

2023-07-14 09:11:12,257 - MainThread - dontwait has been changed to True
2023-07-14 09:11:12,258 - MainThread - ################### Options at start of this print job  #####################
2023-07-14 09:11:12,258 - MainThread - # Environment
2023-07-14 09:11:12,259 - MainThread - -duet  =  192.168.1.128
2023-07-14 09:11:12,259 - MainThread - -basedir  =  /opt/dsf/sd/DuetLapse3
2023-07-14 09:11:12,260 - MainThread - -poll  =  10
2023-07-14 09:11:12,260 - MainThread - -instances  =  single
2023-07-14 09:11:12,260 - MainThread - -logtype  =  both
2023-07-14 09:11:12,261 - MainThread - -nolog  =  False
2023-07-14 09:11:12,261 - MainThread - -verbose  =  True
2023-07-14 09:11:12,261 - MainThread - -host  =  192.168.1.128
2023-07-14 09:11:12,261 - MainThread - -port  =  8082
2023-07-14 09:11:12,261 - MainThread - -keeplogs  =  False
2023-07-14 09:11:12,262 - MainThread - -novideo  =  False
2023-07-14 09:11:12,262 - MainThread - -deletepics  =  False
2023-07-14 09:11:12,263 - MainThread - -maxffmpeg  =  2
2023-07-14 09:11:12,263 - MainThread - -keepfiles  =  True
2023-07-14 09:11:12,264 - MainThread - # Execution
2023-07-14 09:11:12,264 - MainThread - -dontwait  =  True
2023-07-14 09:11:12,264 - MainThread - -seconds  =  30
2023-07-14 09:11:12,264 - MainThread - -detect  =  none
2023-07-14 09:11:12,265 - MainThread - -pause  =  no
2023-07-14 09:11:12,265 - MainThread - -numlayers  =  1
2023-07-14 09:11:12,265 - MainThread - -movehead  =  [0, 0]
2023-07-14 09:11:12,265 - MainThread - -rest  =  1
2023-07-14 09:11:12,266 - MainThread - -standby  =  False
2023-07-14 09:11:12,266 - MainThread - -restart  =  True
2023-07-14 09:11:12,266 - MainThread - # Camera
2023-07-14 09:11:12,266 - MainThread - -camera1  =  usb
2023-07-14 09:11:12,267 - MainThread - -camera2  =  stream
2023-07-14 09:11:12,267 - MainThread - -weburl1  =  http://192.168.1.128:8084/stream
2023-07-14 09:11:12,267 - MainThread - -weburl2
2023-07-14 09:11:12,267 - MainThread - # Video
2023-07-14 09:11:12,268 - MainThread - -extratime  =  0
2023-07-14 09:11:12,268 - MainThread - -fps  =  10
2023-07-14 09:11:12,268 - MainThread - -minvideo  =  5
2023-07-14 09:11:12,268 - MainThread - -maxvideo  =  0
2023-07-14 09:11:12,269 - MainThread - # Overrides
2023-07-14 09:11:12,269 - MainThread - -camparam1
2023-07-14 09:11:12,269 - MainThread - -camparam2
2023-07-14 09:11:12,269 - MainThread - -vidparam1
2023-07-14 09:11:12,270 - MainThread - -vidparam2
2023-07-14 09:11:12,270 - MainThread - # UI
2023-07-14 09:11:12,270 - MainThread - -hidebuttons  =  False
2023-07-14 09:11:12,272 - MainThread - # Special Functions
2023-07-14 09:11:12,272 - MainThread - -execkey
2023-07-14 09:11:12,272 - MainThread - -----------------------------------------------------------------------


2023-07-14 09:11:12,272 - MainThread - ************************************************************************************
2023-07-14 09:11:12,273 - MainThread - Warning: -seconds 30 and -detect none
2023-07-14 09:11:12,273 - MainThread - This combination implies -dontwait and will be set automatically
2023-07-14 09:11:12,274 - MainThread - ************************************************************************************

2023-07-14 09:11:12,275 - MainThread - ##########################################################
2023-07-14 09:11:12,277 - MainThread - Will start capturing images immediately
2023-07-14 09:11:12,277 - MainThread - ##########################################################

2023-07-14 09:11:12,277 - MainThread - ##########################################################
2023-07-14 09:11:12,277 - MainThread - Video will be created when printing ends
2023-07-14 09:11:12,278 - MainThread - or if requested from the UI or M291 "DuetLapse3.completed" S2
2023-07-14 09:11:12,278 - MainThread - ##########################################################

2023-07-14 09:11:12,279 - MainThread - ##########################################################
2023-07-14 09:11:12,279 - MainThread - If running from a console using the command line
2023-07-14 09:11:12,280 - MainThread - Press Ctrl+C one time to stop the program and create a video.
2023-07-14 09:11:12,280 - MainThread - ##########################################################

2023-07-14 09:11:12,281 - MainThread - *****  Initializing state and counters  *****
2023-07-14 09:11:12,340 - MainThread - ##########################################################
2023-07-14 09:11:12,341 - MainThread - ***** Started http listener *****
2023-07-14 09:11:12,341 - MainThread - ##########################################################

2023-07-14 09:11:12,342 - MainThread - Logging in to Printer
2023-07-14 09:11:12,342 - MainThread - 0 url: http://192.168.1.128/rr_disconnect post: False
2023-07-14 09:11:13,397 - MainThread - 1 url: http://192.168.1.128/rr_disconnect post: False
2023-07-14 09:11:14,434 - MainThread - 0 url: http://192.168.1.128/rr_connect?password=reprap post: False
2023-07-14 09:11:14,761 - MainThread - Connected but in emulation mode
2023-07-14 09:11:14,762 - MainThread - 0 url: http://192.168.1.128/machine/disconnect post: False
2023-07-14 09:11:14,893 - Thread-1 - !!!!! http call: {} !!!!!
2023-07-14 09:11:14,943 - Thread-2 - !!!!! http call: {'displayFiles': ['true']} !!!!!
2023-07-14 09:11:14,944 - Thread-2 - list_dir called with path = /opt/dsf/sd/DuetLapse3/Vega600/192-168-1-128
2023-07-14 09:11:14,945 - Thread-2 - Finished parsing the files directory
2023-07-14 09:11:15,796 - MainThread - 1 url: http://192.168.1.128/machine/disconnect post: False
2023-07-14 09:11:16,081 - Thread-3 - !!!!! http call: {'displayFiles': ['true']} !!!!!
2023-07-14 09:11:16,082 - Thread-3 - list_dir called with path = /opt/dsf/sd/DuetLapse3/Vega600/192-168-1-128
2023-07-14 09:11:16,082 - Thread-3 - Finished parsing the files directory
2023-07-14 09:11:16,833 - MainThread - 0 url: http://192.168.1.128/machine/connect?password=reprap post: False
2023-07-14 09:11:16,914 - MainThread - !!!!! Connected to SBC printer !!!!!
2023-07-14 09:11:16,915 - MainThread - 0 url: http://192.168.1.128/machine/status post: False
2023-07-14 09:11:17,124 - Thread-4 - !!!!! http call: {'getfile': ['/opt/dsf/sd/DuetLapse3/Vega600/192-168-1-128/startup.log']} !!!!!
2023-07-14 09:11:17,125 - Thread-4 - Trying to get file /opt/dsf/sd/DuetLapse3/Vega600/192-168-1-128/startup.log
2023-07-14 09:11:17,125 - Thread-4 - application/octet-stream

stuartofmt

@Aurimas

I am travelling and using my phone and have managed to confuse things. My appologies.

I have an incorrect UI element that I need to correct. The line that says Connected to printer at: 192.168.1.128:8082 is misleading (and led me astray).

Here is what happens:

The -port setting is only used for the UI that is generated by DuetLapse3. It has nothing to do with the printer, the SBC or DWC. This port setting needs to be different to any other http setting on your machine.
When DuetLapse3 starts it checks to see if it is trying to connect in Standalaone or SBC mode using a failover approach. Emulation mode is relatively new and is not used by DuetLapse3. If it detects emulation mode, it (rightfully) tries to connect using SBC mode.
Once connected - it checks the version number

Based on your output from this:

i tried to go to:
http://192.168.1.128/rr_connect?password=reprap

and the logfile output, you are using a standard configuration without any port assignments.

Also there is this line in the logfile that confirms SBC mode

2023-07-14 09:11:16,914 - MainThread - !!!!! Connected to SBC printer !!!!!

Bottom line - you can ignore the messages about emulation mode. Did you check that the UI still says Duet Status:= Printer is not connected ?

What is missing from the logfile you posted is the next part of the start sequence that confirms the versions. So I cannot confirm that the version was correctly determined.

Can you do two things please:

resend a more complete logfile.
send a screenshot or similar of the output from this url

http://192.168.1.128/machine/status

I wondering if the firmware is being picked up differently due to differences in duet boards (unlikely).

Aurimas

@stuartofmt here is status output.
i checked the log and that all it is - there is no version section so nothing has been left out

startup.txt
machine-status.txt

stuartofmt

@Aurimas
Thanks.
I was able to take a closer look.
Please make the following changes to your config file

Remove the line -host = 192.168.1.128 as it is not usually needed.
From the documentation
If omitted the default is 0.0.0.0
Generally this can be left out (default) as it will allow connection to the http listener from http://localhost:[port] (locally) or from another machine with network access using http://actual-ip-address-of-server-running-DuetLapse3[port]

There is a problem with your camera settings. You have the following:

-camera1  usb
-camera2  stream
-weburl1  http://192.168.1.128:8084/stream
-weburl2

What this is requesting is two cameras.
The first (-camera1) is a usb camera so -weburl1 will be ignored. The second (-camera2) is expecting a stream input but none is given in the corresponding -weburl2

I may not be trapping this unexpected set of options and this may be the cause of the issue. I'll have a look when I get back to my printer and camera.

Please confirm in your browser that http://192.168.1.128:8084/stream displays the camera output. Provided it does - I think your option settings should be:

-camera1  stream
-weburl1  http://192.168.1.128:8084/stream

with no second camera.

Aurimas

@stuartofmt it looks like there is some mismatch somewhere - might be just me.
there is no USB setting in the config file - please see attached.
Also updated log file attached - i tried before with host and without. made no difference.

DuetLapse3.txt
startup (2).txt

Aurimas

@Aurimas the camera itself is working fine - no issues at all. it is just not taking timelapse images.

stuartofmt

@Aurimas

The default for -camera1 is usb

You still have -camera2 stream in your config.

It should be -camera1 stream

Aurimas

@stuartofmt changed it as you instructed - no difference to connection. Still printer not connected.
log file attached.

startup.txt

stuartofmt

@Aurimas

Thanks - this log shows that it is definitely not happy with getting the version number.

Something strange is happening. I’ll add some additional debug logging and send you a test plugin - hopefully later today.

stuartofmt

@Aurimas

Can you try this please.

Uninstall the existing plugin and install this version. Note that I have made the changes "blind" i.e. do not have access to my printer to test them.
There are two changes:

I added some defensive / debug code to the section that is checking the board version.
No matter what the results of above - I am forcing a valid version to be returned. This should (hopefully) mean that DuetLapse3 continues on its merry way

In either case - there should be more information in the logfile and I can try to determine what the root cause is. Please post the logfile when you are able.

Note: you will need to remove the .txt extension from the attached file.

DuetLapse3-5.3.0.zip.txt

Aurimas

@stuartofmt

Good news - we have progress
so now it is connected and it is even taking pictures.
the only problem is that it is taking images while the printer is idle (that was when the interval was set to 30s)
once I changed to layer detect it is still running but not taking images on its own.

also why do I have detect layer still enabled?
2023-07-21 09:01:12,302 - MainThread - -seconds = 30
2023-07-21 09:01:12,303 - MainThread - -detect = layer

even though it is not in the config.
-weburl1 http://192.168.1.128:8084/stream
-seconds 30
-verbose
startup.txt

DuetLapse3 Version 5.3.0
Connected to printer at: 192.168.1.128:8082

Process Id: 6407
Last Update: Friday - 08:53
Capture Status:= Waiting
DuetLapse3 State:= start
Duet Status:= idle
Images Captured:= 0
Current Layer:= None

stuartofmt

@Aurimas said in Duetlapse3 "printer is not connected":

@stuartofmt

Good news - we have progress
so now it is connected and it is even taking pictures.

Excellent - I now see where the problem lay and had fixed it but not promoted it to to the correct github folder (beta and non-beta variants are different). I'll do some tidy-up and (likely next week) create an updated version.

the only problem is that it is taking images while the printer is idle (that was when the interval was set to 30s)

This is expected with both -detect none and -seconds [some number] There is a message in the earlier log informing that this is equivalent to -dontwait.

once I changed to layer detect it is still running but not taking images on its own.

With no -second setting and -detect layer the first image will not be captured until after layer 1 of the print job (also the logfile name will be changed reflect the printjob name).

also why do I have detect layer still enabled?
2023-07-21 09:01:12,302 - MainThread - -seconds = 30
2023-07-21 09:01:12,303 - MainThread - -detect = layer
even though it is not in the config.

The default for -detect is layer
DuetLapse has expanded its capabilities over time and some values reflect previous defaults. The documentation is fairly comprehensive.

Enjoy! If there are any further issues, let me know.