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

    cannot get 3hc to connect.

    Scheduled Pinned Locked Moved
    Firmware installation
    5
    30
    1.6k
    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.
    • bamundefined
      bam
      last edited by

      m409
      {"key":"","flags":"","result":{"boards":[{}],"directories":{},"fans":[],"heat":{},"inputs":[{},{},{},{},{},{},{},{},{},{},{},{}],"job":{},"limits":{},"move":{},"network":{},"sensors":{},"seqs":{},"spindles":[{},{}],"state":{},"tools":[],"volumes":[{}]}}
      12/31/2020, 11:18:40 PM Warning: 12V under-voltage event (9.4V)
      12/31/2020, 11:16:15 PM m98 p"config.g"
      12/31/2020, 11:16:03 PM m98 p "config.g"
      Error: M98: non-empty string expected
      12/31/2020, 11:15:53 PM m98 p config.g
      Error: M98: non-empty string expected
      12/31/2020, 11:15:42 PM m98 p
      Error: M98: non-empty string expected
      12/31/2020, 11:15:37 PM m98
      Error: M98: missing parameter 'P'
      12/31/2020, 11:14:50 PM Download of config.g successful after 0s
      12/31/2020, 11:14:08 PM M98 P"config.g"
      12/31/2020, 11:13:59 PM M98 P"config.g
      Error: Unterminated string
      12/31/2020, 11:13:35 PM M98 P"config.g
      Error: Unterminated string
      12/31/2020, 11:12:22 PM m115 b15
      Error: M115: Response timeout: CAN addr 15, req type 6024, RID=2
      12/31/2020, 11:12:22 PM Connection to Duet established
      12/31/2020, 11:12:22 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 11:12:05 PM m115 b126
      Error: M115: Response timeout: CAN addr 126, req type 6024, RID=1
      12/31/2020, 11:12:05 PM Connection to Duet established
      12/31/2020, 11:12:04 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 11:05:22 PM m115
      FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-05-19b2
      12/31/2020, 11:04:35 PM m451
      12/31/2020, 11:02:56 PM M952 b126 a1
      Error: M952: Response timeout: CAN addr 126, req type 2010, RID=0
      12/31/2020, 11:02:56 PM Connection to Duet established
      12/31/2020, 11:02:56 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 11:01:45 PM M954 b126
      Warning: M954: Command is not supported
      12/31/2020, 10:59:27 PM Connection to Duet established
      12/31/2020, 10:59:27 PM Warning: Lost connection to Duet (Board is not available (no header))
      12/31/2020, 10:57:43 PM M115 b126
      Error: M115: Response timeout: CAN addr 126, req type 6024, RID=2
      12/31/2020, 10:57:43 PM Connection to Duet established
      12/31/2020, 10:57:43 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 10:54:47 PM M115 b126
      Error: M115: Response timeout: CAN addr 126, req type 6024, RID=1
      12/31/2020, 10:54:46 PM Connection to Duet established
      12/31/2020, 10:54:46 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 10:53:57 PM Warning: 12V under-voltage event (9.5V)
      12/31/2020, 10:52:10 PM M115 b126
      Error: M115: Response timeout: CAN addr 126, req type 6024, RID=0
      12/31/2020, 10:52:10 PM Connection to Duet established
      12/31/2020, 10:52:10 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 10:50:06 PM M115
      FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-05-19b2
      12/31/2020, 10:49:46 PM Upload of Duet3Firmware_MB6HC.bin successful after 0s
      12/31/2020, 10:44:33 PM M115
      FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-05-19b2
      12/31/2020, 10:42:49 PM M115 B1
      Error: M115: Response timeout: CAN addr 1, req type 6024, RID=5
      12/31/2020, 10:42:49 PM Connection to Duet established
      12/31/2020, 10:42:48 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 10:42:44 PM M115 B123
      Error: M115: Response timeout: CAN addr 123, req type 6024, RID=4
      12/31/2020, 10:42:43 PM Connection to Duet established
      12/31/2020, 10:42:43 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 10:42:33 PM M115 B121
      Error: M115: Response timeout: CAN addr 121, req type 6024, RID=3
      12/31/2020, 10:42:33 PM Connection to Duet established
      12/31/2020, 10:42:32 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 10:42:21 PM M115 B122
      Error: M115: Response timeout: CAN addr 122, req type 6024, RID=2
      12/31/2020, 10:42:20 PM Connection to Duet established
      12/31/2020, 10:42:20 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 10:40:47 PM m954
      Warning: M954: Command is not supported
      12/31/2020, 10:40:24 PM m997 b1
      Error: M997: Response timeout: CAN addr 1, req type 6024, RID=1
      12/31/2020, 10:40:24 PM Connection to Duet established
      12/31/2020, 10:40:24 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 10:40:08 PM m954 b1
      Warning: M954: Command is not supported
      12/31/2020, 10:31:45 PM m954 b1
      Warning: M954: Command is not supported
      12/31/2020, 10:31:38 PM m954
      Warning: M954: Command is not supported
      12/31/2020, 10:26:56 PM m997 b1
      Error: M997: Response timeout: CAN addr 1, req type 6024, RID=0
      12/31/2020, 10:26:56 PM Connection to Duet established
      12/31/2020, 10:26:55 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      12/31/2020, 10:19:10 PM m575 p1b57600 s1
      12/31/2020, 10:18:08 PM M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
      Board ID: 08DJM-956BA-NA3TJ-6JTD2-3SN6K-9BAQU
      Used output buffers: 1 of 40 (10 max)
      === RTOS ===
      Static ram: 154604
      Dynamic ram: 161360 of which 20 recycled
      Exception stack ram used: 224
      Never used ram: 77008
      Tasks: NETWORK(ready,1980) HEAT(blocked,1416) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1460) TMC(blocked,204) MAIN(running,5128) IDLE(ready,76)
      Owned mutexes:
      === Platform ===
      Last reset 00:00:40 ago, cause: software
      Last software reset details not available
      Error status: 0
      MCU temperature: min 46.8, current 47.1, max 47.3
      Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0
      Driver 0: standstill, reads 1305, writes 11 timeouts 0, SG min/max 0/0
      Driver 1: standstill, reads 1306, writes 11 timeouts 0, SG min/max 0/0
      Driver 2: standstill, reads 1306, writes 11 timeouts 0, SG min/max 0/0
      Driver 3: standstill, reads 1307, writes 11 timeouts 0, SG min/max 0/0
      Driver 4: standstill, reads 1307, writes 11 timeouts 0, SG min/max 0/0
      Driver 5: standstill, reads 1308, writes 11 timeouts 0, SG min/max 0/0
      Date/time: 2020-12-31 22:18:06
      Slowest loop: 3.44ms; fastest: 0.14ms
      === Storage ===
      Free file entries: 10
      SD card 0 not detected, interface speed: 37.5MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
      Bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
      === AuxDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
      === Heat ===
      Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
      === GCodes ===
      Segments left: 0
      Movement lock held by null
      HTTP* is ready with "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 0, running macro
      Aux2 is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 1.08ms; fastest: 0.01ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
      HTTP sessions: 0 of 8

      • Ethernet -
        State: disabled
        Error counts: 0 0 0 0 0
        Socket states: 0 0 0 0 0 0 0 0
        === CAN ===
        Messages sent 0, longest wait 0ms for type 0
        === Linux interface ===
        State: 0, failed transfers: 0
        Last transfer: 17ms ago
        RX/TX seq numbers: 60298/1291
        SPI underruns 0, overruns 0
        Number of disconnects: 0
        Buffer RX/TX: 0/0-0
        === Duet Control Server ===
        Duet Control Server v3.1.1
        Daemon:
        Finishing macro daemon.g, started by system

      Next stack level
      Code buffer space: 4096
      Configured SPI speed: 8000000 Hz
      Full transfers per second: 32.20
      12/31/2020, 10:17:29 PM m997 b#
      12/31/2020, 10:16:35 PM m997
      12/31/2020, 9:54:11 PM Connected to duet3

      A Former User? 1 Reply Last reply Reply Quote 0
      • Vetiundefined
        Veti
        last edited by

        post your config.g

        also

        12/31/2020, 10:53:57 PM Warning: 12V under-voltage event (9.5V)

        it seems you have a problem with your power supply

        bamundefined 2 Replies Last reply Reply Quote 0
        • A Former User?
          A Former User @bam
          last edited by A Former User

          @bam said in cannot get 3hc to connect.:

          12/31/2020, 11:16:15 PM	m98 p"config.g"
          12/31/2020, 11:16:03 PM	m98 p "config.g"
          Error: M98: non-empty string expected
          12/31/2020, 11:15:53 PM	m98 p config.g
          Error: M98: non-empty string expected
          12/31/2020, 11:15:42 PM	m98 p
          Error: M98: non-empty string expected
          12/31/2020, 11:15:37 PM	m98
          Error: M98: missing parameter 'P'
          12/31/2020, 11:14:50 PM	Download of config.g successful after 0s
          12/31/2020, 11:14:08 PM	M98 P"config.g"
          12/31/2020, 11:13:59 PM	M98 P"config.g
          Error: Unterminated string
          12/31/2020, 11:13:35 PM	M98 P"config.g
          Error: Unterminated string
          

          btw the first one worked (as did the 3rd from the bottom); so no syntax or other errors in the config.g file (edit: at that time)

          1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators
            last edited by

            When the system has settled down, does the red LED on the 3HC flash in sync with the red LED on the main board, half a second pff and half a second on? If it doesn't then the CAN connection is missing.

            I suggest you update DSF and RRF to the 3.2RC2, or alternatively run the main board in standalone mode until you have established communication with the 3HC.

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

            bamundefined 2 Replies Last reply Reply Quote 0
            • bamundefined
              bam @Veti
              last edited by

              @Veti that happened when I flipped the switch off

              1 Reply Last reply Reply Quote 0
              • bamundefined
                bam @dc42
                last edited by

                @dc42 when I had the main board on 3.2 it wouldn’t talk to the DWC

                1 Reply Last reply Reply Quote 0
                • bamundefined
                  bam @dc42
                  last edited by

                  @dc42 4 flashes only on the 3hc

                  dc42undefined 1 Reply Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators @bam
                    last edited by

                    @bam said in cannot get 3hc to connect.:

                    @dc42 4 flashes only on the 3hc

                    Do you mean it flashes 4 times and then repeats, or something else?

                    What do you have the address switches set to?

                    Duet WiFi hardware designer and firmware engineer
                    Please do not ask me for Duet support via PM or email, use the forum
                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                    bamundefined 1 Reply Last reply Reply Quote 0
                    • dc42undefined
                      dc42 administrators
                      last edited by

                      PS - RRF 3.2 on the main board will need DSF 3.2 on the Pi to connect.

                      Duet WiFi hardware designer and firmware engineer
                      Please do not ask me for Duet support via PM or email, use the forum
                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                      1 Reply Last reply Reply Quote 0
                      • bamundefined
                        bam @dc42
                        last edited by

                        @dc42 4 flashes then it stops then 4 flashes. It’s asking for firmware update. I think.

                        1 Reply Last reply Reply Quote 0
                        • dc42undefined
                          dc42 administrators
                          last edited by

                          The error codes indicated by flashes are lisated at https://duet3d.dozuki.com/Wiki/CAN_connection#Section_LED_behaviour_and_error_codes. Normally you would see alternating 2 or 3 flashes (indicating no valid firmware installed followed by 4 flashes. Anyway, 4 flashes indicates that the main board didn't respond. This normally means that either the main board is not running, or the CAN connection is broken or mis-wired.

                          Duet WiFi hardware designer and firmware engineer
                          Please do not ask me for Duet support via PM or email, use the forum
                          http://www.escher3d.com, https://miscsolutions.wordpress.com

                          bamundefined 2 Replies Last reply Reply Quote 0
                          • bamundefined
                            bam @dc42
                            last edited by

                            @dc42 That’s probably the issue then because I am just using standard issue phone cord

                            dc42undefined 1 Reply Last reply Reply Quote 0
                            • bamundefined
                              bam @Veti
                              last edited by

                              @Veti ; Configuration file for Duet 3 (firmware version 3)
                              ; executed by the firmware on start-up
                              ;
                              ; generated by RepRapFirmware Configuration Tool v3.2.0 on Fri Jan 01 2021 12:00:51 GMT-0500 (Eastern Standard Time)

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

                              ; Drives
                              M569 P0.0 S1 ; physical drive 0.0 goes forwards
                              M569 P0.1 S1 ; physical drive 0.1 goes forwards
                              M569 P0.2 S0 ; physical drive 0.2 goes backwards
                              M569 P0.4 S1 ; physical drive 0.4 goes forwards
                              M569 P0.5 S1 ; physical drive 0.5 goes forwards
                              M569 P1.0 S1 ; physical drive 1.0 goes forwards
                              M569 P1.1 S1 ; physical drive 1.1 goes forwards
                              M584 X0.0 Y0.1 Z0.2 E0.4:0.5:1.0:1.1 ; set drive mapping
                              M350 X16 Y16 Z16 E16:16:16:16 I1 ; configure microstepping with interpolation
                              M92 X100.00 Y100.00 Z400.00 E100.00:100.00:100.00:100.00 ; set steps per mm
                              M566 X600.00 Y600.00 Z18.00 E300.00:300.00:300.00:300.00 ; set maximum instantaneous speed changes (mm/min)
                              M203 X6000.00 Y6000.00 Z180.00 E6000.00:6000.00:6000.00:6000.00 ; set maximum speeds (mm/min)
                              M201 X1500.00 Y1500.00 Z100.00 E10000.00:10000.00:10000.00:10000.00 ; set accelerations (mm/s^2)
                              M906 X500 Y500 Z500 E800:800:800:800 I30 ; set motor currents (mA) and motor idle factor in per cent
                              M84 S30 ; Set idle timeout

                              ; Axis Limits
                              M208 X-50 Y-10 Z0 S1 ; set axis minima
                              M208 X300 Y300 Z350 S0 ; set axis maxima

                              ; Endstops
                              M574 Z1 S3 ; configure sensorless endstop for low end on Z

                              ; Z-Probe
                              M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
                              M557 X20:200 Y20:200 S40 ; define mesh grid

                              ; Heaters
                              M308 S0 P"temp0" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 0 as thermistor on pin temp0
                              M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
                              M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
                              M140 H0 ; map heated bed to heater 0
                              M143 H0 S100 ; set temperature limit for heater 0 to 100C
                              M308 S1 P"1.temp0" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin 1.temp0
                              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 S300 ; set temperature limit for heater 1 to 300C
                              M308 S2 P"1.temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 2 as thermistor on pin 1.temp1
                              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 S300 ; set temperature limit for heater 2 to 300C

                              ; Fans
                              M950 F0 C"1.out3" Q500 ; create fan 0 on pin 1.out3 and set its frequency
                              M106 P0 S1 H1:2 T45 ; set fan 0 value. Thermostatic control is turned on
                              M950 F1 C"1.out4" Q500 ; create fan 1 on pin 1.out4 and set its frequency
                              M106 P1 S1 H1:2 T45 ; 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 tool

                              1 Reply Last reply Reply Quote 0
                              • bamundefined
                                bam @dc42
                                last edited by

                                @dc42 changed the can address switches on 3hc to 1, same as the config.g file. now we have a slow flash on the mb and a fast flash on the eb

                                bamundefined 1 Reply Last reply Reply Quote 0
                                • bamundefined
                                  bam @bam
                                  last edited by

                                  @bam fast flash is no connection to mb

                                  1 Reply Last reply Reply Quote 0
                                  • dc42undefined
                                    dc42 administrators @bam
                                    last edited by dc42

                                    @bam said in cannot get 3hc to connect.:

                                    @dc42 That’s probably the issue then because I am just using standard issue phone cord

                                    That should be OK if it is short and wired with the middle 2 pins straight through; however it may be wired crossed.

                                    @bam said in cannot get 3hc to connect.:

                                    @dc42 changed the can address switches on 3hc to 1, same as the config.g file. now we have a slow flash on the mb and a fast flash on the eb

                                    Thar suggests a problem with the CAN wiring.

                                    Duet WiFi hardware designer and firmware engineer
                                    Please do not ask me for Duet support via PM or email, use the forum
                                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                                    bamundefined 3 Replies Last reply Reply Quote 0
                                    • bamundefined
                                      bam
                                      last edited by

                                      TRhAWnAM.jpeg

                                      1 Reply Last reply Reply Quote 0
                                      • bamundefined
                                        bam @dc42
                                        last edited by

                                        @dc42 i just took a look and the wires are not crossed

                                        1 Reply Last reply Reply Quote 0
                                        • bamundefined
                                          bam
                                          last edited by

                                          m122
                                          === Diagnostics ===
                                          RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
                                          Board ID: 08DJM-956BA-NA3TJ-6JTD2-3SN6K-9BAQU
                                          Used output buffers: 1 of 40 (14 max)
                                          === RTOS ===
                                          Static ram: 154604
                                          Dynamic ram: 162320 of which 100 recycled
                                          Exception stack ram used: 272
                                          Never used ram: 75920
                                          Tasks: NETWORK(ready,1968) HEAT(blocked,476) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1436) TMC(blocked,192) MAIN(running,5056) IDLE(ready,76)
                                          Owned mutexes:
                                          === Platform ===
                                          Last reset 00:06:53 ago, cause: software
                                          Last software reset details not available
                                          Error status: 0
                                          MCU temperature: min 43.7, current 44.6, max 44.8
                                          Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
                                          12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
                                          Driver 0: standstill, reads 6854, writes 14 timeouts 0, SG min/max 0/0
                                          Driver 1: standstill, reads 6855, writes 14 timeouts 0, SG min/max 0/0
                                          Driver 2: standstill, reads 6855, writes 14 timeouts 0, SG min/max 0/0
                                          Driver 3: standstill, reads 6858, writes 11 timeouts 0, SG min/max 0/0
                                          Driver 4: standstill, reads 6856, writes 14 timeouts 0, SG min/max 0/0
                                          Driver 5: standstill, reads 6856, writes 14 timeouts 0, SG min/max 0/0
                                          Date/time: 2021-01-01 23:45:44
                                          Slowest loop: 2102.42ms; fastest: 0.14ms
                                          === Storage ===
                                          Free file entries: 10
                                          SD card 0 not detected, interface speed: 37.5MBytes/sec
                                          SD card longest read time 0.0ms, write time 0.0ms, max retries 0
                                          === Move ===
                                          Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
                                          Bed compensation in use: none, comp offset 0.000
                                          === MainDDARing ===
                                          Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                                          === AuxDDARing ===
                                          Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                                          === Heat ===
                                          Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
                                          === GCodes ===
                                          Segments left: 0
                                          Movement lock held by null
                                          HTTP* is ready with "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.
                                          === Network ===
                                          Slowest loop: 0.81ms; fastest: 0.01ms
                                          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
                                          HTTP sessions: 0 of 8

                                          • Ethernet -
                                            State: disabled
                                            Error counts: 0 0 0 0 0
                                            Socket states: 0 0 0 0 0 0 0 0
                                            === CAN ===
                                            Messages sent 1636, longest wait 0ms for type 0
                                            === Linux interface ===
                                            State: 0, failed transfers: 7
                                            Last transfer: 17ms ago
                                            RX/TX seq numbers: 46099/13071
                                            SPI underruns 7, overruns 7
                                            Number of disconnects: 0
                                            Buffer RX/TX: 0/0-0
                                            === Duet Control Server ===
                                            Duet Control Server v3.1.1
                                            Code buffer space: 4096
                                            Configured SPI speed: 8000000 Hz
                                            Full transfers per second: 1.17
                                            1/1/2021, 11:45:04 PM m115
                                            FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-05-19b2
                                          1 Reply Last reply Reply Quote 0
                                          • bamundefined
                                            bam @dc42
                                            last edited by

                                            @dc42 what does this mean?

                                            M32 "0:/gcodes/Duet3Firmware_EXP3HC.bin"
                                            Error: Unterminated string in line 3

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