Wep Page Disconnections



  • Hi folks,

    I originally purchased a chinese clone duet wifi almost a year ago and had nothing but constant wifi disconnections. I looked on the forum for answers and tried everything but got nowhere. I blamed it on the clone board. The disconnections were so bad I often had to stop myself throwing a cup of coffee over the Duet board.
    So, last week I threw the boat out and purchased a genuine Duet Ethernet direct from Duet3D.

    Surprisingly, I still get lost connections on ethernet.
    Here is a small copy and paste from the gcode console during a print today;

    14:01:50
    Connection established!
    14:01:39
    Disconnected.
    14:01:30
    Connection established!
    14:01:02
    Disconnected.
    14:00:49
    Connection established!
    14:00:17
    Disconnected.
    13:59:54
    Connection established!
    13:59:16
    Disconnected.
    13:59:00
    Connection established!
    13:58:14
    Disconnected.
    13:58:05
    Connection established!
    13:57:42
    Disconnected.
    13:47:41
    M32 "CFFFP_7mm_Collet.gcode"
    File CFFFP_7mm_Collet.gcode selected for printing

    The whole thing is frustrating and stressing me out.

    Here's my config.g

    ; Configuration file for Duet WiFi

    ; General preferences
    G21 ; Work in millimetres
    G90 ; Send absolute coordinates...
    M83 ; ...but relative extruder moves
    M667 S1 ; Select coreXY , rev 2.02 and earlier
    ;M669 K1 ; Select CoreXY mode
    M555 P2 ; Set output to look like marlin

    ; Network
    M552 P192.168.1.6 ; Configure static IP address.
    M550 PTronxy X5S ; Set machine name
    M552 S1 ; Enable network
    M586 P0 S1 ; Enable HTTP
    M586 P1 S1 ; Enable FTP
    M586 P2 S1 ; Enable Telnet

    ; Stepper Drives
    M569 P0 S1 ; Drive 0 runs forwards, active low enable, (X)
    M569 P1 S1 ; Drive 1 runs forwards, active low enable, (Y)
    M569 P2 S0 ; Drive 2 runs backwards, active low enable, (Z1)
    M569 P3 S0 ; Drive 3 runs backwards, active low enable, (E0)
    M569 P4 S0 ; Drive 4 runs backwards, active low enable, (Z2 in the E1)

    ; Dual Z
    M584 X0 Y1 Z2:4 E3 ; Dual Z motors Z and E3 (extruder1 drive). Make sure Z drive is L/H stepper and E3 is R/H stepper
    ; Leadscrew positions: The measurement is taken from X=0, Y=0. Therefore X will be negative, Y positive and middle of bed = 160
    M671 X-100:415 Y160:160 S2.0 ; Leadscrews at middle left and middle right (S0 is correction value)

    ;Drive settings
    M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
    M92 X80 Y80 Z400 E96 ; Set steps per mm for 16 microsteps Aibecy E105, Titan E462
    ;M350 X32 Y32 Z32 E128 ; Use to setup new microstepping (dont delete default 16 microstepping)
    M566 X600.00 Y600.00 Z60.00 E300.00 ; Set maximum instantaneous speed changes (mm/min) - Jerk
    ;M203 X9000.00 Y9000.00 Z600.00 E6000.00 ; Set maximum speeds (mm/min)
    M203 X5000.00 Y5000.00 Z500.00 E4000.00 ; Set maximum speeds (mm/min)
    M201 X500.00 Y500.00 Z80.00 E5000.00 ; Set accelerations (mm/s^2) - print moves
    M906 X1100 Y1100 Z1100 E1300 I30 ; Motor currents - mine are 1.68amp, 85% = 1.42
    M84 S30 ; Set idle timeout

    ; Axis Limits
    M208 X-15 Y-12 Z0 S1 ; Set axis minima (adjust to make X=0 and Y=0 the edges of the bed)
    M208 X310 Y310 Z380 S0 ; Set axis maxima (adjust to suit your machine)

    ; Endstops
    M574 X1 Y1 S0 ; Set active low endstops for X and Y
    M581 Z1 S1 T0 C0 ; Set Z1 endstop as an e-stop for Z protection if Z probe fails when probing the bed.

    ; Filament Run Out Sensor
    M591 D0 P1 C4 S1 ; Filament runout Sensor for Extruder E0 on E1 Endstop input P1 = signal HIGH.

    ; Z-Probe
    M574 Z1 S2 ; Set endstops controlled by probe
    ; M558: the P is probe type, H is dive height-the height before probing, A is max number of probing each point, S is tollerance when multi-probing.
    ;M558 P1 H3 F120 A10 S0.03 I0
    M558 P1 H5 F120 T6000 ; Set Z probe type to unmodulated and the dive height + speeds
    ; G31: the P is the reported Z value when triggered. X,Y are offset coordinates. Z is trigger height, you can decrease value if nozzle is too close
    ; or increase if too far away.
    G31 P500 X-30 Y-5 Z1.8

    ; Mesh Grid
    ; The following M557 commands are not needed if you are using a bed.g file to perform bed compensation
    ;*** Adjust the XY coordinates in the following M557 commands to suit your build and the position of the Z probe
    M557 X10:280 Y20:280 S50 ; Define small mesh grid
    ;M557 X10:280 Y10:280 S20 ; Define large mesh grid

    ; Heaters
    M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0 (bed)
    M143 H0 S120 ; Set temperature limit for heater 0 to 90C
    M305 P1 T92000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1 (nozzle)
    M143 H1 S280 ; Set temperature limit for heater 1 to 250C
    M307 H1 A270.4 C96.4 D7.6 S1.00 V12.4 B0 ; Autotune result for hotend
    M307 H0 A109.8 C457.8 D2.1 S1.00 V12.3 B0 ; Autotune result for bed

    ;Expansion pins
    M307 H2 A-1 C-1 D-1 ; Make heater2 on extruder2 available and use it for pwm led lighting

    ; Fans
    M106 P0 S0 H-1 C"Part Cooling" ; Set fan 0 value (Part Cooling)
    ;M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 (hotend), PWM signal inversion and frequency. Thermostatic control is turned on
    M106 P1 S255 I0 F259 L125 H1 T60:140.
    ; Below 60 deg C the fan is off. At 60 deg C the fan will come on at 50% then will ramp up to full full speed between 60 and 140 deg C and remain at 100% for any ; temperature above 140

    ; Set fan 2 value (Duet mcu), PWM signal inversion and frequency. Thermostatic control is turned on, fan comes on at 40 deg and reaches full speed at 65 deg
    M106 P2 F500 T40:65 H100:101:102

    ;CPU Temperature Calibration
    ;M912 P0 S-9.5

    ; Tools
    M563 P0 D0 H1 S"Extruder" ; Define tool 0
    G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
    G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

    ; Automatic power saving
    M911 S10 R11 P"M911 S10 R11 P*M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

    ; Custom settings

    ;M593 F10.0 ; Cancel ringing at this frequency
    ;M207 S2.0 F2400 Z0.5 ; Retraction length, speed and Z lift
    ;M572 D0 S1.5 ; Set pressure advance
    M42 P2 S255 ; Turn led lighting on full
    M98 PLevelLeadscrews.g

    Any one have any suggestions?



  • Please post the results of a M122

    Also do you know if your Wireless system you are trying to connect to is 2.4 or 5 ghz?
    If it is running 5ghz I think you will struggle to connect.



  • 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