error:attempting to extrude with no tool selected while printing

lifeform

@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)
G30

this 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 position

G90 ; absolute positioning
G1 X205 Y164 F6000 ; go to first probe point
G30 ; home Z by probing the bed

lifeform

@Phaedrux

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

Phaedrux

@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?

lifeform

@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 this

tpre, 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

@Phaedrux

btw the error Error: Pin 'zprobe.in' is not free is still exist when m98 P"config.g" send in console. i really do not get it why the error still there. the bltouch working properly

Phaedrux

@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.

lifeform

@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 version

i also flashed it once again and the problem still there. reset it and nothing changes

Phaedrux

Are the errors showing up in the DWC gcode console or only on the Paneldue?

lifeform

@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 this

bad 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?

Phaedrux

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?

lifeform

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

lifeform

@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 either

btw 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?

lifeform

@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....

wilriker

@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.

lifeform

@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 problem

looking another reaso, fighting ha ha ha

Phaedrux

Can you test with a much shorter 4 wire cable that isn't near any other wires just to verify that the paneldue is working properly in an idealized situation?

If it works in that case, then it will be a matter of finding cabling with low resistance and adequate shielding and interference rejection for your environment.

lifeform

@Phaedrux could you recomend what length which best for the paneldue cable?

Phaedrux

You can see your options here.

https://duet3d.dozuki.com/Wiki/Connecting_an_LCD_control_panel#Section_Option_1_Ribbon_cable

Testing the with ribbon cable could be instructive. 400mm recommended.
For a 4 wire cable it's 800mm recommended.

lifeform

@Phaedrux the problem still show up. at lately it more often. i have change the cable to STP lan cable used 4 cable only. i also make it shorter the cable is 50cm long only, before is 1.5m a weeks ago my problem is not occurs often. very rare but sometimes happened but this week it show more often.

is there any trigger event that when it change from active to standby i can forced it back to active?
any way to do it?

@dc42 any help about this. i have disperate to solve it with cabling

Phaedrux

Can you try updating your PanelDue firmware to the new 3.2 release

https://github.com/Duet3D/PanelDueFirmware

Please note this would also require updating your Duet firmware to 3.2 beta4 as well for best results.