Duet3 Mini 5+ - strange messages, Do I run my first print?

PaulHew

So I am about to perform my first test print.
I trammed my bed cold, then heated it to my working temp, every time I tram it I am getting 'Network errors' instead of reporting back the adjustments made

30/03/2021, 11:03:14 	M98 P"0:/macros/2_Tram_Bed.G"
Error: Network error
30/03/2021, 11:01:44 	M98 P"0:/macros/2_Tram_Bed.G"
Error: Network error
30/03/2021, 10:44:08 	Bed Traming Cycle: 1 - Difference was 0.008mm
30/03/2021, 10:44:08 	Leadscrew adjustments made: 0.014 0.026 0.039, points used 3, (mean, deviation) before (0.025, 0.008) after (0.000, 0.000)

Macros.
Tram_Bed runs a G32.
Bed.g

; New 2/5/2020
;M98 P"0:/macros/Lighting/Red-On.g"
if !move.axes[0].homed || !move.axes[1].homed	; If the printer hasn't been homed, home it
M98 P"0:/sys/homex.g"							; home x
M98 P"0:/sys/homey.g"							; home Y
M98 P"0:/sys/homez.g"							; home z
;
M561											; clear any bed transform
;M558 P9 H5 F120 T24000							; increase dive height
;M98 P"0:/sys/bed_FourScrews.g"					; perform bed tramming
M98 P"0:/sys/bed_ThreeScrews.g"					; perform bed tramming
;
echo "Bed Traming Cycle: 1 - Difference was " ^ move.calibration.initial.deviation ^ "mm"
;
while move.calibration.initial.deviation >= 0.009	; 0.01 perform additional tramming if previous deviation was over 0.02mm
	if iterations = 5
		abort "Too many auto tramming attempts"
	M98 P"0:/sys/bed_ThreeScrews.g"
	echo "Bed Traming Cycle: " ^ iterations + 2 ^ " - Difference was " ^ move.calibration.initial.deviation ^ "mm"
		continue

;

G28 Z							; home z

Config.g

; General preferences
G90                                              ; send absolute coordinates...
M83                                              ; ...but relative extruder moves
M550 P"RailCore II"                              ; set printer name
M669 K1                                          ; select CoreXY mode
G4 S1											 ; wait for expansion boards to start

; Drives
M569 P0.0 S1                                     ; X Axis - physical drive 0.0 goes forwards
M569 P0.1 S0                                     ; Y Axis - physical drive 0.1 goes backwards
M569 P0.2 S1                                     ; Left Front physical drive 0.2 goes forwards
M569 P0.3 S1                                     ; Left Rear physical drive 0.3 goes forwards
M569 P0.4 S1                                     ; Right physical drive 0.4 goes forwards
M569 P20.0 S0                                    ; Extruder - physical drive 20.0 goes forwards

M584 X0.0 Y0.1 Z0.2:0.3:0.4 E20.0                ; set drive mapping
;
M350 X16 Y16 Z16 E16 I1                          ; configure microstepping with interpolation
;
M92 X200.00 Y200.00                                ; set steps per mm
M92 Z1600                                        ; set steps per mm Z Axis
M92 E412                                         ; set steps per mm Extruder
;
M566 X600.00 Y600.00 Z200.00 E3600.00            ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z900.00 E3600.00          ; set maximum speeds (mm/min)
M201 X1500.00 Y1500.00 Z250.00 E1500.00          ; set accelerations (mm/s^2)
M906 X1280 Y1280 Z1220 E700 I30                  ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                          ; Set idle timeout

; Leadscrew locations
;New 4-2-21
M671 X-1:-1:350 Y24:281:151 S7.5


; Axis Limits
;M208 X0 Y0 Z0 S1                                 ; set axis minima
;M208 X230 Y300 Z400 S0                           ; set axis maxima
M208 X-10:300 Y0:300 Z-0.5:500 S0

