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

    Posts made by rickypilnik

    • RE: Constant stopping

      Adjusted steps, checked compensation is on and the pauses are still happening. Its not so much a jerk as a complete stop, wait for a bit and then continue. Here is an m122 during a stop
      m122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
      Board ID: 08DGM-956GU-DJMSN-6JTD6-3SJ6L-9BNHF
      Used output buffers: 1 of 24 (21 max)
      === RTOS ===
      Static ram: 27980
      Dynamic ram: 93892 of which 20 recycled
      Exception stack ram used: 504
      Never used ram: 8676
      Tasks: NETWORK(ready,368) HEAT(blocked,1224) MAIN(running,1840) IDLE(ready,80)
      Owned mutexes:
      === Platform ===
      Last reset 00:20:15 ago, cause: software
      Last software reset at 2020-09-20 13:29, reason: User, spinning module GCodes, available RAM 8692 bytes (slot 2)
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
      Error status: 0
      MCU temperature: min 36.0, current 36.1, max 36.4
      Supply voltage: min 13.2, current 13.5, max 13.7, under voltage events: 0, over voltage events: 0, power good: yes
      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: ok, SG min/max not available
      Driver 4: standstill, SG min/max not available
      Date/time: 2020-09-20 13:49:29
      Cache data hit count 2128334024
      Slowest loop: 5.76ms; fastest: 0.12ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Storage ===
      Free file entries: 9
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest read time 1.0ms, write time 0.0ms, max retries 0
      === Move ===
      Hiccups: 0(0), FreeDm: 168, MinFreeDm: 165, MaxWait: 0ms
      Bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves: 489, completed moves: 484, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3
      === AuxDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
      === Heat ===
      Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
      Heater 0 is on, I-accum = 0.4
      Heater 1 is on, I-accum = 0.5
      === GCodes ===
      Segments left: 1
      Movement lock held by null
      HTTP is idle in state(s) 0
      Telnet is idle in state(s) 0
      File is doing "G0 X161.15 Y153.617" in state(s) 0
      USB is idle in state(s) 0
      Aux is idle in state(s) 0
      Trigger is idle in state(s) 0
      Queue is idle in state(s) 0
      Daemon is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 199.89ms; fastest: 0.09ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
      HTTP sessions: 1 of 8

      • WiFi -
        Network state is active
        WiFi module is connected to access point
        Failed messages: pending 0, notready 0, noresp 4
        WiFi firmware version 1.23
        WiFi MAC address 5c:cf:7f:76:6d:15
        WiFi Vcc 3.38, reset reason Unknown
        WiFi flash size 4194304, free heap 24584
        WiFi IP address 172.16.1.144
        WiFi signal strength -64dBm, reconnections 0, sleep mode modem
        Socket states: 0 0 0 0 0 0 0 0
      posted in General Discussion
      rickypilnikundefined
      rickypilnik
    • RE: Constant stopping

      Having changed the motor and thermistor settings, run an auto-tune I started a print again. Unfortunately, the same thing keeps happening

      Here is the updated config for convenience

      ; Configuration file for Duet WiFi (firmware version 3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Sep 19 2020 17:38:32 GMT+0100 (British Summer Time)

      ; General preferences
      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"Ricky's CR-10" ; set printer name

      ; Network
      M551 P"Cyborg123" ; set password
      M552 S1 ; enable network
      M586 P0 S1 ; enable HTTP
      M586 P1 S0 ; disable FTP
      M586 P2 S0 ; disable Telnet

      ; Drives
      M569 P0 S0 ; physical drive 0 goes backwards
      M569 P1 S0 ; physical drive 1 goes backwards
      M569 P2 S1 ; physical drive 2 goes forwards
      M569 P3 S0 ; physical drive 3 goes backwards
      M584 X0 Y1 Z2 E3 ; set drive mapping
      M350 E256 I0 ; configure microstepping without interpolation
      M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z6400.00 E1715.00 ; set steps per mm
      M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X9000.00 Y9000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
      M201 X3000.00 Y3000.00 Z250.00 E5000.00 ; set accelerations (mm/s^2)
      M906 X1125 Y1125 Z1125 E1125 I30 ; set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits
      M208 X0 Y0 Z0 S1 ; set axis minima
      M208 X300 Y300 Z400 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
      M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
      M574 Z1 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop

      ; Z-Probe
      M558 P0 H1 F210 T9000 ; disable Z probe but set dive height, probe speed and travel speed
      M557 X15:230 Y15:285 S30 ; define mesh grid

      ; Heaters
      M308 S0 P"bedtemp" Y"thermistor" T98801 B4185 ; configure sensor 0 as thermistor on pin bedtemp
      M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
      M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
      M140 H0 ; map heated bed to heater 0
      M143 H0 S80 ; set temperature limit for heater 0 to 80C
      M308 S1 P"e0temp" Y"thermistor" T98801 B4185 ; configure sensor 1 as thermistor on pin e0temp
      M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
      M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

      ; Fans
      M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off
      M950 F2 C"fan1" Q500 ; create fan 2 on pin fan1 and set its frequency
      M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off

      ; Tools
      M563 P0 D0 H1 F0 ; 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

      ; Custom settings are not defined

      ; Miscellaneous
      M575 P1 S1 B57600 ; enable support for PanelDue
      M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

      M501

      posted in General Discussion
      rickypilnikundefined
      rickypilnik
    • RE: Constant stopping

      Thanks, I'll do that, set a print going and get back to you

      posted in General Discussion
      rickypilnikundefined
      rickypilnik
    • RE: Constant stopping

      ; Configuration file for Duet WiFi (firmware version 3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Sep 05 2020 17:18:00 GMT+0100 (British Summer Time)

      ; General preferences
      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"Ricky's CR-10" ; set printer name

      ; Network
      M551 P"Cyborg123" ; set password
      M552 S1 ; enable network
      M586 P0 S1 ; enable HTTP
      M586 P1 S0 ; disable FTP
      M586 P2 S0 ; disable Telnet

      ; Drives
      M569 P0 S0 ; physical drive 0 goes backwards
      M569 P1 S0 ; physical drive 1 goes backwards
      M569 P2 S1 ; physical drive 2 goes forwards
      M569 P3 S0 ; physical drive 3 goes backwards
      M584 X0 Y1 Z2 E3 ; set drive mapping
      M350 E256 X256 Y256 Z256 I0 ; configure microstepping without interpolation
      M92 X1280.00 Y1280.00 Z6400.00 E1715.00 ; set steps per mm
      M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X9000.00 Y9000.00 Z480.00 E1200.00 ; set maximum speeds (mm/min)
      M201 X575 Y575 Z100 E575 ; set accelerations (mm/s^2)
      M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits
      M208 X0 Y0 Z0 S1 ; set axis minima
      M208 X300 Y300 Z400 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
      M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
      M574 Z1 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop

      ; Z-Probe
      M558 P0 H1 F210 T9000 ; disable Z probe but set dive height, probe speed and travel speed
      M557 X15:230 Y15:285 S30 ; define mesh grid

      ; Heaters
      M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
      M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
      M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
      M140 H0 ; map heated bed to heater 0
      M143 H0 S120 ; set temperature limit for heater 0 to 120C
      M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
      M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
      M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

      ; Fans
      M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off
      M950 F2 C"fan1" Q500 ; create fan 2 on pin fan1 and set its frequency
      M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off

      ; Tools
      M563 P0 D0 H1 F0 ; 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

      ; Custom settings are not defined

      ; Miscellaneous
      M575 P1 S1 B57600 ; enable support for PanelDue
      M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
      M501

      posted in General Discussion
      rickypilnikundefined
      rickypilnik
    • RE: Constant stopping

      m122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
      Board ID: 08DGM-956GU-DJMSN-6JTD6-3SJ6L-9BNHF
      Used output buffers: 3 of 24 (10 max)
      === RTOS ===
      Static ram: 27980
      Dynamic ram: 93892 of which 20 recycled
      Exception stack ram used: 544
      Never used ram: 8636
      Tasks: NETWORK(ready,384) HEAT(blocked,1168) MAIN(running,1824) IDLE(ready,80)
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:00:30 ago, cause: power up
      Last software reset at 2020-09-06 17:31, reason: User, spinning module GCodes, available RAM 8356 bytes (slot 2)
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
      Error status: 0
      MCU temperature: min 22.8, current 27.4, max 27.7
      Supply voltage: min 13.5, current 13.6, max 13.7, under voltage events: 0, over voltage events: 0, power good: yes
      Driver 0: standstill, SG min/max 0/275
      Driver 1: standstill, SG min/max 4/320
      Driver 2: standstill, SG min/max 0/0
      Driver 3: standstill, SG min/max not available
      Driver 4: standstill, SG min/max not available
      Date/time: 2020-09-19 17:18:24
      Cache data hit count 48905813
      Slowest loop: 7.60ms; fastest: 0.12ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest read time 1.1ms, write time 0.0ms, max retries 0
      === Move ===
      Hiccups: 0(0), FreeDm: 169, MinFreeDm: 167, MaxWait: 18366ms
      Bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves: 5, completed moves: 5, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
      === AuxDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
      === Heat ===
      Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
      === GCodes ===
      Segments left: 0
      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
      USB is idle in state(s) 0
      Aux is idle in state(s) 0
      Trigger is idle in state(s) 0
      Queue is idle in state(s) 0
      Daemon is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 156.25ms; fastest: 0.00ms
      Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
      HTTP sessions: 1 of 8

      • WiFi -
        Network state is active
        WiFi module is connected to access point
        Failed messages: pending 0, notready 0, noresp 0
        WiFi firmware version 1.23
        WiFi MAC address 5c:cf:7f:76:6d:15
        WiFi Vcc 3.38, reset reason Unknown
        WiFi flash size 4194304, free heap 23000
        WiFi IP address 172.16.1.144
        WiFi signal strength -60dBm, reconnections 0, sleep mode modem
        Socket states: 0 0 0 0 0 0 0 0

      config (3).g

      posted in General Discussion
      rickypilnikundefined
      rickypilnik
    • Constant stopping

      I started having an issue recently quite out of the blue, not after any updates or anything where any file I started printing just keeps stopping. Basically it performs a few lines of gcode then stops - e.g the initial wipe maneuver takes place and then the printer stops and pauses for 30 seconds or so and then performs another few lines and pauses again. Any ideas what's going on? Here are the board specs:
      Board: Duet 2 WiFi (2WiFi)
      Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.1.1 (2020-05-19b2)
      Duet WiFi Server Version: 1.23

      posted in General Discussion
      rickypilnikundefined
      rickypilnik
    • RE: Z-Axis not homing

      So after all that, having switched boards around I think I found the underlying problem of this all......... A badly crimped factory connector on the Velleman..........AGHH
      Anyway thanks for all your help you helped solve problems I wasn't even aware of yet!

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • RE: Z-Axis not homing

      @Phaedrux That is quite unfortunate to hear, but if I switch it to a duet 2 wifi you reckon things should be ok?

      As in it should stop shorting to ground if I use a lower motor current on a different printer, say a CR-10 with motors that max out at 1.5A anyways.

      Motor current (mA) - X:1875, Y:1875, Z:1875, E:1875, idle factor 30%

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • RE: Z-Axis not homing

      On the 5th May 2020, from E3D Online, and it's a Maestro

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • RE: Z-Axis not homing

      Yes 15V sounds correct and the message is
      " Error: short-to-ground reported by driver(s) 2 "

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • RE: Z-Axis not homing

      No I can't move the Z-axis, but x and y are fine even with the message of short to drivers from before.

      m122
      === Diagnostics ===
      RepRapFirmware for Duet 2 Maestro version 3.1.1 running on Duet Maestro 1.0
      Board ID: 08DJM-9X66L-LG3SN-6JKDL-3S06Q-K8X6P
      Used output buffers: 3 of 24 (10 max)
      === RTOS ===
      Static ram: 21924
      Dynamic ram: 92804 of which 52 recycled
      Exception stack ram used: 392
      Never used ram: 15900
      Tasks: NETWORK(ready,472) HEAT(blocked,1324) MAIN(running,1996) IDLE(ready,84)
      Owned mutexes:
      === Platform ===
      Last reset 00:01:06 ago, cause: power up
      Last software reset at 2020-05-20 19:20, reason: User, spinning module GCodes, available RAM 16096 bytes (slot 3)
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
      Error status: 0
      MCU temperature: min 32.7, current 35.3, max 35.5
      Supply voltage: min 0.0, current 15.4, max 15.7, under voltage events: 0, over voltage events: 0, power good: yes
      Driver 0: standstill, read errors 0, write errors 0, ifcount 9, reads 2644, timeouts 0
      Driver 1: standstill, read errors 0, write errors 0, ifcount 9, reads 2644, timeouts 0
      Driver 2: short-to-ground, read errors 0, write errors 0, ifcount 9, reads 2644, timeouts 0
      Driver 3: standstill, read errors 0, write errors 0, ifcount 7, reads 2646, timeouts 0
      Driver 4: standstill, read errors 0, write errors 0, ifcount 6, reads 2647, timeouts 0
      Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 2653
      Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 2652
      Date/time: 2020-05-20 19:32:27
      Slowest loop: 10.29ms; fastest: 0.12ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Storage ===
      Free file entries: 9
      SD card 0 detected, interface speed: 15.0MBytes/sec
      SD card longest read time 2.6ms, write time 0.0ms, max retries 0
      === Move ===
      Hiccups: 0(0), FreeDm: 168, MinFreeDm: 168, MaxWait: 26403ms
      Bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves: 14, completed moves: 13, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3
      === AuxDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
      === Heat ===
      Bed heaters = 0 -1, chamberHeaters = -1 -1
      === GCodes ===
      Segments left: 0
      Movement lock held by HTTP
      HTTP is idle in state(s) 1 8, running macro
      Telnet is idle in state(s) 0
      File is idle in state(s) 0
      USB is idle in state(s) 0
      Aux is idle in state(s) 0
      Trigger is idle in state(s) 0
      Queue is idle in state(s) 0
      LCD is idle in state(s) 0
      Daemon is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 129.03ms; fastest: 0.02ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
      HTTP sessions: 1 of 8
      Interface state active, link 100Mbps full duplex

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • RE: Z-Axis not homing

      Same as before. Z - Axis still not moving.

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • RE: Z-Axis not homing

      config (2).g

      I press the home Z button on DWC and nothing moves and I hear no noises.

      (changed all motor currents to 1875mA (max is 2.5A) and Z steps per mm to 400. (200*16)/8 )

      IMG_0611.JPG

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • RE: Z-Axis not homing

      So I've adjusted all the values, X and Y axes home fine but the Z axis still won't home and I'm now getting this error.
      "Error: short-to-ground reported by driver(s) 2"

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • RE: Z-Axis not homing

      @Phaedrux One more thing, I have steps set to *16 with interpolation to 256. Which value do I use?

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • RE: Z-Axis not homing

      For the calculation what is screw lead?
      Okay, I'll try the current adjustment and no upon attempted movement nothing is heard or changed. (I think this value is massively off as I j checked the motors and it says 2.5A on them)
      Before changing any settings I switched the Y and Z motors, and both worked, except a tiny increment in the z movement moved the Y a lot and a lot in the y-direction only moved the z a little. This makes me think it's all related to the steps per mm.

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • RE: Z-Axis not homing

      homeall.g
      No, I simply left it as default.
      Again not sure, that's simply default and I'm running one identical motor so I figured it'd be close enough.
      No, I got no movement.
      No errors appear.
      What do you mean by how are they wired? (only one motor)

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • Z-Axis not homing

      So I was upgrading a Friend's old Velleman K8200 with a Duet Maestro and everything seems to be working bar one small thing. The Z-Axis won't home. Upon requesting nothing happens and eventually DWC just shows it as being at zero, any ideas? All other axes work fine and the motor and endstop were previously working fine. All endstops are low-end active-high and I have no Z-Probe. After homing when attempting to jog the Z-Axis through DWC the distance increases but nothing actually moves.
      Attached is my config.
      config (1).g

      posted in My Duet controlled machine
      rickypilnikundefined
      rickypilnik
    • RE: Javascript Error

      Worked a charm, thanks!

      posted in Duet Web Control
      rickypilnikundefined
      rickypilnik
    • Javascript Error

      I've recently started having a problem when I open up my config.g file I get disconnected and this error shows up.
      × JavaScript Error

      A JavaScript error has occurred so the web interface has closed the connection to your board. It is recommended to reload the web interface now. If this happens again, please contact the author and share this error message:

      Version: 1.22.2
      Message: ResizeObserver loop limit exceeded
      URL: http://172.16.1.144/
      Line: 0:0
      Error object: null

      Everything else works - i.e I can print, send commands open other system files no problem, but the moment I open the config.g file I get disconnected....any ideas?

      posted in Duet Web Control
      rickypilnikundefined
      rickypilnik