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

Wifi Module keeps turning off and board wiping config.g file

Scheduled Pinned Locked Moved
Duet Hardware and wiring
2
5
851
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.
  • undefined
    Ckostikas
    last edited by 21 May 2018, 12:22

    Brand new board with config file from online configurator.

    Went through the guide and setup my wifi. Then went on my browser to boards page and started looking around(not changing anything). Suddenly the wifi was disconnected and the blue light on the board was off. Never came back not even after killing the power and on terminal by sending the screen command I would only receive "no PTY".

    After pressing the erase button and installing the firmware again everything looked fine except navigating to system tap which would give me a disconnect and loose the wifi again. Now in terminal i could send a "M552 S1" and reactivate wifi without having to kill power on the board.

    Next step connecting two motors, x and y, and testing the rotation of them. Cause I wanted to change the rotation went again into config.g and changed the S0 to S1. Board reseted fine and motors run the correct direction. During their run I lost the wifi again and after sending M552 S1 and going online I realised that config.g file is missing and my motors are going the wrong way again and joggering. Somewhere there I lost the wifi once more.

    After the erase of my board and bringing it back to life I managed to get a diagnosis test but it was the first ever run without motors or any changes.

    M122
    === Diagnostics ===
    Used output buffers: 3 of 32 (8 max)
    === Platform ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later + DueX5
    Board ID: 08DGM-956GU-DJ3SN-6J1FA-3SJ6L-KANMF
    Static ram used: 16152
    Dynamic ram used: 100448
    Recycled dynamic ram: 2184
    Stack ram used: 1224 current, 4528 maximum
    Never used ram: 7760
    Last reset 00:03:17 ago, cause: reset button or watchdog
    Last software reset at 2018-05-20 23:55, reason: User, spinning module GCodes, available RAM 7840 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms
    MCU temperature: min 36.5, current 38.3, max 38.8
    Supply voltage: min 24.4, current 24.5, max 24.7, under voltage events: 0, over voltage events: 0
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Driver 5: standstill, SG min/max not available
    Driver 6: standstill, SG min/max not available
    Driver 7: standstill, SG min/max not available
    Driver 8: standstill, SG min/max not available
    Driver 9: standstill, SG min/max not available
    Expansion motor(s) stall indication: no
    Date/time: 2018-05-21 12:18:48
    Slowest main loop (seconds): 0.049171; fastest: 0.000051
    === Move ===
    MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 0, completed moves: 0
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === 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 idle 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 ===
    Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 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.21RC4(08b3)
      WiFi MAC address 5c:cf:7f:76:70:2f
      WiFi Vcc 3.31, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 17024
      WiFi IP address 192.168.1.182
      WiFi signal strength -72dBm, reconnections 0, sleep mode modem
      Socket states: 0 2 0 0 0 0 0 0
      === Expansion ===
      DueX I2C errors 0

    Thanks!

    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by 21 May 2018, 15:05

      If the blue LED on the board (not the one on the WiFi module) was off, that means that VIN power was not present. That means either you have a bad connection in your power wiring, or something was shorting out or overloading the power supply. The first thing to check is that the VIN terminal block screws are tight. Also check that the underside of the Duet isn't shorting against anything metallic.

      Duet WiFi hardware designer and firmware engineer
      Please do not ask me for Duet support via PM or email, use the forum
      http://www.escher3d.com, https://miscsolutions.wordpress.com

      undefined 1 Reply Last reply 21 May 2018, 15:24 Reply Quote 0
      • undefined
        Ckostikas
        last edited by 21 May 2018, 15:12

        Sorry I meant the Blue one on the wifi module.

        I have no idea what's going on but I did a second erase and set up my wifi with M589 S"ccc" P"ccc" Inn.nn.nn.nn Cnn and seems to work without getting any disconnections.

        Can you see anything strange on my diagnosis report?

        1 Reply Last reply Reply Quote 0
        • undefined
          Ckostikas @dc42
          last edited by 21 May 2018, 15:24

          @dc42 Ok just found something weird.

          Safari (Mac) won't open the page every time were firefox will. When safari returns "page not found" firefox works like a charm

          1 Reply Last reply Reply Quote 0
          • undefined
            dc42 administrators
            last edited by 21 May 2018, 21:48

            Your WiFi signal strength is on the low side at -72dBm, and your WiFi server firmware is a release candidate version (1.21RC4), not the 1.21 release. Otherwise your diagnostic report looks OK to me.

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

            1 Reply Last reply Reply Quote 0
            2 out of 5
            • First post
              2/5
              Last post
            Unless otherwise noted, all forum content is licensed under CC-BY-SA