Dave's so proud

fcwilt

; Endstops
M574 X1 Y1 S1 ; Set active low endstops
M574 Z0
M558 P9 X0 Y0 Z1 H5 F100 T2000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds
G31 P600 X0 Y12 Z.96; Set Z probe trigger value, offset and trigger height
M557 X52:300 Y60:335 S40 ; Define mesh grid

correct version and correct wording in config.g probe is unresponsive. a year of flawless performance under build 1.19.1 and now nothing.

The current docs for M558 report that the X, Y and Z parameters are obsolete.

Perhaps that is causing some sort of problem?

Frederick

sjason1377

I would never had upgraded except for those false heater faults he said was a bug from the old version. Now he's got no support for this problem because he won't admit there is one. That my issue. It take many failures from many user before he responds. History proves I was not at fault before. I'm not now either.

sjason1377

I'm not proud I'm not saying I have any answers. I know my spelling sucks. But I'm no liar. We depend on him to help with these issue. But where does that leave us when he won't help.

bot

Do you expect David to drop everything in his real life to help one of the rudest users ever to come on these boards?

You need to learn to be patient, and/or how to resolve issues yourself.

Danal

Ooops... just read the whole thread from the top.

BYE.

You want support from the community, you need a whole different attitude.

fcwilt

@sjason1377 said in Dave's so proud:

; Endstops
M574 X1 Y1 S1 ; Set active low endstops
M574 Z0
M558 P9 X0 Y0 Z1 H5 F100 T2000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds
G31 P600 X0 Y12 Z.96; Set Z probe trigger value, offset and trigger height
M557 X52:300 Y60:335 S40 ; Define mesh grid

correct version and correct wording in config.g probe is unresponsive. a year of flawless performance under build 1.19.1 and now nothing.

Do you have a Z endstop in addition to the Z probe?

In the M574 Z0 there is no S parameter - which indicates an active high endstop - is that correct?

Frederick

sjason1377

yes that's correct. I went back to p7 and it works now

sjason1377

@deckingman eat my load!

fcwilt

@sjason1377 said in Dave's so proud:

yes that's correct. I went back to p7 and it works now

Did you try the latest version after removing the obsolete parameters from M558?

And you do have a Z endstop in addtion to the Z probe?

Frederick

deckingman

@sjason1377 Thanks for this chat message

"hey decking eat my nut load bitch"

Like I said, I'd like to help you but only a qualified psychiatrist could do that.

T3P3Tony

Following an email where I asked sjason1377 to stop abusing/attacking people on the forum he continued with this behaviour so I have banned him.

dc42

@sjason1377 said in Dave's so proud:

yes that's correct. I went back to p7 and it works now

From https://duet3d.dozuki.com/Wiki/Gcode:

P5 (from RepRapFirmware 1.14) selects a switch by default (normally closed) for bed probing between the In and Gnd pins of the Z-probe connector (Duet 0.8.5 and Duet WiFi).
...
P7 (from RepRapFirmware 1.20) selects a switch (by default normally closed) connected to the Z endstop input.
...
P9 (from RepRapFirmware 1.21RC2) is as P5 but for a BLTouch probe that needs to be retracted and redeployed between probe points.

So if P7 worked, he must have his BLTouch connected to the Z endstop input; whereas P9 requires it to be connected to the Z probe input.

fcwilt

@dc42 said in [Dave's so proud]

So if P7 worked, he must have his BLTouch connected to the Z endstop input; whereas P9 requires it to be connected to the Z probe input.

One thing I have noticed is that folks who are not good at attention to details often struggle with configuring 3D printers (and other things as well).

Aside from the occasional mistake they we all make from time to time it is clear you very much know what you are doing.

Thank you for your hard work, the Duet family of products has made building my printers so much easier and enjoyable.

Frederick

dvmourik

I think i can say i have some experience with Duet3D boards and Dave's software.
For reference we produce printers from 3.5m tall and built more than enough of the smaller ones (60cm buildheight). All are using Dave's software. Never found a better supportive programmer than David!

Ofcourse there are bugs. Tell him and he will try to fix it. Don't expect it next day, but believe me he will try his best!

I see Jason is banned allready and that's good! If you don't know how much time is given by people for free! and are bashing them for it? Please leave...

Guys we all have alot of respect for you! Keep up the great work!

Mike

That has quickly devolved into some weird drama, but for what it's worth... This level of entitlement and lack of gratitude is simply astounding. Duet forums are amazing as far as support goes. I haven't seen any big open source projects where the lead dev is so quick to respond and help users with very mundane problems. Not to mention that the whole project is very much alive, with constant firmware and hardware updates. And both are kept as open source as they can be. Simply amazing, hope you guys can keep it up.

deckingman

@mike It was just one individual. The one who started the thread and who behaved so badly that he ended up getting himself banned. No real drama.

jml

Dave's the best

jwalker55

You're the man, David. We are lucky to have someone like you who is so involved in interacting and helping out the community while at the same time being the main developer. Thank you!

edit: didn't realize the last person bumped up an old thread...whoops. Either case, the sentiment remains.