@Tool88 said in Duet 3 6hc canned cycle:
Also is reprap capable of i-0. J-0. Commands
I see the administrator responded
But I don't see a way to respond to thank you
A i-0.0 and j-.0
Would look something like
G03 x location i-0.234 j-0.0038
It's just a way to cut circle without having to do every arc move as a single step
Yes, RRF supports G2 and G3 using I and J parameters, see https://docs.duet3d.com/User_manual/Reference/Gcodes#g3-controlled-arc-move
Ian
@perfetto said in Configurazione bl touch antclabs:
Good evening thanks for the help, I installed firmware version 3.3 even worse the heaters do not work I will try version 3.5.4, I would like to point out that since 2020 the printer was working fine, even not being a veteran I decided to mount the bltouch on it.
Please post your config.g, and the response to M122. When you update to RRF 3.x, you have to update the config.g, as RRF 3 is different from RRF 2. You can downgrade back to RRF 2 if you find it too difficult. See https://docs.duet3d.com/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3
Ideally, update to the latest release 3.5.4, then use the configuration tool to make a new configuration set of files. Then we'll help you fix the issues.
When I configure RRF the limit switch of the Y am I right to disable it or can it also remain as a safety device,
Endstops are only used during homing moves, so most of the time they are disabled anyway. You can set them up as 'triggers', so that they pause the machine if they are touched. See https://docs.duet3d.com/User_manual/Reference/Gcodes#m581-configure-external-trigger
even with the new firmware version the pin 8 of the heater expansion port and it does not work, if I configure on the hot port and e1 = to e2 do I have to connect the wire to e1 pwm v_in?
Are you following the guide here? https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_BLTouch
See also the BLTouch troubleshooting guide here: https://docs.duet3d.com/en/User_manual/Troubleshooting/BLTouch_troubleshooting
Again, seeing your config.g would help. Make sure your deployprobe.g and retractprobe.g are correct, too.
Possibly it is advisable to switch to firmware 3.6 on Duet 2 Ethernet.
Yes, Duet 2 Ethernet will be supported by firmware 3.6, but it is still in beta at the moment. It should be releasing soon, though. Your config from 3.5.4 should work with 3.6 without changes.
Ian
@vaike_peeter please upgrade to 3.6.0-rc.2 and test again.
@Tool88 in RepRapFirmware you can define your own canned cycles using macro files. For example, RRF does not implement G84 internally so you can create a macro file called G84.g in the /sys folder of the SD card. That file will be executed when you send the G84 command and the parameters you provide will be passed to it.
The macro file may contain regular GCode commands along with conditionals, loops and other special commands documented at https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands.
I am not familiar with the term "i-0. J-0. Commands. Please explain what you mean.
@marvineer I'm sorry, I can't reproduce that. I ran this macro file after power up, before any other motor movement and wihtur sending any M17 commands first:
; homey.g
; called to home the Y axis
G91 ; relative positioning
M400 ; make sure everything has stopped before we change the motor currents
M913 X20 Y20 ; drop motor currents to 20%
G1 H2 X2 F1800 ; move x so that the endstop is free to pass
G1 H1 Y-282 F3000 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y2 F1000 ; go back a few mm
;G1 H1 Y-5 F300 ; move slowly to Y axis endstop once more (second pass)
This is similar to your file except that I had to increase the speed of the G1 H1 move to F3000 because I am using stall detect endstops. The head moves diagonally for the 2mm move and in the Y direction for the homing move.
Could it be that 20% current is not always enough to move the motor on your machine?
@marvineer thanks, I'll take a look at it.
@sebkritikel this is expected, because of the flyback diodes connected in parallel with the fan output pins.
If you want to connect a fan or other load between the OUT- pin of an output connector and a positive supply other than the positive supply pin of the OUT connector, the voltage you supply should be lower or the same as the voltage supplied on the OUT connector (which on most Duet 3 boards is selected by the VOUT_LC jumper).
For example, if the VOUT_LC jumper that supplies the OUT connector is set to VIN and VIN is 24V then it is OK to connect a fan between +12V and OUT-. But if VOUT_LC is set to 12V then you should not connect a fan between +24V and OUT-
@sebkritikel I think I've seen the same thing once before, on a 6XD, and yes, it's a hardware limitation. See https://forum.duet3d.com/post/345691
I believe the 6HC is wired the same. It's because you're feeding 24V into OUT_4_NEG, but other fans are jumpered to 12V. I'll double check and update the docs. Thanks!
Ian
@tcamguil I believe I have fixed the issue of the U axis not moving. Please try the 3.6.0-rc.2+2 firmware at https://www.dropbox.com/scl/fo/nlkfneaas1osgtdw37s17/AIS_H0KSAKCmfYSjSRTSOAE?rlkey=ad4omnq36zkdz3wl8i7kthqqt&dl=0.
@crpalmer I have provided main board firmware 3.6.0-rc.2+2 binaries at https://www.dropbox.com/scl/fo/nlkfneaas1osgtdw37s17/AIS_H0KSAKCmfYSjSRTSOAE?rlkey=ad4omnq36zkdz3wl8i7kthqqt&dl=0 which incude this fix.