Posts made by JADoglio

@Phaedrux
Side note: We have gotten pretty off topic at this point, sorry about that, and I am sure there is probably a better string for this discussion. If you want to move it, please do. As your systems are open source, and used and modified by many for their custom purposes I am sure their is a need to continue updating and doing other things as Duet does today. Your devices are popular, well built, and very well supported and there is also a user base that does not care about the open source, or customization opportunities with your hardware. We are just end users looking for a reliable solution to a need. From that perspective, I offer the following comments.

Thanks again, One last suggestion.

If the link in the DWC system-specific tab actually was a "Check for Updates" link that looked at the Github repository, then verified if an update was available or not, and then it gave the user the option of downloading the update and automatically installing it, or not, that would be a huge help for users. That would probably save you all a lot time not having to answer these kind of questions because the right files would be downloaded and installed for the right hardware without the user needing to know any of the specifics.

Github is a great repository for all sorts of technical computer programming/development information. However, it can be very intimidating for many/maybe most, of your users. For me, it has been a very slow learning curve as nothing about navigating Github is obvious. I am a PC computer savvy user (started with an Apple II Plus in 1980). I also have some programming knowledge and a lot of web experience. And even with that, I am just starting to be mostly comfortable navigating Github. When Duet started out, I am sure Github was great/invaluable for the people using it.

Today, people are using your hardware for a lot of things. We have a job to do and we just want do it. We want the systems needed to just do the work and if they need updating periodically, we want them to update behind the scene, without a lot of need to know how it is being done. We just want our hardware to work. I guess the short version of what I am saying is that I think a lot of people using Duet hardware today just wants to know what time it is, we have no inclination to build a watch.

You have a phone and, I am sure, many computers. The programs on those devices update constantly. While that is sometimes annoying, it is at least seamless and does not require me to know anything about the program or how it is being updated.

As I noted at the beginning, this is concept is somewhat antithetical to the whole open source concept, but I think/hope they can both live in harmony making Duet hardware more attractive and easier to manage to a larger user base. Sorry for the long note, but I have been thinking about this since my first update on my Duet 2 WiFi over 4 years ago.

Thanks again for all your help over the past several years.

@Phaedrux Thanks again, I tried to do install procedure 1. I never did find the IAP file. Short editorial, as this is mandatory file to complete the install, it seems like it should be as easy to find as the bin file? You guys really do a yeoman's job keeping us all going, but as this is the second time I have had issues finding this file.. I am just saying.

In the Github repository I did find the Duet2Combinedfirmware.bin file. When I uploaded that, 3.5.1 installed as it should and the firmware and DWC are now both on 3.5.1.

On the original install of 3.5.1 I went to the github page using the link on General tab. I did not realize that that only took me to the DWC update file and not the firmware. So, it was doing what I was telling it to do, I just did not realize that.

As I understand it, you normally recommend updating both the DWC and the firmware and keep them on the same versions. If this is correct, then it would seem that the link should take me to a page where I would download both. As I am a long way from any kind of expert on how other people use these boards, maybe the link makes sense as is. In that case, perhaps adding another link to the combined DWC and the firmware download page could also be added.

Thanks again, I am not being critical, like I said you and David and whoever else are helping you do a great job. I always appreciate the support you all provide.

Jim

@Phaedrux Thanks...I tried here are the results

I also then reinstalled 3.4.6. That installed and reset the DWC to 3.4.6. So, everything matched.

I then did a hard rest on the board powering off, then on.

I then redownloaded 3.5.1 and used the system tab upload to install it again.

Sadly, with the same result as before. Still showing firmware version as 3.4.6 and DWC as 3.5.1.

@Phaedrux I used the install update button on the machine-specific tab. I also, just tried to upload it again from the system tab and again, it installed without errors, but I still got the same result. I did not revert back to 3.4.6 first, not sure if that makes a difference. Thanks

@Phaedrux Thanks. I wound up finding another version of this file online and it seems to work fine. I suspect there was some hidden control characters in the other file messing it up. For the moment no need to pursue further.

However, I did download and install version 3.5.1 on my Duet 2 WiFi board. I down;oaded the zip from the Github page and used the installer in the DWC. It installed fine but when it was done it reported the following. I thought both the DWC and the Duet 2 should have updated to 3.5.1? Was this only a DWC update? Thanks

