Posts made by nachogil

undefined

@droftarts Done!! Thaks a lot!!

undefined

Morning all,

I have two fans installed through a 3HC extension board, that (thank God) works perfectly

As I created two fans in two different connections the web interface shows two controls (obvious).

My doubt is if there is any way to name these two fans as one to have a single control in the web interface.

That is my current code:

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;; FANS ;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M950 F0 C"1.out6"			;create fan 0 on 1.out6
M106 P0 C"Layer Fan 0" S0 H-1		;named fan 0, NOT always O, disables thermostatic mode 
M950 F1 C"1.out7" 			;create fan 1 on 1.out7
M106 P1 C"Layer Fan 1" S0 H-1		;named fan 1, NOT always O, disables thermostatic mode

and I'm thinking in something like:

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;; FANS ;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M950 F0 C"1.out6+1.out7"			;create fan 0 on 1.out6 and 1.out7
M106 P0 C"Layer Fan 0" S0 H-1		;named fan 0, NOT always O, disables thermostatic mode

Its possible to do something like that?

undefined

I have changed from io5 to io4 and works fine

Thanks a lot!!

undefined

@droftarts I'm using 3.4.4 firmware.

I'm going to investigate and test based on your help.

Thanks a lot

undefined

Hi,

I`m trying to move some connections from a Duet 6HC to an Expansion 3HC.

Motors, temp, and limits sensors are working fine, but I`m not able to do work a BLTouch

I checked all the physical connections and wires and don't looks like a hardware problem.

This is my original code with the 6HC that works fine:

M950 S0 C"io7.out"             			; create servo pin 0 for BLTouch (use IO_4/5/7 for 6HC, IO_1/2/3 for Mini 5+)
M558 P9 C"io7.in" H5 F120 T6000 		; set Z probe type to bltouch and the dive height + speeds
G31 X52 Y-36 Z0.5         			; set Z probe trigger value, offset and trigger height 
M557 X80:650 Y80:2000 S250:300 			; define mesh grid; probe from X=10 to 620, Y=10 to 2010mm with a mesh spacing of 100mm

This is the code I`m using with the 3HC:

M950 S0 C"1.io5.out"             		; create servo pin 0 for BLTouch (use IO_4/5/7 for 6HC, IO_1/2/3 for Mini 5+)
M558 P9 C"1.io5.in" H5 F120 T6000 		; set Z probe type to bltouch and the dive height + speeds
G31 X52 Y-36 Z0.5         			; set Z probe trigger value, offset and trigger height ; 1.5 aprox real 0.0 			; define mesh grid; probe from X=10 to 620, Y=10 to 2010mm with a mesh spacing of 100mm

In both cases, I have these deploy and retract codes:

; deployprobe.g
; called to deploy a physical Z probe
M280 P0 S10 ; deploy BLTouch

; retractprobe.g
; called to retract a physical Z probe
M280 P0 S90 ; retract BLTouc

What I`m doing wrong?

undefined

Wow!! How quick!!

I'm gonna take a look over this.

Thanks a lot!!

undefined

Hi,

