#Problem when putting button to enter filament to head.

1 messages · Page 1 of 1 (latest)

covert geyser
#

Hello, I have a problem with the filament input by pressing the button to enter filament to head from the interface in klipper and it gives me error ' I did not understand the change -- CHANGE_TOOL LANE=LANE4', but if I do it by manual commands, I also did the AFC Calibration and it works without problem, the filament ejection button also works. <@&1304550334839918672>

karmic fractalBOT
covert geyser
rotund fossil
covert geyser
#

I got this but I do not throw any link or it is this /tmp/tmp. Uf1BUJRpYj

orchid socket
#

Hmm for some reason it failed to connect

#

Can you upload klippy log and AFC log?

covert geyser
#

si puedo dercargar el de klippy pero el de AFC no tengo la opcion

#

I can download the Klippy one, but I don't have the option for the AFC one.

orchid socket
#

english if you want help
for AFC log you'll have to go to the actual log location

#

change from config view to log view

covert geyser
orchid socket
#
initial_duration = 0
gcode = 
    PREP```
This in the AFC.cfg file should be a duration of 2 instead of 0
covert geyser
#

Thank you so much, it finally worked!

However, I noticed that when I change the filament, the motor makes a loud whirring noise, as if it's jamming.
Lastly, one question: what distance should the filament cutting blade be set to?

orchid socket
#

I would need so much more information to answer that

covert geyser
orchid socket
#

Are you running the latest CW2 filamatrix files?

covert geyser
#

Yes, I'm using it, and I'm also using the dual-sensor head one.

orchid socket
#

Then you shouldn’t need to trim the blade if that is what you were asking

covert geyser
#

I'm referring to the distance or length the blade should be.

orchid socket
#

Full length

covert geyser
#

OK, then I think if they sent it to me wrong.

crystal solstice
#

That looks correct for the last version of the arm. If you prefer, you can print the older files

covert geyser
#

Hello, you know why I get this mistake.
MCU 'mcu' shutdown: Missed scheduling of next digital out event
This is generally indicative of an intermittent
communication failure between micro-controller and host.
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown

orchid socket
#

What was happening when it given?
It’s really hard to answer much of anything with no real info

covert geyser
#

Yes, an apology.
I started printing the HLFT cap. But at the beginning of the impression, I get that mistake and I do not let myself restart my firmware

crystal solstice
#

You won’t be able to recover except with the firmware restart. If you’ve got USB devices you could try replacing their cables, maybe disable your webcam, and check the docs for how to enable the trsync_update. If you continue seeing this problem, please open a help thread

covert geyser
#

Is it normal to do a chip type between sw2 and the hotend?

crystal solstice
covert geyser
#

Sorry, no longer take a picture of him so you can see what it is. But now I have another situation, my extruder has some rotation_distance, but now it no longer extrudes correctly, I already did the calculations as indicated by voron but they always give me results of 62mm,58mm, 61mm, in tests of marking 120mm and seeing how much is left, to make the formulation. I also see that my filament is very tense, I do not know if my head motor is not working, because when I extrude I only see that the htlf motor is activated.

covert geyser
#

Hello team you can support me, I no longer know what to do and I did my rotation_distance test and still it continues to come out so my first layer manages to print but now it does not come out well lanprinera layer I can not continue doing tests
It already caliber my rotation_distance and comes out perfectly but when it prints it comes out as if it were not yet.

karmic fractalBOT
crystal solstice
#

Go ahead and run that ^ and then we can have a little bit better idea how you are configured

covert geyser
#

An apology for the delay, I am not at 100 on my printer. I already tried to do the debugging but I get the mistake before I tried and the same thing happened.
Now I was able to print, however, notice that sometimes my filament extrusion engine stops at the HLFT.
I share with you pictures of the impression that went wrong.

covert geyser
#

I share with you one more test of first layers. I already have the rotation_distance adjustment, but it still remains the same, I do not know, if you have to adjust something of the HLFT

orchid socket
#

Is your TN buffer switches working correctly?

covert geyser
#

replaced the TN with the head sensors

orchid socket
#

You can’t do that, you still need the buffer to sync the extruders

covert geyser
#

Oooh, I did not know that if it was necessary, then I will print it I will have to remove the printer folders.

orchid socket
#

So more than likely what you’re seeing is the buffer decoding it is in trailing mode and your just occasionally getting the toolhead overriding the HTLF stepper since it’s small

covert geyser
#

ok, ask how I remove the function of the HTLF, so that I can print normally and print the TN

rotund fossil
#

Enable the virtual tool sensor and then feed filament into your toolhead bypassing your HTLF

covert geyser
#

Excuse me where I do that, I am new to this HLFT and I am a little lost.

rotund fossil
#

In mainsail/fluidd interface there is a filament sensor called virtual bypass if you enable that then you can bypass your HTLF and feed filament straight to your toolhead

orchid socket
#

Typically in a miscellaneous or sensors section

covert geyser
#

OK, I understand, I better put the AFC # lines in the printer file.

orchid socket
#

what?

#

can we get a klippt.log?

covert geyser