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

    Duet Roto Toolboard Timeout

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    2
    3
    132
    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.
    • ofliduetundefined
      ofliduet
      last edited by

      I've just started to wire in my new Roto Toolboard. I connected the x-probe on the toolboard the same way I had it on the LC1 that it is replacing. But when I configure the input I get a timeout.

      M574 X1 S1 P"21.io1.in"
      CAN response timeout: board 21, req type 6060, RID 26
      

      The board does respond to status requests and the lights are flashign in sync, although it seems slightly out of phase with the motherboard. The main and tool boards are wired to the same power supply. In fact the toolboard is wired to the same terminals the LC1 was using before, which was working fine.

      The only other thing I have changed is the firmware on the motherboard. It was 3.2 with the LC1 and is now 3.5-rc3 with the RR.

      Any ideas what might be causing the timeout? Status repsponse from the toolboard below

      M122 B21
      Diagnostics for board 21:
      Duet TOOL1RR firmware version 3.5.0-rc.1+ (2023-11-17 12:25:22)
      Bootloader ID: SAME5x bootloader version 2.9 (2023-10-06)
      All averaging filters OK
      Never used RAM 165332, free system stack 192 words
      Tasks: Move(3,nWait,0.0%,182) HEAT(2,nWait,0.1%,102) CanAsync(5,nWait,0.0%,67) CanRecv(3,nWait,0.0%,80) CanClock(5,nWait,0.0%,70) ACCEL(3,nWait,0.0%,68) TMC(2,nWait,1.1%,60) MAIN(1,running,93.6%,306) IDLE(0,ready,0.0%,29) AIN(2,nWait,5.2%,231), total 100.0%
      Last reset 00:31:20 ago, cause: software
      Last software reset data not available
      Driver 0: pos 0, 507.0 steps/mm, standstill, SG min 0, temp 35.3C, read errors 0, write errors 0, ifcnt 45, reads 46489, writes 0, timeouts 0, DMA errors 0, steps req 0 done 0
      Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
      Peak sync jitter -2/11, peak Rx sync delay 185, resyncs 0/0, no timer interrupt scheduled
      VIN voltage: min 24.2, current 24.2, max 24.2
      MCU temperature: min 32.2C, current 32.6C, max 32.6C
      Last sensors broadcast 0x00000002 found 1 9 ticks ago, 0 ordering errs, loop time 0
      CAN messages queued 20238, send timeouts 0, received 9104, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
      dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
      Accelerometer: LIS2DW, status: 00
      Inductive sensor: raw value 268435455, frequency 25.00MHz, current setting 13, ok
      I2C bus errors 0, naks 0, contentions 0, other errors 0
      
      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @ofliduet
        last edited by

        @ofliduet you need 3.5-rc3 on the toolboard too as there have been same changes to CAN messages

        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

        ofliduetundefined 1 Reply Last reply Reply Quote 2
        • ofliduetundefined
          ofliduet @jay_s_uk
          last edited by

          @jay_s_uk This did indeed solve the problem. Well spotted!

          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