Topics created by peterfrosta

Refurbished is definitively safer; if we can with some degree of confidence tell from pictures what the problem is https://forum.duet3d.com/topic/13875/community-repairs/ might be a cheaper option if you happen to be near one of the users on that list (but without know what's wrong, the part cost might be substantial)

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Fri Jan 17 2020 14:46:51 GMT+0100 (Mitteleuropäische Normalzeit)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Tronxy" ; set printer name

M667 S1 ; select CoreXY mode

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S1 ; enable Telnet

; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards Z1
M569 P3 S0 ; physical drive 3 goes backwards
M569 P4 S1 ; physical drive 3 goes forwards Z2

; DUAL Z
M584 X0 Y1 Z2:4 E3 ; set drive mapping ;M584 X0 Y1 Z2 E3
M671 X-90:490 Y200:200 S4 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis

M350 X64 Y64 Z64 E64 I1 ; configure microstepping with interpolation
;M92 X323.835 Y320 Z1606.522 E1582 ; set steps per mm
M92 X322.381 Y320.320 Z1606.522 E1582 ; set steps per mm

M201 X2500 Y2500 Z3000 E3000 ; set accelerations (mm/s^2)
M203 X24000 Y24000 Z3000 E6000 ; set maximum speeds (mm/min)
M566 X550 Y500 Z1000 E1000 ; Jerk (mm/min)
M572 D0 S0.5

M906 X1100 Y1100 Z1000 E1200 I35 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-7 Y-14 Z0 S1 ; set axis minima
M208 X400 Y360 Z390 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"!xstop" ; configure active-low endstop for low end on X via pin xstop
M574 Y1 S1 P"!ystop" ; configure active-low endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Filament sensor
M591 P1 C"e0_stop" S1 ;

; Z-Probe

M558 P8 C"zprobe.in+zprobe.mod" H2 F2000 T12000 S0.04 I1 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X-30 Y5 ; set Z probe trigger value, offset and trigger height Z WERT in homeZ.conf
;M556 S50 X0 Y0 Z0 ; set orthogonal axis compensation parameters
;M557 X52:350 Y30:350 S20 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T102400 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M307 H0 A106.4 C953.3 D2.2 V24.1
M140 S65 R40;

M140 H0 ; map heated bed to heater 0

M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M307 H1 A1170.9 C396.6 D5.8 V24.1

; Fans
M950 F0 C"fan0" Q400 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0:1 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R180 S200 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings
;Tappering
M376 H10 ; Bettkompensation läuft über 10mm Linear aus

M501;

@bearer said in FTP with Windows (network drive):

been a while since i did ftp, but i would think just listing files is using the control channel and then opening files would use the data channel and fail as the duet doesn't handle it? but I only skimmed the thread when this was an issue as it wasn't of great concern to me.

The logs show different. Directory uses both channels, and works in either active or pasv.

@peterfrosta My personal opinion is that you have to be very careful indeed before concluding that filament slippage may be an issue. The only reports I've seen as evidence of it are where people have extruded 100mm or so of filament, and measured the filament itself. The problem with that is this is not reprentative of what happens in "real life" because a 100mm filament move would need an XY move of many metres, which will never happen unless you have a really large printer. Also, it is highly likely that if slippage occurs, it would be due to back pressure which will build up during the course of a long move. Therefore that slippage might only happen after say 50 mm of filament has been extruded and there may be no slippage on the first 50 mm, or so which is the band within which most "normal" print moves occur. So using non linear extrusion may be compensating for something that does not happen under normal circumstances. Hence you need to be very careful before deciding that a print issue is due to filament slippage.
That's just my opinion - others will likely disagree.

i got run.

i was not firm with the ne config/gcode that expected from V3.
Unlucky, that the config generator does not import the most settings from my old config.

the problem with movement was the missing inverting from endstops (motor movement was also not inverted as needed).
I tried with line from old config but they doesn't work anymore.

Using new invert style for endstops and i was checking the effects.

M574 X1 S1 P"!xstop"

thanks to all