search

MarlinFirmware / Marlin

Marlin is an optimized firmware for RepRap 3D printers based on the Arduino platform. Many commercial 3D printers come with Marlin installed. Check with your vendor if you need source code for your specific machine.
https://marlinfw.org
GNU General Public License v3.0
16.33k stars 19.25k forks source link

G29 Auto Bed Compensation Not working #2629

Closed bocamarc closed 9 years ago

bocamarc commented 9 years ago

I cannot get G29 command to work. Nothing happens when I use the G29 command. I am using a Prusa I3 with Ramps 1.4. The Prusa I3 works properly except for Auto Bed compensation. I am using Ramps 1.0.2 loaded with Arduino 1.6.5 r5. The servo works with M401 & M402 commands and homing. When I use G28 to Home, I get X=39, Y=70, Z=2.3 ( I am using offsets of X=22, Y=0, Z=2.3). I've tried using G92 to set the home position to X=0, Y=0 and that does not solve the G29 command problem. How can I get auto bed compensation to work ?

KiteLab commented 9 years ago

I suggest before complaining about a defect G29 to repair your G28. Check your endstops. Or try a M502 M500 first, or disable your EEPROM. Branch? Configuration? Printer type?

bocamarc commented 9 years ago

Not complaining. Just looking for help. My end stops work fine without using auto bed compensation.

GrevanGER commented 9 years ago

I had my own problems with G28 and G29 a while ago.

My advice: 

#define DISABLE_X false
#define DISABLE_Y false
#define DISABLE_Z false

If this doesn't solve it, it would help to know the exact error that shows up when you are trying to run the G29 command.

bocamarc commented 9 years ago

Disable_X, Disable_Y, and Disable_Z were all set to false previously.

Checking endstops with M119 code show all end stops work properly. I am currently printing with my Prusa I3 without any problems when auto bed level is turned off.

I have reset the offsets and reloaded the configuration.h to my printer and the following happens -

---Homing displays (LCD) Z=6.3 (my offset is 6.3), X=39, Y=54 ... ---G29 Homes the probe and the display shows Z=6.3 (my offset), X=39, Y=54 with message Z end stop hit. --- The servo/Z end switch works fine - probe extends & retracts & switch works properly

I have also tried setting X=0, Y=0 with G92 followed by M500 after I home Same issue when I home again.

I tested the same configuration.h file with the auto bed level turned off (commented out). My printer works fine. When I home it, I get X=0, Y=0, Z=0. The only difference is that the auto zero is commented out.

Below is the section of my auto zero settings in the configuration.h file. Please let me know if any other information is needed to understand why I can't get it to work.

Configuration.h Settings ... //============================= Bed Auto Leveling ===========================

define ENABLE_AUTO_BED_LEVELING // Delete the comment to enable (remove // at the start of the line)

define Z_PROBE_REPEATABILITY_TEST // If not commented out, Z-Probe Repeatability test will be included if Auto Bed Leveling is Enabled.

ifdef ENABLE_AUTO_BED_LEVELING

// There are 2 different ways to pick the X and Y locations to probe:

// - "grid" mode // Probe every point in a rectangular grid // You must specify the rectangle, and the density of sample points // This mode is preferred because there are more measurements. // It used to be called ACCURATE_BED_LEVELING but "grid" is more descriptive

// - "3-point" mode // Probe 3 arbitrary points on the bed (that aren't colinear) // You must specify the X & Y coordinates of all 3 points

define AUTO_BED_LEVELING_GRID

// with AUTO_BED_LEVELING_GRID, the bed is sampled in a // AUTO_BED_LEVELING_GRID_POINTSxAUTO_BED_LEVELING_GRID_POINTS grid // and least squares solution is calculated // Note: this feature occupies 10'206 byte

ifdef AUTO_BED_LEVELING_GRID

// set the rectangle in which to probe
#define LEFT_PROBE_BED_POSITION 15
#define RIGHT_PROBE_BED_POSITION 110
#define BACK_PROBE_BED_POSITION 110
#define FRONT_PROBE_BED_POSITION 20

 // set the number of grid points per dimension
 // I wouldn't see a reason to go above 3 (=9 probing points on the bed)
#define AUTO_BED_LEVELING_GRID_POINTS 2

