I have already switched from 1.22.6 to 2.04.
I produce printers and always have the same config and firmware on them.
Lan cable is certainly not a problem since I have tested it on other printers and there are no problems.
If this is a guarantee case, I will be happy to discuss this with roland.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet Ethernet 1.02 or later
Board ID: 08DGM-917DA-G4MS8-6JKDL-3S46Q-TVT3B
Used output buffers: 3 of 24 (6 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 92856 of which 0 recycled
Exception stack ram used: 320
Never used ram: 12184
Tasks: NETWORK(ready,764) HEAT(blocked,1232) MAIN(running,3816) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 04:08:33 ago, cause: software
Last software reset at 2019-12-18 07:46, reason: User, spinning module GCodes, available RAM 12032 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 21.5, current 22.8, max 23.1
Supply voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-12-18 11:55:39
Cache data hit count 4294967295
Slowest loop: 4.53ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 4.97ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state 5, link 100Mbps full duplex
=== Filament sensors ===
Extruder 0 sensor: ok
I have a problem with two duet2 ethernets of around 20 installed.
When I start a print job, it loses the connection to the webcontrol shortly thereafter and can only be found again after the job.
sometimes only when the printer has been reset.
ping does not come, even though the display shows an IP.
I then updated to the new firmware and still have the same problem.
I ask for help.
regards
Michel
And the print job is just finished in the middle of the program. Then the printer can no longer operate and only after a network reset it is reflected
I have now switched to a duet ethernet and still have the same errors.
I have the problem only with the paneldue 1.23.2
I do not have that with the old 1.22
M575 P1
Channel 1: baud rate 57600, does not require checksum
now the error still comes
Hello everybody
I have a checksum error every few minutes on a new duet with paneldue.
cable I have already tested and is so far io.
I have already tried to use a shielded cable, but I get the same error.
it may be that the sd card is not good?
06:00:39
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SJ-6JKDA-3SD6Q-1VXRF
Used output buffers: 4 of 24 (19 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93816 of which 0 recycled
Exception stack ram used: 436
Never used ram: 11140
Tasks: NETWORK(ready,524) HEAT(blocked,1236) MAIN(running,3820) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:05:07 ago, cause: power up
Last software reset at 2019-09-27 05:47, reason: User, spinning module GCodes, available RAM 11224 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 26.1, current 27.7, max 27.9
Supply voltage: min 26.6, current 26.9, max 27.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max 0/354
Driver 1: ok, SG min/max 0/346
Driver 2: ok, SG min/max 63/240
Driver 3: ok, SG min/max 0/82
Driver 4: ok, SG min/max 1/356
Date/time: 2019-09-27 06:00:38
Cache data hit count 1063112760
Slowest loop: 56.25ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 163, MinFreeDm: 132, MaxWait: 22034ms
Bed compensation in use: mesh, comp offset 0.000
=== DDARing ===
Scheduled moves: 399, completed moves: 395, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.3
=== GCodes ===
Segments left: 1
Stack records: 3 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is doing "G1 X297.694 Y-16.907 E238.1284" in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 13.93ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8
Waht can i do?
Please help me.
; Tools
M563 P1 S"1xHotend" D0 H1 ; Define tool 1
G10 P1 X0 Y0 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C
M563 P2 S"2xHotend" D1:0 H2:1 ; Define tool 2
G10 P2 X0 Y0 Z0 ; Set tool 2 axis offsets
G10 P2 R0 S0 ; Set initial tool 2 active and standby temperatures to 0C
M568 P2 S1 ; Enable mixing for tool 2
M567 P2 E1:1 ; Set mixing ratios for tool 2
M563 P3 S"3xHotend" D2:0:1 H3:1:2 ; Define tool 3
G10 P3 X0 Y0 Z0 ; Set tool 3 axis offsets
G10 P3 R0 S0 ; Set initial tool 3 active and standby temperatures to 0C
M568 P3 S1 ; Enable mixing for tool 3
M567 P3 E1:1:1 ; Set mixing ratios for tool 3
M563 P4 S"4xHotend" D3:0:1:2 H4:1:2:3 ; Define tool 4
G10 P4 X0 Y0 Z0 ; Set tool 4 axis offsets
G10 P4 R0 S0 ; Set initial tool 4 active and standby temperatures to 0C
M568 P4 S1 ; Enable mixing for tool 4
M567 P4 E1:1:1:1 ; Set mixing ratios for tool 4
;M563 P5 S"5xHotend" D4:0:1:2:3 H5:1:2:3:4 ; Define tool 5
;G10 P5 X0 Y0 Z0 ; Set tool 5 axis offsets
;G10 P5 R0 S0 ; Set initial tool 5 active and standby temperatures to 0C
;M568 P5 S1 ; Enable mixing for tool 5
;M567 P5 E1:1:1:1:1 ; Set mixing ratios for tool 5
M563 P11 S"1xHotend300" D0 H1 ; Define tool 11
G10 P11 X0 Y0 Z0 ; Set tool 11 axis offsets
G10 P11 R0 S0 ; Set initial tool 11 active and standby temperatures to 0C
M563 P12 S"2xHotend300" D0:1 H1:2 ; Define tool 12
G10 P12 X0 Y0 Z0 ; Set tool 12 axis offsets
G10 P12 R0 S0 ; Set initial tool 12 active and standby temperatures to 0C
M568 P12 S1 ; Enable mixing for tool 12
M567 P12 E1:1 ; Set mixing ratios for tool 12
;M563 P13 S"3xHotend300" D1:0:2 H1:2:3 ; Define tool 13
;G10 P13 X0 Y0 Z0 ; Set tool 13 axis offsets
;G10 P13 R0 S0 ; Set initial tool 13 active and standby temperatures to 0C
;M568 P13 S1 ; Enable mixing for tool 13
;M567 P13 E1:1:1 ; Set mixing ratios for tool 13
;M563 P14 S"4xHotend300" D0:1:2:3 H1:2:3:4 ; Define tool 14
;G10 P14 X0 Y0 Z0 ; Set tool 14 axis offsets
;G10 P14 R0 S0 ; Set initial tool 14 active and standby temperatures to 0C
;M568 P14 S1 ; Enable mixing for tool 14
;M567 P14 E1:1:1:1 ; Set mixing ratios for tool 14
M563 P91 S"1xHotend" D0 H1 ; Define tool 1
G10 P91 X0 Y0 Z0 ; Set tool 1 axis offsets
G10 P91 R0 S0
M563 P92 S"1xHotend" D1 H2 ; Define tool 1
G10 P92 X0 Y0 Z0 ; Set tool 1 axis offsets
G10 P92 R0 S0
M563 P93 S"1xHotend" D2 H3 ; Define tool 1
G10 P93 X0 Y0 Z0 ; Set tool 1 axis offsets
G10 P93 R0 S0
M563 P94 S"1xHotend" D3 H4 ; Define tool 1
G10 P94 X0 Y0 Z0 ; Set tool 1 axis offsets
G10 P94 R0 S0
;M563 P95 S"1xHotend" D4 H5 ; Define tool 1
;G10 P95 X0 Y0 Z0 ; Set tool 1 axis offsets
;G10 P95 R0 S0
; Lasersensor
M591 D1 P5 C4 R40: 120 E3.0 S1 ; Der Duet3D-Lasersensor für den Extruderantrieb 0 ist an den Stopp-Eingang 3 (E0) angeschlossen, Toleranz 40 bis 120%, 3 mm Vergleichslänge
M591 D2 P5 C3 R40: 120 E3.0 S1 ; Der Duet3D-Lasersensor für den Extruderantrieb 0 ist an den Stopp-Eingang 3 (E0) angeschlossen, Toleranz 40 bis 120%, 3 mm Vergleichslänge
M591 D3 P5 C0 R40: 120 E3.0 S1 ; Der Duet3D-Lasersensor für den Extruderantrieb 0 ist an den Stopp-Eingang 3 (E0) angeschlossen, Toleranz 40 bis 120%, 3 mm Vergleichslänge
M591 D4 P5 C1 R40: 120 E3.0 S1 ; Der Duet3D-Lasersensor für den Extruderantrieb 0 ist an den Stopp-Eingang 3 (E0) angeschlossen, Toleranz 40 bis 120%, 3 mm Vergleichslänge
;M591 D9 P5 C2 R40: 120 E3.0 S1 ; Der Duet3D-Lasersensor für den Extruderantrieb 0 ist an den Stopp-Eingang 3 (E0) angeschlossen, Toleranz 40 bis 120%, 3 mm Vergleichslänge
; Automatic power saving
M911 S22 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss
M501 ; Load config override
Hello dc42
how must this be now? can the laser also be on the duex5?
and how should they be defined without the c-parameter?
I thank you for the R-parameter in the PT100 this is great.
and then the config
; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Thu Mar 07 2019 12:10:12 GMT+0100 (Mitteleuropäische Normalzeit)
; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M569 P5 S1 ; Drive 5 goes forwards
M569 P6 S1 ; Drive 6 goes forwards
M569 P7 S0 ; Drive 7 goes forwards
M569 P8 S0 ; Drive 8 goes forwards
M569 P9 S0 ; Drive 9 goes forwards
M584 X4 Y3:0 Z2:1 E5:6:7:8:9 ; Apply custom drive mapping
M350 X16 Y16 Z16 E32:32:32:32:32 I0 ; Configure microstepping without interpolation
M92 X266.665 Y266.665 Z1600 E830.00:830.00:830.00:830.00:830.00 ; Set steps per mm
M566 X400.00 Y400.00 Z12.00 E900.00:900.00:900.00:900.00:900.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z800.00 E6000.00:6000.00:6000.00:6000.00:6000.00 ; Set maximum speeds (mm/min)
M201 X320.00 Y320.00 Z10.00 E2500.00:2500.00:2500.00:2500.00:2500.00 ; Set accelerations (mm/s^2)
M906 X1800.00 Y1800.00 Z1800.00 E800.00:800.00:800.00:800.00:800.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30
; Set idle timeout
; Endstops
M574 C5 X1 S1 ; Set X-Axis min. endstop
M574 C6 Y1 S1 ; Set Y-Axis left min. endstop
;M574 Z1 S2 ; Set Z-Axis probe endstop
;M574 C8 Z2 S1
; Axis Limits
M208 X-250 Y-250 Z0 S1 ; Set axis minima
M208 X250 Y250 Z480 S0 ; Set axis maxima
; Z-Probe
M307 H7 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 F250 H5 R0.3 T3000 A5 B1 ; Set Z probe type to bltouch and the dive height + speeds
G31 P25 X-24 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X-225:225 Y-225:225 S150 ; Define mesh grid
; Heaters
M141 H6 P0
M307 H6 B1 S1 C3000 D300 ; Enable bang-bang mode for the bed heater and set PWM limit
M570 H6 T30
M301 H6 P-1 ; Assign chamber heater to heater 0
M305 P0 T100000 B4725 C7.060000e-8 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 X200 ; Configure thermocouple for heater 1
M143 H1 S550 ; Set temperature limit for heater 1 to 550C
M305 P2 X201 ; Configure thermocouple for heater 2
M143 H2 S550 ; Set temperature limit for heater 2 to 550C
M305 P3 X204 ; Configure thermocouple for heater 3
M143 H3 S550 ; Set temperature limit for heater 3 to 550C
M305 P4 X205 ; Configure thermocouple for heater 4
M143 H4 S550 ; Set temperature limit for heater 4 to 550C
M305 P5 X206 ; Configure thermocouple for heater 5
M143 H5 S550 ; Set temperature limit for heater 5 to 550C
M305 P6 T100000 B4725 C7.060000e-8 R4700 X1 ; Set thermistor + ADC parameters for heater 6 and remap it to channel 1
M143 H6 S65 ; Set temperature limit for heater 6 to 65C
; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
Hello RC42
Again, I have a question:
If one of the 4 extruder triggers runout sensors goes into break, this is so far synonymous io, only if I then unload my load and macro launches he loses on the remaining extruders, the temperature and then prints with only one.
How can I handle this, so that the tool always remains active before the break.
Enclosed my load macro.
Then I can pack the whole thing in a macro that when I load for example t4 (4 extruder) he only takes these which are also plugged?
The rest then have a temp mistake.
Do I have a possibility?
I politely ask for help.
regards
Michel
T91
G91
G1 Z5 F400
G90
G1 X0 Y-250 F800 ; Move to service position
G10 S240 ; Set current tool temperature to 240C
M291 P"Warten bis das Hotend 240°C erreicht hat!" R"Filament laden" S0 T600 ; Display message
M116 S5 ; Wait for the temperatures to be reached
G4 P200
M300
G4 P2000
M292
M291 P"Temperatur erreicht" S2
M291 P"Bitte Filament einführen, halten und mit OK bestätigen" S3 ; Display new message
M291 P"Führe Filament zur Düse" S0 T40
G1 E10 F180 ; Feed 1870mm of filament at 3000mm/min
G1 E40 F500 ; Feed 1870mm of filament at 3000mm/min
G4 P1000 ; Wait one second
G1 E100 F200 ; Feed 80mm of filament at 300mm/min
G1 E-2 F500 ; Retract 10mm of filament at 800mm/min
M400 ; Wait for moves to complete
;play sound
G4 P200
M300
G4 P2000
M400
M291 P"Filament laden abgeschlossen bitte bestätigen mit OK" S2 ; Display new message
M292 ; Acknowledge message
unload:
T91
G91
G1 Z5 F400
G90
G1 X0 Y-250 F800 ; Move to service position ; Move to service position
G10 S240 ; Set current tool temperature to 240C
M291 P"Bitte warten bis das Hotend 240°C erreicht hat!" R"Filament entladen" S0 T600 ; Display message
M116 ; Wait for the temperatures to be reached
M400 ; Wait for moves to complete
M292
M291 P"Entlade Filament..." R"Filament entladen" S2 ; Display another message
G1 E30 F180 ; Load 30mm of filament at 180mm/min
G1 E-150 F1000 ; Retract 200mm of filament at 1000mm/min
M400 ; Wait for the moves to finish
M292 ; Acknowledge message
;play sound
G4 P200
M300
G4 P2000
M291 P"Filament kann nun entfernt werden" R"Filament entladen" S2 ; Display another message
hello dc42
I still have a small mistake that you can possibly explain to me.
Soblad the filament is empty, the printer goes into pause.
if I then unload the macros and load and then continue to print the laser is no longer.
that means when I cut the filament he does not recognize more than empty.
how can I fix this?
Thank you very much for your quick help.
as always.
regards
@dc42 Only I do not get anything out at d0
I plugged in the sensors like this.
I have aninst somewhere a mistake
@dc42 on the D0 according to the readout no sensor is installed and the D1 reads it actually clean
