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

    Issues with CAN bus on 6hc and 3hc / 1lc

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    3
    6
    390
    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.
    • bilschundefined
      bilsch
      last edited by

      Hello,

      I've been working on my build for a bit. I have the 6hc control board + a 1lc and 3hc connecting via can bus.

      Initially over usb on the bench I was getting general connectivity from the tool board, could read voltage and run a stepper. I was having some issues and shelved that for a bit - wanted to get everything mounted, cables run etc.

      I am now no longer seeing anything on the can bus. With only the 1lc ( and resistor in place on wire ) and the 6hc - no connectivity. Ditto with the 3hc ( only ) connected and with the jumpers on.

      Full output from M122.

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
      Board ID: 08DJM-9P63L-DJ3S0-7JTDA-3SS6N-KBLRB
      Used output buffers: 1 of 40 (11 max)
      === RTOS ===
      Static ram: 150904
      Dynamic ram: 62964 of which 24 recycled
      Never used RAM 140300, free system stack 200 words
      Tasks: SENSORS(delaying,0.0%,102) SBC(resourceWait:,5.4%,346) HEAT(delaying,0.0%,325) Move(notifyWait,0.0%,302) CanReceiv(notifyWait,0.0%,740) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.1%,93) MAIN(running,85.6%,967) IDLE(ready,1.8%,29), total 100.0%
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 00:11:06 ago, cause: reset button
      Last software reset at 2022-02-06 12:04, reason: User, none spinning, available RAM 140560, 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
      Aux0 errors 0,0,0
      Step timer max interval 681
      MCU temperature: min 37.5, current 39.0, max 48.0
      Supply voltage: min 0.3, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 0.1, 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
      Driver 0: position 0, standstill, reads 41610, writes 11 timeouts 0, SG min/max 0/0
      Driver 1: position 0, standstill, reads 41610, writes 11 timeouts 0, SG min/max 0/0
      Driver 2: position 0, standstill, reads 41610, writes 11 timeouts 0, SG min/max 0/0
      Driver 3: position 0, standstill, reads 41610, writes 11 timeouts 0, SG min/max 0/0
      Driver 4: position 0, standstill, reads 41611, writes 11 timeouts 0, SG min/max 0/0
      Driver 5: position 0, standstill, reads 41611, writes 11 timeouts 0, SG min/max 0/0
      Date/time: 2022-02-06 21:33:30
      Slowest loop: 0.46ms; fastest: 0.04ms
      === 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, maxWait 0ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 -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 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 8222, received 3, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 13363, free buffers 49 (min 48), ts 3333/3148/0
      Tx timeouts 0,0,184,13,0,94 last cancelled message type 30 dest 127
      
      === SBC interface ===
      State: 4, failed transfers: 0, checksum errors: 0
      Last transfer: 1ms ago
      RX/TX seq numbers: 17441/23552
      SPI underruns 0, overruns 0
      Disconnects: 2, timeouts: 0, IAP RAM available 0x2c83c
      Buffer RX/TX: 0/0-0
      === Duet Control Server ===
      Duet Control Server v3.3.0
      Code buffer space: 4096
      Configured SPI speed: 8000000Hz
      Full transfers per second: 35.61, max wait times: 2.8ms/0.0ms
      Codes per second: 0.00
      Maximum length of RX/TX data transfers: 3404/32
      

      All have been recently purchased ( last few months 😉 ). I'm able to move my x/y/z from the 6hc no problem. Read temps etc - just nothing on the boards via can bus.

      Error: M115: Response timeout: CAN addr 1, req type 6024, RID=14
      
      M409 K”boards”
      {
          "key": "",
          "flags": "",
          "result": {
              "boards": [
                  {},
                  {}
              ],
              "directories": {},
              "fans": [
                  null,
                  null,
                  {},
                  null,
                  {},
                  {},
                  null,
                  {}
              ],
              "global": {},
              "heat": {},
              "inputs": [
                  {},
                  {},
                  {},
                  {},
                  {},
                  {},
                  {},
                  {},
                  {},
                  {},
                  {},
                  {}
              ],
              "job": {},
              "limits": {},
              "move": {},
              "network": {},
              "sensors": {},
              "seqs": {},
              "spindles": [
                  {},
                  {}
              ],
              "state": {},
              "tools": [
                  {}
              ],
              "volumes": [
                  {}
              ]
          }
      }
      
      Alex.crundefined 1 Reply Last reply Reply Quote 0
      • Alex.crundefined
        Alex.cr @bilsch
        last edited by

        @bilsch
        So just to confirm, when you had it on the “bench” you had working CAN? Or you just had the main board running over USB power?

        When everything is powered up are the status LEDs on all three boards blinking in time with one another?

        How is the 1lc wired up? Is it the last board in the chain?
        Which revision of the 1lc did you purchase?

        Voron2.4/Duet3 SBC+6HC+3HC+1LC+1HCL(x2) - Delta/Duet2 Wifi - CubePro/Duet2 Wifi+Duex5 - Laser/Duet3 Mini5+ - Cel Robox - U̶p̶3̶0̶0̶+/D̶u̶e̶t̶3̶ ̶6̶H̶C̶+̶LC1̶ - F̶T̶-̶5̶/̶D̶u̶e̶t̶2̶ ̶W̶i̶f̶i̶ - S̶o̶l̶i̶d̶o̶o̶d̶l̶e̶

        bilschundefined 1 Reply Last reply Reply Quote 0
        • bilschundefined
          bilsch @Alex.cr
          last edited by

          @alex-cr When I was using it on the bench I was drawing from usb + I added a 12v to the 6hc and other boards ( could pull many amps if I needed but never did )

          I see on the 3hc or 1lc board a single blink followed shortly by 4 which I believe means its not happy about something 😉

          I found https://forum.duet3d.com/topic/17928/duet-3-expansion-3hc-v1-0-no-can-connection/3 which seems to show the same symptoms so going to read over that thread

          bilschundefined 1 Reply Last reply Reply Quote 0
          • bilschundefined
            bilsch @bilsch
            last edited by

            Ok, issue solved wow!

            So I probably missed it but getting the Duet2and3Firmware-3.3.zip and uploading it via the web interface put the firmware files in place. Once I followed the other forum article and got that hooked up - its working just fine! ( well, 3hc is still need to hit the 1lc )

            bilschundefined 1 Reply Last reply Reply Quote 1
            • bilschundefined
              bilsch @bilsch
              last edited by

              yea confirmed the tool board just loaded up 😉

              Ok, noted new flow! Sorry for the wild excursion there!

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

                @bilsch I'm glad you solved 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

                1 Reply Last reply Reply Quote 0
                • 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