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

    1HCL connecting problems

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    2
    6
    171
    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.
    • semi55undefined
      semi55
      last edited by

      Hi everyone,

      I am having problems getting four 1HCL boards connected to a 6XD mainboard. I have given them individual adresses (1,2,3,4) as described in the wiki page but I cannot get them talking properly to the mainboard.

      When I ping them via M115 B# I get this back which seems fine:

      2.9.2024, 13:55:44: M115 B1: Duet EXP1HCL firmware version 3.4.0beta7+8 (2022-01-25 10:33:00)
      2.9.2024, 13:55:47: M115 B2: Duet EXP1HCL firmware version 3.4.0beta7+8 (2022-01-25 10:33:00)
      2.9.2024, 13:55:48: M115 B3: Duet EXP1HCL firmware version 3.4.0beta7+8 (2022-01-25 10:33:00)
      2.9.2024, 13:55:49: M115 B4: Duet EXP1HCL firmware version 3.4.0beta7+8 (2022-01-25 10:33:00)
      

      Running M98 P"config.g" gives:

      2.9.2024, 13:59:37 	CAN response timeout: board 1, req type 6060, RID 79
      Warning: Macro file config-override.g not found
      2.9.2024, 13:59:36 	Microstepping - X:16(on), Y:16(on), Z:16(on), U:16(on), E:16:16
      CAN response timeout: board 3, req type 6060, RID 78
      2.9.2024, 13:59:34 	M98 P"config.g"
      HTTP is enabled on port 80
      

      All boards are daisy chained and the last one is terminated with both jumpers mounted.
      I also tried just connecting the first board but that unfortunately doesn't help.

      This is the M122 output:

      2.9.2024, 14:04:27: Connected to 192.168.67.17
      2.9.2024, 14:04:32: m122: === Diagnostics ===
      RepRapFirmware for Duet 3 MB6XD version 3.5.1 (2024-04-19 14:39:48) running on Duet 3 MB6XD v1.01 or later (standalone mode)
      Board ID: 0JD2M-999AL-D25SW-6JKD2-3S06M-15ZV1
      Used output buffers: 1 of 40 (39 max)
      === RTOS ===
      Static ram: 153624
      Dynamic ram: 120024 of which 56 recycled
      Never used RAM 72288, free system stack 202 words
      Tasks: NETWORK(1,ready,38.6%,183) ETHERNET(5,nWait 7,0.7%,321) HEAT(3,nWait 6,0.0%,349) Move(4,nWait 6,0.0%,335) CanReceiv(6,nWait 1,0.0%,797) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,348) MAIN(1,running,60.3%,130) IDLE(0,ready,0.4%,30), total 100.0%
      Owned mutexes:
      === Platform ===
      Last reset 00:06:12 ago, cause: software
      Last software reset at 2024-09-02 13:58, reason: User, Gcodes spinning, available RAM 72288, slot 2
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      MCU temperature: min 42.6, current 42.8, max 43.1
      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.0, current 12.0, 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: ok
      Driver 1: ok
      Driver 2: ok
      Driver 3: ok
      Driver 4: ok
      Driver 5: ok
      Date/time: 2024-09-02 14:04:31
      Slowest loop: 14.15ms; fastest: 0.07ms
      === Storage ===
      Free file entries: 20
      SD card 0 detected, interface speed: 25.0MBytes/sec
      SD card longest read time 2.3ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
      no step interrupt scheduled
      Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
      === DDARing 0 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === DDARing 1 ===
      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
      === GCodes ===
      Movement locks held by null, null
      HTTP is idle 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
      File2 is idle in state(s) 0
      Queue2 is idle in state(s) 0
      Q0 segments left 0, axes/extruders owned 0x80000003
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === CAN ===
      Messages queued 102, received 360, lost 0, errs 0, boc 0
      Longest wait 0ms for reply type 0, peak Tx sync delay 4, free buffers 50 (min 50), ts 57/57/0
      Tx timeouts 0,0,0,0,0,0
      === Network ===
      Slowest loop: 10.22ms; fastest: 0.03ms
      Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
      HTTP sessions: 1 of 8
      = Ethernet =
      Interface state: active
      Error counts: 0 0 0 0 0 0
      Socket states: 5 2 2 2 2 0 0 0
      === Multicast handler ===
      Responder is inactive, messages received 0, responses 0
      
      

      Thanks in advance!

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @semi55
        last edited by

        @semi55 you need to update them to the same firmware as the 6XD

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        semi55undefined 2 Replies Last reply Reply Quote 0
        • semi55undefined
          semi55 @jay_s_uk
          last edited by

          @jay_s_uk Thank you very much for this incredibly swift reply. I will give this a try and come back with the result!

          1 Reply Last reply Reply Quote 1
          • semi55undefined
            semi55 @jay_s_uk
            last edited by

            @jay_s_uk I have updated the firmware of all four boards with M997 B# but i am getting the same error message unfortunately.
            The current firmware version of the 1HCL boards is version 3.4.4

            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
            • jay_s_ukundefined
              jay_s_uk @semi55
              last edited by

              @semi55 thats still old compared to your 6XD (so you'll still get the error).
              just upload this zip and let everything update https://github.com/Duet3D/RepRapFirmware/releases/download/3.5.2/Duet2and3Firmware-3.5.2.zip

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              semi55undefined 1 Reply Last reply Reply Quote 1
              • semi55undefined
                semi55 @jay_s_uk
                last edited by

                @jay_s_uk That worked perfectly, thank you very much!

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