; Endstops
M574 X1 S1 P"io5.in"                             ; configure active-high endstop for low end on X via pin io5.in
M574 Y1 S1 P"20.io2.in"                          ; configure active-high endstop for low end on Y via pin 20.io1.in


; Z-Probe - ToolBoard 1LC
M950 S0 C"20.io0.out"                           ; create servo pin 0 for BLTouch
M558 P9 C"^20.io0.in" H5 F120 T6000             ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-7 Y35 Z0.904                            ; set Z probe trigger value, offset and trigger height
;M557 X15:215 Y15:195 S20                         ; define mesh grid
M557 X30:280 Y45:240 S20


; Z-Probe - Using io_1
;M950 S0 C"io1.out"                           ; create servo pin 0 for BLTouch
;M558 P9 C"^io1.in" H5 F120 T6000             ; set Z probe type to bltouch and the dive height + speeds
;G31 P500 X-7 Y35 Z2.5                            ; set Z probe trigger value, offset and trigger height
;M557 X15:215 Y15:195 S20                         ; define mesh grid




; Heaters
M308 S0 P"temp0" Y"thermistor" A"Heated Bed" T100000 B4138     ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                               ; create bed heater output on out1 and map it to sensor 0
;M307 H0 B0 S1.00                                 ; disable bang-bang mode for the bed heater and set PWM limit
M307 H0 R0.853 C250.9 D5.98 S0.60                ; tuned to 50degrees - 28/3/21
M140 H0                                          ; map heated bed to heater 0
M143 H0 S120                                     ; set temperature limit for heater 0 to 120C

M308 S1 P"20.temp0" Y"thermistor" A"Mosquito" T500000 B3950 ; configure sensor 1 as thermistor on pin 20.temp0
M950 H1 C"20.out0" T1                           ; create nozzle heater output on 20.out0 and map it to sensor 1
;M307 H1 B0 S1.00                                 ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                     ; set temperature limit for heater 1 to 280C
M307 H1 R1.632 C237.7 D6.86 S1.00 V24.2

; Other Thermistors
M308 S2 P"temp1" Y"thermistor" A"Bed-Top" T100000 B4138     ; configure sensor 0 as thermistor on pin temp0

; Fans
M950 F0 C"20.out1+out1.tach" Q500                         ; create fan 0 on pin 20.out1 and set its frequency
M106 P0 S0 H-1                                   ; set fan 0 value. Thermostatic control is turned off

M950 F1 C"20.out2" Q500                         ; create fan 1 on pin 20.out2 and set its frequency
M106 P1 S1 H1 T50                                ; set fan 1 value. Thermostatic control is turned on

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

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600                                ; enable support for PanelDue

T0					                             ; select first hot end

It makes me nervous about running a print, especially if it is not reporting back simple things like tramming info.

Paul.

droftarts

@paulhew Does it do the bed tramming and fail to report, or does it not do the bed tramming? Does it make a difference if you turn off the bed just while conducting the tramming (possible interference from bed SSR)? Anything in the other macros that are called in bed.g that could possibly cause it?

Ian

PaulHew

@droftarts Hi Ian, thank you for your prompt assistance.
I have had it report network errors even with the bed not heated or any heaters running at all.
The only other macro that is contained within bed.g is the screw positioning routine, bed_ThreeScrews.g

G30 P0 X0 Y35 Z-99999
G30 P1 X0 Y275 Z-99999
G30 P2 X280 Y150 Z-99999 S3

I even rebooted and this is from the console.

30/03/2021, 11:29:26 	Height map loaded from file heightmap.csv
30/03/2021, 11:29:13 	Bed Traming Cycle: 1 - Difference was 0.003mm
30/03/2021, 11:29:13 	Leadscrew adjustments made: 0.010 0.013 0.005, points used 3, (mean, deviation) before (0.010, 0.003) after (0.000, 0.000)
30/03/2021, 11:17:45 	G29
Error: Network error
30/03/2021, 11:17:01 	M98 P"0:/macros/2_Tram_Bed.G"
Leadscrew adjustments made: 0.011 0.023 0.015, points used 3, (mean, deviation) before (0.017, 0.005) after (-0.000, 0.000)

