error:attempting to extrude with no tool selected while printing

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.

wilriker

@lifeform Some ideas:

Do these issues also appear if you do not activate serial communication on Duet, i.e. comment out M575?
Is your PanelDue inside a case that by chance might put pressure on the screen? This might result in random taps.

Also can you please restate your current issues. I feel they changed along the course of this thread and I lost track what is still left.

lifeform

@wilriker said in error:attempting to extrude with no tool selected while printing:

feel they changed along the course of this thread

hello, the main problem is just it is randomly changed from active tool to standby while printing. when it not printing this will not happened at all

before i post last night, i change a lot. change paneldue to 3.2 but it is beta when i try. and i change it back to the old firmware cause new paneldue firmware fit for rrf3.2 also

i also change the baudrate from 115200 to 57600, looks like the problem still exist but not often like before
i also change the cable. from 1m ribbon cable to connect mainboard to paneldue. i changed with stp cable. it is for LAN cable. i just found this cable and test it with 50cm long. the sympthom looks like more rarely show up

but a weeks ago, i print 8 hours long. not a really long printing object. but it can show 5 times. the last make me desperate cause i do not know the notification and the print failed.

@wilriker emm if i do not use serial how paneldue connected? looks like it happend with the lcd connected
my panel have screen guard before, now i remove it and the problem still show up yesterday. sorry for my long journey about this. sometimes it's not happened but lately it happened and make frustrated

lifeform

the last step i forcely select the tool again when tfree macro called.

but i know it is not solving problem. it is just for emergency.

also measured with my multimeter the resistant of the cable is 0.1

wilriker

@lifeform said in error:attempting to extrude with no tool selected while printing:

@wilriker emm if i do not use serial how paneldue connected? looks like it happend with the lcd connected

The main question I try to solve here is: does it also happen if there is no PanelDue in the first place. Or put differently: is PanelDue really the cause for your issue or is it something different?

lifeform

@wilriker said in error:attempting to extrude with no tool selected while printing:

put differ

oops sorry.. i got your poin now. so the first try i must do is disactivate the paneldue and print without paneldue and check if this problem still happen or not. will try in a week of printing. will update as soon as got the problem occurs

lifeform

@wilriker
tested without paneldue and print ok in several print part and in 5-6days trial
connect the paneldue again and it random change tool again

i used blv project for the printer. and looks like the led cable is cross with paneldue cable event i already used shielded cable and ferit.

now i forced to select tool 0 and cannot change to another
next try is separate and reroute the cable of the led at the front cover. and get messsage if the system change the tool accidently.

dc42

I think the issue is that the cable is picking up noise, causing data corruption, and the checksum is insufficient to detect some instances of data corruption. It's time to change the checksum to a CRC.