-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pre-processor bug ? #3894
Comments
Nope! You will have to look at the commit logs to find who did make that code. But it wasn't me. |
Ooops @Roxy-3DPrintBoard, I did not mean to finger point... I just imagined you were (I konw, I should have verified instead of remembering Richard telling me to close one of my 3 PR I wrote cause you were involved in the probe handling... You are one of those I learn a lot from, thanks to correct me. |
I can take credit for most of the "macro piles" in Marlin. |
So… Yes, the |
To sort this out, it will help to enable |
In
|
@thinkyhead Please have a look in the logs directory in my https://github.com/lrpirlet/Marlin/tree/servo_swing_without_raise_reset_arduino branch... The logs directory shows the Arduino compile full verbose ( no mention around a macro expansion warning in Marlin_main.cpp) Yet the repetier logs shows the servo deploy and retract in G28 (it should not) The logs also contain a diff to facilitate comparison between the RCBugFix and my |
@lrpirlet I will take a look tomorrow. I have to get some sleep now!
@Blue-Marlin We all sound like broken records until someone makes a Pull Request. |
@thinkyhead |
@lrpirlet @@ -2319,10 +2319,18 @@ static void homeaxis(AxisEnum axis) {
#if HAS_SERVO_ENDSTOPS
if (_Z_SERVO_TEST && servo_endstop_id[axis] >= 0) {
#if ENABLED(DEBUG_LEVELING_FEATURE)
if (DEBUGGING(LEVELING)) SERIAL_ECHOLNPGM("> SERVO_ENDSTOPS > Stow with servo.move()");
#endif
+
+ #ifndef Z_RAISE_AFTER_PROBING
+ #define Z_RAISE_AFTER_PROBING 15 // your number
+ #endif
+ current_position[Z_AXIS] = Z_RAISE_AFTER_PROBING;
+ line_to_current_position();
+ stepper.synchronize();
+
servo[servo_endstop_id[axis]].move(servo_endstop_angle[axis][1]);
if (_Z_PROBE_SUBTEST) endstops.enable_z_probe(false);
}
#endif |
That's okay. We've put up Pull Requests that are not going into 1.1.0 but are being held until 1.1.1. There won't be too many changes before 1.1.0 is released. So, feel free to submit any PR that addresses extant issues. It will give us extra time to do cleanup and testing, as well. |
@Blue-Marlin Thanks, I'll try that tonight, if I can spare one hour, and report.. |
@Blue-Marlin Many thanks... I now realize that preprocessor is not at fault... I did not realize that the stow was issued from Inside the homeaxis.. This is what I did... I did add the feedrate as the Z axis went to a real slow move... about 1mm per minute or so (needless to say it was too long for me to wait)... @@ -2326,6 +2321,15 @@ static void homeaxis(AxisEnum axis) {
#if ENABLED(DEBUG_LEVELING_FEATURE)
if (DEBUGGING(LEVELING)) SERIAL_ECHOLNPGM("> SERVO_ENDSTOPS > Stow with servo.move()");
#endif
+
+ #ifndef Z_RAISE_AFTER_PROBING
+ #define Z_RAISE_AFTER_PROBING 5 // your number
+ #endif
+ current_position[Z_AXIS] = Z_RAISE_AFTER_PROBING;
+ feedrate = homing_feedrate[Z_AXIS];
+ line_to_current_position();
+ stepper.synchronize();
+
servo[servo_endstop_id[axis]].move(servo_endstop_angle[axis][1]);
if (_Z_PROBE_SUBTEST) endstops.enable_z_probe(false);
}
More info available in https://github.com/lrpirlet/Marlin/tree/servo_swing_without_raise_reset_arduino logs directory. |
@lrpirlet |
@Blue-Marlin ok, I'll do it, be warned, it may take me a few days as I can't give all the time I like... |
Thanks @lrpirlet & @Blue-Marlin. |
@thinkyhead @Blue-Marlin @jbrazio I did submit a PR in #3942 |
I need to be more careful how I word things. I was not trying to avoid being blamed for something. I was trying not to take credit for all the work somebody else did. |
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. |
I am trying to port my https://github.com/lrpirlet/Marlin/tree/motorized_mesh_bed_leveling_for_LRP and to try it with the https://github.com/Sebastianv650/MarlinRC_LIN_ADVANCE... This for the background info...
BTW, @Sebastianv650, thanks for that very nice algorithm...
Anyway, a diff of my configuration.h from the default in RCBugfix shows
I compile that in ARDUINO 1.6.8 (installed on my new computer, not an upgrade or update) and upload it to my printer...
G28... G28 start it's usual dance, the servo deploy, G28 goes down till the z-probe touch the bed twice, servo trys to stow... power loss on the hardware... I know, too much power drain by the servo, I need to give the servo enough z height so that it does not get blocked...
so, I jump in the code... and change the following that must have been written by @Roxy-3DPrintBoard ...
That compiles without any problem, I download it to the printer... same behavior
oops...
So I scratch my hair, look around in the code... Yes this is normal,
raise_z_for_servo();
needsAUTO_BED_LEVELING_FEATURE
to be defined...SO I will edit right and left to... wait a minute... stop... think... observe... read it all..
The servo should never have moved at all since
deploy_z_probe()
impliesAUTO_BED_LEVELING_FEATURE
Sorry, this is too much for me... Do I face a preprocessor error??
Now, to avoid compiling that, would it be a good idea to put in sanitycheck.h something such as
#error on defined (HAS_Z_ENDSTOP_SERVO) and disabled(AUTO_BED_LEVELING_FEATURE)
(using the correct syntax that I have not figured yet)@thinkyhead , you have always been supportive, what do you think? ( I want to learn). ( I am an old engineeer, but not a C or C++ programmer, I wrote mickey mouse program on PDP 11 and Vax if that tells you some and some Z80 asm code)
That said, I would really appreciate to see my name associate with the solution.. I spend quite a few hours frustration on this one... I will probably NOT touch my computer before June, and I feel we should NOT leave that like that.... Unless I missed something obvious that I should know.
The text was updated successfully, but these errors were encountered: