well, I just made a short test in which I unplugged the Pendant and plugged the PanelDue as usual. The Macro in this configuration works just fine. So, apparently, it is a problem with the Pendant. I will post the problem over the Pendant post.

The closest thing I‘ve seen similar to what would be using Stall detection as a Z probe is the Smart Effector on a Delta. It is not the same, as it is based in some other phenomenon, but you effectively use the nozzle tip a sensor. Maybe one could design a carriage for a cartesian printer this this technology??

BTW, buying the Smart Effector for my Delta was one of the best decisions I‘ve done (3D Printing related, that is).

Well, I did change the trigger height to 16.25 and re-run the delta calibration. The Delta Height changed by 0.2mm (or so). I approached the nozzle to the bed until Z=0 and, sure enough, I got nice paper grab...

Thanks a lot, everybody

Yesterday I noticed something weird while using the pendant. The multiplier knob was set at x10 and, not thinking about it, I tried to move the Z axis. Because I turned the wheel too much, I got a message on the display telling me to chill out (paraphrasing here) because I wanted to move more than the axis allows. So far, so good. However the X axis moved a little bit instead, even though the Z axis was selected on the axis knob. Now that's weird. Once I switched to x0.1 multiplier, the Z axis moved ok.
Knowing that, I'll be more careful from now on, but I am really curious if this is a "global" bug or it is just me.

I am using an Arduino Nano and I changed the resistor on it in order for the bypass of the display to work. The Arduino Pro Micro I ordered came when the Pendant was already assembled, so I saw no reason to open it up again. Also, I did not update the firmware to the latest version, as I understood it was only Pro Micro related and I didn't see a point on doing it.

Cheers!

well, if anyone is following this thread, I just want to mention that it has been solved.

The issue was the name of the macro together with the firmware version of the Paneldue. I changed the name of the macro to be just text and it worked fine. And just for the sake of it, I updated the firmware to the latest version. Everything works just fine now.

@JoergS5 thanks, T0 is at the very end of the config.g file, not shown on the snippet above.

@jay_s_uk that seems to have been the issue, apparently. I added the example line shown on the wiki and it appears to work ok:

M584 X0 Y1 Z2:3 E4:5:6

I wonder why did it work without that line previously...

aren't you missing something?. The error tells you exactly what is happening. Instead of looking to your config files, check the continuity of you motor cables. I got this error once and it pop up because one of the motor cables was pinch by the printer's frame and eventually was severed. I repaired the cable and everything was fine.

Well, i mixed the code on the 3 independent homing files into one homeall.g file (see below). It appears to work without any issues...

I hope this post helps somebody else with similar issues.

Thanks a lot, everyone.

; homeall.g
; called to home all axes

;M98 Phomex.g
;M98 Phomey.g
;M98 Phomez.g

G91			; set relative mode
G1 S2 Z5 F1200 		; lift Z
G29 S2                  ; to clear the height map before Z homing
M561                    ;reset bed compensation


; homex.g

G1 S2 X0.2              ; Move X by 0.2 mm, clear stall status

M400 			; make sure everything has stopped before we make changes
M913 X60 		; X motor % current
M915 X S2 R0 F0 	; set X sensitivity, do nothing when stall, unfiltered
M574 X1 S3 		; set endstops to use motor stall
G1 S1 X-220 F3600 	; move X back, stopping at the end stop

M400 			; make sure everything has stopped
M913 X100 		; XY motors to 100% current

M915 X S30 R0 F0 	; set X sensitivity high, do nothing when stall, unfiltered

M400; 			; make sure everything has stopped




; homey.g


G1 S2 Y0.2              ; Move Y by 0.2 mm, clear stall status

M913 Y75 		; Y motor % current
M915 Y S3 R0 F0 	; set X sensitivity, do nothing when stall, unfiltered
M574 Y S3 		; set endstops to use motor stall

G1 S1 Y-220 F3600 	; move X back, stopping at the end stop

M400 			; make sure everything has stopped
M913 Y100 		; XY motors to 100% current

M915 Y S30 R0 F0 	; set Y sensitivity high, pause when stall, filtered

M400; ; make sure everything has stopped




