PrusSlicer never finishes upload with PI4

bot

@chrishamm I was just taking a look to see what might be going wrong. You could be correct. It encodes the filename directly to the url.

	if (connectionType == ConnectionType::dsf) {
		return (boost::format("%1%machine/file/gcodes/%2%")
				% get_base_url()
				% Http::url_encode(filename)).str();

Which is called like this (filename is the first argument):

auto upload_cmd = get_upload_url(upload_data.upload_path.string(), connectionType);

Which, digging into it, seems to directly set the upload path as the filesystem directory. So, yeah, on WIndows it might have \ instead of /.

In the logs above, I did notice:

Feb 16 16:57:23 malej DuetWebServer[596]: DuetWebServer.Controllers.MachineController[0] [UploadFile Failed upload file gcodes/fixa_cidlo_0.2mm_PETG_malej_12h39m.gcode (resolved to /opt/dsf/sd/gcodes/fixa_cidlo_0.2mm_PETG_malej_12h39m.gcode) Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Unexpected end of request content.    at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1ContentLengthMessageBody.ReadAsyncInternal(CancellationToken cancellationToken)    at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)    at System.IO.Pipelines.PipeReader.CopyToAsyncCore[TStream](TStream destination, Func`4 writeAsync, CancellationToken cancellationToken)    at DuetWebServer.Controllers.MachineController.UploadFile(String filename, ISessionStorage sessionStorage) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetWebServer/Controllers/MachineController.cs:line 410

But I do not understand what it means exactly.

chrishamm

@bot Thanks for looking into it. Unexpected end of request content means the request was too short which can be expected when the HTTP request is cancelled. So nothing unusual in there AFAICS.

bot

@chrishamm

I think the filename argument ends up being different depending on where the upload is initiated from. There seeems to be a background process that will upload files at times, or prepare the data for upload at least.

@Stephen6309 Do you have background slicing/processing enabled in prusaslicer? I forget what the exact feature name is called. It's in the app preferences.

Anyways. It seems to me that the path is set by the user input of the upload dialog.

Plater.cpp Line 6310

    PrintHostSendDialog dlg(default_output_file, upload_job.printhost->get_post_upload_actions(), groups);
    if (dlg.ShowModal() == wxID_OK) {
        upload_job.upload_data.upload_path = dlg.filename();
        upload_job.upload_data.post_action = dlg.post_action();
        upload_job.upload_data.group       = dlg.group();

        p->export_gcode(fs::path(), false, std::move(upload_job));
    }
}

There is a note on the dialog to use forward slashes a directory separators.

PetrKroupa

@chrishamm - Yes, on windows. Today I discovered an interesting thing. I use the arc welder plugin in post-processing scripts. If I do not use it, the upload will go smoothly.

@Stephen6309 - Do you use ARC Welder too?

chrishamm

@petrkroupa That's the reason why it doesn't work. Perhaps PrusaSlicer doesn't wait for ArcWelder to finish or it attempts to use file information of the old unprocessed file before it sends it over to the Duet.

Either way this is no problem in DSF or RRF.

PetrKroupa

@chrishamm - I agree. I assume that @Stephen6309 will confirm that he also uses this plugin. That's probably why no one has solved it yet and had no problem with it. This combination is probably not very common.

Thanks for help.

Stephen6309

@petrkroupa Yes I use arcwelder. But this problem only occurs with the PI4.

PetrKroupa

@stephen6309 - I can't test that because both printers I have with RPi4. However, if without SBC it works ok then it will be something in DSF or RRF. What do you think @chrishamm ?

chrishamm

@petrkroupa I am not convinced this is a problem in DSF. If you can upload files as usual using the web interface and if it works from PrusaSlicer without ArcWelder, it's obvious that ArcWelder interferes somehow with the upload process.

Stephen6309

@chrishamm Upload fine in standalone mode using arcwelder. My Duet 3 Mini 5+ is in standalone mode and everything uploaded fine. When I had a problem on my 6HC, I set it up in standalone mode for troubleshooting and the uploads worked fine.

The only difference between the two, is the PI4.

Stephen6309

@chrishamm PrusaSlicer 2.4.1beta4, SBC mode never finshes upload.

chrishamm

@stephen6309 I cannot confirm that (this is without ArcWelder on Windows x64):

I just checked 2.4.1-b3 on Linux x64 and there it works with ArcWelder too.

PetrKroupa

@chrishamm Without an arc welder, it works on both my printers. Both 6HC + SBC. But not with ARCwelder. It always gets stuck at 96-97% depending on the file size.
I don't have a Linux PC to test it.

Stephen6309

@chrishamm Without arcwelder or the PI, it works fine. Just not working in SBC mode.

Stephen6309

@stephen6309 Still doesn't work with 3.4.0 with the PI4.

STANDALONE mode works fine.

Superslicer 2.4.58.3 nightly from last week.

Phaedrux

@stephen6309 Do you have a different Pi and SD card to test with?

PetrKroupa

@phaedrux - I have two printers and same issue. Also have spare Pi and SD. If you have something to test, no problem.

Stephen6309

@phaedrux The 6HC with a PI4 and the Mini 5+ with a PI4, both running on a seperate meanwell power supply.

6HC's pi4 is running bullseye with current updates.
Mini's pi4 is running buster image from the duet3d doc site, with current updates.

jay_s_uk

@stephen6309 are you using arcwelder?

Stephen6309

@jay_s_uk Yes, using arcwelder.