Posts made by tcj

@Veti Thank you so much!
It works!

@Veti

tried M672 S131:131 without success - even no flashing of the LED

and before you're asking

;### Z-Probe ###
M558 P8 R0.2 F1200 H2 C"zprobe.in"
G31 P100 X0 Y0 Z-0.19           		; Set Z probe trigger value, offset and trigger height             
M557 R180 S40                          		; Define mesh grid

yes, but it's there since I received it and it is only on the lacquer coat

Wiring is ok - worked for months
Updated RRF a few days ago, but not yesterday
Working last night at last

Sep '19 at filafarm.de
I've already sent them a mail

I've already inspected the whole effector with a magnifying glass
There is nothing abnormally

Thanks, but that is not the only thing that I tried several times but without any success.

Hi,
since today my smart effector seems to be faulty.
It continuously triggers even with the board alone (without heatsink, arms, fans ..), green trigger light and 1000 value in web control.
It flashes three times when turned on and then lights green all the time.
I can't see any damage

HELP

Thanks
Thomas

@dc42 Take your time.

I am talking about the wiring
That does not seem to be straight forward

Hi,
how do I have to connect a FYSETC Mini 12864 to a Duet Maestro with the latest Firmware 3.2?
I'm sorry, but I don't get it over the long threads and even https://duet3d.dozuki.com/Wiki/Connecting_an_LCD_control_panel#Section_12864_display_using_ST7567_controller_chip does not really help

Thank you in advance

@Baenwort said in Cura Script to Automatically Probe Only Printed Area:

Does this bring it closer to working for Delta's? Or at least probing a square area of the circular bed?

Yes, this makes it usable for delta's, because
"For Cartesian printers, specify minimum and maximum X and Y values to probe and the probing interval. For Delta printers, specify the probing radius. If you define both, the probing area will be the intersection of the rectangular area and the circle. "
https://duet3d.dozuki.com/Wiki/Gcode#Section_M557_Set_Z_probe_point_or_define_probing_grid

@zapta thank you

C:\Users\tcj-a>C:\Users\tcj-a\AppData\Local\Programs\Python\Python38-32\python.exe C:\Users\tcj-a\Documents\scripts\duet3d_automesh.py C:\Users\tcj-a\Desktop\single_wall_box.gcode --meshable=-185:185,-185:185
MESHABLE area: -185.0:185.0,-185.0:185.0
Opening gcode file: C:\Users\tcj-a\Desktop\single_wall_box.gcode
Read 7472 lines
Parsing state = ParsingState.WAITING_FOR_LAYER1
; Automesh: begin layer 0
Parsing state = ParsingState.IN_LAYER1
; Automesh: begin layer 1
Parsing state = ParsingState.LAYER1_DONE
First layer print areas: 0:22,12:22
printArea: 0:22,12:22
Will use 3 x 3 mesh points
Marker: M557 TBD  ; parameters will be set automatically
Inserted: M557 X-10:32 Y2:32 P3:3

single_wall_box.gcode

obviously the script does not handle negative numbers as needed, because the first layer print area is -22:-22, 22:22

@zapta I'm sorry to say that, but it does not work properly yet.
The script gives

M557 X-10:32 Y-10:32 P3:3

where it should deliver

M557 X-32:32 Y-32:32 P3:3

for a testcube in the middle of the bed with some mm of skirt

total dimensions +/- 21.xx mm

@DK90 said in Cura Script to Automatically Probe Only Printed Area:

but wehn i start the print, there is now mesh leveling ....

and it never will without G29

this is a part of my start sequence

M140 S[first_layer_bed_temperature]
M104 S[first_layer_temperature]
M116; wait for temperatures to be reached
 
; For automesh
M557 TBD  ; parameters will be set automatically
G28 ; home
G29 ; mesh

@DK90 the space in "Program Files" leads to this error
change it to

C:\Users\Dominic\AppData\Local\Programs\Python\Python36-32\python.exe "C:\Program Files\Prusa3D\PrusaSlicer\duet3d_automesh.py"

notice the "

@zapta

Thank you

@zapta thank you for the effort, but ist does not work yet
only defining the default meshable area within the script (line 50) by

default="-185:185,-185:185"

works,
but when adding

<path to your python3> <path_to_the_duet3d_automesh.py file> --meshable "-185:185,-185:185"

to the Post-processing script, it fails