Quotebrucehvn Also, doesn't it seem like there should be a Z_RAISE_BEFORE_RETRACT setting? We have settings to raise the z-axis before homing and before probing to make sure we have clearance to get the probe down, but when it's done, the probe just retracts where it is. It works ok for my case, but it seems like someone could have a probe setup where the probe might need a little clearance toby edn - General Mendel Topics
Quotederletztename Okay, I did everything as you suggested. Probing takes more time now but seems to be accurate. Theres just one thing i don't get. After G29 the nozzle is a little bit higher above the bed than after a G28 (I send a G1 Z0 after both). How could that be? The height after G28 is perfect, but after the G29 it's about 1mm to high... A FAQ would be great btw. Than people could helpby edn - General Mendel Topics
Quotederletztename Okay, the G1 Z0 Command does help. But it varies where zero is. Maybe there is some connection that after the probing the z-axis move faster than it could and therefore lose some steps sometimes. How can i get this slower? It doesn't seem to be affected by the homing speed settings in the config.h Whats wrong with my #define Z_RAISE_... Has it to be bigger? As big as my "Stickby edn - General Mendel Topics
Quotederletztename Thanks for the answer If I change the value of Z_PROBE_OFFSET_FROM_EXTRUDER nothing changes after probing. The nozzle stays at the high it was during probing. And there it stays during printing. The nozzle should be near to the bed after I perform a G28, right? I don't remember the specifics of what happens with the un-enhanced G29 code. If you go to [3dprintboard.com] Anby edn - General Mendel Topics
Quotederletztename I tried a lot and read a lot about this and i'm near to get it working, But I just don't get the Nozzle to touch the Bed after Probing. It just stays where it was after the Probe triggered. The Servo retract as it should, but after that the printer won't turn any lower. And therefor prints into the air... I added my config.h - maybe someone sees my stupid mistake? I am using anby edn - General Mendel Topics
Quoterandyf1965 Installed a full graphics smart controller (128x64 lcd) and am printing a case for it, it appears the issue with my bed leveling is resolved but I will waiting until the back is printed. Should I have power cycled the ramps/arduino controller after updating the firmware? or does it do that on its own? I visually saw the smart controller restart after flashing. You should reset tby edn - General Mendel Topics
Quoterandyf1965 I have enabled auto bed leveling using Marlin firmware (downloaded 4/24/14) and a servo mounted on the right front of my extruder. After doing a G29 it probes 4 spots on the bed ending up at the rear left of the bed. I do a G1 Z0 there and the extruder is at .1mm from the bed but it I move to the right edge of the bed it raises the extruder by .5mm. ... I have tried the 3 pointby edn - General Mendel Topics
Quoteciutateivissa edn, this could get tricky now... With my version of Marlin_main.cpp the auto bed leveling feature is NOT working properly. On the otherhand I´m not able to figure out what can be removed from your file to get a clean code. Only compare the files does not help because some of your changes make the difference here... Yes... I understand what you are saying. Remember, I didby edn - General Mendel Topics
Quoteciutateivissa edn, we´re making progress here! With your Marlin_main.cpp file the printer performs the auto bed leveling as it should be. He moves the Z-axis before every probing point to 10mm and also the values below looking very promising. Btw. there was no need to use the filament change code in the configuration_adv.h file. ... Delta Bed Height: >-0.2159 +0.0352 +0.3006 <-0.3by edn - General Mendel Topics
Quoteciutateivissa edn, I did the changes you´ve suggested and tested with G28 and G29 again. Unfortunately I can´t see any changes and the strange thing is that changing #define Z_RAISE_BETWEEN_PROBINGS 10 doesn´t have any impact on the behavior of the printer. ... The biggest differences left to explore between our Configuration.h file are: //#define EEPROM_SETTINGS //#define EEPROM_CHITCHATby edn - General Mendel Topics
Quoteciutateivissa edn, thanks again for your support. Here is the Marlin:Main.cpp. I found a couple of things I'm not sure about. For starters, lets make a couple of changes. You have: #define LEFT_PROBE_BED_POSITION 15 #define X_PROBE_OFFSET_FROM_EXTRUDER -26 I think I remember some people having problems when they probed in 'negitive' space. Lets change it to: #define LEFT_PROBE_by edn - General Mendel Topics
Did you notice each and every probe point increases by about 4mm? That is clearly wrong, especially if your bed is pretty level. Can you post your Marlin_Main.CPP file? I'll bet a line in it got corrupted. I'm going to run your Config.h and Marlin_main.cpp file through a diff program to compare it to mine. I bet it will be obvious what is going sour when we do the compare.by edn - General Mendel Topics
Quoteciutateivissa edn, following your instruction in the above mentioned post i have: 1. replaced vector_3.cpp 2. put everything from G29.cpp in the "case29" section (replacing the old code) in Marlin_main.cpp ... Bed level matrix: 0.9999848 0.0000000 -0.0055392 0.0000000 0.9991395 0.0414754 0.0055344 -0.0414748 0.9991243 echo:endstops hit: Z:23.79 Hopefully you´ll know the next steps now, cby edn - General Mendel Topics
ciutateivissa: Try the G29 code posted in this message: It is verbose and from the results it prints out we will know exactly what is going wrong with your setup and how to fix it. My guess is at the end it will print out a correction matrix that has a negitive number along the diagonal. If that is the case, we will know how to proceed to fix it.by edn - General Mendel Topics
Quoteregpye Quoteedn There is a characteristic of the G29 bed leveling probe that I don't like. It raises and lowers the probe for each point. From a repeatability perspective, it is better to just lower it once at the start and raise it at the end. If anybody agrees with this view point and wants to deviate from the norm, I can post the (trivial) changes to do that. That is how the earlyby edn - General Mendel Topics
There is a characteristic of the G29 bed leveling probe that I don't like. It raises and lowers the probe for each point. From a repeatability perspective, it is better to just lower it once at the start and raise it at the end. If anybody agrees with this view point and wants to deviate from the norm, I can post the (trivial) changes to do that.by edn - General Mendel Topics
At line 334 of your Config.h file you will see: //#define ENABLE_AUTO_BED_LEVELING // Delete the comment to enable (remove // at the start of the line) You need to delete the two leading // bars and recompile in order to enable auto-bed-leveling. Right now, it is not turned on, and the G29 command does not exist in your firmware. You also need to set the OFFSET's for X, Y, and Z to appropriaby edn - General Mendel Topics
Quotedave3d You can get the proper thermistor here: I bought half a dozen as spares. Quick delivery. I need to do the same thing and order a few spares. Unfortunately, this place charges a lot for shipping to the US (where I am).by edn - Reprappers
QuoteDaveX #1: You can use it, but the B=3950 vs B=3974 would read about 2C low around 200C. Thanks for the concise answer!!! At worst case, I can live with being off 2 degrees C at 200 C. I was worried about melting down my extruder. QuoteDaveX #2: Your new thermistor is probably a good replacement, since the 1% tolerance is better than the 3% tolerance OK! It is good to hear your opiniby edn - Reprappers
Hi everybody! My extruder got plugged up, and in the process of taking it apart I destroyed the thermistor. In the Merlin Configuration.h file it was a Type-5 ATC Semitec 104GT-2. At the Semitec web site it has the parameters for their thermistors specified The 104GT-2 has its parameters listed as: R25 100.0k Ohm±3% B Value 4267K±2by edn - Reprappers
Quotegwandad Thanks edn. I'd given up. The Rambo pin is PWM pin 5 Pins i & 2 are vcc & Gnd I'm now unsure how to wire up the microswitch that I've mounted on the servo. I've currently got the hall effect magnetic switch. Should I try putting it in series with the existing switch, or replace the hall effect switch with another mechanical switch? I would use a mechanical switch until everby edn - General Mendel Topics
Quotegwandad G'day Alex, Great work, Mate! I have built 2 Mendelmax machines, a 1.5+ & a 2.0. Both built with Rambo Cards. I would like to fit them both with this remarkable feature, but have no idea where to attach the hardware to these cards, Can you assist, Please? I'm running on a PrintrBoard, so I can't help you directly. But I had a similar problem due to poor documentation. I couldby edn - General Mendel Topics
Quotejwd Does anyone has an idea how to fix this? Regards, JWD Do you know what logical pin your servo is on? If so, you can use the M42 command to manually move the servo. See my description 3 or 4 posts back about this.by edn - General Mendel Topics
Quotei-make-robots edn - I have use for the second servo and I'm using a RUMBA controller. What I don't know is where to attach it. I see from earlier in the thread that EXP3 pins 2/4/6 are for a servo, provided you swap the GND and 5V pins. In the same message Yotiro references a second servo, but doesn't indicate where to attach it. I'm guessing 8/10/12, same config. Can anyone confirm? Heby edn - General Mendel Topics
Quotei-make-robots edn - I have use for the second servo and I'm using a RUMBA controller. What I don't know is where to attach it. I see from earlier in the thread that EXP3 pins 2/4/6 are for a servo, provided you swap the GND and 5V pins. In the same message Yotiro references a second servo, but doesn't indicate where to attach it. I'm guessing 8/10/12, same config. Can anyone confirm? Iby edn - General Mendel Topics
Quotei-make-robots Where would you attach servo 2? The Marlin firmware doesn't have a use for a second servo right now. But the support is in place to handle more servo's if you have a purpose for one.by edn - General Mendel Topics
Quotemsmone Quoteregpye Check out this part that is further up in this forum. There is a problem in the code for the feedrates when moving for bed leveling. #define XY_TRAVEL_SPEED 6000 // X and Y axis travel speed between probes, in mm/min This is not only used for XY travel but also for Z travel. That is the reason the Z motor stall. I fixed some things in the code so that the Z moves useby edn - General Mendel Topics
Quoteludara edn: Sorry for the delayed response, but I want you to know that when I used the G29 with ACCURATE_BED_LEVELING, nothing in my printer moves, not the carriage, the bed, the servo..... but I got the following data in return: SENDING:G29 xGridSpacing: 200.000000 yGridSpacing: -195.000000 ... Eqn coefficients: a: 0.000000 b: 0.000000 d: 0.000000 planeNormal x: 0.0000000 y: 0.0000000by edn - General Mendel Topics
Quoteludara edn: Thank you very much for your time and knowledge! I did what you instructed me to do and after a G29 here you have what Pronterface returned: SENDING:G29 Bed G29.1: X:45.0000000 Y:10.0000000 Z:1.7938970 Bed G29.2: X:45.0000000 Y:400.0000000 Z:3.0104327 Bed G29.3: X:445.0000000 Y:400.0000000 Z:2.5990529 Bed level matrix: 0.9999996 0.0000000 -0.0010284 0.0000000 0.9999951 0.00by edn - General Mendel Topics
QuoteTobinatorCO Hi Ludara, Just for comparisons sake, what are your settings in configuration.h for the following? #define INVERT_X_DIR false // for Mendel set to false, for Orca set to true #define INVERT_Y_DIR false // for Mendel set to true, for Orca set to false <--Thing to note for me is that I run a mendal and have to set this to "false", not true as noted in comment... #definby edn - General Mendel Topics