Results 151 to 160 of 172
-
09-04-2015, 12:46 PM #151
- Join Date
- Oct 2014
- Posts
- 114
Okay I was wrong, the firmware is the same but still both machines are somewhat sick, depending on how it's wired, it is either x or y that reacts to the triggered z probe, if it's y it's no big deal since i am doing quick homing, the probe is quickly off the bed and when y homes it is no more triggered. Question, I am trying to add home all into the firmware G29, but cant figure out how, any suggestions?
-
09-04-2015, 01:21 PM #152
It is a little bit dangerous to say this kind of thing without actually checking it out.... But I think you can just change the G29 code like this:
Code:case 29: // G29 Detailed Auto Bed Leveling Z-Probe, probes the bed at 3 or more points. // Example Syntax: G29 N 4 V 2 E T { HOMEAXIS(X); HOMEAXIS(Y); HOMEAXIS(Z); plan_bed_level_matrix.set_to_identity(); //Reset the plane ("erase" all leveling data) if ( code_seen('E') || code_seen('e')) retract_flag++;
-
09-04-2015, 01:49 PM #153
- Join Date
- Oct 2014
- Posts
- 114
Thanks, below is what I tried and I get it to do just that, problem is that I need a safe home for the prob to be on the bed.
{
HOMEAXIS(X);
HOMEAXIS(Y);
HOMEAXIS(Z);
plan_bed_level_matrix.set_to_identity(); //Reset the plane ("erase" all leveling data)
st_synchronize();
}
-
09-04-2015, 03:07 PM #154
If you home X & Y, isn't it safe? I guess I don't understand what you are trying to do.
-
09-04-2015, 03:57 PM #155
- Join Date
- Oct 2014
- Posts
- 114
It's very close to what I want it to do, but when x and y are sent home with the "Homeaxis (x)" they are actually at the stop and not at their normal safe homing position. So if x and y are at the stop the probe is off the bed. I need a macro to
simulate a home_all_axis.
-
09-04-2015, 06:03 PM #156
OK, how about you try this and see if it does something reasonable. Be ready to reset the printer if something goes sour:
Code:HOMEAXIS(X); HOMEAXIS(Y); destination[X_AXIS] = round(Z_SAFE_HOMING_X_POINT - X_PROBE_OFFSET_FROM_EXTRUDER); destination[Y_AXIS] = round(Z_SAFE_HOMING_Y_POINT - Y_PROBE_OFFSET_FROM_EXTRUDER); destination[Z_AXIS] = Z_RAISE_BEFORE_HOMING * home_dir(Z_AXIS) * (-1); // Set destination away from bed feedrate = XY_TRAVEL_SPEED; current_position[Z_AXIS] = 0; plan_set_position(current_position[X_AXIS], current_position[Y_AXIS], current_position[Z_AXIS], current_position[E_AXIS]); plan_buffer_line(destination[X_AXIS], destination[Y_AXIS], destination[Z_AXIS], destination[E_AXIS], feedrate, active_extruder); st_synchronize(); current_position[X_AXIS] = destination[X_AXIS]; current_position[Y_AXIS] = destination[Y_AXIS]; HOMEAXIS(Z);
-
09-05-2015, 08:09 AM #157
- Join Date
- Oct 2014
- Posts
- 114
I tried this before and I just tried it again, x doesn't stop when it hits the endstop and I have to reset the machine. Now I just tried this (see below) and it works, unfortunately only the first time after flashing after that I have to send M502 to get it to work again. Can you think of a way where i wouldn't have to do that?
That bedlevel matrix is effecting the endstop behavior as we realized before.
plan_bed_level_matrix.set_to_identity(); //Reset the plane ("erase" all leveling data)
st_synchronize();
HOMEAXIS(X);
HOMEAXIS(Y);
destination[X_AXIS] = round(Z_SAFE_HOMING_X_POINT - X_PROBE_OFFSET_FROM_EXTRUDER);
destination[Y_AXIS] = round(Z_SAFE_HOMING_Y_POINT - Y_PROBE_OFFSET_FROM_EXTRUDER);.................... ...........................................Last edited by Fri; 09-05-2015 at 09:25 AM.
-
09-05-2015, 09:55 AM #158
I don't know what is causing the failure. That is really weird. But the good news is this weekend the testing for the Marlin Release Candidate is happening. If things go as I expect, this branch is probably going to be promoted to 'Stable Release' status. https://github.com/Wackerbarth/Marli.../Configuration
Do you feel like crossing your configuration.h settings over to this branch? It is going to be much easier to support that branch going forward.
-
09-05-2015, 10:39 AM #159
- Join Date
- Oct 2014
- Posts
- 114
I will give it a shot as soon as I have some time. Takes quite some fiddling.....Anyhow, I don't really think that this is a glitch, more a conflict in the macros. After the matrix is saved to eeprom, or even if you just uncomment the erase bedleveling, the stop switches are acting weird. I guess we will get to the bottom of this sometime. Thanks for all the help.
-
09-05-2015, 03:08 PM #160
- Join Date
- Oct 2014
- Posts
- 114
I will give it a shot as soon as I have some time. Takes quite some fiddling.....Anyhow, I don't really think that this is a glitch, more a conflict in the macros. After the matrix is saved to eeprom, or even if you just uncomment the erase bedleveling, the stop switches are acting weird. I guess we will get to the bottom of this sometime. Thanks for all the help.
Printing time- Is this right?
09-13-2024, 07:51 AM in General 3D Printing Discussion