Wep Page Disconnections



  • I am connected via ethernet on my new Duet board.
    I'm still printing at the mo but ive had no further disconnections since 14.09.

    Here is M122:

    14:58:28
    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet Ethernet 1.02 or later
    Board ID: 08DGM-917DA-G4MS4-6JKD6-3S46N-9TZBB
    Used output buffers: 1 of 20 (8 max)
    === RTOS ===
    Static ram: 25524
    Dynamic ram: 98472 of which 12 recycled
    Exception stack ram used: 512
    Never used ram: 6552
    Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,1692) IDLE(ready,200)
    Owned mutexes:
    === Platform ===
    Last reset 01:15:28 ago, cause: power up
    Last software reset at 2019-06-21 21:44, reason: User, spinning module GCodes, available RAM 6816 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 61.4ms, max retries 0
    MCU temperature: min 36.5, current 47.7, max 48.0
    Supply voltage: min 12.0, current 12.2, max 12.5, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max 0/179
    Driver 1: standstill, SG min/max 0/117
    Driver 2: standstill, SG min/max 0/141
    Driver 3: ok, SG min/max not available
    Driver 4: standstill, SG min/max 0/109
    Date/time: 2019-06-24 14:58:27
    Cache data hit count 4294967295
    Slowest loop: 12.23ms; fastest: 0.07ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 4, FreeDm: 163, MinFreeDm: 150, MaxWait: 299961ms, Underruns: 0, 0
    Scheduled moves: 73924, completed moves: 73894
    Bed compensation in use: none
    Bed probe heights: 0.044 0.070 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 0 is on, I-accum = 0.2
    Heater 1 is on, I-accum = 0.7
    === GCodes ===
    Segments left: 1
    Stack records: 5 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 doing "G1 X149.607 Y145.67" 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 ===
    Slowest loop: 61.94ms; fastest: 0.02ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8
    Interface state 5, link 100Mbps full duplex
    === Filament sensors ===
    Extruder 0 sensor: ok


  • administrators

    @chas2706 said in Wep Page Disconnections:

    ; Network
    M552 P192.168.1.6 ; Configure static IP address.

    Are you quite certain that nothing else uses that IP address? Your router might be assigning it to something else via DHCP. I suggest you check your router settings, to make sure that the pool of available DHCP addresses doesn't include 192.168.1.6. If it does, then move the Duet's IP address to be outside that range.



  • That sounds feasable. Nice one, I will check and change if necessary.



  • @chas2706 My Bad, I read tooo fast! Did not realise you have an ethernet now.



  • @PaulHew

    No problem, thanks for your input anyway.
    Im going with @dc42 's suggestion but can't look into it yet. Work is in the way!



  • @dc42 said in Wep Page Disconnections:

    @chas2706 said in Wep Page Disconnections:

    ; Network
    M552 P192.168.1.6 ; Configure static IP address.

    Are you quite certain that nothing else uses that IP address? Your router might be assigning it to something else via DHCP. I suggest you check your router settings, to make sure that the pool of available DHCP addresses doesn't include 192.168.1.6. If it does, then move the Duet's IP address to be outside that range.

    I think it's good practice to set a static IP for the Duet on the router itself.



  • Changed my static ip to 192.168.1.106 (definately not used by anything else) and here's what i get today:

    22:46:19
    Connection established!
    22:46:02
    Disconnected.
    22:45:50
    Connection established!
    22:45:31
    Disconnected.
    22:44:37
    Connection established!
    22:44:29
    Disconnected.
    22:43:16
    Connection established!
    22:42:57
    Disconnected.
    22:42:25
    Connection established!
    22:42:16
    Disconnected.
    22:41:33
    Connection established!
    22:41:04
    Disconnected.
    22:40:40
    Connection established!
    22:40:23
    Disconnected.
    22:39:39
    Connection established!
    22:39:21
    Disconnected.
    22:38:48
    Connection established!
    22:38:24
    Disconnected.
    22:38:05
    Connection established!
    22:37:38
    Disconnected.
    22:37:25
    Connection established!
    22:36:57
    Disconnected.
    22:36:23
    Connection established!
    22:35:55
    Disconnected.
    22:35:42
    Connection established!
    22:35:24
    Disconnected.
    22:34:41
    Connection established!
    22:34:33
    Disconnected.
    22:31:47
    Connection established!
    22:31:38
    Disconnected.
    22:31:04
    Connection established!
    22:30:46
    Disconnected.
    22:29:38
    Connection established!
    22:29:12
    Disconnected.
    22:27:43
    Connection established!
    22:20:15
    Page Load complete!



  • do you have an ethernet crossover cable?

    if so connect a laptop directly to the duet to rule out problems with the infrastructure.
    both need to be set up for static ip for it to work.



  • is the crossover cable required? i'm of the understanding the Duets does not support Auto MDI/MDX, but I thought it was enough for one of the two sides to support this, effectively rendering crossover cables a moot point since early 2000.



  • Sorry, I don't have a crossover cable and no such cable is mentioned in the Duet "get connected" pages.



  • if you computer supports auto mdi/mdx it will work with a normal ethernet cable


Log in to reply