Posts made by janko

I faced some issues today with my extruder: it started skipping steps due to a clogged nozzle. Sadly enough, that started when I was already a few hours in the print. Pondering how handy it would be that when the extruder engine starts skipping steps, it would just pause the print and wait for user interaction, I wonderend if I couldn't use sensorless homing for it.

The stepperdrivers can detect when there is a stall (within a certain amount ofcourse ). I see some practical issues because for sensorless homing I drop the current the motors get, something I obviously don't want to do while printing for the extrudermotor. I havent found really a fix for that part, but I thought, let's just put the idea here and maybe a bright soul has a solution.

@dc42 i think i finally found it When the ABL finishes, it puts the Z on +10 and starts moving to x20y20, when it reaches that point, the bed moves to z 0.2, but, the acceleration/speed of the Z-axis seemed to be too high, which made the motors skip steps. For the normal z-hop the acceleration is however no problem.

Seems adjusting the accelerationsettings solves it.

@dc42 as soon as the current print is finished, i'll give that a spin and keep you posted here about the results

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.02RC2(RTOS) (2018-09-07b2)
WiFi Server Version: 1.21RC4(08b3)
Web Interface Version: 1.22.3

and the fileupload is refusing a bit:

wetransferlink for the configfiles

So I have this really weird issue which i just can't get figured out.

The problem: when I start a print, all goes well. The printer starts with fixing the tilt on one plane, does a small ABL, primes and prints along, so far so good. However: after this print has finished and I want to start a second print, this print starts with a z height of +2 (eg: in stead of 0.2, because the first layer is 0.2mm, the printer starts on 2.2, which results in some nice airprinting no need saying ).

The samen happens when i cancel a print and start a new one. Restarting the duet completely solves it for the next print.

I have digged through the configfiles but can't figure out where that +2 comes from.

Configfiles for my Duet Wifi:
[0_1544888213532_download.zip](Uploading 0%)

My startup g-code is:

; Startup Gcode
M83
M140 S[first_layer_bed_temperature] ; set bed temperature
M190 S[first_layer_bed_temperature] ; wait for temperature
M104 S[first_layer_temperature]
M561 ; Clear any bed transform
G32 ; Do a single probe
G29 ; Load heightmap (you can use G29 S1 instead)
G1 Z20.0 F100 ; Move Z to 20
G1 X10 Y10 F900 ; Move Head to front left
M109 S[first_layer_temperature]
G0 X5 Y10 F9000 ; Go to front
G0 Z0.2 ; Drop to bed
G92 E0 ; zero the extruded length
G1 X40 E25 F100 ; Extrude 25mm of filament in a 4cm line
G92 E0 ; zero the extruded length
G1 E-1 F500 ; Retract a little
G1 X80 F4000 ; Quickly wipe away from the filament line

My End-gcode is:
G10 P0 R-273.15 S-273.15 ; Turn off Tool0
M140 S0 ; Turn off Bed
M109 S0
M106 S0 ; Object fan off
G1 X0 Y0 ; Move Z to Z210
G92 E0 ; Zero Extruder
G1 E-2 F300 ; Retract 2mm
G92 E0 ; Zero Extruder
M84 ; All motors Off

@scachi let me test that next

