Filament change cura не работает

4.8 Post Processing Filament change does not properly return to proper Z #9058

Comments

Grey-Lancaster commented Jan 2, 2021

Application version
4.8

Platform
Windows 10 saving to Micro Sd Card

Printer
Creallity Ender 3

Reproduction steps

1. Use post processing change filament at layer

Screenshot(s)
(Image showing the problem, perhaps before/after images.)

Actual results
I have problems with 4.8 change at layer vs 4.5 change at layer. Both show M600 in the code but they behave differently. 4.5 returns to 0,0 far left bed retracted. 4.8 returns to the middle of the bed 110? with the bed all the way back. That is not actually an issue I just ponder what is happening. If I hit change filament on the LCD it goes to 0,0.

My issue is maybe it is not locking the stepper motor? Seems like 8 times out of 10 I manage to lower the «z» and when it returns to print the nozzle is burning a hole in my print.

Expected results
Z should go back to the proper value for the next layer

Project file
45.zip

Log file
(See https://github.com/Ultimaker/Cura#logging-issues to find the log file to upload, or copy a relevant snippet from it.)

Additional information
(Extra information relevant to the issue.)

The text was updated successfully, but these errors were encountered:

Ghostkeeper commented Jan 11, 2021

Note that the 4.8 project file doesn’t produce any filament change command since the post-processing script sets the layer trigger to layer 100, but the print doesn’t have 100 layers.

Ghostkeeper commented Jan 11, 2021

I’m not seeing a whole lot of difference in the way that Cura behaves here. The M600 command is exactly the same. And the surrounding g-code has different coordinates (due to the new arranger and the new simplification algorithm most likely) but the structure is the same.

This is a snippet of the 4.5 output (my comments):

And this is a snippet from 4.8:

In both cases, the next Z command is at the end of the next layer, some 6000 commands later ( Z2.2 ).

Ghostkeeper commented Jan 11, 2021 •

The two look identical to me, and also correct (they don’t alter the Z coordinate). The printer should behave the same. What would we need to improve in the g-code output to make it function correctly?

Grey-Lancaster commented Jan 15, 2021

I was hoping it was a known issue and someone would jump in with a fix. I will have to dbl check the code I posted.

Outside the box.

• So it used to work fine. Could it be possible my stepper motors are «weak» and do not lock during a change?
• On my Ender 3 for the majority of my prints it would not affect the print if the head returned to 0,0,0. Could there be a post processing script (return home) that would go to 0,0,0 and then raise up and go to where it should be. In case x,y,z got moved during a filament change?

fvrmr commented Jan 22, 2021

• So it used to work fine. Could it be possible my stepper motors are «weak» and do not lock during a change?

It is possible that your stepper motor receive not enough power. If you want to know how to measure it, please let me know.

• On my Ender 3 for the majority of my prints it would not affect the print if the head returned to 0,0,0. Could there be a post processing script (return home) that would go to 0,0,0 and then raise up and go to where it should be. In case x,y,z got moved during a filament change?

The x and y are already homing:

M600 X0.00 Y0.00 ; Generated by FilamentChange plugin

The Z is not homing, because if you will home Z the changes are that the object will be destroyed by the x and y. 😉
But I will discuss this with the team. Keep you posted!

Grey-Lancaster commented Jan 22, 2021

See that is what I do not understand. The code says M600 x0.0 and y0.0 but it goes to X 0.00 and Y 110.0
If I hit filament change on the LCD it goes to 0,0

But I just noticed that filament change on the LCD does not lock any of the stepper motors. A Pause print does.

I was wrong 4.5 does also go to x0 and Y 110. I am old, but I swear it used to go to ),) and I never had an issue with changes like this.

Perhaps I need to upgrade the motherboard? This is an Ender 3 by SainSmart

On the reset Z concept. My print very seldom fill the bed and most of the color changes are done at less than layer 15. Doing luggage tags, signs, dog tags, that kind of thing.

Thanks again for looking at this.
Grey

Ghostkeeper commented Jan 25, 2021 •

But I just noticed that filament change on the LCD does not lock any of the stepper motors. A Pause print does.

This could be your answer then. Some printers kill power to the motors while the print is paused, to reduce energy usage and wear on the steppers. While power is killed, it’s easy to move the gantry by hand and this would then destroy any knowledge of where the print head is until it’s homed again. Changing filament is one way to «pause» it so perhaps the issue is indeed that it’s losing track of its Z coordinate. The only real way to fix that is to home Z again after the filament change then.