else // not AUTO_BED_LEVELING_GRID

// with no grid, just probe 3 arbitrary points.  A simple cross-product
// is used to esimate the plane of the print bed
  #define ABL_PROBE_PT_1_X 15
  #define ABL_PROBE_PT_1_Y 120
  #define ABL_PROBE_PT_2_X 15
  #define ABL_PROBE_PT_2_Y 20
  #define ABL_PROBE_PT_3_X 120
  #define ABL_PROBE_PT_3_Y 20

endif // AUTO_BED_LEVELING_GRID

// these are the offsets to the probe relative to the extruder tip (Hotend - Probe) // X and Y offsets must be integers

define X_PROBE_OFFSET_FROM_EXTRUDER 22

define Y_PROBE_OFFSET_FROM_EXTRUDER 16

define Z_PROBE_OFFSET_FROM_EXTRUDER -6.3

define Z_RAISE_BEFORE_HOMING 4 // (in mm) Raise Z before homing (G28) for Probe Clearance.

                                    // Be sure you have this distance over your Z_MAX_POS in case

define XY_TRAVEL_SPEED 8000 // X and Y axis travel speed between probes, in mm/min

define Z_RAISE_BEFORE_PROBING 15 //How much the extruder will be raised before traveling to the first probing point.

define Z_RAISE_BETWEEN_PROBINGS 5 //How much the extruder will be raised when traveling from between next probing points

//#define Z_PROBE_SLED // turn on if you have a z-probe mounted on a sled like those designed by Charles Bell //#define SLED_DOCKING_OFFSET 5 // the extra distance the X axis must travel to pickup the sled. 0 should be fine but you can push it further if you'd like.

//If defined, the Probe servo will be turned on only during movement and then turned off to avoid jerk //The value is the delay to turn the servo off after powered on - depends on the servo speed; 300ms is good value, but you can try lower it. // You MUST HAVE the SERVO_ENDSTOPS defined to use here a value higher than zero otherwise your code will not compile.

// #define PROBE_SERVO_DEACTIVATION_DELAY 300

//If you have enabled the Bed Auto Leveling and are using the same Z Probe for Z Homing, //it is highly recommended you let this Z_SAFE_HOMING enabled!!!

define Z_SAFE_HOMING // This feature is meant to avoid Z homing with probe outside the bed area.

                      // When defined, it will:
                      // - Allow Z homing only after X and Y homing AND stepper drivers still enabled
                      // - If stepper drivers timeout, it will need X and Y homing again before Z homing
                      // - Position the probe in a defined XY point before Z Homing when homing all axis (G28)
                      // - Block Z homing only when the probe is outside bed area.

ifdef Z_SAFE_HOMING

#define Z_SAFE_HOMING_X_POINT (X_MAX_LENGTH/2)    // X point for Z homing when homing all axis (G28)
#define Z_SAFE_HOMING_Y_POINT (Y_MAX_LENGTH/2)    // Y point for Z homing when homing all axis (G28)

endif

ifdef AUTO_BED_LEVELING_GRID // Check if Probe_Offset * Grid Points is greater than Probing Range

#if X_PROBE_OFFSET_FROM_EXTRUDER < 0
  #if (-(X_PROBE_OFFSET_FROM_EXTRUDER \* AUTO_BED_LEVELING_GRID_POINTS) >= (RIGHT_PROBE_BED_POSITION - LEFT_PROBE_BED_POSITION))
     #error "The X axis probing range is not enough to fit all the points defined in AUTO_BED_LEVELING_GRID_POINTS"
  #endif
#else
  #if ((X_PROBE_OFFSET_FROM_EXTRUDER \* AUTO_BED_LEVELING_GRID_POINTS) >= (RIGHT_PROBE_BED_POSITION - LEFT_PROBE_BED_POSITION))
     #error "The X axis probing range is not enough to fit all the points defined in AUTO_BED_LEVELING_GRID_POINTS"
  #endif
#endif
#if Y_PROBE_OFFSET_FROM_EXTRUDER < 0
  #if (-(Y_PROBE_OFFSET_FROM_EXTRUDER \* AUTO_BED_LEVELING_GRID_POINTS) >= (BACK_PROBE_BED_POSITION - FRONT_PROBE_BED_POSITION))
     #error "The Y axis probing range is not enough to fit all the points defined in AUTO_BED_LEVELING_GRID_POINTS"
  #endif
