Dave's so proud
-
it's not on my end. It's his code and again he won't admit what he was force to admit a year ago. Once again Im the lair. Until a few hundred other agree and he fixes it. Until than I can't print.
-
@sjason1377 If the machine is reporting firmware as being 2.0 as you have posted, then that is what you've installed. The version you should be using, which has been pointed out numerous times is 2.01. Just look at the release notes and the bug fixes.
Oh and don't send me this again like you did last time I tried to help. For the rest of you, this is a quote from an email that this guy sent me a while back
Quote....
Hey Just wanted to respond. You wear your feelings on your sleeve like a little bitch! Stop proof reading old post and concentrate on the real issues. How bout the faulty board dc42 is refusing to honor warranty for after admitting it the mcu path that is defective. I'm a ginny pig for his testing, not a costumer I see. Just stop being a winney lit bitch, You fucking fag!"
..........end of quote.
So be warned people. If you try to help this guy, that's the kind of abuse that you'll get for your efforts.
-
@deckingman said in Dave's so proud:
So be warned people. If you try to help this guy, that's the kind of abuse that you'll get for your efforts.
Well I hope he builds printers better than he spells.
Frederick
-
RepRapFirmware for Duet 2 WiFi/EthernetFirmware Electronics: Duet Ethernet 1.02 or later
Firmware Version: 2.0(RTOS) (2018-06-05b3)
Web Interface Version: 1.21.2-dc42this is what he told me to upload direct from his link
-
@sjason1377 said in Dave's so proud:
RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet Ethernet 1.02 or later
Firmware Version: 2.0(RTOS) (2018-06-05b3)
Web Interface Version: 1.21.2-dc42this is what he told me to upload direct from his link
Seems to me he suggested you install 2.01.
Frederick
-
i did but thats what board is reporting
-
@sjason1377 said in Dave's so proud:
i did but thats what board is reporting
So that tells you that the firmware did not get updated.
Double check you are trying to upload the 2.01 version and try again.
Frederick
-
RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet Ethernet 1.02 or later
Firmware Version: 2.01(RTOS) (2018-07-26b2)
Web Interface Version: 1.21.2-dc42ok guess what probe doesn't work still
-
; 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 -
This post is deleted! -
This post is deleted! -
RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet Ethernet 1.02 or later
Firmware Version: 2.01(RTOS) (2018-07-26b2)
Web Interface Version: 1.21.2-dc42 -
; 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 gridcorrect version and correct wording in config.g probe is unresponsive. a year of flawless performance under build 1.19.1 and now nothing.
-
This post is deleted! -
@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 gridcorrect 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
-
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.
-
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.
-
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.
-
Ooops... just read the whole thread from the top.
BYE.
You want support from the community, you need a whole different attitude.
-
@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 gridcorrect 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
