Best posts made by Scachi

The selftest command is supposed to do an endless cycle, mine does that too.
The "startup selftest" when the BLTouch gets powered (printer switched on) is two times only, but there is no command for the "startup selftest".

When the probe input responds when you trigger the probe manually, it sounds like it is working ?
Have you tried to move your probe up above the bed a bit and issue a "G30 S-1" (you may have to home x and y first) and trigger the probe manually with a light touch against the pin ? This should stop the movement and show you that everything works as it should. Keep a finger near the power button of you printer so you can stop it if the touch against the pin isn't stopping the movement.

@cdl1701yahoo-com said in Second extruder will not work again:

M92 X80 Y80 Z1600 E848.2:E848.2 ; Set steps per mm

I don't know if this is the cause, but it looks like there is in error in this line,
shouldn't that read (without the second "E")
M92 X80 Y80 Z1600 E848.2:848.2 ; Set steps per mm

@bobskinner according to this page: http://files.fieldofview.com/cura/Replacement_Patterns.html
it should be "{speed_travel}" , not "{travel_speed}"

I had a precision piezo ordered some time ago after I had trouble with my BLTouch (I damaged it).
As the shipping was taking some time I bought and installed a new BLTouch and never used the piezo.

Modifying my printer a few days ago, I took the chance and build a custom mount for the precision piezo to give it a try.

I am more than impressed:
G32 bed probe heights: 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013 0.013, mean 0.013, deviation from mean 0.000

Looks like it is as good as a z-probe can get

Replacing the TR5 did fix my issue.
I'll spend more attention now to not shorten it again as I don't want to solder something tiny like that again

I had this issue with the page showing up like that too some time ago.
I cleared my browser cache (firefox) and tried a different browser, both without success. Opening the webpage from my phone did work.
Rebooting my router (fritzbox) did the trick finally.

I have modified my perl script. It will add the first tool to the file if not is found before the first layer change.
Now I can use a single print & printer settings with slic3r PE.

You need to add this line to your start gcode in slic3r so the script knows the default tool to use:

;my_default_tool=[perimeter_extruder]

and this line to the end of your start gcode for the script to know when the first layer is started:

;my_startgcode_end

Here is the script:

#!/usr/bin/perl -i
#
# - Translates Fan gcodes 
# -	Adds the default tool as first tool when none is found before the first layer change
# -	Removes M109 : set and wait for temperature command
#
# You need to add this line to your start gcode in slic3r so the script knows the default tool:
#	;my_default_tool=[perimeter_extruder]
# and this line to the end of your start gcode for the script to know when the first layer is started:
#	;my_startgcode_end

use strict;
use warnings;

$^I = '.bak';
# read stdin and any/all files passed as parameters one line at a time

my $DefaultTool="0";
my $FirstToolCheck="0";
my $SlicerTool="-1";

while (<>) {
	if (/^;my_default_tool\=([0-9]{1})/) { # search for ;my_default_tool
		#print "; Found Default Tool $1\n";
		$DefaultTool=$1-1;
	}
	
	s/M106/M106 P0/; 	# model fan speed command
	s/M107/M106 P0 S0/; # model fan turn off
	
	s/M104\s*(S[0-9]{1,3}) T([0-9])/G10 P$2 $1/; # set tool temperature (old)
	
	# first tool search , use DefaultTool if none is found before the first line containing ;BEFORE_LAYER_CHANGE
	if ($FirstToolCheck > 0) { # check if first tool is defined
		#print "; First Tool Check > 0\n";
		if (/^T([0-9]{1})/) { # search for first tool set
			$SlicerTool=$1;
		}
		if (/^;BEFORE_LAYER_CHANGE/) { # when no tool is found use DefaultTool parsed from GCODE line, example: ;my_default_tool=[perimeter_extruder]
			$FirstToolCheck = "0";
			if ($SlicerTool < 0) {
				print "T$DefaultTool; set default tool as first tool as none was found\n";
			}
		}
	}
	if (/^;my_startgcode_end/) { # search for ;my_startgcode_end
	  print "; is a tool defined before reaching line ;BEFORE_LAYER_CHANGE ?\n";
	  $FirstToolCheck="1";
	}
	
	s/M109/;M109/; # deprecated don't use "set temperature and wait for it to be reached" - use duets own tool change macros and G10 command
	print;
}

