In addition to @bearer here is the topic where all originated:
https://forum.duet3d.com/topic/11389/cnc-style-pendant
I have one of these with a modified Arduino Nano (a SMD resistor has to be changed) working together with the Panel Due. It makes a world of a difference how easier it is now to jog around...
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, 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.
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
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, 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.
So, the printer has undergone several Y-homings since I changed the speed and has suffered 0 fails, so I would say the issue is solved. Thanks again!
Well, I finally got the time to do some experimenting. If I understood that correctly, I was mistaken regarding the G10 command. It seems it's like this:
P1 is G54 (WCS #1)
P2 is G55 (WCS #2)
etc.
I sounds like motors not correctly wired to the board. Make sure that the coils are correctly paired...
@Phaedrux said in Move command not executed from PanelDue + Pendant:
And firmware version on the Duet?
RRF2, this one I got it right, I'm sure... 
@Phaedrux said in Move command not executed from PanelDue + Pendant:
1.24 maybe?
yes, certanly. I was talking on the top of my head earlier. I knew there was a 2 and a 4 somewhere...
So sorry, I missed that.
RRF2 and PanelDue 2.4, I think
Hi all,
I have a PanelDue with a CNC Pendant on my Duet driven Workbee. I have a macro to rapidly move to the current WCS origin. It is as simple as this
G28 Z
G1 X0 Y0
The macro is not executed from the PanelDue, but if I send the G1 command from the web interface is no problem.
Any idea on what the problem could be?
@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!
Well just an update on my side. I finally finished upgrading my Workbee with a worthy electronics box where everything is well organized. I never liked it to have the controller board exposed and on the moving gantry.
Anyway, I've been able to put my laser to work by following the indications here. I used the brake-out board suggested and it works just fine. Amazingly enough, it worked on the first try, which for my standards is amazing to say the least.
I have a problem though when switching back to CNC mode and it is the following error:
M98 P"0:/macros/Laser/Switch to CNC"
CNC mode selected Error: G10: Attempt to set/report offsets and temperatures for non-existent tool: 999
The macro I'm using to switch back to CNC mode is the following, which is a mix between what I've seen and what I found on my config.g file
M106 P2 S0 ; turn off 12v PSU
M453 ; Put the machine into CNC Modes
M140 H-1 ; Disable heated bed
M564 S1 H1 ; Disable jog commands when not homed
M911 S21.0 R23 P"G91 G1 Z3 F1000" ; Configure power loss resume
M501 ; Load Stored Parameters
M98 Pcustomconfig.g ; Execute custom config settings
any clue in what is this about? it would be much appreciated!
@PopstarPorcupine thanks a lot for your info. I prepared the mentioned board and I used the heated-bed PWM port. I still have to bring it on-line, however. Not tried it yet. I've been really busy preparing a new electronics box for my Workbee with the Duet, the SuperPID and everything else... I think your snippets will be much uselfull. Thanks a lot again.
EDIT: what about the Lightburn software? is it worth it? There are not many options for for mac users, Lightburn beign one of the few I found...
Hi all again,
I am today trying to wire the laser but, before I do I have a doubt regarding the following diagram:
https://duet3d.dozuki.com/Wiki/Laser_PWM_control
in this diagram, what is exactly HEATER_3 ?? It is the heated bed, extruder 1 or extruder 2 ?? Also, I am assuming is the "negative" pin of said heater, right?
So, the printer has undergone several Y-homings since I changed the speed and has suffered 0 fails, so I would say the issue is solved. Thanks again!