Duet 2 WiFi - Config Issues or bad board? Belt Printer

KnightBelt

@jay_s_uk
Thanks, Panel now can control, though I lost my Z move option, as in it no longer shows on the panel Move menu. All other issues are still in place.
BTW - Fan jumper set to VIN

jay_s_uk

@KnightBelt can you post an output of M122 after an X move and the output of M98 P"config.g"

KnightBelt

@jay_s_uk

Here you go and thanks for the interest. I do not know was a bad grid definition is.....

M98 P"config.g"

HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Unknown pin name 'null'
Error: bad grid definition: X range too small
Tool 0: offsets X0.000 Y0.000 Z0.000

M122

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
Board ID: 0JD2M-9F8TA-GJ4TJ-6JTD4-3S06P-1QUL7
Used output buffers: 1 of 26 (18 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 74984 of which 0 recycled
Never used RAM 13188, free system stack 124 words
Tasks: NETWORK(ready,13.9%,242) HEAT(notifyWait,0.0%,317) Move(notifyWait,0.0%,274) MAIN(running,86.0%,462) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:27:33 ago, cause: power up
Last software reset at 2023-06-11 07:59, reason: User, GCodes spinning, available RAM 13332, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x08
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 26.9, current 38.5, max 39.1
Supply voltage: min 24.1, current 24.3, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 1 queued, 1 completed
Driver 0: phase A short to ground, standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2023-06-11 15:00:33
Cache data hit count 4294967295
Slowest loop: 8.07ms; fastest: 0.18ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 10.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 1463776ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 21, completed 21, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 4], 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, chamber heaters -1 -1 -1 -1, ordering errs 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 15.99ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address e8:68:e7:7f:6d:a6
WiFi Vcc 3.42, reset reason Power up
WiFi flash size 2097152, free heap 25024
WiFi IP address 192.168.137.224
WiFi signal strength -42dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

jay_s_uk

@KnightBelt if you're sure that each motor does the same when connected to X but work fine when connected to another driver then I would say that the X driver is damaged and would need to be replaced.

Theres also no need to null anything in your config so this line isn't needed

M574 Z1 S1 P"null"

Its also nil and not null

The always on fans get their voltage from here

so i would be checking that fuse again.

KnightBelt

@jay_s_uk

I do have the jumper set that way. See attached photos. I am very much leaning towards that there is a board problem. As some functions work just fine while others don't. I think it is time to start the RMA process. As there has been no other Aha!! moments.

Thanks for your help on this.

KnightBelt

Needing to get this addressed. How do I get an administrator or a moderator to engage on this thread?

jay_s_uk

@KnightBelt @Phaedrux

jay_s_uk

@KnightBelt btw, when and where was it purchased?

KnightBelt

@jay_s_uk
on 3DMakerWorld Inc. through Amazon Dec 15th, 2022. Came out of the box to this machine last month (May). I have contacted them and they are waiting for this process.

Phaedrux

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.

KnightBelt

@Phaedrux

Thank you for your quick response

droftarts

@KnightBelt I can see slivers of metal on some of the pictures, eg on the top of the main microcontroller, and something on one of the 3.3V regulator pins. I suggest you disconnect everything from the board, remove the board from its housing, and give it a thorough clean. Then reassemble, checking there is enough clearance behind the board that nothing is shorting out behind, and test each connection as you connect it, starting with the X stepper. You also seem to have bent/broken off some of the connector tabs?

Ian

KnightBelt

@droftarts

You definitely got my attention and got me out from behind my desk. Was hoping for that Aha moment. I just took the board and used canned air over a black piece of paper. What you see is white and red (it looks orange) shavings and possibly a hair. The board sits in a PLA+ tray (three parts, red, white, and orange as it is a long tray) that has a tendency to make these shavings that you see when I take out and put it in. The board is completely isolated, and the bottom rests on the PLA+ only on the edges with no contact on solder points. The items you pointed out are PLA+. I know the Duet is a solid product so I would be OK with the problem being between the chair and the keyboard. As long as I knew what it is and learn from it.

As for the connector tabs, nothing is broken, bent yes. Direct plugging a fan in bent them out a bit. They still lock a KK connector in.

Thank you for your help and for pointing out that I need to address this issue as I don't want plastic shavings everywhere.

droftarts

@KnightBelt These are the sorts of bits I saw:
Screenshot 2023-06-13 at 21.00.59.png
If they are just bits of plastic, then that shouldn't hurt, but some look a bit more metallic. If you've blown it off with compressed air and still no improvement, I'd say follow through on the warranty replacement.

In the picture of the back of the board, the light is shining on the soldered pins of the X driver, do they look properly soldered?

Ian

KnightBelt

@droftarts
From left to right the first two are Orange DuraMic PLA Plus and the third arrow is pointing to White Esun PLA+. Board is reinstalled. Taking it out (for a walk and cleaning) unfortunately did not solve the issue. Thanks again for pointing this out, without your keen eye and me blowing it on to a clean catch sheet I would have most likely not caught this.