Rostock MAX V2 Auto Calibration

[Acidshock]

Hi Guys,

I am writing because I am having some issues with trying to get Auto Calibration working with the Rostock MAX v2. I bought and setup some FSRs using information from Mhackney and Nylocke's post as a guide. I then setup, compiled, and flashed with Repetier 0.92.6. The FSRs are responding just fine and the G29 command works, probes, etc. However I am still running into issues where the unit is going kamikaze right into the build plate.

I am sure I am leaving something out. Can anyone give a quick guide on how to Auto Calibrate? Shouldn't I be able to have the unit automatically determine its build height? Also I tried OpenDACT as well but it does the same thing, starts up, goes to calibrate and runs into the bed. My FSRs are registering the force but its not stopping. I have verified that they are setup correctly because the G29 portion works just fine and probes all over the bed.

Thanks!


Just an FYI. I am using MatterControl

[Eaglezsoar]

See these links: http://forum.seemecnc.com/viewtopic.php ... &start=175

http://forum.seemecnc.com/viewtopic.php?f=82&t=7936

http://forum.seemecnc.com/viewtopic.php?f=77&t=8111

http://forum.seemecnc.com/viewtopic.php ... &start=700

[Acidshock]

Thanks eaglezsoar. I appreciate the help.

Unfortunately I read most of these as I was setting up the fsrs and I have reread them but with no success. I guess what I am not understanding is more of the procedure. How I get the auto calibration procedure to measure bed distance and then store it for future use. I believe there is a code G31(?) that does this but only for Cartesian printers. I know I can use g29 and take the output and stick it into repetier-host's heightmap system but I've been using mattercontrol. I assume to I want to have this run before every print too in order to insure the best possible output too and also just in case I put some type of material on the bed such as build tak.

[Eaglezsoar]

Thanks eaglezsoar. I appreciate the help.

Unfortunately I read most of these as I was setting up the fsrs and I have reread them but with no success. I guess what I am not understanding is more of the procedure. How I get the auto calibration procedure to measure bed distance and then store it for future use. I believe there is a code G31(?) that does this but only for Cartesian printers. I know I can use g29 and take the output and stick it into repetier-host's heightmap system but I've been using mattercontrol. I assume to I want to have this run before every print too in order to insure the best possible output too and also just in case I put some type of material on the bed such as build tak.

Could some of you heavy hitters that have already installed the FSR's comment and give a fellow member some help?

[mhackney]

I've been talking to the OP via PM about this. With Repetier, I don't believe this can be done currently. You have to manually update the Z Max value in EEPROM (if you have EEPROM enabled) on a delta. The issue is that homing on a Rostock (and most deltas) is towards the top. On most Cartesian printers it is at Z=0. So using FSRs under the bed of a Cartesian printer (like my Taz 4 printer) a G29 causes it to home DOWN towards the bed, the nozzle touches the bed and sets Z=0 exactly the way you want. But not so on a delta.

[Acidshock]

Thanks guys. Been a busy work week for me so I haven't had much time to fiddle with it. Been reviewing the repetier code too, seeing how it homes the z axis. Wasn't sure if I might be able to add a routine that does it. Out of curiosity does Marlin have the ability? I've been reluctant to even try it because it seems like there are so many negative posts about it.

[626Pilot]

Use Repetier if you're stuck in 8-bit land. It stores a lot more values in EEPROM. With Marlin, you have to recompile to change almost any little thing. There is a reason why SeeMeCNC pushes Repetier firmware.

[Acidshock]

Stuck in 8-bit land. Do I see a smoothieboard upgrade in my future? is it worth it? Working on the printer today so I'll let everyone know my results.

[626Pilot]

It's worth it if an 8-bit board isn't doing it for you. Maybe you want to run nicer firmware, be more future-proof, etc. If you can't get a full-bed print with your 8-bit controller, Smoothie + my firmware can help.

If the 8-bit board already does everything you need, now and for the foreseeable future - if you look at the extra features, what the other firmware can do, etc., and think, "I don't care" - then I don't see a reason to do it, other than "cool factor."

[Acidshock]

Well so far I haven't been able to get a full print. I did make a lot of progress though over the weekend. I got g29 s2 to work. At least as much as it can with the current condition the firmware is in. Also got opendact to start working but it still is having an issue where it's running the head into the build plate whenever it tries to measure the different parts of the bed. I feel like I am making progress just tired of hearing the head hit the build plate and turning off the printer in a panic. Like nails on a chalkboard. I have been thinking of doing the smoothieboard. I would just like to get a few decent prints out of the printer first haha.

[Acidshock]

Ok well made progress. Wiped my eeprom values and started over. Helped a lot. Somewhere I must of picked up a bad setting and didn't notice it. Been running opendact. Does a pretty decent job but for some reason it keeps setting the 0 point of the bed at about 2.5-5mm higher than what it actually is at. So after it calibrates I can fit an oreo cookie under the extruder at Z0. Out of curiosity does any know if the auto-level portion of Repetier needs the endstops to be calibrated via a stick of a set length? It recommends that in their write-up but we have Endstops at the top of our units compared to the bottom so I wasn't sure if that is required for the Rostocks.

[magicmushroom666]

After calibrating my printer with opendact, I had to take the EEPROM Z travel figure, and copy it into Repetiers max height. It seems to use this when homing the machine and caused different z heights between SD card and computer hosted.