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

    3HC Error in config: Board 2 received unknown msg type 6042

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    4
    6
    214
    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.
    • mjimeygundefined
      mjimeyg
      last edited by

      I have a Duet3D 6HC connected to a 3HC via the CAN BUS.

      There are:

      • 1 x-axis motor
      • 1 y-axis motor
      • 3 z-axis motor
      • 2 Extruder Motors
      • 1 E3D Cyclops Hotend

      When turning on the printer or using the Emergency Stop or restart on changing the config.g I get the following errors:

      Error: M584: Board 2 received unknown msg type 6042
      Error: M906: Board 2 received unknown msg type 6043
      Error: M92: Board 2 received unknown msg type 6042
      Error: M350: Board 2 received unknown msg type 6042

      My config.g is below:

      ; Configuration file for Duet 3 (firmware version 3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v2.1.5 on Thu Jan 09 2020 15:44:47 GMT+0000 (Greenwich Mean Time)
      
      ; General preferences
      G90                                                   ; send absolute coordinates...
      M83                                                   ; ...but relative extruder moves
      M550 P"Cyclops"                                          ; set printer name
      
      
      M667 S1                                               ; select CoreXY mode
      
      ; 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 forwards ; Left
      M569 P0.3 S0					                      ; physical drive 0.3 goes forwards ; Rear
      M569 P0.4 S0                                          ; physical drive 0.4 goes forwards ; Right
      M569 P0.5 S1					                      ; physical drive 0.5 goes backwards
      M569 P2.0 S1					                      ; physical drive 1.0 goes backwards
      M584 X2.0 Y0.1 Z0.2:0.3:0.4	E0.5:0.0                                         ; set drive mapping
      M671 X-22.0:260.0:530 Y120.0:550.0:130.0 S15 	          ; Kinematic bed ball locations - front left, front right and rear center
      M350 X16 Y16 Z16 E16:16 I1                               ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z400.00 E409.00:409.00                     ; set steps per mm
      M566 X900.00 Y900.00 Z12.00 E120.00                   ; set maximum instantaneous speed changes (mm/min)
      M203 X6000.00 Y6000.00 Z1000.00 E1200.00              ; set maximum speeds (mm/min)
      M201 X500.00 Y500.00 Z20.00 E250.00                   ; set accelerations (mm/s^2)
      M906 X800 Y800 Z800 E1000:1000 I30                         ; set motor currents (mA) and motor idle factor in per cent
      M84 S30                                               ; Set idle timeout
      
      ; Axis Limits
      M208 X0 Y0 Z0 S1                                      ; set axis minima
      M208 X500 Y500 Z500 S0                                ; set axis maxima
      
      ; Endstops
      M574 X1 S3                                              ; configure sensorless endstop for low end on X
      M574 Y1 S3                                              ; configure sensorless endstop for low end on Y
      M574 Z1 S3                                              ; configure sensorless endstop for low end on Z
      
      ; Z-Probe
      ;M950 S0 C"io7.out"                                    ; create servo pin 0 for BLTouch
      M558 P8 H5 C"io6.in" F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
      ;M558 H30                                              ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
      G31 P50 Z3.19                              ; set Z probe trigger value, offset and trigger height
      M557 X35:475 Y15:475 S40                              ; define mesh grid
      
      ; Heaters
      M308 S0 P"temp0" Y"thermistor" A"Bed" T100000 B3950   ; 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
      M143 H0 S120                                          ; set temperature limit for heater 0 to 120C
      M307 H0 A436.5 C459.5 D4.1 S1.00 V0 B0                ; disable bang-bang mode for the bed heater and set PWM limit
      M140 H0                                               ; map heated bed to heater 0
      M308 S1 P"temp1" Y"thermistor" A"Hotend" T100000 B4725 C7.06e-8   ; configure sensor 1 as thermistor on pin temp1
      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 S280                                            ; set temperature limit for heater 1 to 280C
      
      ; Fans
      M950 F0 C"out7" Q500                                    ; create fan 0 on pin out7 and set its frequency
      M106 P0 S0 H-1                                          ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"out8" Q500                                    ; create fan 1 on pin out8 and set its frequency
      M106 P1 S1 H-1 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
      M563 P1 D1 H1 F0                                        ; define tool 0
      G10 P1 X0 Y0 Z0                                         ; set tool 0 axis offsets
      G10 P1 R0 S0                                            ; set initial tool 0 active and standby temperatures to 0C
      
      ; Custom settings are not defined
      
      ; Miscellaneous
                                                      ; load saved parameters from non-volatile memory
      M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"    ; set voltage thresholds and actions to run on power loss
      T0                                                    ; select first tool
      M501  
      
      

      When trying to update the 3HC firmware via the CAN using:

      M997 B2 S3;
      

      I get the following error message:

      Error: M997: Firmware file Duet3Bootloader-Board EXP3HC firmware 3.1.0 (2020- not found

      I have tried changing the address of the 3HC and switching the cable from in to out.

      I have tried changing the motor attached to the 3HC to the x-axis motor and the relevant config lines.

      Removing any reference to the 3HC connection from the lines reporting errors removes the errors.

      Help would be appreciated.

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Can you post the results of M122 and M122 B2?

        Z-Bot CoreXY Build | Thingiverse Profile

        mjimeygundefined 1 Reply Last reply Reply Quote 0
        • mjimeygundefined
          mjimeyg @Phaedrux
          last edited by

          @phaedrux

          M122;
          === Diagnostics ===
          RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (SBC mode)
          Board ID: 08DJM-956BA-NA3TJ-6JTD6-3S46R-TB8GS
          Used output buffers: 1 of 40 (12 max)
          === RTOS ===
          Static ram: 151000
          Dynamic ram: 66476 of which 20 recycled
          Never used RAM 133176, free system stack 219 words
          Tasks: SBC(ready,0.5%,478) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.7%,92) MAIN(running,91.4%,945) IDLE(ready,0.5%,30), total 100.0%
          Owned mutexes: HTTP(MAIN)
          === Platform ===
          Last reset 00:02:35 ago, cause: power up
          Last software reset at 2022-03-21 02:48, reason: User, none spinning, available RAM 133176, slot 2
          Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
          Error status: 0x00
          Step timer max interval 140
          MCU temperature: min 24.4, current 37.7, max 37.8
          Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
          12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
          Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
          Events: 0 queued, 0 completed
          Driver 0: standstill, SG min 0, mspos 8, reads 18357, writes 14 timeouts 0
          Driver 1: standstill, SG min 0, mspos 8, reads 18357, writes 14 timeouts 0
          Driver 2: standstill, SG min 0, mspos 8, reads 18357, writes 14 timeouts 0
          Driver 3: standstill, SG min 0, mspos 8, reads 18357, writes 14 timeouts 0
          Driver 4: standstill, SG min 0, mspos 8, reads 18358, writes 14 timeouts 0
          Driver 5: standstill, SG min 0, mspos 8, reads 18358, writes 14 timeouts 0
          Date/time: 2022-03-21 15:32:46
          Slowest loop: 1.26ms; fastest: 0.03ms
          === 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 ===
          DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
          === MainDDARing ===
          Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === AuxDDARing ===
          Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === Heat ===
          Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
          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 1308, received 6, lost 0, boc 0
          Longest wait 1ms for reply type 6042, peak Tx sync delay 51008, free buffers 50 (min 49), ts 779/778/0
          Tx timeouts 0,0,0,0,0,0
          === SBC interface ===
          Transfer state: 4, failed transfers: 0, checksum errors: 0
          RX/TX seq numbers: 5980/5980
          SPI underruns 0, overruns 0
          State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b880
          Buffer RX/TX: 0/0-0, open files: 0
          === Duet Control Server ===
          Duet Control Server v3.4.0
          Code buffer space: 4096
          Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
          Full transfers per second: 0.13, max time between full transfers: 105.1ms, max pin wait times: 49.9ms/9.9ms
          Codes per second: 0.00
          Maximum length of RX/TX data transfers: 3180/796
          
          M122 B2;
          Diagnostics for board 2:
          Board EXP3HC firmware 3.1.0 (2020-05-15b1)
          Never used RAM 163.6Kb, max stack 312b
          HEAT 1272 CanAsync 1452 CanRecv 1420 TMC 156 AIN 524 MAIN 2208
          Last reset 00:02:41 ago, cause: software
          Driver 0: standstill, reads 61127, writes 11 timeouts 0, SG min/max 0/0
          Driver 1: standstill, reads 61129, writes 11 timeouts 0, SG min/max 0/0
          Driver 2: standstill, reads 61132, writes 11 timeouts 0, SG min/max 0/0
          Moves scheduled 0, completed 0, hiccups 0
          VIN: 24.2V, V12: 12.3V
          MCU temperature: min 36.9C, current 37.1C, max 37.1C
          Ticks since heat task active 204, ADC conversions started 161448, completed 161447, timed out 0
          Last sensors broadcast 00000000 found 0 207 ticks ago
          Free CAN buffers: 36
          NVM user row de9a9239 aeecffb1 ffffffff ffffffff
          
          dc42undefined 1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators @mjimeyg
            last edited by

            @mjimeyg the problem is that your 3HC is still running firmware 3.1.0. Send M997 B2 to update it.

            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

            mjimeygundefined 1 Reply Last reply Reply Quote 1
            • mjimeygundefined
              mjimeyg @dc42
              last edited by

              @dc42 said in 3HC Error in config: Board 2 received unknown msg type 6042:

              @mjimeyg the problem is that your 3HC is still running firmware 3.1.0. Send M997 B2 to update it.

              That seems to have fixed it.

              I was following these instructions: Updating the bootloader on Duet 3 expansion and tool boards

              It specifically says to use the S3 parameter in the M997 command.

              Is there a different time to use it or is the instruction incorrect?

              Regardless, thank you for the aid and solution.

              Rushmere3Dundefined 1 Reply Last reply Reply Quote 0
              • Rushmere3Dundefined
                Rushmere3D @mjimeyg
                last edited by

                @mjimeyg Bootloader and firmware are two different things.

                Follow my adventures in 3D Printing, laser cutting and electronics. https://linktr.ee/Rushmere3D

                1 Reply Last reply Reply Quote 1
                • Phaedruxundefined Phaedrux marked this topic as a question
                • Phaedruxundefined Phaedrux has marked this topic as solved
                • First post
                  Last post
                Unless otherwise noted, all forum content is licensed under CC-BY-SA