It's working better than ever. Guess it just needed a firmware update.
Thanks a bunch for your fast and professional help. Even though the solution was simple, i likely wouldn't have ever fixed the issue since I was at the end of my rope. So, thanks again.
Awesome. You guys have been a great help. I'll respond today or tomorrow after I've updated it. Thank you again.
Thanks. I'll update a little later today and give that a shot.
Here is the M122 code that appeared after the same issue.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 2.02RC5(RTOS) running on Duet Maestro 1.0
Board ID: 08D8M-9T8A2-MQNSS-6J9D2-3SD6R-967GY
Used output buffers: 3 of 20 (20 max)
=== RTOS ===
Static ram: 21236
Dynamic ram: 96988 of which 0 recycled
Exception stack ram used: 380
Never used ram: 12468
Tasks: NETWORK(ready,456) HEAT(blocked,1300) MAIN(running,3672) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:19:20 ago, cause: power up
Last software reset at 2019-07-16 13:02, reason: User, spinning module GCodes, available RAM 12468 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 4
Free file entries: 9
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest block write time: 63.0ms, max retries 0
MCU temperature: min 24.0, current 38.2, max 38.3
Supply voltage: min 23.0, current 23.2, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, read errors 0, write errors 0, ifcount 12, reads 46375, timeouts 0
Driver 1: standstill, read errors 0, write errors 0, ifcount 12, reads 46375, timeouts 0
Driver 2: standstill, read errors 0, write errors 0, ifcount 12, reads 46375, timeouts 0
Driver 3: standstill, read errors 0, write errors 0, ifcount 10, reads 46376, timeouts 1
Driver 4: standstill, read errors 0, write errors 0, ifcount 8, reads 46379, timeouts 0
Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 46386
Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 46386
Date/time: 2019-07-20 14:55:27
Slowest loop: 4581228.50ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 130, MaxWait: 737781ms, Underruns: 0, 0
Scheduled moves: 594, completed moves: 594
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.9
Heater 1 is on, I-accum = 0.2
=== GCodes ===
Segments left: 0
Stack records: 3 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, link 100Mbps full duplex
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 2.02RC5(RTOS) running on Duet Maestro 1.0
Board ID: 08D8M-9T8A2-MQNSS-6J9D2-3SD6R-967GY
Used output buffers: 3 of 20 (18 max)
=== RTOS ===
Static ram: 21236
Dynamic ram: 96988 of which 0 recycled
Exception stack ram used: 420
Never used ram: 12428
Tasks: NETWORK(ready,456) HEAT(blocked,1300) MAIN(running,3672) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:47:24 ago, cause: power up
Last software reset at 2019-07-16 13:02, reason: User, spinning module GCodes, available RAM 12468 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 34.6, current 34.7, max 35.1
Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, read errors 0, write errors 0, ifcount 15, reads 871, timeouts 0
Driver 1: standstill, read errors 0, write errors 0, ifcount 15, reads 871, timeouts 0
Driver 2: standstill, read errors 0, write errors 0, ifcount 15, reads 871, timeouts 0
Driver 3: standstill, read errors 0, write errors 0, ifcount 11, reads 871, timeouts 0
Driver 4: standstill, read errors 0, write errors 0, ifcount 8, reads 871, timeouts 0
Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 871
Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 871
Date/time: 2019-07-20 11:48:46
Slowest loop: 3.82ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 7, completed moves: 7
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 1.0
=== GCodes ===
Segments left: 0
Stack records: 3 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: 69.93ms; 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
The JavaScript error code showed up again, but this time it showed up right after I tried to disable the mesh bed leveling.
Alright, here's the gcodes , except the backup gcode, and the picture of the new javascript error. Thanks so much for you help.
0_1563647079305_config.g
0_1563647122748_CFFFP_f094a0f4-815f-4efa-8e16-e975c668113f.gcode
Thank you. I'll do that in just a few.
I also just recieved a new error code after homing the printer.
The error code reads that there is a java script error and that it disconnected the duet board. I will send a screenshot with my next message that includes the g.codes
Hi, my Promega has the Duet Maestro. It just started to randomly change layers while printing. It often skips several layers at a time. Such as layer one skipping to layer 10. After that about 100 error codes show up letting me know the machine is out of bounds. I then have to turn the printer off since the buttons are unresponsive. Please help. I'm trying to point some business parts and it is somewhat urgent! Thanks