So, without changing anything else, I added a G28 to home after the Z offset probing commands. With just the G28 the system homes but the probe still does not retract. However, if I add a M402 command after the G28, the system does the G30 probes, then the G28 homes, then M402 forces the probe to retract. I also added manual G1 commands to the end of the file to retract the probe and those work as well. Not sure if that helps understand what is going on, but I hope it means something to somebody here because I should not need the last G28/M402 or the manual movements to retract the probe in this macro. At least I have a work around for the issue but I would like to understand why macro does not work as it should. Thanks for any help anyone might have.

;Z Offset Calibration Finish

M98 P"Check to see if probe is attached.g" 

G90												;set absolute

M401

G1 Z20											;raise Z up 20 mm

G30 S-1	F150									;(G30) home z (S-1) record z height

G4 P500											;pause .5 sec

G1 Z20											;raise Z up 20 mm

G30 S-1	F150									;(G30) home z (S-1) record z height

G4 P500											;pause .5 sec

G1 Z20											;raise Z up 20 mm

G30 S-1	F150									;(G30) home z (S-1) record z height

G4 P500											;pause .5 sec

G1 X175 Y175 Z25								;move Hot End to X175 Y175

M291 P"Check Consule for Results of Probing "  S2 ;instruct user to check results in Consol

G1 X63 Z20 F20000
G1 Y345
G1 X175
G1 Y175

;G28 Z

;M402

@Phaedrux Do you have any ideas why a macro would execute normally up until the last command line and then terminate without reporting an error and without executing the last command line in the macro (in this case M402)? It seems not executing all lines in the macro would create some kind of abend that would trigger some kind of error? Thanks

@OwenD Thanks for the input. See comments below.

So your condition is going to return true any time the micro switch is not actually pressed if it's an N/O circuit and likewise return false if it's an N/C circuit
How is it defined in config.g?

Config.g M558 P5 C"^io2.in" H10 A10 S0.005 F1200:150 T18000 ; set Z probe type to switch type for Voron PCB Klicky on pins IO_2.in and the dive height (H10)
Switch is NC

You can check in the object model browser which value you have during the process.
When connected as a NC switch the probe value is 0. When triggered it is 1000

I would have thought you'd be checking if the probe was attached rather than whether it's "active" ?
Semantics.. I used active/attached interchangeably in this case, attached is more descript.

EDIT
Your code seems to assume that as soon as the probe is picked up you get a value of 1000. When picked up, as noted above, the probe value is 0. The code doesn't assume this, that is what happens.

That may be possible, but as stated the value is meant to be an indicator of whether the switch is depressed by touching the bed.
If the probe is docked and not electrically present do you get a null value? Sorry, not sure what this is asking.
That may be a way to check if it's attached.

Also it's much better to put your code in blocks rather than as attachments Thanks will use this in the future.

@Phaedrux Thanks. I just did that (M291 P"Check Consule for Results of Probing " S2) and it did block and ask for OK to proceed, when I clicked on the OK the system just cleared the message and then stopped. Probe still not docked.

BTW, if I manually issue a M402 the probe docks as it should. But if I include M402 in the file, it just reports "Probe Retract Failed"

I am running a Duet 3 Mini 5+ (Mini5plus)
Firmware: RepRapFirmware for Duet 3 Mini 5+ 3.4.6 (2023-07-21)
Duet WiFi Server Version: 1.27
Probe: PCB Klicky

I included the set of macros I use for determining my Z offset. The first file is used to start the process and then bed.g is called to tram the bed, then the finish macro runs the G30 probing to determine the offset.

Everything runs as expected, except that at the end of the Z Offset Calibration Finish file either the hot end just stops after the M291 command and the probe does not retract, or I get a message "probe failed to retract". Which one depends on what I put after M291. The current version just stops and does not retract with no message. If I use M402, or M98P"retractprobe.g" I get the error. I even tried adding a g28 at the end. With that, it did the homing but still did not retract the probe.

Any ideas to get this probe to retract after this routine would be appreciated. Thanks

_Z Offset Calibration Macro.txt
bed.g.txt
Z Offset Z Calibration Finish.g.txt
retractprobe.g.txt

@moth4017 Thanks. That pretty well answers the question. I am buying an Omron and will start over. I suspect it will help.

As always, I am never quite sure where to ask questions. So, if this is the wrong group, please point me in the right direction. I built a new klicky probe for my Voron 2.4 running Duet 3 Mini 5+ hardware and DWC 3.4.6. I bought cheap Chinese switches instead of the Omron (my mistake). The switches seem to be less accurate than the Omron I was using , as it seems to often take more probe attempts to get a good reading.