I now tried without the resistor between ground / signal wire (since duet 'bragged' about how idiotproof the board is, i felt lucky

results now:
19:18:03G30 S-1
Stopped at height 0.000 mm
19:17:56G0 Z5
19:17:40G30 S-1
Stopped at height 0.065 mm
19:17:32G0 Z5
19:17:24G30 S-1
Stopped at height -0.039 mm
19:17:19G0 Z5
19:17:11G30 S-1
Stopped at height 0.005 mm
19:17:04G0 Z5
19:17:00G30 S-1
Stopped at height -0.013 mm

This seems to be somewhat normal

18:53:47G30 S-1
Stopped at height -0.762 mm
18:53:43G0 Z5
18:53:35G30 S-1
Stopped at height -0.647 mm
18:53:30G0 Z5
18:53:26G30 S-1
Stopped at height -0.641 mm
18:53:23G0 Z5
18:53:17G30 S-1
Stopped at height -0.757 mm

Results after putting the trigger value up to 70 in stead of the 10 I started with. I followed the guide to setup the 3dtouch (bltouch guide actually) which stated that the trigger value had to be low, since the pulse of the sensor is very short. Seems it however has a negative effect on the output when you go low/very low.

@drammy some time ago i had some issues here, which i fixed by using x16 with interpolation. The movement is pretty much as smooth as i could wish for.

As of feeling the motors: tested it here and i can feel something but barely, not a level that i can imagine it would cause any issue.

For the oozing: i first configured my printer here to print straight lines, then started tuning the instantDV and acceleration. Last steps: in your slicer up travelspeed (helps bigtime against stringing) and start with retraction settings (there are some testfiles for that on thingiverse)

@drammy in that way The pulsing is i presume some vibration-ish you feel right? Or like a small electric flow (do you start dancing funny every 0.3 seconds when you touch it )

To make sure it's not a firmwarethingie: upgraded just to 2.0(RTOS)RC6 (2018-05-29b4)

results now:
17:50:13G30 S-1
Stopped at height 4.403 mm
17:50:09G0 Z10
17:50:01G30 S-1
Stopped at height 4.257 mm
17:49:57G0 Z10
17:49:47G30 S-1
Stopped at height 4.202 mm
17:49:43G0 Z10
17:49:29G30 S-1
Stopped at height 3.736 mm
17:49:24G0 Z10
17:48:52G30 S-1
Stopped at height 3.542 mm
17:48:47G0 Z10
17:48:42G30 S-1
Stopped at height 2.804 mm
17:48:37G0 Z10
17:48:23G30 S-1
Stopped at height -0.107 mm
17:48:11G28 Z

you mean every 0.3 seconds you zaxis moves up a bit and back down again?

I have a weird problem here with my touch sensor: each probe keeps going up higher and higher in the offset. I am breaking my head over it, but can't figure out what is going on.

First of: what i mean:
Stopped at height 3.408 mm
Stopped at height 3.948 mm
Stopped at height 4.191 mm
Stopped at height 4.503 mm
Stopped at height 4.589 mm
Stopped at height 4.738 mm

Probing is done at x110 y 110 Z10 with G30 S-1 command

Parts out of the config.g:

; Z-Probe
; BLTouch - Heaters
M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board.
M558 P9 X0 Y0 Z1 H5 F500 T2000 A1 R0.5
G31 X24 Y-2 Z0 P10

homez.g (don't think that G30 uses this? but still, bytes are free
G91
G1 Z10 S2 F200
G30 ; Do a single probe to home our Z axis
G90 ; Make sure we are in absolute mode
G1 Z10 F6000 ; Rapidly move the Z axis to Z=10.

bed.g:
M561 ; clear any bed transform
; Probe the bed at 4 points
G30 P0 X15 Y15 H0 Z-99999
G30 P1 X15 Y195 H0 Z-99999
G30 P2 X195 Y195 H0 Z-99999
G30 P3 X195 Y15 H0 Z-99999 S

The touchsensor is a 3dtouch (i know, not as accurate as a bltouch, but this is a bit weird what is going on ), wired on the probe-in port for the signal, with a resistor between ground and signal wire.

If anyone has any idea: i would be thankful, I'm kinda stuck at the moment.

@dc42 your solution is confirmed, tried it on the same file again i sended you, it now continues

@t3p3tony it does call for some testing, doesn't it? After the mount for my psu and my xcarrage has finished, i'll see what happens if i thinker with the layerspeed at 256 microstepping.

@t3p3tony it not even might be, they are. However, the feedback i got from printing was a bit mixed. I had one which only did the first layer outline before just stopping. I'm now trying dc42 his solution, see what it brings.

@dc42 you really rock! Thanks for your help, it was driving me mad here haha It still is very weird that it does print a few layers very nicely (that's how i think i managed to get those numbers so high, it printed fine). Will try your solution now asap.

just did another test: still the same. In the printing module, the layertime keeps counting though. Maybe another clue of some sort.

Also after a firmware reflash: still the same thing

the config-files
0_1523349898943_config-override.g 0_1523350166726_config.g

and the g-code files via wetransfer (both give the issue here, though every gcode file does currently :P). The printer stalls at around ~1.35mm height (printing at 0.2 layerheight) :
https://we.tl/2hXLfVSJQb

It stops at the same layer (for the same gcode if i slice the stl different (other percentage support), it stops at another layer). For each different stl i have, the layer and xy at which it stops is different. When I run the same stl several times, the layer and xy at which it stops is the same.

At the topright it still says 'Printing', however, in the printer module there is no reaction on whatever. Pause and babystepping do not trigger any reaction.

It is a duet wifi