Bed Traming Cycle: 1 - Difference was 0.005mm
30/03/2021, 11:15:44 	M98 P"0:/macros/2_Tram_Bed.G"
Leadscrew adjustments made: 0.026 0.016 0.019, points used 3, (mean, deviation) before (0.021, 0.004) after (-0.000, 0.000)

Bed Traming Cycle: 1 - Difference was 0.004mm
30/03/2021, 11:12:42 	G28
Error: Network error
30/03/2021, 11:12:21 	Connection established

Regards,

Paul

PaulHew

1LC has Y endstop, BLTouch, Stepper, hotend heater, hotend temp.
Could it be a CANBus issue? It is terminated.

droftarts

@paulhew There's also the homex, y and z.g files called in bed.g.

But does it actually do the tramming, despite the error message and no response? Or does it stop part way through? Does it home x, y and z, then fail, or not start at all? As it's doing it after the first time, presumably the axes are homed already, so is it something as simple as the check whether it's homed not working properly? What version of DSF are you running (check in DWC > Settings > Machine-specific > General)?

Ian

chrishamm

@paulhew Sounds odd to me that you are getting network errors. Do you get any more details? It sounds like the commands are terminated which is why it outputs those messages. To be clear: You are using DSF+DWC+RRF 3.2.2, aren't you?

If yes, please open a terminal on the SBC and start looking for potential error messages in the DCS log viajournalctl -u duetcontrolserver -f. Then run G28/G29 and see what happens.

PaulHew

@droftarts It completes the tasks, homing or tramming but pops these messages up.
Sometimes it completes and gives me the correct feedback.

M122 on Board and 1LC

