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

    Court-circuit

    Scheduled Pinned Locked Moved Solved
    Firmware installation
    3
    18
    632
    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.
    • Vetiundefined
      Veti
      last edited by

      please post the output of m122

      check that your wiring is like described here
      https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring
      observe the important notes there.

      @chris974M said in Court-circuit:

      M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin
      M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp

      your themistor set it incorrect. B4138 is the default and wrong for your setup. you need to look up your specific thermistor settings

      1 Reply Last reply Reply Quote 0
      • chris974Mundefined
        chris974M
        last edited by

        m122
        1 ms, nombre maximal de tentatives 0 Température MCU: min 33,3, courant 33,6, max 33,8 Tension d'alimentation: min 24,1, courant 24,2, max 24,4, événements de sous-tension: 0, événements de surtension: 0, alimentation bonne: oui Driver 0: arrêt, SG min / max non disponible Pilote 1: à l'arrêt, SG min / max non disponible Pilote 2: à l'arrêt, SG min / max non disponible Pilote 3: à l'arrêt, SG min / max non disponible Pilote 4: à l'arrêt, SG min / max non disponible Pilote 5: arrêt de température! arrêt court-à-terre, SG min / max non disponible Driver 6: arrêt température! arrêt court-à-terre, SG min / max non disponible Driver 7: arrêt température! arrêt court au sol, SG min / max non disponible Driver 8: arrêt température! arrêt court-à-terre, SG min / max non disponible Driver 9: arrêt température! arrêt court au sol, SG min / max non disponible Date / heure: 2020-10-01 17:46:03 Nombre de succès des données du cache 2452080743 Boucle la plus lente: 12,45 ms; plus rapide: 0.07ms I2C nak erreurs 0, envoi des délais 0, réception des délais 0, finishTimeouts 0, réinitialisation 0 === Déplacer === Hoquet: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms Compensation de lit en cours d'utilisation: aucune , Comp offset 0,000 === DDARing === Mouvements programmés: 0, coups terminés: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Chauffe-lits = 0 -1 -1 - 1, ChamberHeaters = -1 -1 === GCodes === Segments à gauche: 0 Enregistrements de pile: 1 alloué, 0 en cours d'utilisation Verrou de mouvement maintenu par null http est inactif dans l'état (s) 0 telnet est inactif dans l'état (s) 0 fichier est inactif dans l'état (s) 0 série est inactif dans l'état (s) 0 aux est inactif dans l'état (s) 0 démon est inactif dans l'état (s) 0 file d'attente est inactif dans l'état (s) 0 autopause est inactif dans état (s) 0 La file d'attente de codes est vide. === Réseau === Boucle la plus lente: 200,58 ms; le plus rapide: 0.

        1 Reply Last reply Reply Quote 0
        • Vetiundefined
          Veti
          last edited by

          thats not how a console output looks like.

          are you connecting via usb? if so please observe https://duet3d.dozuki.com/Wiki/USB_ground_loops

          1 Reply Last reply Reply Quote 0
          • chris974Mundefined
            chris974M
            last edited by

            Non j'utilise en wifi

            1 Reply Last reply Reply Quote 0
            • Vetiundefined
              Veti
              last edited by

              i am a bit confused. how are you getting french output from M122?
              i dont see an option to change the language of the duet firmware.

              1 Reply Last reply Reply Quote 0
              • Vetiundefined
                Veti
                last edited by

                post a photo of your wiring between the duet and the duex

                1 Reply Last reply Reply Quote 0
                • chris974Mundefined
                  chris974M
                  last edited by

                  J'ai juste suivi les steps sur https://duet3d.dozuki.com/c/Getting_Started
                  M122 en Français et avec la traduction

                  1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined
                    Phaedrux Moderator
                    last edited by

                    Can you change the line ending setting in YAT so we can see the full M122 report?

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • chris974Mundefined
                      chris974M
                      last edited by

                      Comment je dois faire ? Désoler c'est la première fois que j'utilise une Duet

                      1 Reply Last reply Reply Quote 0
                      • chris974Mundefined
                        chris974M
                        last edited by

                        === 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: 0

                        Free 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
                        1 Reply Last reply Reply Quote 0
                        • chris974Mundefined
                          chris974M
                          last edited by

                          En connection USB je n'est plus de court-circuit

                          1 Reply Last reply Reply Quote 0
                          • Vetiundefined
                            Veti
                            last edited by

                            @Veti said in Court-circuit:
                            post a photo of your wiring between the duet and the duex

                            1 Reply Last reply Reply Quote 0
                            • chris974Mundefined
                              chris974M
                              last edited by

                              oui je post la photo des que je rentre in my home

                              1 Reply Last reply Reply Quote 0
                              • chris974Mundefined
                                chris974M
                                last edited by

                                Plus de court-circuit problème résolu merci beaucoup 1 fil était sorti du logement de la duex5

                                1 Reply Last reply Reply Quote 1
                                • Vetiundefined
                                  Veti
                                  last edited by

                                  ok. but do adhere to the wiring as described in the guide. otherwise you will encounter more strange results.

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