@3dware said in Checksum errors:

I have now switched to a duet ethernet and still have the same errors.

I had similar issues. For me the fix was using a shielded cable for the paneldue connection and having the shield connected to the - panel due pin on the duetwifi board. The correct solution for my case should be grounding the whole printer correctly.
https://forum.duet3d.com/topic/11104/paneldue-checksum-errors-when-heater-on-or-hand-near-pdue-cable

The first step, moving the duet wifi from the cartesian style to the new core-xy style one did work fine without bigger issues.
The wiki about the corexy configuration and bltouch did help a lot

A broken wire (white one, probe) in my bltouch and a bad crimped contact on the y-connected cable to the stepper-motor were the biggest issues.

I am using a y-splitter too.
To un/load my filament from the spool to above the Y-splitter I select the tool to use with the P0 argument in my load/unload macros.
It activates the tool without running the tool change macros.
After load/unload is finished I select a non existing tool, T99, with P0 too.

T1 P0 ; select tool 1 but don't run any tool change macro files

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

There is a setting to configure a fan to run at startup at 100% for some time to get those fans running first and then set it to the requested speed:
https://duet3d.dozuki.com/Wiki/Gcode#Section_M106_Fan_On
Extra Parameters :
Bnnn Blip time - fan will be run at full PWM for this number of seconds when started from standstill. Default is B0.1.
Try a longer time than 0.1 to test if that helps.

@devleon
I use the "Filament Density" g/cm³ field to enter a value as the standby temperature per filament type as I am used to it from my earlier printer with two separate tools/heaters/nozzles and I use it now as the initial temperature to soften the filament at the nozzle for probing Z with a precision piezo.

The main usage of my script it to track the tool set at the start of the print and if it is missing set it to my default one.
Using Slic3r Prusa Edition 1.41.2 the gcode doesn't contain the starting tool in all cases so I fixed via the script, it also translates the fan gcode to work with my settings.
You can get the script here and check if it is useful for you: https://drive.google.com/drive/folders/1uOl2hUzCcJHYZljG15EenpiywwpBvULu

This are my "Start G-code" settings for using the density as standby temp:

;slic3r start g-code
;my_default_tool=[perimeter_extruder]
;my_part_fan=P0
M115 U3.1.0 ; tell printer latest fw version
M83 ; extruder relative mode
;
T-1 P0 ; deselect all tools
G10 P0 S0 R0 ; clear settings of tool 0, rear extruder
G10 P1 S0 R0 ; clear settings of tool 1, front extruder
;
;G29 S1; load last heightmap ; not needed atm as my bed is flat enough
;
M140 S[first_layer_bed_temperature_0] ; set bed temp
G10 P0 S[first_layer_temperature_0] R[filament_density_0] ; set standby temp to filament density
G10 P1 S[first_layer_temperature_1] R[filament_density_1] ; set standby temp to filament density
T0 P0; select tool for heating, do not run tool macros
T1 P0; select tool for heating, do not run tool macros
T99 P0; select dummy tool to set the previous tool to standby  temp
;
G28 ; home
;
M190 S[first_layer_bed_temperature_0] ; wait for bed temp
M116 ; wait for all temps to reach
G28 Z ; home Z again because of bed heating/filament at nozzle
;
;
;my_startgcode_end

@paulhew Pressure Advance, I have this configured in config.g duet :
https://duet3d.dozuki.com/Wiki/Pressure_advance
https://duet3d.dozuki.com/Wiki/Gcode#Section_M572_Set_or_report_extruder_pressure_advance

Have you tried printing with the part fan off to see if it still looks the same ?

@CorvoDewittV2 Did you buy it as a kit ? Did you ask them (where you bought it from or the guys who designed it) if the have experience with this issues ? Perhaps it is a common issue and they know the most common cause in their design that can cause it.