Ignoring the number of wipes.

zBeeble

I recently extended my reprap build (custom) to include a wipe area. This is supported by Cura. Cool.

But as I was kibitzing about the interference of Z higher than 50mm and the wipe, I looked at the Cura generated code. An example is thusly:

;LAYER:1
;WIPE_SCRIPT_BEGIN
G0 F7200 X250 Y20.41
G0 X270 Y20.41
G0 X250 Y20.41
G0 X270 Y20.41
G0 X250 Y20.41
G0 X270 Y20.41
G0 X67.383 Y20.41
G1 F1500 E2.54158
;WIPE_SCRIPT_END

So... if I read this right, the intent is that it should move over to 250, wiggle back-and-forth between 250 and 270 a coupe times and then go back to the print. Cool. That's what I'd like.

But that's not what it does. It goes over and back. No wiggle. Is the firmware trying to be "smart" and skipping the wiggle because there's no extrusion?

(on edit... oops: here's the versions):

gloomyandy

@zBeeble I'd suggest updating to the 3.5.1 release version and trying things again.

Phaedrux

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.1

zBeeble

@gloomyandy So much stress. I hate updating. Do you actually think this behaviour has changed, or is this just a stock answer. I suppose it's only a point revision ... but still... stress.

Phaedrux

Release candidates and betas are not supported once the full release is available. We need to verify if the issue is still present in current firmware to be able to address it.

moth4017

@zBeeble here is my wipe routine if this helps you, i have 2 wipe parts one is silicone and a wire brush that's why there are 2 different locations

;Wipe
echo "Wipe"
G90
;Wipe
var speed1 = 12000
var speed2  = 9000
var xMinBrush = 110
var xMaxBrush = 155
var xMinWipe = 168
var xMaxWipe = 194


M564 S0      ; let travel outside print zone
G1 Z21 F6500 ; cleaning height for silicon wiper 
G1 X{var.xMinWipe}
G1 Y-43.5 
while true
    if iterations = 6
        G1 F{var.speed1} Y0
        break
    G1 F{var.speed1} X{var.xMinWipe}
    G1 F{var.speed1} X{var.xMaxWipe}
             ; end loop
G1 F{var.speed1} X{var.xMaxBrush}
G1 Z19       ; cleaning height for brush 
G1 Y-43.5 
while true
    if iterations = 10
        break
    G1 F{var.speed1} X{var.xMinBrush}
    G1 F{var.speed1} X{var.xMaxBrush}
; end loop
G1 F{var.speed1} Y152.5 
G1 F{var.speed1} X152.5 Z19
M564 S1      ; re activate travel inside print zone  only
echo "Wiping finished"

zBeeble

@Phaedrux Ah ... fair enough. I think I was on the RC for some good reason --- I normally wouldn't. I think it had to do with my filament monitor. Anyways... will take me a bit. But I will retest it.

zBeeble

@moth4017 Both types of brushes fit, but it's a manual change for me. I have almost as much fun making the printer as using it. Here's a pic of the setup:

https://nextcloud.towernet.ca/s/67BRHqrXppDaKmQ

zBeeble

If anyone's curious, the brush-head comes from a brush amazon sells in bulk ... in steel, brass (?) and nylon. I published the modified parts on both thingieverse and printables.

zBeeble

So... I upgraded to 3.5.1 and I retested. I have video.

https://nextcloud.towernet.ca/s/f3zsFwwsGRdw6kp

I shot the web console tracing the GCode there, too. Pertinently, the layer change and wipe is as above.

(note there is no wipe back-and-forth) ...

gloomyandy

@zBeeble I wasn't able to view your video (I even tried to download it, others may have more luck). Can you post your config.g file and a sample gcode file so we can see the commands that are executed before the wipe operation.

zBeeble

@gloomyandy So... I think it's a windows fail. New codec. Linux understands it. Anyways... here's a utube. https://youtu.be/Az021pmf5Y4

G code is exactly the code in the first post for the wipe. You will see just that code going by.

I will upload config.g in a sec.

zBeeble

config.g

gloomyandy

@zBeeble I'm using a chromebook not Windows, so I guess that doesn't support whatever codec has been used.

Anyway looking at your config.g you have:

M208 X250 Y210 Z110 S0

But your movements to perform the "wiggle" are all out to X=270 which will not be allowed. I'm a little surprised you did not get any warning messages in the console, but perhaps you only get them for print moves.

zBeeble

@gloomyandy hrm. Fair enough. I'll make that modification and try after it finishes leveling.

zBeeble

@gloomyandy had the right pick. Changing Cura's notion of the wipe position to x=230 makes it go back and forth between 230 and 250 --- which is what is desired. Documentation is a bit of a problem for Cura ... welll ... that and complexity.

Thanks ...