Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - furious1y

Pages: [1]
1
Pretend Prusa Chitchat / Re: Waggster X-1 BLTouch v1.5
« on: July 23, 2020, 09:53:35 AM »
First off, thanks to Steve for making this available.
I tried to print the slider piece. But it looks really bad on the slide portion, like a spiral. I did a temp tower, calibrated extruded and the flow.
I am using eSun PLA+, 210/60.
Any help is greatly appreciated.
That's some weird extrusion.

Things to check:
Fan speed - drop to 25% to see if it changes the extrusion
Slicer - I've had many issues with Cura, try prusa or simplify3d
Ensure in the slicer:
    Nozzle settings are correct size
    Multiplier is 0.96 or higher
    speed is around 40-50mm/s
Calibrate - see if the correct amount is extruded:
https://3dprintbeginner.com/artillery-sidewinder-x1-calibration-guide/

Try different fresh filament - just to rule out the geometry. Also, bake the filament at 50C for an hour in an oven to get any moisture out.
Also, some filament may say 210-240, but that may be low. I regularly run filament at the top end of the manufacturers spec, so try going up to 225-230

2
Pretend Prusa Chitchat / Re: Weird z offset problem
« on: July 22, 2020, 02:37:06 AM »
Well, I'm having some success after I found this particular gem:
https://github.com/MarlinFirmware/Marlin/issues/17166

I'd kind of mitigated the issue by getting the offset dialled in and working and then removing the G29, even though it defeated the point of having ABL.

Then I finally managed to put the right words into google to yield the above.

So, if anyone is getting weird fluctuating z offsets, try the following:
Code: [Select]
M420 S1 Z0
G28 ; home all axes
G29
M420 S1 Z5 ; Enable ABL using saved Mesh and Fade Height

In fact, you don't need the last line at all.

3
Pretend Prusa Chitchat / Weird z offset problem
« on: July 14, 2020, 04:43:05 AM »
Hi all,
just wondered if I can pick someones brain here.

I have 1.5 installed and working. I can check the mesh data, doesn't seem to vary much, only the usual stuff from having a removable bed with PEI.
The sprung steel isn't perfectly flat, but not much is :)

So, I'll print something. Have to restart to adjust the z offset a few times. Like this morning - kicked off a new print, no layer adhesion, had to lower the z-offset by 0.2mm, then prints fine.

Problem is... I have to do this every time. After each print, I make sure the bed plate is clean, ensure that its seated correctly, yet for some reason the mesh levelling doesn't seem to counter the bed being reseated and I have to do the z-offset again.

Am I missing something here? I'm taking this isn't normal, and surely the whole point of the mesh is to counter the geography of the bed, and if its 0.2mm higher or 0.2mm lower in any or all spots (z offset is usually -2mm +/- 0.3mm each new print), it should counter that?

Is there something I should be putting in the gcode to ensure it's using the mesh properly or to actually apply the offset?

Here's my start gcode for my slicer:
Code: [Select]
M280 P0 S60 ; Test Mode
G4 P500
M280 P0 S90 ; Stow Probe
G4 P200
;*** Start Preheating ***
M140 S{material_bed_temperature_layer_0} ; start preheating the bed
M104 S{material_print_temperature_layer_0} T0 ; start preheating hotend
M190 S{material_bed_temperature_layer_0} ; heat to Cura Bed setting
M109 S{material_print_temperature_layer_0} T0 ; heat to Cura Hotend
;*** End Preheating ***
G28 ; home
G29 A; ABL
M500
M117 Purge extruder
G92 E0 ; reset extruder
G1 Z1.0 F3000 ; move z up little to prevent scratching of surface
G1 X2 Y20 Z0.3 F5000.0 ; move to start-line position
G1 X2 Y200.0 Z0.3 F1500.0 E15 ; draw 1st line
G1 X2 Y200.0 Z0.4 F5000.0 ; move to side a little
G1 X2 Y20 Z0.4 F1500.0 E30 ; draw 2nd line
G92 E0 ; reset extruder
G1 Z1.0 F3000 ; move z up little to prevent scratching of surface

4
Pretend Prusa Chitchat / Re: Waggster X-1 BLTouch v1.5
« on: May 21, 2020, 05:17:12 AM »
Just to reply back with my experiences with 1.5