I’d consider this to be a bug in your firmware, rather than Cura. Normally the pause operation doesn’t need homing again, and homing can also cause a layer shift because the endstops don’t always respond in precisely the same location. I don’t think upgrading the motherboard would have any effect. Changing the firmware would. If it’s keeping the power on for normal pause, then it should certainly keep the power on for a filament change pause.

As a workaround, you can add a post-processing script that inserts a home command after every M600. This is done with a Search-and-Replace post-processing script with regex enabled. You’d need to search for the following string:

And replace that by:

This would effectively place a G28 command after every M600 command, instructing the printer to home. You can also use G28 Z to just home the Z axis or something.

Since this is an issue with a specific firmware, not a bug in Cura, we’re not going to fix it.

Источник

Пауза для смены филамента на Tronxy XY2 pro

Подпишитесь на автора

Подпишитесь на автора, если вам нравятся его публикации. Тогда вы будете получать уведомления о его новых статьях.

Отписаться от уведомлений вы всегда сможете в профиле автора.

Статья относится к принтерам:

Ни одно стандартное расширение Cura не ставит данный принтер на паузу и смену филамента. Если просто задавать вручную M25 — принтер уходит на вечную паузу. Наконец то я нашел решение и хочу им поделиться.

Надо скачать скрипт и установить его в C:\Users\ИмяПользователя\AppData\Roaming\cura\4.8\scripts. Что бы долго не рыскать по диску, можно из Cura выбрать каталог и затем зайти в scripts

Далее перегружаем Cura и теперь можно ставить скрипт с паузой для Tronxy

Дойдя до нужного слоя принтер станет на паузу и на экране это покажет

Затем снимаем принтер с паузы. Принтер выдавит указанное в скрипте количество пластика и продолжит печать.

Очень рекомендую, рядом с основной моделью печатать какую нибудь башеньку, проверив в слайсере, что печать начинается с нее, а не с основной детали. Тогда, после смены филамента, сначала начнет печатать на ней, убирая последствия смены, и уже потом на основной детали.

Ну и собственно печать после смены цвета:

Подпишитесь на автора

Подпишитесь на автора, если вам нравятся его публикации. Тогда вы будете получать уведомления о его новых статьях.

Отписаться от уведомлений вы всегда сможете в профиле автора.

Источник

[3.3.1] Post processing filament change, changes filament at the wrong layer #3775

Comments

CPS-3 commented May 5, 2018 •

Application Version
3.3.1

Platform
W10

Printer
Creality CR10S-S4

Steps to Reproduce
filament change with a print, in my case, @ layer18 — text on a print. print is black and text should be white

Actual Results
filament change happens @ layer 16

Expected results
filament change @ layer 18

Additional Information

The text was updated successfully, but these errors were encountered:

dmsulliva commented May 6, 2018

Same thing happens for me with my Tarantula, it was supposed to stop at layer 12, but stopped at 9 instead

diegopradogesto commented May 7, 2018

Yes, confirmed. I set the filament to change in layer 50 and instead the script set the change in layer 47:

G0 X46.039 Y47.619
G0 X44.487 Y44.487
;TIME_ELAPSED:902.097665
;LAYER:47
G0 X44.487 Y44.487 Z4.8
M600 E30.00 L300.00 ; Generated by FilamentChange plugin
;TYPE:FILL
G1 F3600 X46.024 Y46.024 E149.4953
G1 X46.103 Y46.103
G0 F7200 X46.176 Y47.606

diegopradogesto commented May 7, 2018

For developers’ reference: CURA-5335

CPS-3 commented May 7, 2018

@diegopradogesto thank you for confirming

djunisol commented May 8, 2018

yup same as CPS-3

southsidebrewer commented May 12, 2018

I have this exact same issue. I have to manually set any filament changes now. I am pretty sure this is a new issue with the latest release, but I do not know for sure.

AbeFM commented May 13, 2018

Every time I use this plug in I did test print columns to figure out what really happens.

Also the retract sometimes tries to feed several mm of material through nozzle at high speed.

Every single wrong in the macro meds to be tested each time to use safely. By adding or subtracting an offset, negating inputs, etc, it works.

CPS-3 commented May 28, 2018

Is anybody working on this yet?

diegopradogesto commented May 29, 2018

It is in the planning.

CPS-3 commented May 29, 2018

Ok thank you for the heads up

jackha commented Jun 14, 2018

Fixed in master. Unfortunately it just didn’t make it to 3.4, so it’s in the release after.

diegopradogesto commented Jun 14, 2018

I thought that it is not dangerous and I just add it to the next 3.4 RC.

