@dc42:

Your M574 commands say that you are homing to high end endstops (X2, Y2) but you are homing to the low end so it should be X1, Y1.

Yes you are right! now homing great, now just getting the Bltouch to work as Z axis homing!

The interpolated option makes the motors much quieter. It tell the drivers to generate x256 microsteps even though the Duet only sends step pulses at x16. It only works when you have x16 selected.

Thank you for your answer

Correct,
This also overrides the temperatures defined in G10, right?
I was hoping that there would be a possibility to work with the new G10 (for example G10 P0 S225 R170) function.

But I need a variant to implement the preheat.
Is there something there?

As DjDemonD says. If you want to add an additional thermistor, connect it between your chosen thermistor input on the expansion connector and VSSA. Connect a 4k7 1% reference resistor between the thermistor input and ADVREF.

OK, I will look into using the M579 but that may get tricky with the scaling. That said, X and Y are off nearly by the same amount so maybe it won't be too bad. Will make small adjustments until I get it in that sweet spot.

If X and Y jog in the correct directions but Y homes the wrong way, that implies that your homall.g and homey.g files are homing Y the wrong way.

Looking at the front of your printer, which directions are +x and +y, and where are your endstop switches located?

I may not have written correctly
The slower the switch-on is turned on, the bed bends more.

Increasing the frequency of inclusions - will reduce this problem.
but there are long off bed

Just to follow up, i did get my slic3r dialed in using a volumetric max speed of 8 mm^3/s and 60mm/s max auto speed. I tried letting slic3r do all speeds automatically except the first layer and small perimeters. Print speed wasnt too bad, every now and then a single layer would print very slow while the rest appeared to be closer to the max of 60mm/s. I was not trying to really print faster, just make sure that the filament flow was consistent. I ended up going back to Simplify3D. While i wish they did more updates and had some newer features like setting up more speeds for different features and native firmware features, the prints came out better even with similar settings. I also ran out of PETG and picked up another roll. I was using eSUN white but the local fry's electronics store didnt have anymore so i got some MG chemicals PETG natural… they have a pretty poor filament selection. The MG chemicals PETG prints much different than the eSUN and actually is drastically better in terms of quality and strength. FYI for those interested.

As FMA says, but add parameter S2 to that G1 command. You may need to move the motor at least one full step to clear the stall status, so about 0.2mm or a little higher instead of 0.01mm. You can put that command near the start of your homeall.g file.

I do have a Cartesian printer and mesh works fine for me. I am homing to Z-max and using a capacitive probe for bed leveling. I would suggest you to perform a repeatability test wit a Macro:

[[language]] G1 X86.5 Y105 Z20 ; Move probe to bed center, not nozzle tip. G30 ; Find the bed G1 Z10 ; Raise the X-carriage G30 S-1 ; Probe and report the value G1 Z10 ; Raise the X¡-Carriage G30 S-1 ; Probe and report the value .... ; Repeat G1 Z10 G30 S-1 as many times as samples required

I copied the output of the G-Code console onto an spreadsheet and calculated average and standard deviation. My standard deviation is 0.016 for a capacitive sensor. On the config file I used "average+standard deviation" as Z offset.

For the mesh leveling, I am using a Macro which works beatifully and because I probed in the center, the view if very representative of the tunings that I need to do for a better leveling:

[[language]] G28 Z0 ; lets move to the ceiling to avoid crashes G28 ; homeall.g G1 X86.5 Y105 F6000 ; move to center of the bed G1 Z40 F1000 ; Fast move to lower Z G1 Z10 F500 ; Medium move to lower Z G30 ; Probe the bed at the current XY position. When the probe is triggered, set the Z coordinate to the probe trigger height. G29 S0 ; Run probing sequence defined by M557 on the config.g M374 ; Save calibration data. Default is sys/heightmap.csv G1 X-5 Y-2 Z10 F4000 ; Go outside the bed

Because the firmware assumes that any drivers of the 12 supported that you haven't assigned explicitly areused for extruders.

Thanks, this is what I was looking for.

It looks to me that your leadscrews have got out of sync. This happens on printers with dual lZ eadscrews, because when you lose power and then restore it, each motors jumps to a nearby multiple of 4 steps that matches the motor current; and the 2 motors may jump in opposite directions.

For now I suggest you resync the motors manually to level the bed or gantry. When you have your printer running well, you may wish to do this resync automatically, as described at https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors.

Im still at it and yet to find a sollution, however i think it actually has something to do with the speed of the print.
I belive it might have something to do with the speed overrides and adjusting print speed for layers below x sec.

Still trouble shooting

@dc42:

I see some issues with those files. In config.g you have:

M558 P5 R0.4 H10 F300 T2400 ; Set Z probe type to effector and the dive height + speeds

In the M558 command, F300 is too low, see the Smart Effector instructions on the wiki.

I noticed the reprap configurator gives these values for the smart effector, I had issues with mine not probing properly (basically it just slowly pressed the nozzle into the bed) until I read the wiki and adjusted the dive speeds.

Yes it does.

I have two duet printers, I access them by going to:

http://railcore.local

and

http://nostock.local

I have no clue what their IP addresses are, or if they change. I use Windows 10.

You can download bonjour here:
https://support.apple.com/downloads/bonjour-for-windows

"Bonjour Print Services for Windows"

Thank you David that was the Clue I needed all now sorted.

I did indeed put it on the E0 thermistor input instead of the bed one Doh

Doug

The maximum speed of homing moves is much slower than for printing moves, because the endstops have to be checked. So if you use high microstepping, you need to use slower homing speeds. The 1.21RC firmware should allow slightly faster homing than previous versions did.

To check whether you are trying to home too fast for the microstep setting, first make sure the printer has a long way to go to home, then run M122, then home it. Then run M122 again and check the MaxReps field. If it is higher than about 50 then you are homing too fast.

@DjDemonD:

start gcode for my kossel XL
M80 ;PSU on
G4 P2000 ;pause for paneldue
M98 P/macros/rapidcold ; set extruder temp to 130 with max cooling
M109 S0 ;hotend off
G28 ;home
;G32 ;autocalibration - set grid on/off in bed.g
M190 S[first_layer_bed_temperature] ;heat bed
M116 ;wait for temps.
;M98 P/macros/NozzleClean ;nozzle clean macro
G1 X5 Y0 Z5 ;bed centre
G30 ;set Z
M564 S0 ;disable movement limits
G1 Z15 X47.7 Y-160.1 F3000 ;move to front
M109 S[first_layer_temperature] ; set extruder temp
G1 E20 F100 ;extrude 20mm slowly
G4 P1500 ;pause
G1 Z4 X40 Y-168 F6000 ;move down to swipe filament off
G1 Z2 X0 Y0 F6000 ;move to bed centre
M564 S1 ;restore movement limits
M220 S100 ;optional speed control default 100

End gcode
M220 S100 ; set speed back to 100%
G28 ; home
M98 P/macros/rapid130 ; set extruder temp to 130 with max cooling
M140 S0 ; turn off bed temperature
M141 S0 ; turn off chamber heater
M104 S50 ; set nozzle below GTT
M116
M84 ; disable motors
M106 S0 ; part fans off
M81 ;PSU off

The last part of your end gcode is the same as mine but M116 for me just get ignored which is annoying, have you ever had that issue?