#else
  #if ((Y_PROBE_OFFSET_FROM_EXTRUDER \* AUTO_BED_LEVELING_GRID_POINTS) >= (BACK_PROBE_BED_POSITION - FRONT_PROBE_BED_POSITION))
     #error "The Y axis probing range is not enough to fit all the points defined in AUTO_BED_LEVELING_GRID_POINTS"
  #endif
#endif

endif

endif // ENABLE_AUTO_BED_LEVELING

// The position of the homing switches

define MANUAL_HOMEPOSITIONS // If defined, MANUAL*_HOME_POS below will be used

//#define BED_CENTER_AT_0_0 // If defined, the center of the bed is at (X=0, Y=0)

//Manual homing switch locations: // For deltabots this means top and center of the Cartesian print volume.

define MANUAL_X_HOME_POS 0

define MANUAL_Y_HOME_POS 0

define MANUAL_Z_HOME_POS 0

//#define MANUAL_Z_HOME_POS 402 // For delta: Distance between nozzle and print surface after homing.

//// MOVEMENT SETTINGS

define NUM_AXIS 4 // The axis order in all axis related arrays is X, Y, Z, E

define HOMING_FEEDRATE {50_60, 50_60, 150, 0} // set the homing speeds (mm/min)

// default settings

define DEFAULT_AXIS_STEPS_PER_UNIT {80,80,4000,841} // default steps per unit for Ultimaker

define DEFAULT_MAX_FEEDRATE {250,250,2,22} // (mm/sec)

define DEFAULT_MAX_ACCELERATION {1000,1000,5,1000} // X, Y, Z, E maximum start speed for accelerated moves. E default values are good for Skeinforge 40+, for older versions raise them a lot.

define DEFAULT_ACCELERATION 500 // X, Y, Z and E max acceleration in mm/s^2 for printing moves

define DEFAULT_RETRACT_ACCELERATION 500 // X, Y, Z and E max acceleration in mm/s^2 for retracts

// Offset of the extruders (uncomment if using more than one and relying on firmware to position when changing). // The offset has to be X=0, Y=0 for the extruder 0 hotend (default extruder). // For the other hotends it is their distance from the extruder 0 hotend. // #define EXTRUDER_OFFSET_X {0.0, 20.00} // (in mm) for each extruder, offset of the hotend on the X axis // #define EXTRUDER_OFFSET_Y {0.0, 5.00} // (in mm) for each extruder, offset of the hotend on the Y axis

// The speed change that does not require acceleration (i.e. the software might assume it can be done instantaneously)

define DEFAULT_XYJERK 20.0 // (mm/sec)

define DEFAULT_ZJERK 0.4 // (mm/sec)

define DEFAULT_EJERK 5.0 // (mm/sec)

bocamarc commented 9 years ago

Sorry, meant to say toward the end of my comments that auto bed level is commented out not auto zero

bocamarc commented 9 years ago

Problem solved. See Issue #2109. My problem was similar.

I changed the following in the configuration.h file:

const bool X_MAX_ENDSTOP_INVERTING = true; // CHANGED set to true to invert the logic of the endstop. const bool Y_MAX_ENDSTOP_INVERTING = true; // CHANGED set to true to invert the logic of the endstop. const bool Z_MAX_ENDSTOP_INVERTING = true; // CHANGED set to true to invert the logic of the endstop.

The original configuration when I bought the printer, was set to false. Previously, it had no effect on my use of the printer until I tried to use Auto Bed Level.

When using the G28 G code, my printer does not home at X=0, Y=0. It now homes at a point in the center of the bed. The X & Y positions are correct. Using a G1 X=0 Y=0 the hot end goes to X=0 Y=0.

I had to readjust the Z offset, however, my prints are good.

KiteLab commented 9 years ago

You could have been faster. See my first message, sentence two.

bocamarc commented 9 years ago

Your first message was not explained well. You were not helpful. I was able to understand the explanation by Thinkyhead. I have a technical background, however, I am not a developer or programmer. I am just getting familiar with the technical side of 3D printing and Marlin.

