IO_4 not working
-
I don't immediately see anything wrong with the config.
Can you provide the results of M122 and M98 P"config.g" when configured to use io4?
What type of endstop is it and how was it wired?
Can you post a photo of the io4 port front and back so that we may see the soldering?
When did you purchase from E3D?
-
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (standalone mode) Board ID: 08DJM-956BA-NA3TN-6JKDL-3SN6N-9986U Used output buffers: 3 of 40 (11 max) === RTOS === Static ram: 149788 Dynamic ram: 92948 of which 24 recycled Never used RAM 116072, free system stack 200 words Tasks: NETWORK(ready,183) ETHERNET(blocked,119) HEAT(blocked,300) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,51) MAIN(running,1119) IDLE(ready,19) Owned mutexes: === Platform === Last reset 00:00:23 ago, cause: software Last software reset at 2021-06-18 20:58, reason: User, GCodes spinning, available RAM 116072, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 41.6, current 42.6, max 42.7 Supply voltage: min 24.4, current 24.5, max 24.5, 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 Driver 0: position 0, standstill, reads 65315, writes 14 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 65316, writes 14 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 65316, writes 14 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 65316, writes 14 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 65319, writes 11 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 65319, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2021-06-18 20:59:00 Slowest loop: 4.08ms; fastest: 0.05ms === Storage === Free file entries: 10 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, 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 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by 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 Code queue is empty. === Network === Slowest loop: 6.21ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 1 of 8 - Ethernet - State: active Error counts: 0 0 1 0 0 Socket states: 5 2 2 2 2 2 0 0 === CAN === Messages queued 92, send timeouts 206, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48M98 P"config.g" HTTP is enabled on port 80 FTP is enabled on port 21 TELNET is disabled Warning: Macro file config-override.g not found
This board was a gift for christmas and due to the cancelled flights from London to Poland as a result of the lockdown restrictions I have just received it now. It was bought on 07.12.2020 and I received on 11.06.2021 when the flights resumed.
I forgot to write in post that after I received it I was not able to boot it so I reflushed the frimware as stated in documentation on Duet website.
-
Your photo shows the wire connected to io1, not io4.
-
I know I unpluged it to show the headers and soldered components
-
Ok, just making sure. It happens sometimes.
Can you get a better photo? It's so small I can't actually make anything out in detail.
-
live test: https://youtu.be/8r-NbxDijDw
-
-
-
Thanks. It's rather unusual for a port to fail like that.
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
Sorry for the inconvenience.
-
@phaedrux THX for your help It was pleasure to talk to you
