Can´t print with extruder 2.
-
Now it actually happened with T0 as well (for the first time), crashed with five layers remaining at a five-hour spiral vase print.
I'm going nuts, what can cause these crashes?
As I´ve said before, it happens every time with T1 but almost never with T0 (this was the first).
I can´t see anything wrong in the config or g codes (but I´m no expert needs to be said).
And I don´t think that it´s a wiring issue since the problem follows that extruder that is connected as T1 on the board.
Anyone else that experience mid-print faults, that might have a solution to my problem?
Could it be something wrong with my board? -
Now it actually happened with T0 as well (for the first time), crashed with five layers remaining at a five-hour spiral vase print.
I'm going nuts, what can cause these crashes?
As I´ve said before, it happens every time with T1 but almost never with T0 (this was the first).
I can´t see anything wrong in the config or g codes (but I´m no expert needs to be said).
And I don´t think that it´s a wiring issue since the problem follows that extruder that is connected as T1 on the board.
Anyone else that experience mid-print faults, that might have a solution to my problem?
Could it be something wrong with my board?Please explain what you mean by "crashes". Does the board reset? Run M122 to find out. If the "Last reset time" corresponds to when the print stopped unexpectedly, instead of before you started the print, tell us what it shows for "Last reset reason" and "Last software reset code".
-
Now it actually happened with T0 as well (for the first time), crashed with five layers remaining at a five-hour spiral vase print.
I'm going nuts, what can cause these crashes?
As I´ve said before, it happens every time with T1 but almost never with T0 (this was the first).
I can´t see anything wrong in the config or g codes (but I´m no expert needs to be said).
And I don´t think that it´s a wiring issue since the problem follows that extruder that is connected as T1 on the board.
Anyone else that experience mid-print faults, that might have a solution to my problem?
Could it be something wrong with my board?Please explain what you mean by "crashes". Does the board reset? Run M122 to find out. If the "Last reset time" corresponds to when the print stopped unexpectedly, instead of before you started the print, tell us what it shows for "Last reset reason" and "Last software reset code".
With crashes I mean that everything freezes, web interface showes 100% progress and then everything freezes.
I have noted that if I wait a couple of seconds then I´m able to disconnect and then reconnect and when I run M122 these are the resets codes:
Last reset 00:00:11 ago, cause: software
Last software reset code: 0x5004, available RAM 24636 bytes (slot 0) -
The software reset code info at https://duet3d.com/wiki/Error_codes_and_software_reset_codes indicates that a software reset occurred because the firmware was trying to write debug info or other essential info to the USB port, but writing was b!Locked because the port wasn't connected or the program at the other end had stopped reading data from it.. This should only occur if you enable debug output using the M111 S1 command.
Assuming you do not have the USB port connected, I suggest you connect it to a PC, load Pronterface or another USB host program, and connect to the printer. Then do something that normally provokes the problem and see what messages appear on the PC.
-
The software reset code info at https://duet3d.com/wiki/Error_codes_and_software_reset_codes indicates that a software reset occurred because the firmware was trying to write debug info or other essential info to the USB port, but writing was b!Locked because the port wasn't connected or the program at the other end had stopped reading data from it.. This should only occur if you enable debug output using the M111 S1 command.
Assuming you do not have the USB port connected, I suggest you connect it to a PC, load Pronterface or another USB host program, and connect to the printer. Then do something that normally provokes the problem and see what messages appear on the PC.
Pronterface messages this:
[ERROR] Can't read from printer (disconnected?) (SerialException): call to ClearCommError failed
Exception in thread Thread-20:
Traceback (most recent call last):
File "threading.pyc", line 808, in __bootstrap_inner
File "threading.pyc", line 761, in run
File "printrun\printcore.pyc", line 357, in _sender
File "printrun\printcore.pyc", line 623, in _send
File "encodings\utf_8.pyc", line 16, in decode
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe4 in position 38: invalid continuation byte -
Unfortunately, that doesn't help because Pronterface has reported an exception in its own code without displaying the rest of the data. Do you have Arduino (any version) installed on your computer? If so, please try the same test again, but with Arduino Serial Monitor connected to the COM port that the Duet provides instead of Pronterface.
Also please check that the software reset code reported by M122 is the same as before.
-
Unfortunately, that doesn't help because Pronterface has reported an exception in its own code without displaying the rest of the data. Do you have Arduino (any version) installed on your computer? If so, please try the same test again, but with Arduino Serial Monitor connected to the COM port that the Duet provides instead of Pronterface.
Also please check that the software reset code reported by M122 is the same as before.
The seriell monitor shows this at start up and then nothing more:
RepRapFirmware for Duet WiFi Version 1.17c dated 2017-01-14
Executing config.g…RepRap name: My Duet
M570 S parameter is no longer required or supported
Done!
RepRapFirmware for Duet WiFi is up and running.
WiFi server starting up
WiFi server connected to access point
WiFi host name duetwiSame software reset code is reported as before when running M122
Also tried removing all M570 since the monitor said it´s no longer supported, didn´t help -
This one has me puzzled. You reported software reset code 0x5004. This means that the Move module was executing at the time and it was stuck in a spin loop for too long while waiting for the USB output buffer to clear. For that to happen, Move or DDA debug output would have to be enabled, but the USB would either have to be disconnected or the program at the other end not receiving. The error from Pronterface suggests that it did receive something (that it didn't understand). The serial monitor output shows that the connection was working when the Duet started up. But there are a couple of odd things: it has started up as an access point (i.e. not connected to your router), and it hasn't printed the whole of the access point name - it should be "duetwifi" not "duetwi". It's as if the USB connection stopped working at that point.
-
This one has me puzzled. You reported software reset code 0x5004. This means that the Move module was executing at the time and it was stuck in a spin loop for too long while waiting for the USB output buffer to clear. For that to happen, Move or DDA debug output would have to be enabled, but the USB would either have to be disconnected or the program at the other end not receiving. The error from Pronterface suggests that it did receive something (that it didn't understand). The serial monitor output shows that the connection was working when the Duet started up. But there are a couple of odd things: it has started up as an access point (i.e. not connected to your router), and it hasn't printed the whole of the access point name - it should be "duetwifi" not "duetwi". It's as if the USB connection stopped working at that point.
When it freezes I actually loses the contact to the board and needs to restart/reconnect.
Could it be something wrong with the firmware installation on the board?
Wondering if it would be a solution to reinstall everything?
I have 1.17c (2017-01-14) installed, thought it would get better to upgrade but it actually got worse.
Before the upgrade I only had problem when I used T1 but now I experienced more freezes also when using T0 -
Please upgrade to firmware 1.17c+2 (in the Edge folder in github). Connect the serial monitor as before. If you still get the same problem, please check for output on the serial monitor, also run M122 and report the software reset code, along with the additional parameters displayed with it.
-
Please upgrade to firmware 1.17c+2 (in the Edge folder in github). Connect the serial monitor as before. If you still get the same problem, please check for output on the serial monitor, also run M122 and report the software reset code, along with the additional parameters displayed with it.
Same problem.
Last reset 00:00:20 ago, cause: software
Last software reset code 0x1004, PC 0x00000000, HFSR 0x00000000, CFSR 0x00000000, available RAM 24396 bytes (slot 0)RepRapFirmware for Duet WiFi Version 1.17c+2 dated 2017-01-24
Executing config.g…RepRap name: My Duet
M570 S parameter is no longer required or supported
Done!
RepRapFirmware for Duet WiFi is up and running.
WiFi server starting up
WiFi server connected to access point
WiFi host name duetwifi, free memory 31544 bytes, reset reason: Turned on by main processorThe whole text from the serial monitor doesn´t always shows, stops at duet or duetw sometimes
Noted a strange thing, when the interface freezes I can move the head with the machinecontrol but I can´t send M122, I need to disconnect and reconnect to do this.
-
Thanks. That's a different software reset code - 0x1004 instead of 0x5004. It's still taking too long in the Move module, but this time it's not doing USB output. So I think the USB output flag last time was a red herring.
Please provide your config.g file, also your tool change files if you have any.
-
Thanks. That's a different software reset code - 0x1004 instead of 0x5004. It's still taking too long in the Move module, but this time it's not doing USB output. So I think the USB output flag last time was a red herring.
Please provide your config.g file, also your tool change files if you have any.
Have no tool change files, deleted these since I thought these was causing the problem
; Configuration file for Mini Kossel kit from Think3DPrint3D
; Communication and general
M111 S0 ; Debug off
M550 MHCoreXY ; Machine name and Netbios name (can be anything you like)
M551 xxxxx ; Machine password (used for FTP)
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address
;*** Wifi Networking
M552 P0.0.0.0 S1 ; Enable WiFiM555 P1 ; Set output to look like RepRapfirmware
;M575 P1 B57600 S1 ; Comms parameters for PanelDueG21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M667 S1 ; switch to CoreXY mode; Axis and motor configuration
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X300 Y300 Z440 S0 ; Set axis maxima
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M574 X1 Y2 Z0 S0 ; set endstop configuration (all endstops at high end, active high)
;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
M350 X16 Y16 Z16 E16:16 I1 ; Set 16x microstepping with interpolation
M92 X100 Y100 Z1600 ; Set axis steps/mm
M906 X1200 Y1200 Z1200 E400:400 I30 ; Set motor currents (mA) and increase idle current to 60%
M201 X1000 Y1000 Z100 E2000:2000 ; Accelerations (mm/s^2)
M203 X6000 Y6000 Z800 E12000:12000 ; Maximum speeds (mm/min)
M566 X600 Y600 Z60 E2400:E2400 ; Maximum instant speed changes mm/minute
M84 S30; Thermistors heaters
M143 S260 ; Set maximum heater temperature to 280C
M305 P0 T100000 B4138 C0.0000000000000000 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4388 C0.0000000000000000 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 1
M305 P2 T100000 B4388 C0.0000000000000000 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 2
M570 S180 ; Hot end may be a little slow to heat up so allow it 180 seconds
M570 H1 P10 T15
M570 H2 P10 T15
M307 H1 A295.5 C122.8 D9.4 B0
M307 H2 A295.5 C122.8 D9.4 B0; Tool definitions
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 ; Set tool 0 axis offsets
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
;*** If you have a single-nozzle build, comment the next 2 lines
M563 P1 D1 H2 ; Define tool 1
G10 P1 X18 Y0 ; Set tool 1 axis offsets
G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures
M92 E154:154 ; Set extruder steps per mm; Z probe and compensation definition
;*** If you have a switch instead of an IR probe, change P1 to P4 in the following M558 command
M558 P1 X0 Y0 Z0 H3 F300 T12000 ; Z probe is an IR probe and is not used for homing any axes
G31 X0 Y0 Z1.67 P500 ; Set the zprobe height and threshold (put your own values here);*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0 ; Axis compensation here
;T1 ; select first hot end -
I think I solved the problem but I don't know what the problem was.
Used a friends config file, that has built a almost exactly the same printer as mine, and it worked.
The only difference in the configs was that I used two M92, one for the axis and one for the extruders.
And we had the codes in a different order.
