-
@Phaedrux said in error:attempting to extrude with no tool selected while printing:
M98 P"config.g"
the replied are
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Pin 'zprobe.in' is not free
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 536Cfor the information the heater used PID bed and extruder
-
@lifeform said in error:attempting to extrude with no tool selected while printing:
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 536C
for the information the heater used PID bed and extruderThis part is ok. https://duet3d.dozuki.com/Wiki/FAQ#Section_M307_Heater_1_appears_to_be_over_powered_If_left_on_at_full_power_its_temperature_is_predicted_to_reach_521C
@lifeform said in error:attempting to extrude with no tool selected while printing:
Error: Pin 'zprobe.in' is not free
Will need to see the config.g and M122 to be able to fix that one. And probably homing files.
-
@Phaedrux said in error:attempting to extrude with no tool selected while printing:
22 to be able to fix that on
[0_1602737785250_download.zip](Uploading 100%)
here is my config file and home macro.
would you mind to check mine?
-
You'll have to either copy and paste the text into a post, or drag and drop the actual .g files onto the forum message post window to upload them directly. Zip files are not allowed by the forum software so your upload failed.
-
this is for config.g
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Fri Oct 02 2020 12:18:13 GMT+0700 (Indochina Time); General preferences
M80 ; Turns on the ATX power supply
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"BLV mgn Cube" ; set printer nameM669 K1 ; select CoreXY mode
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes backwards
M569 P4 S0 ; physical drive 4 goes backwards
M584 X0 Y1 Z2:4 E3 ; set drive mapping
;M671 X-50:378 Y164:164 S0.5 ; Define the X and Y coordinates of the leadscrews.
M671 X379:-51 Y164:164 S5 ; Define the X and Y coordinates of the leadscrews.M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
;M92 X200.00 Y200.00 Z400.00 E418.00 ; set steps per mm
M92 X198.65 Y200.5 Z399.60 E417.71 ; set steps per mm
M566 X660.00 Y660.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X20000.00 Y20000.00 Z600.00 E2000.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X1700 Y1700 Z1600 E300 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Pressure advance
M572 D0 S0.13 ; enabled Pressure advance; Axis Limits
;M208 X0 Y0 Z0 S1 ; set axis minima
;M208 X350 Y350 Z350 S0 ; set axis maxima
M208 X-7:343 Y0:340 Z0:450; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y2 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop; Filament sensor
;M591 D0 P1 C3 S1 ; Set Filament sensor Simple type (High) for extruder drive 0, connected to endstop input 3 (E0);disabled port
;M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board.; Z-Probe
M558 P9 C"^zprobe.in" H5 F200 T4000 X0 Y0 Z0 A2 R0.1 S0.02 ; set Z probe type to bltouch and the dive height + speeds H=Dive Height. F=Speed the bed moves
M574 Z1 S1 P"zprobe.in" ; Set endstops controlled by probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
G31 P25 X-41 Y0 Z2.11 ;sblumnya 2.88 ; set Z probe trigger value, offset and trigger height
M557 X20:308 Y20:308 S92 ; define mesh grid; Heaters
;M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 C0 R4700 ; 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 S110 ; set temperature limit for heater 0 to 110C
M308 S1 P"e0temp" Y"thermistor" T100000 B3950 C0 R4700 ; 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
M143 H1 S260 ; set temperature limit for heater 1 to 260C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit;PID set values
M307 H1 A511.8 C182.7 D9.7 V23.8 B0 ; Set PID for hotend values
M307 H0 A126.6 C968.3 D0.6 v23.8 B0 ; Set PID for heated bed values; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 C"Part" ; 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 H1 T35 C"Hotend" ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" ; create fan 2 on pin fan1 and set its frequency
M106 P2 S0 H-1 C"LED" ; set fan 2 value. Thermostatic control is turned on; 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
;M564 H0 ; Let the Jog buttons work blv: added to allow jog buttons
M593 F90.5 ; cancel ringing at 40.5Hz; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
M911 S21 R22 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss;filament sensor setting
M591 D0 P7 C"e0_stop" L6.2 R50:200 E12.4 S1 ; s1 enable s0 disable
;M591 D0 P7 C"e0_stop" R50:200 L6.2 E18.6 S0T0 ; select first tool
-
@Phaedrux this is for homeall
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Fri Oct 02 2020 12:18:14 GMT+0700 (Indochina Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-355 Y355 F6000 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-355 ; home X axis
G1 H1 Y355 ; home Y axis
G1 X5 Y-5 F6000 ; go back a few mm
G1 H1 X-355 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y355 ; then move slowly to Y axis endstop
;G1 H1 Z-355 F360 ; move Z down stopping at the endstop
G90 ; absolute positioning
G1 X205 Y164 F6000 ; go to first bed probe point and home Z
;G92 Z0 ; set Z position to axis minimum (you may want to adjust this)
G30this is for homez
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Fri Oct 02 2020 12:18:14 GMT+0700 (Indochina Time)
G91 ; relative positioning
G1 H2 Z8 F6000 ; lift Z relative to current positionG90 ; absolute positioning
G1 X205 Y164 F6000 ; go to first probe point
G30 ; home Z by probing the bed -
this is for M122
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID:
Used output buffers: 5 of 24 (18 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 94140 of which 236 recycled
Exception stack ram used: 304
Never used ram: 8412
Tasks: NETWORK(ready,384) HEAT(blocked,1224) MAIN(running,1816) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:05:34 ago, cause: software
Last software reset at 2020-10-15 13:18, reason: User, spinning module GCodes, available RAM 8308 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 35.1, current 35.4, max 36.2
Supply voltage: min 23.7, current 23.8, max 23.9, 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: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-10-15 13:23:40
Cache data hit count 540770322
Slowest loop: 11.78ms; fastest: 0.14ms
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 2.1ms, write time 2.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, 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
Heater 1 is on, I-accum = 0.0
=== 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: 41.38ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 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 cc:50:e3:e3:ba:9d
WiFi Vcc 3.31, reset reason Unknown
WiFi flash size 4194304, free heap 25400
WiFi IP address 192.168.1.30
WiFi signal strength -45dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: no data received
- WiFi -
-
@lifeform said in error:attempting to extrude with no tool selected while printing:
;filament sensor setting
This line appears to be causing some of the error message problem since the text matches what you're getting in the paneldue.
I think maybe it's parsing the ; without a space behind it differently in that case for some reason.
I can't see where the 04 error might be coming from.
Do you have any tool change files in your system folder? tpre tpost tfree?
Do you have the paneldue wires running near any steppers or endstops or fan wires?
-
@Phaedrux
i already change and added space after ;
but the ; is comment symbol right?
the error changing 04 to 202 to 240 and keep changing... so i really confused what cause of thistpre, tpost, tfree is generated by generator only. i do not change at all. cause i just have 1 extruder
the cable near z stepper but i already move it to not near any stepper, enmdstop cable or fan wires. the option i still not try is use shielded cable. i bought shield cable online so it might took 2-4 days to deliver
any other option i can check?
-
-
@lifeform said in error:attempting to extrude with no tool selected while printing:
the option i still not try is use shielded cable
There have been a few cases where updating the firmware has made previous cabling deficiencies apparent, and using a shielded cable has helped. So that might be the best option to try.
-
@Phaedrux i am waiting for cable to deliver, still in shipping.
i still not found why zprobe.in is not free. i change all my remark with "; " added space if there is no space after ;
still got random error bad comment in panel due also. but the bad command number always changing.
i use paneldue firmware 1.24 with nologo versioni also flashed it once again and the problem still there. reset it and nothing changes
-
Are the errors showing up in the DWC gcode console or only on the Paneldue?
-
@Phaedrux for the error zprobe.in is not free found the problem
i declared with m558 and then i also declared with m574 so i removed the m574. error in dwc is disappeared. trying bltouch still ok. so it must be the problem. thanks about thisbad command just in paneldue. it is random bad command code. i have video about it. how to send video to this forum?
must linked to youtube? -
If it's an MP4 you can upload direct to the forum now.
I understand the problem you're describing. As I said it's very similar to previously reported false errors.
Can you post a photo of how your wiring is routed?
-
sorry for my late reply, lately i change my cable route. i take it away from motor cable and fan. but i did not changing the cable. this morning i got random change tool once again.
this night i already changed the cable. hope this problem really dissapeared
i will update it after several days
-
@Phaedrux hello, after change the cable the problem show up today.
suddenly it said no tools selected. i change the cable to STP LAN cable.
there is no body around to taps the screen eitherbtw this problem exist when i upgrade to wdc 3.x
with 2.0 there is no problem like this.any option what i must check?
-
@Phaedrux check with M98 P"config.g" in the console there is no error found.
paneldue first boot no error found. but if i tap the stop button, bad command always show up. the number of bad command is random.this one not resolved, it might one of the sympthoms why my attempting extruder no tool happened.
frustrated....
-
@lifeform If you tap the Stop button the error message is expected. Reason for this is that the stop button will send the command together with a checksum (as every command does) but RRF has changed a while back that when it sees
M112
it will react immediately not even waiting for the checksum. Then it will try to parse the checksum as a new command which of course is invalid hence the error message for this case. This cannot be changed though because PanelDueFirmware has to work with older RRF versions that still expect the checksum.As to why you see other errors like this I have no good answer.
-
@wilriker noted... the real problem is random change of heater extruder from active to standby. and there is no confirmation or anything. that cause my printing is failure.
thanks a lot for your explanation. i describe all the weird behavior that might can help someone notice my real problem
thanks, so the bad command is nothing to do with my real problemlooking another reaso, fighting ha ha ha