RRF 1.21 WiFi now failing, didn't before



  • Just started getting WiFi problems. Been using this machine for months with no WiFi issues at all and nothing else has changed. In the last hour it's failed twice with DWC reporting "Communication Error" and "Syntax Error: Unexpected end of JSON Input".

    The Javascript console says:

    Error! The following JSON response could not be parsed:
    dwc.js:417 {"status":"P","coords":{"axesHomed":[1,1,1],"xyz":[3.500,3.243,10.400],"machine":[0.175,1.682,10.400],"extr":[640.4]},"currentTool":0,"params":{"atxPower":0,"fanPercent":[80.86,100.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00],"speedFactor":100.00,"extrFactors":[100.00],"babystep":0.000},"seq":5998,"sensors":{"probeValue":0,"fanRPM":0},"temps":{"bed":{"current":21.1,"active":0.0,"state":2,"heater":0},"current":[21.1,190.0,2000.0,2000.0,2000.0,2000.0,2000.0,2000.0],"state":[2,2,0,0,0,0,0,0],"heads":{"current":[190.0],"active":[190.0],"standby":[190.0],"state":[2]},"tools":{"active":[[190.0]],"standby":[[190.0]]},"extra":[{"name":"MCU","temp":31.3}]},"time":7113.0,"spindle":{"current":0,"active":0},"coldExtrudeTemp":160,"coldRetractTemp":90,"tempLimit":290,"endstops":4088,"firmwareName":"RepRapFirmware for Duet 2 WiFi/Ethernet","geometry":"delta","axes":3,"axisNames":"XYZ","volumes":2,"mountedVolumes":1,"name":"Kossel Mini","probe":{"threshold":500,"height":0.00,"type":0},"tools":[{"number":0,"name":"","heaters":[1],"

    After it failed, the IP address is still pingable but DWC cannot connect, I guess the web server has crashed.

    How can I get more info as to what's happened?



  • Ah, just discovered, I can reload the web page OK but it won't connect, just keeps failing with the error mentioned above. Only recourse is to power cycle the Duet.


  • administrators

    Please check that you are running version 1.21 of both the main firmware and the wifi firmware. M122 will report both versions. So will DWC on the Settings->General page if it stays connected for long enough.



  • I should also say that when it fails during a print, the print keeps going happily to the end.

    === Diagnostics ===
    Used output buffers: 19 of 32 (23 max)
    === Platform ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
    Board ID: 08D6M-91AST-L2MS0-6J9F6-3SJ6K-1NDTL
    Static ram used: 16152
    Dynamic ram used: 100568
    Recycled dynamic ram: 2064
    Stack ram used: 1224 current, 6632 maximum
    Never used ram: 5656
    Last reset 01:03:40 ago, cause: power up
    Last software reset at 2018-02-19 09:28, reason: User, spinning module GCodes, available RAM 3840 bytes (slot 1)
    Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, 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 30.6, current 31.1, max 36.2
    Supply voltage: min 12.2, current 12.4, max 12.6, under voltage events: 0, over voltage events: 0
    Driver 0: standstill, SG min/max 0/312
    Driver 1: standstill, SG min/max 0/1023
    Driver 2: standstill, SG min/max 0/294
    Driver 3: standstill, SG min/max 0/1023
    Driver 4: standstill, SG min/max not available
    Date/time: 2018-03-23 15:38:38
    Slowest main loop (seconds): 0.041617; fastest: 0.000046
    === Move ===
    MaxReps: 4, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 120, MaxWait: 3679443528ms, 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
    Heater 0 is on, I-accum = 0.0
    Heater 1 is on, I-accum = 0.6
    === 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.21
    WiFi MAC address 5c:cf:7f:f8:24:5e
    WiFi Vcc 3.38, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 17024
    WiFi IP address 192.168.1.108
    WiFi signal strength -49dBm, reconnections 0, sleep mode modem
    Socket states: 2 0 0 0 0 0 0 0
    
    

  • administrators

    Thanks. You can get more info by connecting a PC running YAT, pronterface or similar via USB to the Duet and sending M111 S1 P14. This enables wifi debugging so that significant WiFi events will send a message over USB. Also, when you send M122, the status of the wifi connections will also be sent to USB.



  • Thanks, I will try and get some more info when it next occurs.



  • It failed again, M122 on the USB says:

    === Diagnostics ===
    Used output buffers: 30 of 32 (32 max)
    === Platform ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
    Board ID: 08D6M-91AST-L2MS0-6J9F6-3SJ6K-1NDTL
    Static ram used: 16152
    Dynamic ram used: 10064WiFi: memerr:Conn 0: free
    0
    Recycled dynamic ram: 1992
    Stack ram used: 3576 current, 6632 maximum
    Never used ram: 5656
    Last reset 02:00:11 ago, cause: power up
    Last software reset at 2018-02-19 09:28, reason: User, spinning module GCodes, available RAM 3840 bytes (slot 1)
    Software WiFi: Conn 1: free
    reset code 0x0003 WiFi: Conn 2: free
    HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
    Error status: 4
    [ERROR] Error status: 4
    
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms
    MCU temperature: min 30.6,WiFi: Conn 3: free
    WiFi: Conn 4: free
    WiFi: Conn 5: free
    WiFi: Conn 6: free
    WiFi: Conn 7: free
    WiFi:
    WiFi: xmit: 0
    WiFi: recv: 0
    WiFi: fw: 0
    WiFi: drop: 0
    WiFi: chkerr: 0
    WiFi: lenerr: 0
    WiFi: memerr: 0
    WiFi: rterr: 0
    WiFi: proterr: 0
    WiFi: opterr: 0
    WiFi: err: 0
    WiFi: cachehit: 0
    WiFi:
    WiFi: xmit: 26
    WiFi: recv: 355
    WiFi: fw: 0
    WiFi: drop: 1135
    WiFi: chkerr: 0
    WiFi: lenerr: 0
    WiFi: memerr: 0
    WiFi: rterr: 0
    WiFi: proterr: 1135
    WiFi: opterr: 0
    WiFi: err: 0
    WiFi: cachehit: 39733
    WiFi:
    WiFi: xmit: 39768
    WiFi: recv: 63982
    WiFi: fw: 0
    WiFi: drop: 463
    WiFi: chkerr: 0
    WiFi: lenerr: 0
    WiFi: memerr: 0
    WiFi: rterr: 0
    WiFi: proterr: 0
    WiFi: opterr: 0
    WiFi: err: 0
    WiFi: cachehit: 0
    WiFi:
    WiFi: xmit: 25
    WiFi: recv: 393
    WiFi: drop: 0
    WiFi: chkerr: 0
    WiFi: lenerr: 0
    
    

  • administrators

    When it failed, and before you ran M122, did you get any messages beginning "WiFi:" received over USB?



  • No, I don't think so. I will use it some more over the weekend and report back if I get any messages.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.