Duet Maestro Web Control Issues
I am having issues with the Duet web control. Some of it I have seen on other posts, but it's either not the same or the resolution does not really apply to me. Here goes.
- Biggest issue right now is that the filament change function under tool on the top left corner of machine control is no longer responsive. It does not bring up the dialogue box that it is initiating the sequence. I have not made a change to filament files since the time it was working. So right now I have to manually extrude or retract my filament to make a change. Super frustrated. ABS sequence below
M291 P"Please wait while the nozzle is being heated up" R"Loading ABS" S0 T0 ; Display message
G10 S240 ; Set current tool temperature to 240C
M116 ; Wait for the temperatures to be reached
M291 P"Feeding filament..." R"Loading ABS" S0 T0 ; Display new message
G1 E50 F300 ; Feed 50m of filament at 600mm/min
G1 E90 F3000 ; Feed 90mm of filament at 3000mm/min
G1 E100 F300 ; Feed 100mm of filament at 300mm/min
G4 P1000 ; Wait one second
M400 ; Wait for moves to complete
M292 ; Hide the message
G10 S0 ; Turn off the heater again
M291 P"Please wait while the nozzle is being heated up" R"Unloading ABS" S0 T0 ; Display message
G10 S240 ; Heat up the current tool to 240C
M116 ; Wait for the temperatures to be reached
M291 P"Retracting filament..." R"Unloading ABS" S0 T0 ; Display another message
G1 E20 F300 ; Extrude 20mm of filament at
G1 E-350 F3000 ; Retract 350mm of filament at 3000mm/min
M400 ; Wait for the moves to finish
M292 ; Hide the message again
M84 E0:1 ; Turn off extruder drives 1 and 2
So again I can select load or unload but it does nothing. I can still control motors, edit settings, change temperatures, etc.
I have occasional issue where I can edit the config files, but not save them. I can open them, make changes, but when I hit the save button, nothing happens. The editor does not close and ask me to restart (if editing config.g). The save button does nothing. I have to refresh the browser page to get out, and the changes are not saved. I saw some post with this issue, but they were able to close the editor, just not save the changes.
I have occasional issue where I have a long reconnect time. This is for a pc hardwired to my network. It will take 1 or 2 minutes to connect to the machine.
I have a current windows 10 machine using Chrome. Both autoupdate so should be very current. The Maestro has the firmware it shipped it with a couple days back.
Let me know what other info I can provide. Below is the firmware diagnostic
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 2.01beta1(RTOS) running on Duet Maestro 1.0
Board ID: 08DGM-95762-FD3T8-6JTD0-3S07J-KTHH9
Used output buffers: 1 of 20 (14 max)
=== RTOS ===
Static ram: 22420
Dynamic ram: 92600 of which 16 recycled
Exception stack ram used: 288
Never used ram: 15748
Tasks: NETWORK(ready,460) HEAT(blocked,1292) MAIN(running,576)
Mutexes: FilamentSensors(null) DHT(null) W5500(null) TelnetGCodeReply(null) HttpGCodeReply(null) Telnet(null) HTTP(null) SD1(null) SD0(null) DirSearch(null) FileSystem(null) Aux(null) USB(null) MessageBox(null) ToolList(null) SPI(null) Malloc(null) NetworkGCodeInput(null) NetworkGCodeInput(null) FileInfoParser(null)
=== Platform ===
Last reset 01:14:00 ago, cause: software
Last software reset at 2018-08-06 06:28, reason: User, spinning module GCodes, available RAM 15748 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x04418000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest block write time: 114.6ms
MCU temperature: min 30.5, current 30.9, max 32.4
Supply voltage: min 23.2, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0
Driver 0: standstill, read errors 0, write errors 1, ifcount 50, reads 28239, timeouts 0
Driver 1: standstill, read errors 0, write errors 1, ifcount 49, reads 28239, timeouts 0
Driver 2: standstill, read errors 0, write errors 1, ifcount 49, reads 28238, timeouts 0
Driver 3: standstill, read errors 0, write errors 1, ifcount 25, reads 28243, timeouts 0
Driver 4: standstill, read errors 0, write errors 1, ifcount 25, reads 28243, timeouts 0
Date/time: 2018-08-06 07:42:07
Slowest loop: 4581230.00ms; fastest: 1.53ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 234, MaxWait: 4294190694ms, Underruns: 0, 0
Scheduled moves: 179, completed moves: 179
Bed compensation in use: mesh
Bed probe heights: 1.480 0.997 0.824 0.919 0.943
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 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
lcd is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 4581228.50ms; 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
I can't remember the details, but there was a bug in this area in one of the beta firmware versions, which was fixed in the next beta. So if you are running my fork of RRF, please upgrade your firmware to the 2.01 release version. If you are running M3D's fork, ask them if they have a release based on 2.01 yet.
@dc42 Hi, Just installed your RRP 2.01. Motors are now unresponsive. Config files have not changed. The change filament button works, but the motor extruder motor does not move. Cannot home anymore either.
Common reasons for motors being unresponsive:
- Motor currents are not set. Run M906 without parameters to check. Also run M913 and check that motor currents are at 100%.
- Axis movement is by default not allowed until the axis has been homed. In this case, if you try to jog the axes, there should be an error message in the Console page of DWC or PanelDue. You can allow axis movement by including M564 H0 in config.g.
Thanks for all your help so far. Yes motor currents are at 1500 for the axis and 1300 for the extruder. All at 100%. These were working fine before RRF update. Including M564 H0 in the config.g and then trying to move the axis gives me a stack overflow error.
G1 Z-5 F6000
Error: G0/G1: insufficient axes homed
Error: Pop(): stack underflow!
Okay, got it. I had previously updated the DuetMaestroFirmware.bin but it did not ask me to install it unlike rrf. I did this a few times. The file would get stored but the web interface did not ask to install. On a whim I did it again just now and it installed. and the motors are moving.....
One step closer to printing....