#Why isnt my printer making a camp purge line?

74 messages · Page 1 of 1 (latest)

wooden ruin
#

I think its a slicing issue

quiet ice
#

Send a gcode and klippy.log.....We still don't have magic glass bowls

wooden ruin
#

iam sorry , i forgot to download it as a 3mf. Those magic glasses would be fun tough

quiet ice
#

Please send a gcode and not a 3mf

wooden ruin
#

here:

quiet ice
#

I also still need the klippy.log....

wooden ruin
ebon tinsel
#

So that’s the name of your macro [gcode_macro LINE_PURGE]

#

And that is what you have in your start gcode section of your slicer BED_MESH_CALIBRATE PURGE_LINE

#

Do I need to write more?

civic crystal
#

making two purgue lines:

  M118 Haciendo lineas de purga
  # Dibuja la primera linea de purga
  G92 E0 
  G1 X10 Y1 Z0.28 F2000
  G1 X225 Y1 Z0.28 E20 F1000
  G92 E0 
  G1 X225 Y1.03 Z0.28
  G1 X10 Y1.03 Z0.28

  # Dibuja la segunda linea de purga
  G92 E0 
  G1 X10 Y2.5 Z0.28 F2000
  G1 X225 Y2.5 Z0.28 E25 F1000
  G92 E0 
  G1 X225 Y2.53 Z0.28
  G1 X10 Y2.53 Z0.28
quiet ice
civic crystal
#

???? KAMP?

quiet ice
#

