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

    Toolboard LC1 - IO1 failed?

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    2
    5
    303
    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.
    • Marshalundefined
      Marshal
      last edited by

      Hi all,

      i ran into issues today with the IO1 of a tool board
      It is not working anymore.

      IO1 was configured for an optical end stop

      M574 X1 S1 P"20.io1.in"
      

      and it was working for quite some time.

      As off today the sensors is showing as triggered when it is not.
      When connecting the sensor to IO2 and changing the configuration accordingly, the sensor is working fine.

      I checked the supply voltage on IO1, it is 3.3 V.
      The optical end stop has one led which is lit up when the sensor is not triggered.
      I tried to only connect V+ and GND, in this case the led is lit and triggers when triggering the sensor.

      Maybe there is a short on the signal line? Can i check this somehow?

      Without power

      • IO1.in to V+ is shorted on the tool board
      • IO2.in to V+ is not shorted on the tool board

      Thx in advance.

      Additional info:

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.4.0beta5 (2021-10-12 13:53:56) running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
      Board ID: 08DJM-956L2-G43S8-6J9D4-3SN6M-TU0UG
      Used output buffers: 1 of 40 (12 max)
      === RTOS ===
      Static ram: 151104
      Dynamic ram: 65740 of which 516 recycled
      Never used RAM 133312, free system stack 200 words
      Tasks: SBC(ready,0.4%,508) HEAT(notifyWait,0.0%,327) Move(notifyWait,0.0%,299) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,8.0%,92) MAIN(running,89.9%,921) IDLE(ready,1.6%,30), total 100.0%
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 00:02:30 ago, cause: power up
      Last software reset at 2021-11-03 15:19, reason: User, GCodes spinning, available RAM 133356, slot 2
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
      Error status: 0x00
      Step timer max interval 132
      MCU temperature: min 20.8, current 33.2, max 33.2
      Supply voltage: min 24.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
      Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
      Driver 0: pos 0, standstill, SG min/max 0/0, reads 54840, writes 14 timeouts 0
      Driver 1: pos 0, standstill, SG min/max 0/0, reads 54840, writes 14 timeouts 0
      Driver 2: pos 0, standstill, SG min/max 0/0, reads 54840, writes 14 timeouts 0
      Driver 3: pos 0, standstill, SG min/max 0/0, reads 54840, writes 14 timeouts 0
      Driver 4: pos 0, standstill, SG min/max 0/0, reads 54840, writes 14 timeouts 0
      Driver 5: pos 0, standstill, SG min/max 0/0, reads 54843, writes 11 timeouts 0
      Date/time: 2021-11-03 15:36:59
      Slowest loop: 1.27ms; 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, 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, chamberHeaters = -1 -1 -1 -1
      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 1285, received 2763, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 46, free buffers 49 (min 48), ts 754/753/0
      Tx timeouts 0,0,0,0,0,0
      === SBC interface ===
      State: 4, failed transfers: 1, checksum errors: 0
      Last transfer: 2ms ago
      RX/TX seq numbers: 4992/4992
      SPI underruns 0, overruns 0
      Disconnects: 0, timeouts: 0, IAP RAM available 0x2b7dc
      Buffer RX/TX: 0/0-0
      === Duet Control Server ===
      Duet Control Server v3.4-b5
      Code buffer space: 4096
      Configured SPI speed: 8000000Hz
      Full transfers per second: 4.19, max wait times: 28.8ms/5.3ms
      Codes per second: 0.04
      Maximum length of RX/TX data transfers: 2988/580
      
      m122 b20
      Diagnostics for board 20:
      Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.0beta5 (2021-10-12 13:59:06)
      Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
      Never used RAM 3612, free system stack 2789 words
      Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.3%,97) CanAsync(notifyWait,0.0%,60) CanRecv(notifyWait,0.0%,77) CanClock(notifyWait,0.0%,64) TMC(notifyWait,3.0%,57) MAIN(running,91.8%,348) IDLE(ready,0.0%,41) AIN(delaying,4.9%,142), total 100.0%
      Last reset 01:07:15 ago, cause: power up
      Last software reset time unknown, reason: AssertionFailed, available RAM 4592, slot 1
      Software reset code 0x0120 ICSR 0x00000000 SP 0x20003cac Task   Freestk 130 bad marker
      Stack: 00000544 00023174 00019cb5 20003044 00016e33 20003044 00016505 20000ed0 00000000 00000001 0000828d 200071c8 200071c8 200071e0 00000000 20000f50 000116b3 00022530 000225e8 00021c40 00019c55 200071c8 200071c8 20000f50 00008405 200071d8 000009c6
      Driver 0: pos 0, 419.2 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 22, reads 51870, writes 22, timeouts 0, DMA errors 0, steps req 0 done 0
      Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
      Peak sync jitter 4/9, peak Rx sync delay 215, resyncs 0/5, no step interrupt scheduled
      VIN voltage: min 23.0, current 24.3, max 24.3
      MCU temperature: min 35.8C, current 39.0C, max 41.3C
      Last sensors broadcast 0x00000002 found 1 240 ticks ago, loop time 0
      CAN messages queued 80639, send timeouts 0, received 36266, lost 0, free buffers 37, min 37, error reg 150000
      dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
      Accelerometer detected: no
      I2C bus errors 4509, naks 4509, other errors 4509
      

      In Progress CoreXY:

      • Duet3 6HC
      • 1 Toolboard LC1
      alankilianundefined 2 Replies Last reply Reply Quote 0
      • alankilianundefined
        alankilian @Marshal
        last edited by alankilian

        @marshal

        The inputs on the toolboard are "Pulled-up" to 3.3 Volts and that is why you are reading 3.3 Volts on the pin when it's disconnected.

        Capture.png

        Try using a jumper to connect the IO pin to a ground pin and see if you can configure and read the state of the pin changing.

        Also, is there something going wrong with your toolboard? (I'm unfamiliar with these boards, sorry.)

        Last software reset time unknown, reason: AssertionFailed, available RAM 4592, slot 1
        
        Software reset code 0x0120 ICSR 0x00000000 SP 0x20003cac Task  Freestk 130 bad marker
        
        I2C bus errors 4509, naks 4509, other errors 4509
        

        SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

        1 Reply Last reply Reply Quote 0
        • alankilianundefined
          alankilian @Marshal
          last edited by

          Without power

          • IO1.in to V+ is shorted on the tool board
          • IO2.in to V+ is not shorted on the tool board

          I also see that IO2 is NOT connected to 3.3 Volts, but rather connected to 5 Volts.
          Capture.png

          Do you have both power LEDs lit when the board is turned on?
          Capture1.png

          SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

          Marshalundefined 1 Reply Last reply Reply Quote 0
          • Marshalundefined
            Marshal @alankilian
            last edited by

            @alankilian

            THX for the input, especially jumping the connector.

            With

            M409 K"endstops.sensors"
            

            I observed the input working.

            I changed my config.g from

            M574 X1 S1 P"20.io1.in" # old
            M574 X1 S1 P"^20.io1.in" # new
            

            to activate the pull up resistor.
            Like this its back working.

            Probably I have messed the line up, can't explain when or why though ...

            Thx

            In Progress CoreXY:

            • Duet3 6HC
            • 1 Toolboard LC1
            alankilianundefined 1 Reply Last reply Reply Quote 1
            • alankilianundefined
              alankilian @Marshal
              last edited by

              @marshal

              GREAT!

              I'm glad you're running again.

              SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

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