So, it was down to the bed tuning - looks like 1.4 was not saving it, so when you had too much temp differential between current and target, it wouldn't get there in time and the firmware would stop the printer, with the thermal runaway error.

1.5 allowed me to tune and it saves, so it heats the bed in seconds rather than the minute or so it used to. Also, no more thermal runaways.

One thing I will comment on - after trying ABS with a bed temp of 105, I'm thinking that the thermal expansion is too much on my magnetic bed and PEI sheet combo.
After getting a major clog and constant under extrusion, I decided to check the ABL mesh generated. At 105C, I get a massive high spot in the centre of the bed. Like 0.6 to 0.7 higher than the edge where it does a wipe.
I'm thinking there's some kind of limit that the ABL is hitting, as I have to baby step at least 0.5mm higher when printing ABS otherwise I just get an extruder stall where it grinds the filament due to it literally touching the bed.

What do you think? Is such a thing in the firmware, so that it can only compensate a certain difference? Comparing the mesh stored to the mesh generated manually, I'm seeing that there is a slight difference in the high spot of at least 0.2mm.

5
Pretend Prusa Chitchat / Re: Waggster X-1 BLTouch v1.5
« on: April 23, 2020, 03:18:54 AM »
Wow, just got around to this from v1.4, you weren't kidding about the speed of ABL. Did it have a load of waits in there for testing or something?
With 1.4 I'd also get thermal runaway errors for the bed heating occasionally, especially when warming from cold - like the temp wasn't reaching the range quick enough, so will report back if still get it now that I've tuned the bed after this 1.5 install :)

Thanks, and keep up the good work.

6
Pretend Prusa Chitchat / Re: Wagster mod with octoprint
« on: February 18, 2020, 07:32:01 AM »
Install the terminal commands extended plugin - you can define specific buttons to go on the terminal tab, and label them.
So rather than having to remember each code, you can click the button - define one for up and one for down.

EG
M290 Z0.25 for up
M290 Z-0.25 for down

7
Pretend Prusa Chitchat / Re: Waggster X-1 BLTouch v1.3
« on: February 16, 2020, 11:02:16 AM »
Ok, so replaced with a different probe - same issues.
Reflashed with v1.4....
Success!

First print already done, home and ABL worked flawlessly.

Thank you very much, looks like the v4 has some weird problems with the LED stuff :)

8
Pretend Prusa Chitchat / Re: Waggster X-1 BLTouch v1.3
« on: February 15, 2020, 02:58:26 PM »
Just an update - saw someone posting about weirdness with the cooling fan, so gave that a try....
Get this - if I force the fan to 100%.... it completes the homes 100% of the time.
But then, it will never complete an autolevel - always fails to either deploy on the 5th or 6th probe, or it will deploy but not register and so error.
So, I then put gcode in to spin the fan at 100% for home, then turn it off for the ABL part.

Tried to print something - doesn't work. I'm suspecting that the probe is flaky and is barely triggering, the fan is enough to get it to work but the extruder heating is too much of a drop and stops working again.

Seems a lot of people do not like the 3.1 version, problem is you can't find any other previous versions out there :(

I've returned this one and got another one coming tomorrow, will see if 1.4 makes a difference.
BTW, I compiled your 1.3 firmware, yet I get a few KB less - do you include all the files needed in the zip file?

9
Pretend Prusa Chitchat / Re: Waggster X-1 BLTouch v1.3
« on: February 14, 2020, 04:27:42 PM »
Hi - thanks for posting such a comprehensive guide.
I wonder if someone could help me though - I've got v4 and just installed a BLtouch v3.1.

Sending home has a 50% chance of deploying the probe. Seems to work if I use the reset button on the touchscreen a few times. It'll then work for a while then stop working again. I've managed to get it to do a complete bed probe, then when it came to print, the home command didn't deploy the probe and it wanted to bury the head into the bed.

Sending the gcode for deploying and retracting works 100% of the time, so I'm thinking this is some quirk I've read from some searching that the version of marlin needs to be newer or have the V3 of bltouch enabled.

Any advice appreciated, would setting it to 5v mode using gcode make it behave better?

Pages: [1]