Perhaps you need to take a lesson from Thinkyhead on how to provide support & answer a question. I've looked at some of his other responses and he is very good. This can be a learning experience for you. He provides details and explains the problem & solution well.

You're first response was defensive & you accused me of complaining. I was not happy with your attitude & did not want to continue to work with you for support. I looked elsewhere for answers.

I've managed systems engineers & service engineers at HP, GE, Philips, and Siemens. If a support person spoke to a customer the way you responded to my request for help, you would have been put on probation.

brainscan commented 9 years ago

I think people are getting frustrated with new users constantly opening new problems when the solution is already there (and has been for a long time). It wasn't like this a couple of years ago but recently people seem to love blaming marlin when it has more to do with their lack of experience. There are multiple forums to gather info from before opening a new issue.

Sent from my iPhone

On 25 Sep 2015, at 02:09, bocamarc notifications@github.com wrote:

Your first message was not explained well. You were not helpful. I was able to understand the explanation by Thinkyhead. I have a technical background, however, I am not a developer or programmer. I am just getting familiar with the technical side of 3D printing and Marlin.

Perhaps you need to take a lesson from Thinkyhead on how to provide support & answer a question. I've looked at some of his other responses and he is very good. This can be a learning experience for you. He provides details and explains the problem & solution well.

You're first response was defensive & you accused me of complaining. I was not happy with your attitude & did not want to continue to work with you for support. I looked elsewhere for answers.

I've managed systems engineers & service engineers at HP, GE, Philips, and Siemens. If a support person spoke to a customer the way you responded to my request for help, you would have been put on probation.

— Reply to this email directly or view it on GitHub.

bocamarc commented 9 years ago

I think Marlin is very good. I'm finding that there is a good amount of documentation, however, it is not always consistant/comprehensive. Since there are many people working on Marlin it is understandable. I keep finding additional G & M codes not listed and not explained thoroughly. Many links in the Github issue comments section are dead ends.

In the case of Auto Bed Level, I spent a considerable amount of time on websites and YouTube to try to get it working. Not one site mentioned anything about endstops. At first, it was not obvious to Thinkyhead in the previous issue post what was causing the same problem. My configuration.h was provided to me by the company that shipped me the kit. It had been working fine for the past 2 years. I had no reason to suspect my endstops were not configured properly. Guess what, everyone that has received the same generic configuration.h will have trouble adding Auto Bed Level and will either give up or post issue questions.

As 3D printing becomes more and more mainstream, the technical abilities of users are less then the early adopters and developers. It might be worthwhile to have an Auto Bed Level Installation Guide (as well as for other capabilities). This can be updated as issues arise. If you have the information correct and in one place, it will elimanate answering the same questions & posts multiple times. The websites & YouTube videos I reviewed trying to set this up all missed some steps or did not provide comprehensive instructions. I had to review several sites to get the information needed. It was both time consuming and frustrating.

Sent from my iPad Marc Rosenkranz

On Sep 25, 2015, at 2:08 AM, brainscan notifications@github.com wrote:

I think people are getting frustrated with new users constantly opening new problems when the solution is already there (and has been for a long time). It wasn't like this a couple of years ago but recently people seem to love blaming marlin when it has more to do with their lack of experience. There are multiple forums to gather info from before opening a new issue.

Sent from my iPhone

On 25 Sep 2015, at 02:09, bocamarc notifications@github.com wrote:

Your first message was not explained well. You were not helpful. I was able to understand the explanation by Thinkyhead. I have a technical background, however, I am not a developer or programmer. I am just getting familiar with the technical side of 3D printing and Marlin.

Perhaps you need to take a lesson from Thinkyhead on how to provide support & answer a question. I've looked at some of his other responses and he is very good. This can be a learning experience for you. He provides details and explains the problem & solution well.

You're first response was defensive & you accused me of complaining. I was not happy with your attitude & did not want to continue to work with you for support. I looked elsewhere for answers.

I've managed systems engineers & service engineers at HP, GE, Philips, and Siemens. If a support person spoke to a customer the way you responded to my request for help, you would have been put on probation.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

Wackerbarth commented 9 years ago