Click on that blue highlighted KAMP word above (it's an embedded link) ^^
Basically it will generate adaptive meshes and purge lines depending on your print size. So if your print is only a small benchy in the middle of your printer, it will only generate a mesh for the needed print area.

civic crystal
#

Now I know, the idea to make my two single lines, started after some experience with similar macros and procedures, in the beginning I was even used an Excel sheet to decode the equivalent gcode from original macros, and I understand you need to make the lines, just in the way you want, but finally, I wrote my pure gcode purgue lines, and move my efforts to other issues

#

I know it's important for you, but in my case, my start_print macro, makes some beeps, alights some leds, make the first homing procedure and raises the extruder head for not suffer tbe heat while heating nozzle and bed, then, once everything is hot, makes home again, Z-tilt, mesh adjusting, two purgue lines, and finally starts printing the part, then for me it's not so important to take less time, or just make the mesh of only the real printing area, but I really understand you

quiet ice
#

I didn't mean to judge anyone. Everyone is doing their macros how they like it. I was just trying to inform you that the OP asked about KAMP and not overall for purge lines. And as you asked what KAMP is, at least I interpret your message like that, I explained it.
Sry if you misunderstood the intention of my messages, but it's sometimes crucial to stay at the correct and asked topic to not confuse anyone.

civic crystal
#

No sorry, I don't want to make you feel bad, I understand you perfectly, and I'm grateful with you to remember me what KAMP is, I only wanted to explain you my point of view, I don't like to bother you in any way, and if I could help you I'll do it, don't doubt it.

vagrant pecan
#

Hallo, kann mir jemand mein Fehler sagen warum alles mit Kamp geht außer Adaptive Meshing nicht, wo liegt da der Fehler bei mir, versuche es schon eine weile.

#

Hello, can someone tell me my error, why everything doesn't work with Kamp except Adaptive Meshing, where is the error in my case, I've been trying for a while.

ebon tinsel
#

Let’s start with the message you seeing

#

And post a Klipper.log

vagrant pecan
#

Is this possibly the one with the BTT_BED_MESH_CALIBRATE

ebon tinsel
#

[EXCLUDE_OBJECT]``` one time is enough, let the lower case in. The UPPER case is wrong any how
vagrant pecan
#

ok

ebon tinsel
#

Remove that [gcode_macro BED_MESH_CALIBRATE] rename_existing = BTT_BED_MESH_CALIBRATE gcode = SET_GCODE_VARIABLE MACRO=_KNOMI_STATUS VARIABLE=probing VALUE=True BTT_BED_MESH_CALIBRATE SET_GCODE_VARIABLE MACRO=_KNOMI_STATUS VARIABLE=probing VALUE=False

#

You can have only one BED_MESH_CALIBRATE

#

You loose KAMP as that is most likely included lower than Kamp

#

In the Klippy.log you see what printer.cfg Klipper loaded. That is very important in a case where you have a lot of includes

vagrant pecan
#

Where can I find it I don't see it... BTT........

ebon tinsel
#

You need to look in your printer.cfg and all files you included there. I can not see where it is that information is “lost” in the klippy.log

vagrant pecan
#

ok

#

oh in KNOMI.CFG

#

Klipper meldet: ERROR

gcode command BED_MESH_CALIBRATE already registered

#

echo: "extruder" not hot enough
17:47
Error evaluating 'gcode_macro BED_MESH_CALIBRATE:gcode': TypeError: bad operand type for abs(): 'Undefined'
17:47
Error evaluating 'gcode_macro BED_MESH_CALIBRATE:gcode': TypeError: bad operand type for abs(): 'Undefined'

#

nach QGL geht es nicht weiter , kommt dann mit dem Fehler

#

After QGL it doesn't go any further, then the error appears

ebon tinsel
#

First do a rollover of your Klipper.log

#

Then start it again and if the failure is Bach send a Klipper.log

#

You do not need to write in German

vagrant pecan
#

I would love to, but the translator can help

#

I'll test it

#

I also stopped now because he didn't do the adaptive meshing, he just did it normally.

#

oh

ebon tinsel
#

You did not do a rollover …The file is already rather big so please do that it is a pain to scroll thru a ~9MB text file.

#

Kamp is now in

#

So how is the output in the console. It’s sends a few messages

vagrant pecan
#

it's like he's still doing the whole BED_MESH_CALIBRATE thing.

#

I reset the klipper log

ebon tinsel
#

Make a screenshot of your console output

#

Found it ```[gcode_macro PRINT_START]
variable_pa_default = 0.030
variable_pa_asa = 0.025
variable_pa_abs = 0.03
variable_pa_petg = 0.07
variable_pa_pla = 0.025
gcode =
{% set FILAMENT = params.FILAMENT|default('Default')|string %}
{% set MIN_TEMP = params.EXTRUDER_TEMP|int * 0.9 %}
{% set BED_TEMP = params.BED|default(70)|int %}
{% set EXTRUDER = params.EXTRUDER_TEMP|default(205)|float %}

{% if params.FILAMENT == 'ASA' %}

SET_PRESSURE_ADVANCE EXTRUDER=extruder ADVANCE={pa_asa}

{% elif params.FILAMENT == 'ABS' %}

SET_PRESSURE_ADVANCE EXTRUDER=extruder ADVANCE={pa_abs}

{% elif params.FILAMENT == 'PETG' %}

SET_PRESSURE_ADVANCE EXTRUDER=extruder ADVANCE={pa_petg}

{% elif params.FILAMENT == 'PLA' %}

SET_PRESSURE_ADVANCE EXTRUDER=extruder ADVANCE={pa_pla}

{% else %}
SET_PRESSURE_ADVANCE EXTRUDER=extruder ADVANCE={pa_default}
{% endif %}

STATUS_READY
M117 STATUS_HOME
G28
G90
STATUS_HEATING
M117 STATUS_HEATING_BED_u._NOZZEL
M117 {params.FILAMENT}
{% set BED = params.BED_TEMP|int %}
{% set EXTRUDER = params.EXTRUDER_TEMP|int %}
M190 S{BED}
M109 S{155}
M117 STATUS_QGL
QUAD_GANTRY_LEVEL
M117 STATUS_BED_MASH_CLEAR
BED_MESH_CLEAR
STATUS_MESHING
M117 STATUS_BED_MASH_CALIBRATE
_BED_MESH_CALIBRATE
M117 STATUS_SMART_PARK
SMART_PARK
STATUS_HEATING
M117 STATUS_HEATING_EXTRUDER
M109 S{EXTRUDER}
M117 STATUS_NOZZLE_CLEAN
NOZZLE_CLEAN
M117 STATUS_VORON_PURGE_LOGO
VORON_PURGE
M117 STATUS_READY
M117 STATUS_PRINT```
#

_BED_MESH_CALIBRATE must be changed in BED_MESH_CALIBRATE

vagrant pecan
#

I'll try it

#

can I no longer use my KNOMI????

#

echo: "extruder" not hot enough
18:49
Error evaluating 'gcode_macro BED_MESH_CALIBRATE:gcode': TypeError: bad operand type for abs(): 'Undefined'
18:49
Error evaluating 'gcode_macro BED_MESH_CALIBRATE:gcode': TypeError: bad operand type for abs(): 'Undefined'

ebon tinsel
#

I never see a Konami config

#

You could put the Konami status around BED_MESH_CALIBRATE in your print_start

#

Send your _KAMP_Settings

vagrant pecan
#

have a TAP

ebon tinsel
#
variable_probe_dock_enable: False           # Set to True to enable the usage of a dockable probe.      # ---------------------------------------------
variable_attach_macro: 'Attach_Probe'       # The macro that is used to attach the probe.               # Klicky Probe:   'Attach_Probe' | 'Dock_Probe'
variable_detach_macro: 'Dock_Probe'         # The macro that is used to store the probe.                # Euclid Probe:   'Deploy_Probe' | 'Stow_Probe'
                                                                                                        # Legacy Gcode:   'M401'         | 'M402'``` change that and comment it in
#

variable_probe_dock_enable: False this insures that you do not use it and is the source of your error

vagrant pecan
#

thank you thank you thank you very much

ebon tinsel
#

You welcome, happy printing

vagrant pecan
#

Can you speak German too

ebon tinsel
#

Yes but not on the Mainsail server. The language here is English

#

Increase your probe points. KAMP calculates the distance between your points and use that to define the new amount of points