I did a probe repeatability and got these results;
M292 G32 bed probe heights: -0.090 -0.094 -0.094 -0.097 -0.097 -0.097 -0.090 -0.090 -0.094 -0.094 -0.094 -0.094 -0.092 -0.094 -0.094 -0.097 -0.099 -0.097 -0.094 -0.092 -0.090 -0.092 -0.096 -0.094 -0.097 -0.094 -0.092, mean -0.094, deviation from mean 0.003. These results seem pretty good to me, but if anyone can confirm that, or tell me what they should, be that would be appreciated.

@gloomyandy Thanks. That was the source of the issue. I figured out how to get around it. I appreciate the help. Regards, Jim

@gloomyandy

It is a macro that is called at the start of a print. If the machine is already homed, it will not home again even though there is a G28 in the start g code file for the printer.

if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed ; if homed don't home again
G28 ; if not, continue homing

@dc42
David, thanks for the reply. Here is the file you asked for

retract attach probe.txt

gloomy,

The command to test for probe attachment is in the file. When I remove it, I get the same error

if sensors.probes[0].value[0] == 0 ; if sensor value is 0 do this, 0 = probe attached
echo "Probe already attached"

Thanks all

NOT SURE WHERE TO POST THIS SO I THOUGHT I WOULD START HERE. SORRY IF IT SHOULD BE IN A DIFFERENT CHAT!

My machine is a Voron 2.4r2.

Board: Duet 3 Mini 5+ (Mini5plus) with the 2 port expansion board

Firmware: RepRap Firmware for Duet 3 Mini 5+ 3.4.6 (2023-07-21)

Duet WiFi Server Version: 1.27

The Situation

When I issue a homeall.g command using DWC HomeAll Button. X and Y home as they should while Z homes but issues the error message below. The homing files are attached as is my config.g. As I am using a klicky probe I have written macros to check to see if the probe is attached before the execution of the most moves. During maintenance I seem to frequently leave it attached and that creates issues chasing it down when it gets knocked off.

The Issue

When I include G30 in the homing file I get the error message below. When I don't include the G30, Z moves to position to home, but does not home. I assume G30 is calling G28 which is why the firmware complains about it but then ignores it and does the homing anyway. I would like to find a way to make this home without getting the error. Is that possible?

4/2/2024, 4:08:46 PM M292
Error: G28 may not be used within a homing file
Probe already attached
Attach Probe Successful

config.g.txt
HomeAll Incuding X Y Z Files.txt

Not a huge issue but I suspect there is a simple solution.

Thanks

@fcwilt

Thanks appreciate the help.

@fcwilt

Thanks, Interesting. I got it working. Since I am inside my home network I assume this is a secure connection? Is that correct? I know FTP is a pretty obsolete protocol and as a general rule is not very secure. Thanks again and I look forward to any other comment you might have.

Jim

Not sure exactly where to post this si I will start here. It would be useful to have both save and save as buttons on the edit screens for system and macro files. Then you could not only save it to the SD card you could save a backup on your computer. In that regard it would also be useful to include a file download button on the system and Macro folder screens for the doing the same thing in bulk. I know I can use the SD card and a computer to do this but on my build it is not that easy to get to the SD card, so just a suggestion. Thanks

@LeeElms

Lee, I am not very familiar with its use but I believe M118 can be used for that purpose. You can also use the "echo" command in macros to sent messages to the console as he macros progress. No G code required and no parameters required. just add a line "echo "sending note to console"" and when it is read in the macro it will be sent. The following example is my current deployprobe.g file. Hope that helps.

M564 S0									; let travel outside print zone

if sensors.probes[0].value[0] == 0	; if sensor is value ia 0 do this, 0 = probe attached
		echo "Probe already attached"

if sensors.probes[0].value[0] == 1000		; if sensor is 1000 do this, 1000 = probe detached

	G1 X53 F20000						; X position of klicky dock
	G1 Y347 F20000						; Y position of klicky dock
	M400
	G1 Y175 F12000						; slide out of dock return to bed Y center
	G1 X175 F12000						; slide out of dock return to bed X center
	M400								;	wait for moves to finish
		
if sensors.probes[0].value[0] == 1000	;Check to see if probe is attached 1000 = not attached
	G1 X175 Y175 F10000  
	abort "Attach probe FAILED!"
else	
	echo "Attach Probe Successfull"
M564 S1