Closed tyssoon closed 8 years ago
Roxy-3D
commented
8 years ago I answered over at RepRap.org. But really, this issue would be better handled here. I said:
OK. Turn on:
And give a M111 S 32767 to the system right after power up.
It will give us a very detailed summary of what the printer is doing at each point in time.
It would be good to annotate the log and tell us what you are seeing at various points in the log.
Please post the log here.
tyssoon
commented
8 years ago hey roxy ! :)
Roxy-3D
commented
8 years ago Yuch! Can you re-post with the line breaks as they show up in PronterFace? Maybe attach it as a .TXT file ???
tyssoon
commented
8 years ago is the txt file good ?
Roxy-3D
commented
8 years ago Yes. The file is good. Can you reset the machine, do a G28 and then lower the Z-axis to the middle of the print envelope? I want to see a M119 with the printer positioned there. And then do a M401 and another M119 I think you have end stops (in particular, the Z-Probe) showing as triggered when they are not.
Do you have your Z-Probe plugged into the Z-Min endstop? If so, I think you might have these two items reversed. I think you ought to try:
//#define Z_MIN_PROBE_ENDSTOP
#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
thinkyhead
commented
8 years ago @tyssoon Since your probe extends 13.4mm below the nozzle, you need to make sure your Z_PROBE_DEPLOY_HEIGHT and Z_PROBE_TRAVEL_HEIGHT are larger than that magnitude so the probe will clear the bed. For example, if you want the probe to be 5mm above the bed between probes, you need set the Z_PROBE_TRAVEL_HEIGHT to 18.4.
tyssoon
commented
8 years ago @thinkyhead hi ! i have done what you said, i realy thought it could work but it didnt. i tried Z_PROBE_TRAVEL_HEIGHT 20 and the effector still go down during g29 without raising between probes. i believed in you ! :D
@Roxy-3D
i tried this
//#define Z_MIN_PROBE_ENDSTOP
define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
and that didnt change the no raising.
z probe is plugged on the zmin endstop yes.
m119 in the middle of the print enveloppe:
Reporting endstop status x_max: open y_max: open z_min: open z_max: open
m401 had no effect for an mysterious reason
i hope i have done the manipulation right.
thinkyhead
commented
8 years ago By the way, welcome to Github!
tyssoon
commented
8 years ago @thinkyhead
Hey thank you ! :)
thinkyhead
commented
8 years ago Your configuration looks ok to me, except you should definitely be using Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN. The last log you posted has nothing of use in it. You need to run G29 and log the entire procedure, then post the output.
tyssoon
commented
8 years ago oh ok sorry, i had switch it back to see the difference.
so with Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN i let my finger on the switch during the whole g29 to let him finish it.
and thanks for the answers btw
thinkyhead
commented
8 years ago And, again, not useful. The output we're looking for isn't present. You must do two things, as Roxanne described above. First, enable this option in your configuration:
#define DEBUG_LEVELING_FEATURE...and after you have re-flashed the firmware, execute the command M111 S255 before you do G28 or G29. Also, please clear the log before you start, and only include the output from one session of homing and/or bed leveling.
Thanks ! and sorry to keep going back to this.
tyssoon
commented
8 years ago no no, im sorry, i really dont know what i am doing. I just understood that repetier kept everything from the beginning, i think i have cleaned it now, even if it's still quite long
thanks for your patience, really. i hope the txt is ok.
Roxy-3D
commented
8 years ago @tyssoon I've been looking at the latest m111-4.txt log. I need to see the output of this code block in the G29:
if (verbose_level) {
SERIAL_PROTOCOLPGM("Eqn coefficients: a: ");
SERIAL_PROTOCOL_F(plane_equation_coefficients[0], 8);
SERIAL_PROTOCOLPGM(" b: ");
SERIAL_PROTOCOL_F(plane_equation_coefficients[1], 8);
SERIAL_PROTOCOLPGM(" d: ");
SERIAL_PROTOCOL_F(plane_equation_coefficients[2], 8);
SERIAL_EOL;
if (verbose_level > 2) {
SERIAL_PROTOCOLPGM("Mean of sampled points: ");
SERIAL_PROTOCOL_F(mean, 8);
SERIAL_EOL;
}
}Can you clear the log, do the following:
The V4 on the G29 will print those values for me.
tyssoon
commented
8 years ago @Roxy-3D tell me if it's okay:
Roxy-3D
commented
8 years ago @tyssoon I made a mistake. I forgot this is on a Delta printer. The coefficients do not get calculated using qr_solve() on a Delta. But the log is good. I keep looking at it.
tyssoon
commented
8 years ago the beast ! :)
https://goo.gl/photos/9f4q7piJpAfHMRK76
maybe someone have a similar delta build with a marlin well configured where i would just need to change the rods lengths, etc. ?
thinkyhead
commented
8 years ago The log shows that your Z never goes below ~453mm in height. That points to a possible mis-configuration. Is this known to be correct? :
#define MANUAL_Z_HOME_POS 684 // Distance between the nozzle to printbed after homingThis specifies the distance between the nozzle tip and the bed when homed.
And, if that is correct, what does the output of M119 show as you press each endstop and the probe? Are your endstops triggering normally in the way that they should? That is, open when not pressed, and TRIGGERED when they are pressed?
tyssoon
commented
8 years ago Hi @thinkyhead
Z never goes below 453 cause i stay with my finger on the probe switch. I don't want it to crash on the print bed. otherwise the G29 goes to it "normally", it just doesn't raise between probes.
with the four switches pressed:
09:48:19.505 : Reporting endstop status
09:48:19.505 : x_max: TRIGGERED
09:48:19.505 : y_max: TRIGGERED
09:48:19.505 : z_min: TRIGGERED
09:48:19.505 : z_max: TRIGGEREDand the four unpressed;
09:49:33.863 : Reporting endstop status
09:49:33.863 : x_max: open
09:49:33.863 : y_max: open
09:49:33.863 : z_min: open
09:49:33.863 : z_max: openwow, it works now and i dont understand why, i have changed nothing. after u told me about the height i let the effector going down to the bed with my finger on reset waiting for the crash, and he didnt crashed. So in the code i suppose that if an height isnt reach by the probe et doesnt raise between probes.
im happy but also puzzled.
anyway thanks guys, you made it work ! even if i dont understand how ! :D :+1:
thaaaaaaaaaaaanks !!!
thinkyhead
commented
8 years ago I'm glad to hear it was resolved. Sometimes all it takes is a re-flash and reset of EEPROM to clear up anomalies.
github-actions[bot]
commented
2 years ago This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
hi everyone !
im conceiving and making a delta XXL.
im struggling as the big noob i am with marlin for a whole week now. I have finnally manage to have a decent homing and the g29 command is recognized.
when i pull the button of the omron switch with my finger oh the Z probe i have this on m119:
the fact that the zmin and zprobe arent the same might be a problem but i dont understand why they arent.
and when i ask a g29, after a g28, the effector get down. the omron hit the print surface, stop, move on x/y and get down again. And of course he crash on it.
i can of course do it mid air with my finger.
do you guys have an idea of where i messed up ?
here are the config files
Marlin.zip
thanks !