Only probe where printed. Solution here!

Exerqtor

Shouldn't the code be:

if exists(var.minPrintX)
  set var.m557MinX = var.minPrintX
if exists(var.maxPrintX)
  set var.m557MaxX = var.maxPrintX
if exists(var.minPrintY)
  set var.m557MinY = var.minPrintY
if exists(var.maxPrintY)
  set var.m557MaxY = var.maxPrintY

dc42

@exerqtor said in Only probe where printed. Solution here!:

@dc42

Shouldn't the code be:

if exists(var.minPrintX)
  set var.m557MinX = var.minPrintX
if exists(var.maxPrintX)
  set var.m557MaxX = var.maxPrintX
if exists(var.minPrintY)
  set var.m557MinY = var.minPrintY
if exists(var.maxPrintY)
  set var.m557MaxY = var.maxPrintY

Correct! I did say it was untested.

Exerqtor

@dc42 said in Only probe where printed. Solution here!:

@exerqtor said in Only probe where printed. Solution here!:
@dc42

Shouldn't the code be:
if exists(var.minPrintX)
  set var.m557MinX = var.minPrintX
if exists(var.maxPrintX)
  set var.m557MaxX = var.maxPrintX
if exists(var.minPrintY)
  set var.m557MinY = var.minPrintY
if exists(var.maxPrintY)
  set var.m557MaxY = var.maxPrintY
Correct! I did say it was untested.

Yeah np, just trying to get why it don't work lol. For some reason still won't probe just the print area.

Exerqtor

@dc42
Looks like it might be a scope issue, even though "var minPrintX = 88.6323" (for example) is in the start gcode of an ongoing print I get this

3.12.2021, 13:47:51	set var.m557MinX = var.minPrintX
Error: meta command: unknown variable 'minPrintX'

when entered in DWC console.

dc42

@exerqtor each GCode input channel has its own set of local variables. So a local variable created by a print file will not be visible from the console.

supernovae

@pcr said in Only probe where printed. Solution here!:

@supernovae

easier solution

(Cura slicer plugin) To make the macro to work in Cura slicer, you need to install the post process plugin by frankbags - In cura menu Help -> Show configuration folder. - Copy the python script from the above link in to plugins folder. - Restart Cura - In cura menu Extensions -> Post processing -> Modify G-Code and select Mesh Print Size (PLUGIN)

the
M557 X%MINX%:%MAXX% Y%MINY%:%MAXY% S8

Not sure if you can help, but running the python plugin and enabling the M557 in start gcode I always get a huge max X

For example:

looking at the gcode output:

M557 X131.900:1500.000 Y131.900:168.100 S35.000 ; Leveling mesh defined by LevelingMeshOptimizer

Not sure where 1500 comes from.. any idea where to look for in fixing/address that? Or anyone getting this in latest cura?

Exerqtor

@dc42 said in Only probe where printed. Solution here!:

@exerqtor each GCode input channel has its own set of local variables. So a local variable created by a print file will not be visible from the console.

Well in that case I have no idea what to do except declare them as global instead of local, and reset them to the default in the end of each probing session.

dc42

@exerqtor yes that should work.

supernovae

@supernovae

Found the issue, I have some commands to set speed on layers and it shows up as X1500 which the regex catches... maybe i'll try and see if i can limit/exclude it lol

Dogma2k

I'm trying to do this on my printer right now, but somehow I can't get S3D to output the min/max XY for the file to be printed.
Anyone have a tip on how to do this with S3D?

Proschi3D

This post is deleted!