I'm trying to fine-tune and calibrate my new printer, but my Duet 3 6HC restarts at the very first layers.
I suspect that can be related to the gcodes, but I`m not sure, som

Any orientation or suggestion?

This is my current conf.g file

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;; GENERAL PREFERENCES ;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
G90                                     ; send absolute coordinates...
M83                                     ; ...but relative extruder moves
M550 P"Redemption Machine"              ; set printer name

; Network
M552 P192.168.1.100 S1                  ; enable network and set IP address
M553 P255.255.255.0                     ; set netmask 
M554 P192.168.1.1                       ; set gateway
M586 P0 S1                              ; enable HTTP
M586 P1 S0                              ; disable FTP
M586 P2 S0                              ; disable Telnet

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;; EXPANSION BOARD  ;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
G4 S2 					; wait for expansion boards to start

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;; DRIVERS  ;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M569 P0.1 S0                            ; physical drive 1 goes backwards -Y I-
M569 P0.4 S1                           	; physical drive 1 goes forwards -Y II-
M569 P0.2 S0                            ; physical drive 2 goes forwards -X-
M569 P0.3 S1                            ; physical drive 3 goes forwards -Z-
M569 P122.0 S0 R0			; physical drive 122 goes forwards -1XD-

M584 X0.2 Y0.1:0.4 Z0.3 E122.0  	; set drive mapping
M350 X16 Y16 Z16 E16 I1         	; configure microstepping with interpolation
M92 X53.33 Y53.33 Z640 E135  		; set steps per mm
M566 X300 Y300 Z60 E:120		; set maximum instantaneous speed changes (mm/min);
M203 X6000 Y6000 Z180 E8000		; set maximum speeds (mm/min);
M201 X1250 Y1250 Z200 E250		; set accelerations (mm/s^2)
M906 X3000 Y3000 Z3000 E1680 I30	; set motor currents (mA) and motor idle factor in per cent
M84 S30                           	; Set idle timeout

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;  LIMITS  ;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M208 X-30 Y-150 Z0 S1                   ; set axis minima
M208 X670 Y2020 Z250 S0                 ; set axis maxima

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;; ENDSTOPS ;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M574 X1 S1 P"!io3.in"                   ; configure switch-type (e.g. microswitch) endstop for low end on X via pin !io3.in
M574 Y1 S1 P"!io1.in"                   ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin !io1.in

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;; BLTouch Bed Probe ;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Z-Probe
M950 S0 C"io7.out"           		; create servo pin 0 for BLTouch (use IO_4/5/7 for 6HC, IO_1/2/3 for Mini 5+)
M558 P9 C"io7.in" H5 F120 T6000 	; set Z probe type to bltouch and the dive height + speeds
G31 X52 Y-36 Z0.5         		; set Z probe trigger value, offset and trigger height
M557 X80:650 Y80:2000 S250:300 		; define mesh grid

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;; PULSAR HEATERS ;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;--- TOP ---------------------------
M308 S0 P"spi.cs0" Y"rtd-max31865"    		; configure sensor 0 as PT100 on pin spi.cs0; TOP
M950 H0 C"out3" T0                     		; create nozzle heater output on out3 and map it to sensor 0
M307 H0 B0 S1.00                       		; disable bang-bang mode for heater  and set PWM limit
M143 H0 S250                            	; set temperature limit for heater 0 to 480C
M307 H0 R0.929 K0.101:0.000 D40.37 E1.35 S1.00 B0 V23.6 ; PID AUTO TUNING

;--- MIDDLE ---------------------------
M308 S1 P"spi.cs1" Y"rtd-max31865"      	; configure sensor 1 as PT100 on pin spi.cs1; MIDDLE
M950 H1 C"out1" T1                      	; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00                        	; disable bang-bang mode for heater  and set PWM limit
M143 H1 S250                            	; set temperature limit for heater 1 to 480C
M307 H1 R0.711 K0.137:0.000 D23.70 E1.35 S1.00 B0 V23.7 ; PID AUTO TUNING

;--- NOZZLE --------------
M308 S2 P"spi.cs3" Y"rtd-max31865"      	; configure sensor 2 as PT100 on pin spi.cs3; NOZZLE
M950 H2 C"out2" T2                      	; create nozzle heater output on out2 and map it to sensor 2
M307 H2 B0 S1.00                        	; disable bang-bang mode for heater  and set PWM limit
M143 H2 S250                            	; set temperature limit for heater 2 to 480C
M307 H2 R0.690 K0.085:0.000 D17.77 E1.35 S1.00 B0 V23.7 ; PID AUTO TUNING

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;; BED HEATERS ;;;;,;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;--- BED -----------------
M308 S3 P"spi.cs2" Y"rtd-max31865"      ; configure sensor 3 as PT100 on pin spi.cs2 BED
M950 H3 C"out0" T3                      ; create bed heater output on out0 and map it to sensor 3
M307 H3 B0 S0.50                        ; disable bang-bang mode for the bed heater and set PWM limit
M140 H3                                 ; map heated bed to heater 3
M143 H3 S120                            ; set temperature limit for heater 3 to 120C
M307 H3 R0.224 K0.163:0.000 D132.77 E1.35 S0.50 B0 ; PID AUTO TUNING

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;; TOOLS ;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
M563 P0 S"PULSAR" D0 H0:1:2 F0          ; define tool 0 S"PULSAR" D0 H1:2 F0
G10 P0 X40 Y40 Z0                       ; set tool 0 axis offsets
G10 P0 R0 S0                            ; set initial tool 0 active and standby temperatures to 0C

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;; MISCELLANEOUS ;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; ----------- M501	; load saved parameters from non-volatile memory

This is a log extracted immediately after the reset:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.4 (2022-10-20 16:19:01) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6JTD0-3SN6P-1BA6U
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 152824
Dynamic ram: 97436 of which 12 recycled
Never used RAM 100400, free system stack 202 words
Tasks: NETWORK(ready,30.7%,260) ETHERNET(notifyWait,0.0%,453) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,340) TMC(notifyWait,8.0%,91) MAIN(running,61.0%,1083) IDLE(ready,0.2%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:57 ago, cause: power up
Last software reset at 2022-12-24 12:16, reason: User, GCodes spinning, available RAM 100328, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 126
MCU temperature: min 41.1, current 42.9, max 43.1
Supply voltage: min 23.6, current 23.7, max 23.7, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 56408, writes 11 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 56405, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 56405, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 56405, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 56405, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 56409, writes 11 timeouts 0
Date/time: 2022-12-24 12:56:31
Slowest loop: 7.66ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 3 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 514, received 463, lost 0, boc 0
Longest wait 1ms for reply type 6042, peak Tx sync delay 6, free buffers 50 (min 49), ts 288/287/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 2.40ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

undefined

Hi,

I'm starting with a Pulsar Extruder (that is provided with an external driver Microstep Driver R60) over my Duet 6HC.

I have added the Expansion 1XD to connect the external driver, the wiring looks correct, all LEDs flashing as expected, communication with the 1XD works, both firmwares are updated (6HC and 1XD) and the motor is OK because works fine wired as a regular motor directly to the 6HC.

I have been following this threat but there is something wrong in my config that I'm unable to detect.

Is any guru available?

G4 S2 ; wait for expansion boards to start

M569 P0.2 S0                              ; physical drive 0.2 goes forwards -X- INVERSO
M569 P0.1 S0                              ; physical drive 0.1 goes backwards -Y- INVERSO
M569 P0.4 S1                              ; physical drive 0.1 goes forwards -Y II-
M569 P0.3 S1                              ; physical drive 0.3 goes forwards -Z                    
M569 P122.0 S1 R1 T3:3:5:0                ; EXTRUDER

M584 X0.2 Y0.1:0.4 Z0.3 E122.0         	        ; set drive mapping          
M350 X16 Y16 Z16 E16  I1                        ; configure microstepping with interpolation
M92 X53.33 Y53.33 Z640.0 E3200.00	        ; set steps per mm;
M566 X900 Y900 Z60.00 E120.00                   ; set maximum instantaneous speed changes (mm/min);
M203 X6000.00 Y6000.00 Z180.00 E1200.00         ; set maximum speeds (mm/min);
M201 X500.00 Y500.00 Z20.00 E250.00             ; set accelerations (mm/s^2);


M906 X3000 Y3000 Z3000 E2700 I30             ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                      ; set idle timeout