30/03/2021, 12:19:58 	m122 b20
Diagnostics for board 20:
Duet TOOL1LC firmware version 3.2.2 (2021-02-11)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 4000, free system stack 48 words
HEAT 90 CanAsync 89 CanRecv 83 TMC 56 MAIN 218 AIN 64
Last reset 01:07:40 ago, cause: software
Last software reset data not available
Driver 0: position 271609, 412.0 steps/mm, standstill, SG min/max 0/18, read errors 0, write errors 1, ifcnt 31, reads 63919, writes 15, timeouts 0, DMA errors 0
Moves scheduled 1583, completed 1583, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 24.3V
MCU temperature: min 40.2C, current 40.3C, max 61.1C
Ticks since heat task active 65, ADC conversions started 4043854, completed 4043853, timed out 0
Last sensors broadcast 0x00000002 found 1 69 ticks ago, loop time 0
CAN messages queued 49844, send timeouts 0, received 39096, lost 0, free buffers 36
30/03/2021, 12:19:51 	m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus Ethernet (SBC mode)
Board ID: A45XG-F396U-D65J0-40KML-1F03Z-H03XP
Used output buffers: 1 of 40 (18 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 94964 of which 120 recycled
Never used RAM 51400, free system stack 122 words
Tasks: Linux(ready,99) HEAT(blocked,291) CanReceiv(blocked,807) CanSender(blocked,366) CanClock(blocked,370) TMC(blocked,97) MAIN(running,386) IDLE(ready,20) AIN(blocked,260)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 01:07:31 ago, cause: software
Last software reset at 2021-03-30 11:12, reason: User, none spinning, available RAM 51428, slot 0
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 0.0, current 23.9, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 58000, standstill, SG min/max 0/478, read errors 0, write errors 1, ifcnt 54, reads 51641, writes 21, timeouts 564, DMA errors 0, failedOp 0x72
Driver 1: position -54000, standstill, SG min/max 0/494, read errors 0, write errors 1, ifcnt 54, reads 51570, writes 21, timeouts 635, DMA errors 0, failedOp 0x71
Driver 2: position 55982, standstill, SG min/max 0/240, read errors 0, write errors 1, ifcnt 56, reads 49281, writes 21, timeouts 2924, DMA errors 0, failedOp 0x6f
Driver 3: position 0, standstill, SG min/max 0/260, read errors 0, write errors 1, ifcnt 56, reads 51410, writes 21, timeouts 795, DMA errors 0, failedOp 0x6a
Driver 4: position 0, standstill, SG min/max 0/266, read errors 0, write errors 1, ifcnt 56, reads 52205, writes 21, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-03-30 12:19:50
Cache data hit count 4294967295
Slowest loop: 201.31ms; fastest: 0.07ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 124236ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 2001, completed moves 2001, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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 39020, send timeouts 0, received 49736, lost 0, longest wait 2ms for reply type 6031, free buffers 16
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 4ms ago
RX/TX seq numbers: 13708/13708
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x113bc
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.2
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.74
Maximum length of RX/TX data transfers: 2960/676

PaulHew

@chrishamm Current journal, no errors.

pi@RailCoreII:~ $ journalctl -u duetcontrolserver -f
-- Logs begin at Mon 2021-03-29 21:18:43 BST. --
Mar 30 11:29:13 RailCoreII DuetControlServer[4869]: [info] Bed Traming Cycle: 1 - Difference was 0.003mm
Mar 30 11:29:13 RailCoreII DuetControlServer[4869]: [info] Starting macro file homez.g on channel File
Mar 30 11:29:13 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel File
Mar 30 11:29:14 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 11:29:21 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel File
Mar 30 11:29:21 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 11:29:22 RailCoreII DuetControlServer[4869]: [info] Finished macro file homez.g
Mar 30 11:29:26 RailCoreII DuetControlServer[4869]: [info] Height map loaded from file heightmap.csv
Mar 30 11:53:39 RailCoreII DuetControlServer[4869]: [info] Finished job file
Mar 30 11:53:39 RailCoreII DuetControlServer[4869]: [info] Finished printing file 0:/gcodes/ABS Shape-Box-1.61566g-22m.gcode, print time was 0h 27m

Regards,

Paul.

PaulHew

considering the logs begin at 21:18 last night, there have not been many entries..
I have been testing tramming, homing, bed mesh multiple times this morning.
P.

chrishamm

@paulhew Thanks, so nothing is wrong there. Perhaps G28 and G29 just take too long and time out and/or the connection is interrupted while the web interface is waiting for a response. In SBC mode a code HTTP request remains active as long as the code hasn't finished.

PaulHew

@chrishamm Since running that command on the Pi no issues with network errors etc.
I spoke too soon!

Console

30/03/2021, 12:37:45 	G32
Error: Network error
30/03/2021, 12:36:33 	g32
Leadscrew adjustments made: 0.051 0.042 0.038, points used 3, (mean, deviation) before (0.044, 0.005) after (-0.000, 0.000)

Bed Traming Cycle: 1 - Difference was 0.005mm
30/03/2021, 12:35:24 	g28

Mar 30 12:37:04 RailCoreII DuetControlServer[4869]: [info] Starting macro file homeall.g on channel HTTP
Mar 30 12:37:19 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:37:19 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:37:27 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:37:27 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:37:27 RailCoreII DuetControlServer[4869]: [info] Finished macro file homeall.g
Mar 30 12:37:39 RailCoreII DuetControlServer[4869]: [info] Starting macro file bed.g on channel HTTP
Mar 30 12:37:39 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homex.g on channel HTTP
Mar 30 12:37:46 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homex.g
Mar 30 12:37:46 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homey.g on channel HTTP
Mar 30 12:37:53 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homey.g
Mar 30 12:37:53 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homez.g on channel HTTP
Mar 30 12:37:56 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:37:56 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:38:04 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:38:04 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:38:05 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homez.g
Mar 30 12:38:08 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/bed_ThreeScrews.g on channel HTTP
Mar 30 12:38:11 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:38:11 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:38:13 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:38:13 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:38:17 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:38:17 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:38:19 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:38:19 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:38:23 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:38:23 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:38:26 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:38:26 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:38:26 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/bed_ThreeScrews.g
Mar 30 12:38:27 RailCoreII DuetControlServer[4869]: [info] Starting macro file homez.g on channel HTTP
Mar 30 12:38:29 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:38:29 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:38:34 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:38:34 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:38:35 RailCoreII DuetControlServer[4869]: [info] Finished macro file homez.g
Mar 30 12:38:38 RailCoreII DuetControlServer[4869]: [info] Finished macro file bed.g

droftarts

@paulhew If the timing is right, you got the error when it ran homex.g. Can you post that?

Ian

PaulHew

@droftarts Homex.g as requested.

G91               ; relative positioning
G1 H2 Z5 F3000    ; lift Z relative to current position
G1 H1 X-340 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000       ; go back a few mm
G1 H1 X-15 F360  ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

droftarts

@paulhew Looks unequivocally correct!

Ian

PaulHew

@droftarts
Just popped up with a network error whilst running a G32, continued to run the g32.

30/03/2021, 12:53:44 	g32
Error: Network error
30/03/2021, 12:53:19 	g32
Leadscrew adjustments made: 0.013 0.020 0.027, points used 3, (mean, deviation) before (0.019, 0.005) after (0.000, 0.000)

Bed Traming Cycle: 1 - Difference was 0.005mm
30/03/2021, 12:52:16 	g32
Leadscrew adjustments made: 0.026 0.023 0.017, points used 3, (mean, deviation) before (0.022, 0.003) after (0.000, 0.000)

Bed Traming Cycle: 1 - Difference was 0.003mm
30/03/2021, 12:51:12 	g28
30/03/2021, 12:50:42 	g28
30/03/2021, 12:50:11 	g28

pi log - note the bottom line, issue possibly?

Mar 30 12:49:44 RailCoreII DuetControlServer[4869]: [info] Starting macro file homeall.g on channel HTTP
Mar 30 12:49:59 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:49:59 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:50:07 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:50:07 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:50:08 RailCoreII DuetControlServer[4869]: [info] Finished macro file homeall.g
Mar 30 12:50:16 RailCoreII DuetControlServer[4869]: [info] Starting macro file homeall.g on channel HTTP
Mar 30 12:50:31 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:50:31 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:50:39 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:50:39 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:50:39 RailCoreII DuetControlServer[4869]: [info] Finished macro file homeall.g
Mar 30 12:50:45 RailCoreII DuetControlServer[4869]: [info] Starting macro file homeall.g on channel HTTP
Mar 30 12:51:00 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:51:00 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:51:08 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:51:08 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:51:09 RailCoreII DuetControlServer[4869]: [info] Finished macro file homeall.g
Mar 30 12:51:17 RailCoreII DuetControlServer[4869]: [info] Starting macro file bed.g on channel HTTP
Mar 30 12:51:17 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homex.g on channel HTTP
Mar 30 12:51:25 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homex.g
Mar 30 12:51:25 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homey.g on channel HTTP
Mar 30 12:51:32 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homey.g
Mar 30 12:51:32 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homez.g on channel HTTP
Mar 30 12:51:35 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:51:35 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:51:42 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:51:43 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:51:43 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homez.g
Mar 30 12:51:46 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/bed_ThreeScrews.g on channel HTTP
Mar 30 12:51:49 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:51:49 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:51:52 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:51:52 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:51:55 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:51:55 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:51:58 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:51:58 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:52:01 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:52:01 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:52:04 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:52:04 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:52:05 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/bed_ThreeScrews.g
Mar 30 12:52:05 RailCoreII DuetControlServer[4869]: [info] Starting macro file homez.g on channel HTTP
Mar 30 12:52:07 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:52:07 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:52:12 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:52:12 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:52:13 RailCoreII DuetControlServer[4869]: [info] Finished macro file homez.g
Mar 30 12:52:16 RailCoreII DuetControlServer[4869]: [info] Finished macro file bed.g
Mar 30 12:52:20 RailCoreII DuetControlServer[4869]: [info] Starting macro file bed.g on channel HTTP
Mar 30 12:52:20 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homex.g on channel HTTP
Mar 30 12:52:28 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homex.g
Mar 30 12:52:28 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homey.g on channel HTTP
Mar 30 12:52:35 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homey.g
Mar 30 12:52:35 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homez.g on channel HTTP
Mar 30 12:52:38 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:52:38 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:52:45 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:52:45 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:52:46 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homez.g
Mar 30 12:52:49 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/bed_ThreeScrews.g on channel HTTP
Mar 30 12:52:52 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:52:52 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:52:54 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:52:55 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:52:58 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:52:58 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:53:00 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:53:00 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:53:04 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:53:04 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:53:07 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:53:07 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:53:08 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/bed_ThreeScrews.g
Mar 30 12:53:08 RailCoreII DuetControlServer[4869]: [info] Starting macro file homez.g on channel HTTP
Mar 30 12:53:10 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:53:10 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:53:15 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:53:15 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:53:16 RailCoreII DuetControlServer[4869]: [info] Finished macro file homez.g
Mar 30 12:53:19 RailCoreII DuetControlServer[4869]: [info] Finished macro file bed.g
Mar 30 12:53:24 RailCoreII DuetControlServer[4869]: [info] Starting macro file bed.g on channel HTTP
Mar 30 12:53:24 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homex.g on channel HTTP
Mar 30 12:53:32 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homex.g
Mar 30 12:53:32 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homey.g on channel HTTP
Mar 30 12:53:39 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homey.g
Mar 30 12:53:39 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/homez.g on channel HTTP
Mar 30 12:53:42 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:53:42 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:53:50 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:53:50 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:53:50 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/homez.g
Mar 30 12:53:53 RailCoreII DuetControlServer[4869]: [info] Starting macro file 0:/sys/bed_ThreeScrews.g on channel HTTP
Mar 30 12:53:56 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:53:56 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:53:59 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:53:59 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:54:02 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:54:02 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:54:05 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:54:05 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:54:08 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:54:09 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:54:11 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:54:11 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:54:12 RailCoreII DuetControlServer[4869]: [info] Finished macro file 0:/sys/bed_ThreeScrews.g
Mar 30 12:54:12 RailCoreII DuetControlServer[4869]: [info] Starting macro file homez.g on channel HTTP
Mar 30 12:54:14 RailCoreII DuetControlServer[4869]: [info] Starting macro file deployprobe.g on channel HTTP
Mar 30 12:54:14 RailCoreII DuetControlServer[4869]: [info] Finished macro file deployprobe.g
Mar 30 12:54:20 RailCoreII DuetControlServer[4869]: [info] Starting macro file retractprobe.g on channel HTTP
Mar 30 12:54:20 RailCoreII DuetControlServer[4869]: [info] Finished macro file retractprobe.g
Mar 30 12:54:20 RailCoreII DuetControlServer[4869]: [info] Finished macro file homez.g
Mar 30 12:54:23 RailCoreII DuetControlServer[4869]: [info] Finished macro file bed.g
Mar 30 12:55:51 RailCoreII DuetControlServer[4869]: [warn] RepRapFirmware got a bad header checksum

PaulHew

random! Throws error but completes task

30/03/2021, 13:02:29 	g28
Error: Network error
30/03/2021, 13:02:21 	g28

PaulHew

chrishamm

@paulhew Yes, started codes always complete, even if the underlying connection is terminated. I suggest you press F12 to open the dev tools, go to Network, and check the cause for interrupted connections. It sounds like either the browser or OS kills the HTTP connection(s) after a brief moment.