homez.g


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

@phaedrux ... I guess I should start reading the release notes from now on... thanks!

@Phaedrux thanks a lot for your help. Actually shortly after I posted the question I found where the problem was. The command disabling the heated bed was being called twice. I cleaned it up and now everything seems to be working just fine. Thanks a lot again!

@dc42 would the G31 command not work on that situation?

@phaedrux from the time I started with 3D printers, I used to find really difficult to adjust the nozzle Z-Height by moving the Z-Endstop up and down. That's the main reason I tended to do it that way. I am not saying it is not possible, but I am unable to physically move one endstop on an Al-Profile by 0.x mm. Even if I loosen it up, and move it, say, 0.2mm, by the time I tighten it again, the forces upon the screw have already moved it...

anyway... I've made some progress yesterday and today. The main problem was that actually one of the wires on one motor was not crimped correctly. After that, I only had to adjust the code I was given. After modifying the endstops configuration and axis configuration, I had to modify the homeall.g and the homey.g files, which I attach here for future reference:

homeall.g

G91 ; relative positioning
G21 ; Set units to mm
G1 H1 Z{move.axes[2].max*2} F900 ; move quickly to Z axis endstop and stop there (first pass)
G1 H1 X{move.axes[0].max*2} F2400 ; move quickly to X axis endstops and stop there (first pass)
G1 H1 Y{move.axes[1].max*2} F2400 ; move quickly to Y axis endstops and stop there (first pass)

M584 P4 ; set 4 axis CNC
M669 K0 X1:0:0:0 Y0:1:0:0 U0:0:0:1 Z0:0:1:0 ; enable speed for U axis
G92 X{move.axes[0].max} Y{move.axes[1].max} U{move.axes[3].max} Z{move.axes[2].max} ; Set Home Position

G1 X-3 Y-5 U-5 F2400 ; go back a few mm in Y and U
G1 Z-3 F900 ; go back a few mm in Z
G1 H1 Y{move.axes[1].max*2} U{move.axes[3].max*2}F300 ; move slowly both Y and U axis enstops and stop there (second pass)

G1 Y-0.23 F150 ; fully align gantry IMPORTANT move only in negative direction (select Y or U and change accordingly)

G92 Y{move.axes[1].max} U{move.axes[3].max} ; set Y and U home Position

M584 P3 ; set 3 axis CNC
M669 K0 X1:0:0:0 Y0:1:0:1 Z0:0:1:0 ; enable Y speed for U axis
G1 H1 X{move.axes[0].max*2} F300 ; move slowly to X axis endstops once more (second pass)
G1 H1 Z{move.axes[2].max*2} F300 ; move slowly to Z axis endstop once more (second pass)
G92 X{move.axes[0].max} Y{move.axes[1].max} Z{move.axes[2].max}; Set Home Position
G90 ; absolute positioning

homey.g

G91 ; relative positioning
G21 ; Set units to mm
G1 H1 Z{move.axes[2].max*2} F900 ; move quickly to Z axis endstop and stop there (first pass)
G1 H1 Y{move.axes[1].max*2} F2400 ; move quickly to Y axis endstops and stop there (first pass)

M584 P4 ; set 4 axis CNC
M669 K0 X1:0:0:0 Y0:1:0:0 U0:0:0:1 Z0:0:1:0 ; enable speed for U axis
G92 Y{move.axes[1].max} U{move.axes[3].max} Z{move.axes[2].max} ; Set Home Position

G1 Y-5 U-5 F2400 ; go back a few mm in Y and U
G1 Z-3 F900 ; go back a few mm in Z
G1 H1 Y{move.axes[1].max*2} U{move.axes[3].max*2}F300 ; move slowly both Y and U axis enstops and stop there (second pass)

G1 Y-0.23 F150 ; fully align gantry IMPORTANT move only in negative direction (select Y or U and change accordingly)


G92 Y{move.axes[1].max} U{move.axes[3].max} ; set Y and U home Position

M584 P3 ; set 3 axis CNC
M669 K0 X1:0:0:0 Y0:1:0:1 Z0:0:1:0 ; enable Y speed for U axis
G1 H1 Z{move.axes[2].max*2} F300 ; move slowly to Z axis endstop once more (second pass)
G92 Y{move.axes[1].max} Z{move.axes[2].max}; Set Home Position
G90 ; absolute positioning

