Multiple Errors Duet3

dk

Changed. I still cant extrude

droftarts

@droftarts

Changed. I still cant extrude

Are there any errors now if you run M98 P"config.g"? You need to reset Duet for changes to config.g to take effect, or run M98 P"config.g". If there are still errors, please post your current config.g, along with the list of errors reported.

Assuming everything is set correctly with no errors, to extrude you either need to heat up the hot end to a temperature above 160C, or allow cold extrusion with M302 P1 (see https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M302_Allow_cold_extrudes).

For the probe, you have already defined the servo pin with M950 S0 C"121.io0.out" ; create servo pin 0 for BLTouch in config.g, so it's unnecessary (and may cause confusion if you change the configuration later) in deployprobe.g and retractprobe.g. Delete the M950 line in these files.

Does the BLTouch do a self-test at startup? It should extend and retract the pin itself twice if it has power (which you say it does as the red LED comes on). If deployprobe.g and retractprobe.g still don't work, try inverting the input in config.g with '!', ie M950 S0 C"!121.io0.out". You can either send this command in the gcode console (and add it to config.g if it works), edit config.g and reset Duet, or edit config.g and run M98 P"config.g" for the command to take effect. If it still isn't functioning, check the wiring, and post a picture of how it's wired.

@dk said in Multiple Errors Duet3:

Can I find somewhere configuration files for any real working Delta printer on Duet3 with Tool board?

We don't have a machine with this configuration to share a working config with you. Many home-built printers are bespoke, and it's possible that you are the first with this combination! If there are any other users who see this and have a similar setup, please share your config files.

Ian

dk

@droftarts

I have change Toolboard address to 20 following this procedure See https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board#Section_Set_the_CAN_address , and change M569 P20.0 S1
Now I can extrude.
I also change address for heater and Thermistor and gget them work to!
M308 S1 P"20.temp0" Y"thermistor" T500000 B4723 C1.19622e-7
M950 H1 C"20.out0" T1

And I also change address for BL-touch (with and without ! ) and delete M950 line from deployprobe.g and retractprobe.g files. But it's still don't work.
; Z-Probe
M950 S0 C"20.io0.out" ; create servo pin 0 for BLTouch
M558 P9 C"20.io0.in" H5 F120 T1000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X20 Y25 Z3 ; set Z probe trigger value, offset and trigger height
M557 R160 S40 ; define mesh grid

And BLTouch does not self-test at startup. Just steady red light. I connect it to Duet2 I have on another printer and it perform startup test as usual.

M98 P"config.g" give me just one warning (no Errors any more)
Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C

So I assume the problem is in Z-probe settings

Phaedrux

Does the BLTouch power up if you connect it directly to the main board and change your pin names accordingly?

dk

@Phaedrux
Yes, it does

Phaedrux

Do you have a different BLTouch that isn't V3.1 to test with on the tool board?

dk

@Phaedrux

I have 3 BL-touch 3.1 And I test all 3 of them. They all work with IO_7 and doesn't work with Toolboard

dk

@Phaedrux
When I change the white and yellow wire in places, BL-touch does self-test at startup. And Status window DWC shows Z-Probe 1000
But it still does not work. I can't extract pin. M280 P0 S10 has no effect.
And G32 give Error: Z probe already triggered at start of probing move

Z-Probe settings from Config.g:
M950 S0 C"20.io0.out" ; create servo pin 0 for BLTouch
M558 P9 C"20.io0.in" H5 F120 T1000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X20 Y25 Z3 ; set Z probe trigger value, offset and trigger height
M557 R160 S40 ; define mesh grid

; deployprobe.g
M280 P0 S10 ; deploy BLTouch

; retractprobe.g
M280 P0 S90 ; retract BLTouch

Phaedrux

@dk said in Multiple Errors Duet3:

When I change the white and yellow wire in places

What do you mean by this?

dk

@Phaedrux
Swap these two wires

Phaedrux

Ah ok, so you had the io in and io out swapped.

Since it says it's already triggered you could invert the signal pin, but I don't think that should be necessary.

Try adding an ! to the pin name. M558 P9 C"!20.io0.in"

That should get rid of the already triggered error, but do carefully test that touching the deployed pin halts movement.

https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Dynamic_test

dk

@Phaedrux

No, with ! Status window DWC shows Z-Probe 0
But it did self-test at startup.
Should I chenge any other settings ?

; Z-Probe
M950 S0 C"20.io0.out" ; create servo pin 0 for BLTouch
M558 P9 C"20.io0.in" H5 F600 T1000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X20 Y25 Z3 ; set Z probe trigger value, offset and trigger height
M557 R160 S40 ; define mesh grid

dk

@Phaedrux
When I connect BL-touch to IO_7 it works. So I think the problem is in Toolboard

dc42

@dk, please can you do the following tests:

Connect the BLTouch to the tool board as usual, but instead of connecting the BLTouch control wire (orange or yellow) to IO0_OUT, connect it to ground along with the 2 wires already connected to ground. Then check whether the BLTouch does a self test when you power up the tool board.
Repeat but with the control wire connected to +5V on the IO) connector instead of ground. Does it do a self test at power up?

Note, in either case deploy/retract commands won't work, so don't try probing!

dk

@dc42

If I connect control wire (orange) to ground BLTouch does not perform a self test at power up. It flashes rapid red.
If I connect control wire (orange) to +5 I get same result: BLTouch does not perform a self test at power up. It flashes rapid red.
And if I connect BL Touch folowing this instruction
https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board#Section_Connecting_a_BL_Touch Connecting a BL Touch
it also doesn't perform a self test at power up. It just glows steady red. And several times in one minute red light turns off for 2-3 second.
I try both options, with and without ! in M558 command.
The only time BLTouch does self test at power up is when I connect orange wire to io0.in and white wire to io0.out without ! in M558 command (as shown at the foto above)

dc42

Thanks, this thread is very long and I I missed the post in which you said that after correcting the wiring of orange and white wires to io0.out and io0.in, it does the self test.

Is the problem now that the firmware doesn't recognise when it is triggered? If so, you could try changing the M558 line to this following, although it shouldn't be necessary:

M558 P9 C"^20.io0.in" H5 F600 T1000 ; set Z probe type to bltouch and the dive height + speeds

Does it deploy and retract when you send M401 and M402?

Please use M115 to confirm the firmware version on the Duert 3 main board (should be 3.1.1), and M115 B20 to confirm the firmware version on the tool board (should be 3.1.0).

dk

@dc42
But this instruction and picture https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board#Section_Connecting_a_BL_Touch
shows Orange wire to io0.out and white to io0.in. Not vice versa as I did by mistake and get BLTouch does perform a self-test at power-up. So orange and white wires work similarly and they can be interchanged?

dk

@dc42 said in Multiple Errors Duet3:

M558 with ^ doesn't change anything.
M401 and M402 doesn't work in both cases (I swap orange and white wires 2 times).

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-05-19b2

M115 B20
Board TOOL1LC firmware 3.1.0 (2020-05-15b1)

droftarts

@dk Thanks for your patience. We think your Toolboard may be faulty. I authorise a warranty replacement. Please contact the supplier, and follow their warranty process, quoting this thread as evidence and authorisation for the warranty replacement. Apologies for the inconvenience.

Ian

dk

@droftarts
I also think about the board faulty, and already bought one more Toolboard and test it - same exact result.