@bocamarc -- I cannot agree more with you. Unfortunately, Marlin is not a commercial product and those working on it are, by nature, very knowledgable on technical issues. Further, on this project, like all others, they seem to be more interested in generating "capability" rather than worrying about "usability" for the less knowledgable. As a result, documentation seems to be the last thing that gets addressed, if it gets addressed at all.

We have also experienced some technical access problems to the documentation files. Someone did some work on documentation in the past but, when they stopped, failed to "return the access keys".

In the last day, or so, we have started to address that problem. I think they are moving items such as you mention into a wiki associated with this repository.

We invite you to add the knowledge that you have gained through your research to the resources available to the next new user.

In some ways, new users are more qualified to decide what, and how, features get documented. Those very close to the code perceive aspects as "obvious" when they are not obvious to those farther removed.

It takes a community to develop a complete product. We invite you to be a part of that community.

bocamarc commented 9 years ago

Richard, I would be glad to provide my information to help others. What's involved in participating  ?  How does one get started. I will also be doing the following over the next several months:

I anticipate that I will be having a similar experience with each of these upgrades. I do have an engineering degree, however, it is from ancient times.

Marc

  From: Richard Wackerbarth <notifications@github.com>

To: MarlinFirmware/Marlin Marlin@noreply.github.com Cc: bocamarc marc_rosenkranz@yahoo.com Sent: Friday, September 25, 2015 8:41 AM Subject: Re: [Marlin] G29 Auto Bed Compensation Not working (#2629)

@bocamarc -- I cannot agree more with you. Unfortunately, Marlin is not a commercial product and those working on it are, by nature, very knowledgable on technical issues. Further, on this project, like all others, they seem to be more interested in generating "capability" rather than worrying about "usability" for the less knowledgable. As a result, documentation seems to be the last thing that gets addressed, if it gets addressed at all.We have also experienced some technical access problems to the documentation files. Someone did some work on documentation in the past but, when they stopped, failed to "return the access keys".In the last day, or so, we have started to address that problem. I think they are moving items such as you mention into a wiki associated with this repository.We invite you to add the knowledge that you have gained through your research to the resources available to the next new user.In some ways, new users are more qualified to decide what, and how, features get documented. Those very close to the code perceive aspects as "obvious" when they are not obvious to those farther removed.It takes a community to develop a complete product. We invite you to be a part of that community.— Reply to this email directly or view it on GitHub.

brainscan commented 9 years ago

If you're thinking of switching to a Bowden for an upgrade(?), I would suggest looking at the flexi drive on the mendelflex. Bowdens will help reduce weight but negatively affect quality, and need lots more trial and error to get things working. The flexi drive keeps best of both worlds, if you actually want an upgrade.

Sent from my iPhone

On 25 Sep 2015, at 19:20, bocamarc notifications@github.com wrote:

Richard, I would be glad to provide my information to help others. What's involved in participating ? How does one get started. I will also be doing the following over the next several months:

  • Upgrading to E3D hot end
  • Upgrading to Bowden
  • Upgrading to Dual Extrusion
  • Building a larger print area/frame

I anticipate that I will be having a similar experience with each of these upgrades. I do have an engineering degree, however, it is from ancient times.

Marc

From: Richard Wackerbarth notifications@github.com To: MarlinFirmware/Marlin Marlin@noreply.github.com Cc: bocamarc marc_rosenkranz@yahoo.com Sent: Friday, September 25, 2015 8:41 AM Subject: Re: [Marlin] G29 Auto Bed Compensation Not working (#2629)

@bocamarc -- I cannot agree more with you. Unfortunately, Marlin is not a commercial product and those working on it are, by nature, very knowledgable on technical issues. Further, on this project, like all others, they seem to be more interested in generating "capability" rather than worrying about "usability" for the less knowledgable. As a result, documentation seems to be the last thing that gets addressed, if it gets addressed at all.We have also experienced some technical access problems to the documentation files. Someone did some work on documentation in the past but, when they stopped, failed to "return the access keys".In the last day, or so, we have started to address that problem. I think they are moving items such as you mention into a wiki associated with this repository.We invite you to add the knowledge that you have gained through your research to the resources available to the next new user.In some ways, new users are more qualified to decide what, and how, features get documented. Those very close to the code perceive aspects as "obvious" when they are not obvious to those farther removed.It takes a community to develop a complete product. We invite you to be a part of that community.— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

bocamarc commented 9 years ago

Thank you for the information.  I was not familiar with the Flexi Drive.  It looks good. I was going to try a direct drive extruder and/or  a modified Wades geared extruder. I wasn't sure which would be better.  I don't want to add any more trial & error or quality issues.  I will be looking more closely at the Flexi Drive. Marc

  From: brainscan <notifications@github.com>

To: MarlinFirmware/Marlin Marlin@noreply.github.com Cc: bocamarc marc_rosenkranz@yahoo.com Sent: Friday, September 25, 2015 2:35 PM Subject: Re: [Marlin] G29 Auto Bed Compensation Not working (#2629)

If you're thinking of switching to a Bowden for an upgrade(?), I would suggest looking at the flexi drive on the mendelflex. Bowdens will help reduce weight but negatively affect quality, and need lots more trial and error to get things working. The flexi drive keeps best of both worlds, if you actually want an upgrade.

Sent from my iPhone

On 25 Sep 2015, at 19:20, bocamarc notifications@github.com wrote:

Richard, I would be glad to provide my information to help others. What's involved in participating ? How does one get started. I will also be doing the following over the next several months:

  • Upgrading to E3D hot end
  • Upgrading to Bowden
  • Upgrading to Dual Extrusion
  • Building a larger print area/frame

I anticipate that I will be having a similar experience with each of these upgrades. I do have an engineering degree, however, it is from ancient times.

Marc

From: Richard Wackerbarth notifications@github.com To: MarlinFirmware/Marlin Marlin@noreply.github.com Cc: bocamarc marc_rosenkranz@yahoo.com Sent: Friday, September 25, 2015 8:41 AM Subject: Re: [Marlin] G29 Auto Bed Compensation Not working (#2629)

@bocamarc -- I cannot agree more with you. Unfortunately, Marlin is not a commercial product and those working on it are, by nature, very knowledgable on technical issues. Further, on this project, like all others, they seem to be more interested in generating "capability" rather than worrying about "usability" for the less knowledgable. As a result, documentation seems to be the last thing that gets addressed, if it gets addressed at all.We have also experienced some technical access problems to the documentation files. Someone did some work on documentation in the past but, when they stopped, failed to "return the access keys".In the last day, or so, we have started to address that problem. I think they are moving items such as you mention into a wiki associated with this repository.We invite you to add the knowledge that you have gained through your research to the resources available to the next new user.In some ways, new users are more qualified to decide what, and how, features get documented. Those very close to the code perceive aspects as "obvious" when they are not obvious to those farther removed.It takes a community to develop a complete product. We invite you to be a part of that community.— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

Wackerbarth commented 9 years ago

@bocamarc - "I do have an engineering degree, however, it is from ancient times." Compared to me, those are likely "modern" times.

The documentation effort IS on the MarlinFirmware/Marlin wiki You should be able to find information to help you get started here

bocamarc commented 9 years ago

Ok, now I am curious, when did you graduate  ?  I graduated in 1972.

  From: Richard Wackerbarth <notifications@github.com>

To: MarlinFirmware/Marlin Marlin@noreply.github.com Cc: bocamarc marc_rosenkranz@yahoo.com Sent: Friday, September 25, 2015 3:29 PM Subject: Re: [Marlin] G29 Auto Bed Compensation Not working (#2629)

@bocamarc - "I do have an engineering degree, however, it is from ancient times." Compared to me, those are likely "modern" times.The documentation effort IS on the MarlinFirmware/Marlin wiki You should be able to find information to help you get started here— Reply to this email directly or view it on GitHub.

Wackerbarth commented 9 years ago

BSEE 1965

bocamarc commented 9 years ago

You got me beat.  I have a BEE with specialty in biomedical. From: Richard Wackerbarth notifications@github.com To: MarlinFirmware/Marlin Marlin@noreply.github.com Cc: bocamarc marc_rosenkranz@yahoo.com Sent: Friday, September 25, 2015 5:05 PM Subject: Re: [Marlin] G29 Auto Bed Compensation Not working (#2629)

BSEE 1965— Reply to this email directly or view it on GitHub.

Wackerbarth commented 9 years ago

Yeh, biomedical was a new speciality when I was in Grad School. They were major users of "my" computer.

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.