the problem I found is that after reassigning the axis with the M584 and M669 commands, the homing is lost. Even if I want to split the combined Y into Y and U for the autosquaring, when the M584 followed by the M669 command is executed, all the homing are lost, even X and Z.

Now, as I was collecting the info for the update, I remembered that on my 3D printers I am able to set an offset for the Z probe with the G31 command. I was wondering if I could use this G31 command to set offsets for the Y and U axis. That way, I guess I could skip the moving of one of the axis "manually" ?? or am I missing something here?

Thanks a lot!

@phaedrux to be honest, when I saw all the code I had to modify, this was my first thought… but I wanted to try it programmatically, as it would have more room for fine tunning

Hi all,

for a long time I wanted to add some kind of auto-squaring function to the Workbee. So much so, that I already routed the cable for the Endstop on the Left-Side Y axis.

I assumed it was just a matter of plugging the Endstop, set some sort of Endstop offset and be done with it. However, I stumble upon this post here where it is explain that there are no Endstop offsets but there is a workaround, because of course there is one.

I contacted the people at Ooznest and they sent me come code another user was using successfully and, as far as my ignorance can realize, looks like this user is doing what @dc42 explains on the other post. The code they sent me is as follows:

Homeall.g
; homeall.g
; called to home all axes
G91 ; relative positioning
G21 ; Set units to mm
G1 H1 Z{move.axes[2].max*2} F900 ; move quickly to Z axis endstop and stop there (first pass)
G1 H1 X{move.axes[0].max*2} F2400 ; move quickly to X axis endstops and stop there (first pass)
G1 H1 Y{move.axes[1].max*2} F2400 ; move quickly to Y axis endstops and stop there (first pass)
G92 X{move.axes[0].max} Y{move.axes[1].max} Z{move.axes[2].max} ; Set Home Position
M584 P4 ; set 4 axis CNC
M669 K0 X1:0:0:0 Y0:1:0:0 U0:0:0:1 Z0:0:1:0 ; enable speed for U axis
G1 X-3 Y-5 U-5 F2400 ; go back a few mm in X Y and U
G1 Z-3 F900 ; go back a few mm in Z
G1 H1 Y{move.axes[1].max*2} U{move.axes[3].max*2}F300 ; move slowly both Y and U axis enstops and stop there (second pass)
G1 U0.0 F150 ; fully align gantry IMPORTANT move only in negative direction (select Y or U and change accordingly)
G92 Y{move.axes[1].max} U{move.axes[3].max} ; set Y and U home Position
M584 P3 ; set 3 axis CNC
M669 K0 X1:0:0:0 Y0:1:0:1 Z0:0:1:0 ; enable Y speed for U axis
G1 H1 X{move.axes[0].max*2} F300 ; move slowly to X axis endstops once more (second pass)
G1 H1 Z{move.axes[2].max*2} F300 ; move slowly to Z axis endstop once more (second pass)
G92 X{move.axes[0].max} Y{move.axes[1].max} Z{move.axes[2].max} ; Set Home Position
G90 ; absolute positioning



config-axes-calibration.g
; Axes Calibration configuration executed by config.g
M92 X400 Y400 U400 Z400 ; Set steps per mm



config-axes-endstops.g
; Endstop configuration executed by config.g
M574 X2 P"!xstop" S1 ; Set active low X endstop
M574 Y2 P"ystop" S1 ; Set active low Y endstop
M574 U2 P"e1stop" S1 ; Set active low U endstop
M574 Z2 P"!zstop" S1 ; Set active low Z endstop



config-axes-limits.g
; Axes Limits configuration executed by config.g
M208 X0 Y0 U0 Z0 S1 ; Set axis minima (ADDED U Axis 211225)
M208 X1311 Y1245 U1245 Z120 ; Set axis maxima (ADDED U Axis 211225)

however, when I try to use it, the CNC is stuck with the U axis as well, because it appears on the web interface. It does the first Y-axis homing and only stops when the "old" Endstop is triggered. Then it switches to 4 axis (line 10 of the code above, I guess). However then the console throws the errors (paraphrasing here):

