• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login
  1. Home
  2. divvet
  • Profile
  • Following 0
  • Followers 0
  • Topics 3
  • Posts 10
  • Best 0
  • Controversial 0
  • Groups 0

divvet

@divvet

0
Reputation
1
Profile views
10
Posts
0
Followers
0
Following
Joined 24 Mar 2017, 09:28 Last Online 18 Aug 2018, 12:35

divvet Unfollow Follow

Latest posts made by divvet

  • RE: Duet Wifi interface suddenly stopped working

    I despair sometimes πŸ™‚ Don't know why but I just reset the board and now the web interface is working and my terminal output has gone back to normal. I have done this 100 times today, why this latest one was any different I don't know.

    Sorry to be a waste of time, don't have a clue what has happened πŸ™‚

    posted in General Discussion
    undefined
    divvet
    18 Aug 2018, 12:35
  • RE: Duet Wifi interface suddenly stopped working

    Just changed cable, as you can see YAT output is worse:

    serial: M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet WiFi 1.0 or 1.01
    Board ID: 08DAM-999TL-MQ4SD-6J1FA-3SJ6P-959MW
    Used output buffers: 1 of 20 (11 max)
    === RTOS ===
    Static ram: 28476
    Dynamic ram: 96236 of which 0 recycled
    Exception stack ram used: 380
    Never used ram: 5980
    Tasks: NETWORK(ready,548) HEAT(blocked,1248) MAIN(running,3484)
    Owned mutexes:
    === Platform ===
    Last reset 01:39:51 ago, cause: reset button or watchdog
    Last software reset at 2018-08-14 23:21, rWiFi: pr<DEL>Conn 0: free
    eason: User, spinning module GCodes, availWiFi: Conn 1: free
    able RAM 5656 bytes (slot 1)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0xffffffff
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interfWiFi: Conn 2: free
    ace speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 38.8, current 39.2, max 39.4
    Supply voltage: min 24.0, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0
    Driver 0: standstill, SG miWiFi: Conn 3: free
    WiFi: Conn 4: free
    n/max nWiFi: Conn 5: free
    ot 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
    Date/time: 1970-01-01 00:00:00
    Slowest loop: 1.0WiFi: Conn 6: free
    9ms; fastest: 0.08ms
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 14, completed moves: 14
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    ===WiFi: Conn 7: free
    WiFi: 
     Heat ===
    Bed heateWiFi: xmit: 0
    rs = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 1 is on, I-accum = 0.0
    === 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 inWiFi: recv: 0
     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: 166.77ms; fastest: 0.08ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) TelWiFi: fw: 0
    net(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.21
    WiFi MAC addresWiFi: drop: 0
    s 5c:cf:7f:2c:24:51
    WiFi Vcc 3.36, reset reason Turned on by main processor
    WiFi flash sWiFi: chkerr: 0
    ize 4194304, free heap 16384
    WiFi IP address 192.168.0.239
    WiFi signal strength -56dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    === Expansion ===
    ok
    WiFi: lenerr: 0
    WiFi: memerr: 0
    WiFi: rterr: 0
    WiFi: proterr: 0
    WiFi: opterr: 0
    WiFi: err: 0
    WiFi: cachehit: 0
    WiFi: 
    WiFi: xmit: 56
    WiFi: recv: 341
    WiFi: fw: 0
    WiFi: drop: 197
    WiFi: chkerr: 0
    WiFi: lenerr: 0
    WiFi: memerr: 0
    WiFi: rterr: 0
    WiFi: proterr: 197
    WiFi: opterr: 0
    WiFi: err: 0
    WiFi: cachehit: 355
    WiFi: 
    WiFi: xmit: 527
    WiFi: recv: 3203
    WiFi: fw: 0
    WiFi: drop: 1123
    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: 120
    WiFi: recv: 83
    WiFi: drop: 0
    WiFi: chkerr: 0
    WiFi: lenerr: 0
    WiFi: memerr: 0
    
    posted in General Discussion
    undefined
    divvet
    18 Aug 2018, 12:09
  • RE: Duet Wifi interface suddenly stopped working

    Apologies, I am currently connected by USB but did notice the output from YAT was jumbled up. I got the output from Repetier because I thought it had outputted correctly, on closer inspection I can see what you mean.

    This is another problem, why am I receiving garbled output? I will try another USB cable now.

    To answer your other questions, I am able to ping the Duet's IP, and the message I get is:

    Your Duet rejected the HTTP request: page not found

    edit: spelling

    posted in General Discussion
    undefined
    divvet
    18 Aug 2018, 12:06
  • Duet Wifi interface suddenly stopped working

    Hi there,

    I have been running my duet for months without issue, a couple of days ago I run a print fine, come to set up a print today but I am unable to connect to the wifi interface.

    Everything seems to be reporting fine on the duet, the m122 command shows :

    12:00:25.050 : === Diagnostics ===
    12:00:25.050 : RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet WiFi 1.0 or 1.01
    12:00:25.050 : Board ID: 08DAM-999TL-MQ4SD-6J1FA-3SJ6P-959MW
    12:00:25.050 : Used output buffers: 1 of 20 (11 max)
    12:00:25.050 : === RTOS ===
    12:00:25.050 : Static ram: 28476
    12:00:25.050 : Dynamic ram: 96236 of which 0WiFi: Conn 1: free
    12:00:25.050 : recycled
    12:00:25.050 : Exception stack ram used: 316
    12:00:25.050 : Never used ram: 6044
    12:00:25.050 : Tasks: NETWORK(ready,1112) HEAT(blocked,1248) MAIN(running,3484)
    12:00:25.050 : Owned mutexes:
    12:00:25.050 : === Platform ===
    12:00:25.050 : Last reset 00:32:49 ago, cause: reset button or watchdog
    12:00:25.050 : Last software reset at 2018-08-14 23:21, WiFi: Conn 2: free
    12:00:25.050 : reason: User, spinning module GCodes, available RAM 5656 bytes WiFi: Conn 3: free
    12:00:25.050 : (slot 1)
    12:00:25.050 : Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0xffffffff
    12:00:25.050 : Error status: 0
    12:00:25.050 : Free file entries: 9
    12:00:25.050 : SD card 0 detected, interfWiFi: Conn 4: free
    12:00:25.051 : WiFi: Conn 5: free
    12:00:25.051 : ace speed: 20.0MBytes/sec
    12:00:25.051 : SD card longest block write time: 0.0ms, max retries 0
    12:00:25.051 : MCU temperature: min 38.4, current 38.8, max 39.1
    12:00:25.051 : Supply voltage: min 24.0, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0
    12:00:25.052 : Driver 0: standstill, SG miWiFi: Conn 6: free
    12:00:25.052 : n/max not available
    12:00:25.052 : Driver 1: standstill, SG min/max not available
    12:00:25.052 : Driver 2: standstill, SG min/max not available
    12:00:25.052 : Driver 3: standstill, SG min/max not available
    12:00:25.052 : Driver 4: standstill, SG min/max not available
    12:00:25.052 : Date/time: 1970-01-01 00:00:00
    12:00:25.052 : Slowest loop: 20.WiFi: Conn 7: free
    12:00:25.052 : 06ms; fastest: 0.08ms
    12:00:25.052 : === WiFi:
    12:00:25.052 : Move ===
    12:00:25.052 : Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
    12:00:25.052 : Scheduled moves: 0, completed moves: 0
    12:00:25.052 : Bed compensation in use: none
    12:00:25.052 : Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    12:00:25.052 : === Heat ===
    12:00:25.052 : Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    12:00:25.052 : Heater 1 is on, I-accum =WiFi: xmit: 0
    12:00:25.052 : 0.0
    12:00:25.052 : === GCodes ===
    12:00:25.052 : Segments left: 0
    12:00:25.052 : Stack records: 1 allocated, 0 in use
    12:00:25.052 : Movement lock held by null
    12:00:25.052 : http is idle in state(s) 0
    12:00:25.052 : telnet is idle in state(s) 0
    12:00:25.052 : file is idle in WiFi: recv: 0
    12:00:25.053 : WiFi: fw: 0
    12:00:25.053 : state(s) 0
    12:00:25.053 : serial is ready with "M122" in state(s) 0
    12:00:25.053 : aux is idle in state(s) 0
    12:00:25.053 : daemon is idle in state(s) 0
    12:00:25.053 : queue is idle in state(s) 0
    12:00:25.053 : autopause is idle in state(s) 0
    12:00:25.053 : Code queue is empty.
    12:00:25.053 : === Network ===
    12:00:25.053 : Slowest loop: 167.18ms; fastest: 0.08ms
    12:00:25.053 : Responder sWiFi: drop: 0
    12:00:25.054 : tates: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    12:00:25.054 : HTTP sessions: 0 of 8
    12:00:25.054 : - WiFi -
    12:00:25.054 : Network state is running
    12:00:25.054 : WiFi module is connected to access point
    12:00:25.054 : Failed messages: pending 0, notready 0, noresp 0
    12:00:25.054 : WiFi firmware version 1.21
    12:00:25.054 : WiFi MAC addressWiFi: chkerr: 0
    12:00:25.054 : 5c:cf:7f:2c:24:51
    12:00:25.054 : WiFi Vcc 3.36, reset reason TWiFi: lenerr: 0
    12:00:25.054 : urned on by main processor
    12:00:25.054 : WiFi flash size 4194304, free heap 16792
    12:00:25.054 : WiFi IP address 192.168.0.239
    12:00:25.054 : WiFi signal strength -53dBm, reconnections 0, sleep mode modem
    12:00:25.054 : Socket states: 0 0 0 0 0 0 0 0
    12:00:25.054 : === Expansion ===
    12:00:25.054 : WiFi: memerr: 0
    12:00:25.054 : WiFi: rterr: 0
    12:00:25.054 : WiFi: proterr: 0
    12:00:25.055 : WiFi: opterr: 0
    12:00:25.055 : WiFi: err: 0
    12:00:25.056 : WiFi: cachehit: 0
    12:00:25.056 : WiFi:
    12:00:25.056 : WiFi: xmit: 31
    12:00:25.056 : WiFi: recv: 218
    12:00:25.056 : WiFi: fw: 0
    12:00:25.057 : WiFi: drop: 102
    12:00:25.057 : WiFi: chkerr: 0
    12:00:25.057 : WiFi: lenerr: 0
    12:00:25.057 : WiFi: memerr: 0
    12:00:25.058 : WiFi: rterr: 0
    12:00:25.058 : WiFi: proterr: 102
    12:00:25.058 : WiFi: opterr: 0
    12:00:25.058 : WiFi: err: 0
    12:00:25.059 : WiFi: cachehit: 116
    12:00:25.059 : WiFi:
    12:00:25.059 : WiFi: xmit: 204
    12:00:25.059 : WiFi: recv: 1777
    12:00:25.060 : WiFi: fw: 0
    12:00:25.060 : WiFi: drop: 592
    12:00:25.060 : WiFi: chkerr: 0
    12:00:25.060 : WiFi: lenerr: 0
    12:00:25.060 : WiFi: memerr: 0
    12:00:25.061 : WiFi: rterr: 0
    12:00:25.061 : WiFi: proterr: 0
    12:00:25.061 : WiFi: opterr: 0
    12:00:25.061 : WiFi: err: 0
    12:00:25.062 : WiFi: cachehit: 0
    12:00:25.062 : WiFi:
    12:00:25.062 : WiFi: xmit: 65
    12:00:25.062 : WiFi: recv: 48
    12:00:25.063 : WiFi: drop: 0
    12:00:25.063 : WiFi: chkerr: 0
    12:00:25.063 : WiFi: lenerr: 0
    12:00:25.063 : WiFi: memerr: 0
    

    Gone as far as erasing the board, and reinstalling all firmware to no affect.
    Turned all debugging on but I don't seem to get any reaction from the Duet when trying to connect to the web interface. I just get the following error from the web interface:

    This site can’t be reached
    192.168.0.239 refused to connect.

    However if I specify port 80 I still get an error in the webpage, but this time the debugging picks up the attempted connection and gives:

    12:31:45.580 : New conn on socket 1 for local port 80
    12:31:45.580 : HTTP connection accepted
    12:31:45.580 : Found responder
    12:31:45.580 : Received 179 bytes
    12:31:45.581 : Sending reply, file = no
    12:31:45.581 : Webserver: rejecting message with: 500 unexpected newline
    

    No other port seems to prompt a response.

    If anyone can help I would appreciate it. If I have missed out any useful information please say.

    posted in General Discussion
    undefined
    divvet
    18 Aug 2018, 11:33
  • RE: Unable to upload ANY files to Duet Wifi

    Don't know why, but the Duet seemed to take issue with my virtual access points. It connects fine but I got stupid delays after hitting connect, and the issue with the uploads.

    Just switched it to the main SSID of the router and everything works fine. Not ideally what I wanted to do, but sorts the issue for now.

    If this is of any concern to you at Duet then I can do any testing you want, otherwise forget I asked a question.

    Thanks for the help anyway πŸ™‚

    posted in General Discussion
    undefined
    divvet
    6 Nov 2017, 12:39
  • RE: Unable to upload ANY files to Duet Wifi

    Unfortunately that did not work either.

    posted in General Discussion
    undefined
    divvet
    6 Nov 2017, 12:34
  • RE: Unable to upload ANY files to Duet Wifi

    oh sorry already tried.

    chrome: error as described
    firefox: oddly wont actually load the duet wifi webpage
    edge: dont get any progress on the progress bar and then proceeds to error

    Also tried on 2 different machines with the same issues.

    The only thing I can think of changing recently is the wifi ssid (same network, closer ap as I was getting frequent connection losses).

    posted in General Discussion
    undefined
    divvet
    5 Nov 2017, 22:31
  • Unable to upload ANY files to Duet Wifi

    Hi there,

    Don't know why but suddenly I am unable to upload any files, gcode or firmware. when ever I attempt to the progress bar goes up a few percent (changes with different files), shows a transfer rate, but doesn't actually progress at all and eventually ends in an error.

    I have tried swapping the SD card,
    I have tried updating the firmware
    Currently running Firmware and Wifi version 1.19.2 and web interface 1.19.3
    Originally had issues with 1.19.

    If anyone can give me some help I would appreciate it.

    posted in General Discussion
    undefined
    divvet
    5 Nov 2017, 20:34
  • RE: IR Probe bought seperately

    brilliant, order placed thanks!!

    posted in Order discussion
    undefined
    divvet
    24 Mar 2017, 10:54
  • IR Probe bought seperately

    Hi there,

    Is it possible to purchase the IR Probe on its own as I need to replace a broken one?

    posted in Order discussion
    undefined
    divvet
    24 Mar 2017, 09:29
Unless otherwise noted, all forum content is licensed under CC-BY-SA