There are a lot of virtual knobs to turn when getting a machine dialed in. Is there consensus or an expert opinion on what to tackle first? There are so many interactions between speed, accel, jerk, PA, DA, X, Y. Z, & E. Also, when starting to adjust the first variable, how do you have the others set?

I'm not having any significant issues, but it seems there could be an endless cycle of test prints and tweaks as one sorts out the interactions. I just feel like I'm probably not taking the most efficient approach.

Opinions/Advice/Links to existing threads? TIA

I have replaced the control boards in my 3 printers with Duet boards, and it's the best thing I ever did to these machines. When I've had issues I've been able to post specific questions here on the forum and have always received prompt help that got me going.

Take a deep breath and give us enough information to start getting you going.

The Duet Wifi board has been replaced with an Ethernet board, and the machine is now on a separate network that will not be accessible from the public wifi or publicly accessible computers.

Thanks.

Achieving dimensional accuracy isn’t as simple as a single scale measurement. I use S3D for slicing and it has X, Y, Z part scaling plus a horizontal offset. I don’t know IdeaMaker well, but I’m guessing X and Y-axis compensations in the Printer Settings dialog work for XY scale. Part Scaling can also work, although I don’t know why they have chosen Width Depth and Height over X, Y, and Z. Under the OTHER tab, XY size compensation may be the same as S3D’s Horizontal Offset.

Attached you will find a part I'm calling a Calibration Cross - STL and JPG drawing. It includes internal and external features, both large and small. I have also attached an Excel Spreadsheet (Zipped) which allows you (by trial and error) to see the impact of scaling and horizontal offset values in correcting part dimensions.

Print off a Calibration Cross with no scaling and no horizontal offset. Enter the measured values into the spreadsheet and experiment with different X & Y scale factors as well as the horizontal offset value to minimize the resulting error on all of the measured dimensions. The solver add-in can help narrow in on the best values.

Whenever I’m going to print using a new setup, filament, significantly different print speed, layer height, temperature, etc, I start by running a Calibration Cross and use the spreadsheet to calculate scaling and offset numbers. This technique has proven to be a reliable way to ensure dimensional accuracy on parts. The Z-scale on my N2+ has proven to be quite accurate, so I just use 100% on that.

I can generally achieve part accuracy better than +/- .1mm (.004") on all dimensions.

calibration-cross.xlsx
calibration-cross.stl
100mm.stl

@Phaedrux

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 687C

I haven't tuned heater 1.

DISCLAIMER - I haven't red the DWC documentation carefully - if the answer to my post is RTFM, I'm OK with that - and I did search first but didn't find anything. I doubt I'm the first person to raise an issue.

I use an iPad (Gen 4 retina display) at my printers - landscape mode. I also pop the printer interface up on my phone pretty often.

I just updated one of my printers to V3 today. I'm disappointed with DWC on the smaller displays.

Here's a comparison of my iPad display:
DWC V2

DWC V3

On the new DWC all the elements are a lot bigger and it just feels cramped. The machine movement buttons were the first thing that really got my attention. When setting the Z-Offset in a new nozzle, the Z movements are 5mm and .05mm. On the older layout there's more room for buttons and there's a .5mm. I wrote a macro for 1mm so I could get close enough to use the .05mm.

I have to scroll to access macros - scroll to access extruder control.

The display on my iPhone is also a lot more drawn out with less room for stuff because all the elements are larger.

Would like to have a setting to scale things down so more information can fit on the display.

Thanks.

Probing speed also impacts accuracy. I was getting good results with 2mm/s probe, but slowed it down to 1mm/s for good measure - reduce the probing height to help recover the time.

I really appreciate all the help.
I changed the can lines per @DIY-O-Sphere to

M950 F1 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P1 S1 H1 T40 ; set fan 2 value. Thermostatic control is turned on

Functioning properly and not showing up on the dashboard slider.
The Z-Probe on this machine is accelerometer-based and that's a little flaky, but doesn't seem to be software related.

Up and running now, so 'til next time ...

@rechrtb Nothing has blanked out in since I installed the beta on all three machines.
Thank you ... seems to be solved.

Have you tried printing with that height map? How does your first layer look?

@rechrtb Yes. I have all three machines open in different browser tabs on multiple computers.

@rechrtb Nothing has blanked out in since I installed the beta on all three machines.
Thank you ... seems to be solved.

@rechrtb So far the machine running the BETA wifi server has not flaked out. Both of the other machines have.
I will load the BETA onto the other two machines later today and see if that seems to hold up.

@rechrtb Results in inconclusive at this point, but the machine with the BETA code has not yet blanked out.

One of the machines running 2.1.0 is still OK - the other has gone white in Chrome, and in Firefox the first refresh come up white, a second refresh looks like this:

@rechrtb I installed the beta on one of the three machines. It takes a while for things to misbehave. I will follow up.

@chrishamm said in DWC White Page only in CHROME:

@zemlin What WiFi server version are you using and do you have FTP/Telnet enabled as well?

The duet wifi server is 2.1.0 on all three machines.

FTP and Telnet are both disabled.

; Network
M552 S1                                            ; enable network
M586 P0 S1                                         ; enable HTTP
M586 P1 S0                                         ; disable FTP
M586 P2 S0                                         ; disable Telnet

@Phaedrux I have plenty of fresh SD cards on hand. I always have multiple computers connected to the DWC. I use the one Chromebook with Chrome and usually 2 windows machines connected by Firefox. I'll put a new SD card in one of the machines.

@Phaedrux

This machine was displaying OK on the Chromebook. I did a refresh for no good reason, and it came up white. Double checked it with Chrome on a PC and it was also white screen. This is from the PC.

That link was going to the status page.

If I just go to the machine IP, the console looks like this:

One of the machines when white in Chrome again. The first sign of trouble is a refresh brings up a mostly text version of the page. Next refresh is all white.

Cycling power on the machine brought it back again.

@Phaedrux said in DWC White Page only in CHROME:

Clear the cache in chrome?

That was the first thing I tried. I then did a full reset (Powerwash) on the Chrome book. That did not resolve it. This morning I cycled power on all three 3D printers and they all started working in Chrome again.

Odd one ... but fixed for now.