• G0/G1: insufficient axis homed
• G28 Y Warning: motor phase A may be siconnected reported by driver(s) 1 3

I am guessing I have some errors with the M669 command, as the other Ooznest user might not have wired the motors as I've done. I looked into the documentation on M669, but it wasn't clear for me.

My wiring setup is as the picture below shows:

any help on sorting this out would be much welcome. I just wished there were Endstop Offsets to make life a bit easier...

Thanks in advance!

@o_lampe sounds great and simple, but am I right to think you are working with a 3D printer setup?

@o_lampe

Felix, would it be possible to go through a real tool change? Then you could free the laser pin in tfree.g* while you are still in laser mode.

I will try it when I get back home, yeah. Thanks!

@radiomodell thanks a lot for your snippets! As it so happens a couple of days ago, I came out with nearly the same ones on another thread: https://forum.duet3d.com/topic/19842/weird-laser-mode/36?_=1640511378171

And they work very fine.
Thanks again!

well, just as usual after I posted something I myself come up with an improvement...

I changed the macros as follows:

Laser focus ON

M106 P2 S255  ; turn on laser's 12v PSU

 
M453   ; Enable CNC Mode

M950 P0 C"!exp.heater3" Q1000   ; assign laser pin to a pin number

M42 P0 S0.01  ; set 1% PWM on GPIO port 0


; do the focusing stuff

Laser Focus OFF

M42 P0 S0 ; disable laser

M950 P0 C"nil" ; free heater3 again for use in laser mode

M106 P2 S0  ; turn on laser's 12v PSU

And I changed my "switch to CNC macro to:

M5 
M106 P2 S0  ; turn off 12v PSU
M452 C"nil" ; free "exp.heater3" pin
M453 ; Put the machine into CNC Mode

M550 P"WorkBee CNC Machine" ; Set machine name

in which I added the M452 C"nil" line.

This seems to work, although when I go back to CNC mode the console throws a red warning:

Error: DueX fan or GPIO pins may not be used to control lasers

but well, it looks like I will have to live with it. On a positive side, I think that the M42 command lets me control the power of the laser somehow better. Yesterday I used it "the old way" with a Fan port and even a M106 P3 S0.001 would start burning the plywood after a couple of seconds.

@phaedrux following the original poster's suggestion, I prepared two macros for that:

FOCUS LASER ON

M106 P2 S255  ; turn on laser's 12v PSU


M451   ; disable Laser Mode

M950 F3 C"nil"     

M950 F3 C"!exp.heater3" Q1000   ; assign laser pin to a free fan Numbe

M106 P3 S0.001 ; enable laser with 1% power 


; do the focusing stuff

FOCUS LASER OFF

M106 P3 S0 ; disable laser


M950 F3 C"nil" ; free heater3 again for use in laser mode

M106 P2 S0  ; turn on laser's 12v PSU

it works ok. My problem is now that I have to do the focusing BEFORE switching to Laser mode with:

M452 C"!exp.heater3" S1 F200  

If I have done something in laser mode and I have to refocus or pinpoint another work origin, even if I switch to CNC mode it throws an error telling me that the pin "exp.heather3" is occupied (or assigned, I don't remember). So, how do "unassign" the pin when I switch from Laser mode to CNC mode?

Sincerely I can understand the safety concerns behind not being able to use M3 while not moving, but at the end of the day, if I have a laser I have to be able to set it onto the correct origin and also focus it. Even I am not able to do that with a M3 command, I have been able to do find a workaround.
I think this is an issue it should be addressed. It makes working with a laser cumbersome and overly complicated if you are not use to tinker with the RRF3 environment. Maybe a solution would be limit the power output of the M3 command to 1% when stationary? Just an idea...

So @pauledd how do you focus your laser now?

I need to do some engravings today and I haven‘t used the laser since I updated the RRF to 3.3, so I fear I will have some troubles there.

I understand the safety issue behind, but I used to use the laser at 1% power to align it with my work and also focus. I don‘t understand how I am supposed to do it now if the laser can only be ON while moving…