Board doesnt respond

Veti

[Warning: Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.]

please change the line setting and repost

ezemaff

@Veti Sorry i dont understand.. what i have to change ?

ezemaff

@Veti i think you are talking about YAT SOFTWARE..

im right ?

droftarts

@ezemaff Yes, change the line ending in YAT, otherwise we can't see the WiFi report.

Send M98 P"config.g" and post the response. This should show errors in config.g. I can see you have defined tool T0 with fan F0, but you have defined fans F2 and F1, not F0.

What is not working for thermistors? You are using the default settings, which is probably not correct. If you are not getting a reading at all, check where you have plugged each thermistor in.

Ian

ezemaff

first.. thanks for all the help !!!

i fixed YAT !.

Second.. i repost the commands.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.2.2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-02-11
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MSD-6J9D8-3S46K-KSVMB
Used output buffers: 1 of 24 (16 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73228 of which 24 recycled
Never used RAM 15368, free system stack 183 words
Tasks: NETWORK(blocked,186) HEAT(blocked,308) MAIN(running,471) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 00:16:19 ago, cause: power up
Last software reset at 2021-02-24 13:35, reason: User, GCodes spinning, available RAM 15368, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 28.2, current 34.1, max 34.2
Supply voltage: min 0.0, current 0.3, max 0.5, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-02-24 14:11:41
Cache data hit count 1374503477
Slowest loop: 6.11ms; fastest: 0.13ms
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 2.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, 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, chamberHeaters = -1 -1 -1 -1
=== 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 ready with "M122" 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.38ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
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.25
WiFi MAC address ec:fa:bc:2d:e2:55
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25496
WiFi IP address 192.168.0.130
WiFi signal strength -43dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok

Third i leave you the M98 response

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
ok

ezemaff

Guys ... With this code I got it but on FAN2 because on FAN0 it doesn't work. Is there any chance that FAN0 has died?
Can i test it ?

; Fans
;M950 F0 C"fan0" Q500
;M106 P0 C"LAYER_FAN" S0 H-1
M950 F1 C"fan1" Q500
M106 P1 C"E3D_FAN" S0 H1:1 T35
M950 F2 C"fan2" Q500
M106 P2 C"FAN_LAYER" S0 H-1

; Tools
M563 P2 S"E3Dv6" D0 H1 F2
G10 P0 X0 Y0 Z0
G10 P0 R0 S0

droftarts

@ezemaff Possibly, but it's difficult to say with the information you have provided. You can blow the MOSFET by connecting the fan the wrong way around and applying power. See https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_fans#Section_Caution

Can you post a close up well lit photo of the area near the fan ports so we can see the small mosfets? Sometimes when they fail they will have visible damage. An example of blown MOSFETs: https://forum.duet3d.com/post/210694

Testing MOSFETs is quite difficult. If you want to test it, this thread has a good guide for testing the fan mosfet: https://forum.duet3d.com/topic/10027/duet-2-wifi-fan-pwm-0-shorted-dead-fuse-not-blown.

Ian

ezemaff

Mosfet looks good. But I will try to test.

ezemaff

It looked good ... but I turn on the dash and the TR9 blowup... I don't know why ... I want to cry ... So is there any chance to fix it?

droftarts

@ezemaff Are you sure the fan is wired the correct way around? Is it a particularly big fan? Is there exposed wiring that is shorting out? You can replace the MOSFETs, though it's quite fiddly to do, see https://duet3d.dozuki.com/Wiki/Connector_and_spare_part_numbers#Section_Fan_mosfet
If you can't do it yourself, there are people in the community that offer repairs, see https://forum.duet3d.com/topic/13875/community-repairs though this may depend on where you are in the world.

Ian

ezemaff

Hello everyone, first of all. Thanks for all the help and for your time. The wiring is ok, I tested it and now I am using another duet 2 wifi. I bought two at that time. And now everything seems to be going well. I didn't need to change a cable or something ... So I think the board was not right at first.

Now I want to fix it, but I need to ask you if all mosfet fans use PMV40UN2. I will change all three at once.

Thanks again!

On the current functional board (the good one) I have all the motors working fine, the mini infrared sensor too. I just need to calibrate.
Is there a video explaining how to do it (bed / motors / heaters / sensor ==> calibration)?

Blacksheep99

The Ender 3 Pro guides here: https://duet3d.dozuki.com/c/Duet_2_Maestro are very good for taking you through how to commission a printer. Obviously depending on your printer apply what is relevant but the core calibration stuff is for most instances.