Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

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

    Scheduled Pinned Locked Moved
    My Duet controlled machine
    4
    21
    808
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • chrishammundefined
      chrishamm administrators @PaulHew
      last edited by

      @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.

      Duet software engineer

      PaulHewundefined 1 Reply Last reply Reply Quote 0
      • PaulHewundefined
        PaulHew @droftarts
        last edited by

        @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
        

        RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
        Voron 2.4 disassembled..... Waiting for the RailCore Mini....

        1 Reply Last reply Reply Quote 0
        • PaulHewundefined
          PaulHew @chrishamm
          last edited by

          @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.

          RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
          Voron 2.4 disassembled..... Waiting for the RailCore Mini....

          1 Reply Last reply Reply Quote 0
          • PaulHewundefined
            PaulHew
            last edited by

            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.

            RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
            Voron 2.4 disassembled..... Waiting for the RailCore Mini....

            chrishammundefined 1 Reply Last reply Reply Quote 0
            • chrishammundefined
              chrishamm administrators @PaulHew
              last edited by

              @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.

              Duet software engineer

              PaulHewundefined 1 Reply Last reply Reply Quote 0
              • PaulHewundefined
                PaulHew @chrishamm
                last edited by

                @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
                

                RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                droftartsundefined 1 Reply Last reply Reply Quote 0
                • droftartsundefined
                  droftarts administrators @PaulHew
                  last edited by

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

                  Ian

                  Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                  PaulHewundefined 1 Reply Last reply Reply Quote 0
                  • PaulHewundefined
                    PaulHew @droftarts
                    last edited by

                    @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
                    

                    RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                    Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                    droftartsundefined 1 Reply Last reply Reply Quote 0
                    • droftartsundefined
                      droftarts administrators @PaulHew
                      last edited by

                      @paulhew Looks unequivocally correct!

                      Ian

                      Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                      PaulHewundefined 1 Reply Last reply Reply Quote 0
                      • PaulHewundefined
                        PaulHew @droftarts
                        last edited by

                        @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
                        

                        RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                        Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                        1 Reply Last reply Reply Quote 0
                        • PaulHewundefined
                          PaulHew
                          last edited by

                          random! Throws error but completes task

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

                          RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                          Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                          chrishammundefined 1 Reply Last reply Reply Quote 0
                          • PaulHewundefined
                            PaulHew
                            last edited by

                            1a1e8118-83d7-4419-a7b8-86b528485013-image.png

                            RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                            Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                            1 Reply Last reply Reply Quote 0
                            • chrishammundefined
                              chrishamm administrators @PaulHew
                              last edited by

                              @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.

                              Duet software engineer

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Unless otherwise noted, all forum content is licensed under CC-BY-SA