Court-circuit
-
post a photo of your wiring between the duet and the duex
-
J'ai juste suivi les steps sur https://duet3d.dozuki.com/c/Getting_Started
M122 en Français et avec la traduction -
Can you change the line ending setting in YAT so we can see the full M122 report?
-
Comment je dois faire ? Désoler c'est la première fois que j'utilise une Duet
-
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N8PS4-6JKD8-3S06T-KBVRN
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93528 of which 0 recycled
Exception stack ram used: 244
Never used ram: 11588
Tasks: NETWORK(ready,1448) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,3816) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:00:33 ago, cause: power up
Last software reset at 2020-10-01 16:17, reason: User, spinning module GCodes, available RAM 11516 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
[ERROR] Error status: 0Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 21.1, current 24.6, max 24.8
Supply voltage: min 0.8, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Driver 5: ok, SG min/max not available
Driver 6: ok, SG min/max not available
Driver 7: ok, SG min/max not available
Driver 8: ok, SG min/max not available
Driver 9: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 106636381
Slowest loop: 1.07ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.48ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address f4:cf:a2:66:94:6a
WiFi Vcc 3.43, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26176
WiFi IP address 192.168.1.122
WiFi signal strength -41dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
En connection USB je n'est plus de court-circuit
-
@Veti said in Court-circuit:
post a photo of your wiring between the duet and the duex -
oui je post la photo des que je rentre in my home
-
Plus de court-circuit problème résolu merci beaucoup 1 fil était sorti du logement de la duex5
-
ok. but do adhere to the wiring as described in the guide. otherwise you will encounter more strange results.