uwezi commented Mar 5, 2019 •

is the problem back in 3.6.0? It appears that the pause is inserted randomly at +/- 1 layers from the desired position

;TYPE:CUSTOM
;added code by post processing
;script: PauseAtHeight.py
;current layer: 27
M83
G1 F1500 E-15
G1 F300 Z6.4
G1 F9000 X190 Y190
G1 F300 Z15
M104 S150; standby temperature
M0;Do the actual pause
M109 S210; resume temperature
G1 F1500 E15
G1 F199.998 E3
G1 F1500 E-15
G1 F300 Z6.4
G1 F9000 X96.636 Y86.693
G1 F1500 E15
G1 F9000
M82
G92 E1608.46202
;LAYER:26
;MESH:Uwe Zimmermann.stl
G0 X96.636 Y86.693 Z5.4
;TYPE:WALL-OUTER
G1 F2100 E1608.46202
`

Ghostkeeper commented Mar 6, 2019

Note that the ;LAYER comment in the g-code is zero-indexed while Cura’s interface shows the layer indices as one-indexed. So you’d expect Cura to indicate the layer number as one higher than what it says in the g-code.

abrenoch commented Feb 13, 2021 •

How is this still a problem?

With cura 4.8.0. I do have ironing enabled — so I’m thinking that is probably the issue!

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

А кому скриптик для удобной смены филамента?

Подпишитесь на автора

Подпишитесь на автора, если вам нравятся его публикации. Тогда вы будете получать уведомления о его новых статьях.

Отписаться от уведомлений вы всегда сможете в профиле автора.

Статья относится к принтерам:

Работает на Marlin, что стоит в основе Cheap3D V300. Вначале поднимает сопло на 20мм (чтобы можно было сопли подтирать)

Потом греет экструдер до 200С (обычно достаточно даже для тугоплавкого керамо)

Затем срыгивает пластик ретрактом на 80мм (это для директа, для боудена надо гораздо дольше, но там быстрее его вручную вытащить, отжав пружину)

Дальше сам встает на паузу и пишет сообщение ChangeWire! Странность работы команды паузы в марлине (M25) в том, что она выполняет перед тем как остановиться следующую команду О_о. Я сунул туда M117 (вывод сообщения на экран) и этого было достаточно.

После надо заправить новую нить в экструдер, и нажать Resume Print — пруток вдавит на 60мм ,промыв тем самым экструдер от нового пластика, а затем голова опустится на -20мм (туда где была).

Вот весь код. Можно сохранить его как changeWire.gcode и ‘печатать’ с флешки когда надо поменять нить. Или вставлять его в произвольные места своего кода ,когда надо на ходу поменять, например, цвет филамента.

; Change filament begin

G91 ;Use Relative coord

G1 Z20 F6000 ;Head up

G90 ;Use Absolute coord

M117 HeatEX! ;Write Message

M109 S200.000000 ;Heat Extruder

M82 ;use absolute distances for extrusion

G92 E0 ; Reset Extruder coord

G1 E-80 F200 ;Retract wire 80mm

M25 ;Pause Print

M117 ChangeWire! ;Write Message

G92 E0 ; Reset Extruder coord

G1 E60 F150 ; Push 60mm wire for clean extruder

G91 ; Use Relative coord

G1 Z-20 F6000 ; Head down

G90 ; Use Absolute coord

; Change filament end.

; Check Extruder coord.

Последняя строка предупреждает, что надо проверить координаты экструдера. Экструдер обычно работает в абсолютных координатах. Так что если вы врезаете смену филамента прямо в код, между слоями, например тут:

G1 X98.958 Y77.103 E4.5256

G1 X98.960 Y77.159 E4.5290

G1 X98.960 Y77.164 E4.5293

G1 X99.056 Y80.677 E4.7396

G1 X99.056 Y80.695 E4.7407

То видно, что последняя координата экструдера у нас E4.5256, а скрипт смены филамента координату обнуляет, а потом еще и накручивает на +60. В результате, при выполнении следующей команды экструдер попытается вернуть в E4.5293 т.е. выплюнет ваш филамент обратно. Чтобы это не произошло после скрипта смены надо вставить команду установки координаты экструдера в точке где прервались. В нашем примере это

И тогда все пойдет правильно ,без соплей и откатов.

Мы у себя пользуемся, удобно. Пользуйтесь и вы 🙂

Подпишитесь на автора

Подпишитесь на автора, если вам нравятся его публикации. Тогда вы будете получать уведомления о его новых статьях.

Отписаться от уведомлений вы всегда сможете в профиле автора.

Источник