@secure if droidcam is serving a rtmp or IP cam stream then you should be able to run DuetLapse on just about any other device on your network that can run python3.

It's built for a Pi but I'm using it on a Ubuntu laptop and it is working fine.

@Phaedrux the running twice is because the normal process for a Delta is repeated G32s until the value converges on a acceptable value (typically >.05 for a good stiff build and >.1 for cheaper ones). Then M500 and provided nothing shifts one or two G32s should do you.

As to the why of the outside bounds I'm not sure. The fixing by resetting makes me think that something is up with the config-override being generated.

Could you give us the output from editing the bed.g to change the S parameter on the final G30 command to S-1 to get a report only?

I thought I remembered this was possible long ago and I checked the Wiki.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M557_Set_Z_probe_point_or_define_probing_grid

You used to be able to define the probe points on a Cartesian bed like you can with a Delta back in the 1 series firmware.

It sounds like Phaedrux thinks it might happen again some day.

@NitroFreak do you have a test you recommended?

So at the start of one of the macro's I use on my Delta printer the macro leads with:

M291 P"FIRST PROBE PRINTER SETUP: Did you delete heightmap.csv and config-override.g?  To Continue Click OK" R"SETUP PRINTER" S3

In 2.0.7 and 2.1.1 it worked. However, in both 2.1.4 and 2.1.5 the pop up has no text or cancel. Only a gray (I am using the dark theme) box with the words "OK" displayed.

Has something changed about how M291 should be configured?

Board: Duet 2 Ethernet
Firmware: 2.05_1
DWC: 2.1.5
Delta - Rostock V3.2 design

@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 1920x1080

functions fine

@CorvoDewittV2 do you have a good clear video of it in action?

Phaedrux is right that if changing the controller did not cause a change in the outcome it is most likely mechanical. I had hoped it would be noticeable from the video.

The only other thing is slicer. Have you tried any other ones or validated all the non-physics related settings are the same between the printer that doesn't do it and the Rat one?

@bearer I am hosting myself (or plan to) but was asking what he has done that works.

@vwegert the B value controllable the work area radius. It acts as a safety but otherwise doesn't affect anything but how far out the platform can move.

I wouldn't adjust the R value as that affects the G32 calibration.

@Schild0r yes, I have tried changing to M122 P1 and it doesn't crash but only gives the SD card info and complains about wanting a T parameter.

@arhi how do you trigger the Duet to stop printing when Spaghetti Detective finds a problem?

I've got a Jetsen Bank that isn't being used (was mentioned to be the new heart of a PS2 replacement for my wife but her parents got her a retrocade before I completed) and am thinking of using it for Spaghetti Detective but I haven't figured out how to stop the print.

I have Duet2Ethernet running 2.05_1 firmware and 3.1.1 DWC.

When I send a M122 via DWC console the web site stops responding (err_connection_refused) in both Firefox (stable newest update) and Vivaldi.

There are no arguments to the M122

The only way to return function is walking over and power cycle the printer.

The printer otherwise works fine. I was adding this to my end gcode to monitor for problems.

@Elvis0z so did disabling fix it or did not disabling fix it?

@Phaedrux the running twice is because the normal process for a Delta is repeated G32s until the value converges on a acceptable value (typically >.05 for a good stiff build and >.1 for cheaper ones). Then M500 and provided nothing shifts one or two G32s should do you.

As to the why of the outside bounds I'm not sure. The fixing by resetting makes me think that something is up with the config-override being generated.

Could you give us the output from editing the bed.g to change the S parameter on the final G30 command to S-1 to get a report only?

I think the pop up in FW2 is the one that shows up at the bottom for a short while. I use the dark UI so it shows in a light blue. Most messages fade away after a few seconds.but some are persistent.

I'll try taking a screen shit if that didn't make sense.

@bearer the spaghetti detective bit was because with a SBC to act as the plugin host it would be potentially easier to port the octoprint plugin.

The comment about smoothness is because I was told once that because of the complexity of the Delta math that on Duet 2 if you enabled mesh bed compensation that it no longer calculated every point to move but fell back on arcs and segments like ordinary RAMPS. But if a SBC offloads some work from the duet I wondered if more could be calculated with the now freed up resources.

It presumes that the DWC takes up some amount of resources to run on the Duet processor.

I found the blog post at https://www.sublimelayers.com/2017/05/fdffsd.html?m=1 helpful when I was learning what trigger height means and how it changes.

He posts still in some of the Delta communities and the visuals really help one understand. With the FSR and Smart Effector style probes the understanding is key and confusing with all the negative values.