Welcome to the SeeMeCNC Community

Some caveats....

1. You MUST have current dev firmware installed - this means a firmware date of 20161207 or later. If you don't feel like being treated like a Scratch Monkey*, DO NOT LOAD THIS FIRMWARE.

2. You're on your own. If the plugin devours your printer, destroys half your house, and your spouse leaves you...well you've got material for a good book I guess. Regardless, I'm not responsible.

3. Read README.md. It's not hard, it's on the front page of the repository. Then read it AGAIN. Maybe, just maybe, read it yet AGAIN.

4. If you don't have an HE280 equipped printer (or at least the fancy probe board), THIS WILL NOT WORK. The calibration code depends on responses generated by the SeeMeCNC fork of Repetier Firmware and the attached probe. That being said, this should work on any delta so equipped. (Upgraded v2, Orion, Eris, etc.)

Here's the link: https://github.com/geneb/OctoPrint-Delta-Calibration

You can install it via pip (see the readme!) (for you octopi users, pip is in /home/pi/oprint/bin/), or you can download the zip file and unpack it into /home/pi/.octoprint/plugins. I recommend you use pip as it's simply easier to deal with, and subsequent pip installation attempts will pull a new version if it's available.

g.

*https://en.wikipedia.org/wiki/Scratch_monkey

1970s jargon Geneb? Way to show that age. Nice work

Well downloaded it and ran it and it throws a disconnect while heading to the second probing location. The connection pane shows disconnected but the terminal pane is showing a death stream.

Also I dont know if it's actually loading the eprom when I press the load eprom button

I haven't tried it yet but installation of the plugin via the OctoPrint Plugin Manager also seemed to work. Use the Git master branch download URL (https://github.com/geneb/OctoPrint-Delt ... master.zip) in the plugin manager.

If you're using Firefox or Chrome, hit the F12 key to see the debugging console. If you're using "Edge" or Internet Exploder....well, not my monkey, not my circus.

When you load the EEPROM, you'll see all the fields it loads in the console tab, prefixed with "Desc:" As it probes, you'll see more info.

g.

I'd recommend running G29 immediately before running the plugin. That'll check for probe sensitivity problems and get them adjusted before you load eeprom and run the wizard and generally save you some rage inducing problems.

Also: we've got new firmware out in the master branch today. Update to that first. New toys, more stable, and bugfixes.

You didn't read the readme, did you?

g.

geneb wrote:You didn't read the readme, did you?

g.

Not only did I read the instructions four time but I printed them out and read them another three times

\o/

g.

I can verify that OctoPrint plugin manager installs the latest version (as of 10 minutes ago).

I installed the latest firmware /dev branch too (verified a build date of 1209). Gene, when I try to run the Delta Auto Clibration I get a status connected and a "Your machine is not a SeeMeCNC 3D printer!" Shh, don't tell my stock V3 that it's not genuine. Chrome browser.

But seriously, what to do?

Uploading the new master branch from today.

Well, that did the trick! The /dev branch was not recognized as genuine. Just like a Krups K-cup v2.

And I just completed the calibration in 20 seconds. Deviation of 0.02 which is very good.

Sometimes the code doesn't see the results of the M115 that it uses to figure out what printer it's connected to. I've yet to figure out why it fails to see the output on occasion.

g.

I have installed the master firmware from 120916 and it is not working for me:
M115 gets this:
Send: N11 M115*22
Recv: ok 11
Recv: FIRMWARE_NAME:Repetier_0.92.2 FIRMWARE_DATE:20161209 MACHINE_TYPE:Rostock MAX v3
Recv: Printed filament:0.00m Printing time:0 days 0 hours 0 min

But i get this in the Delta Autocalibration Plugin:
Connection Status: connected
Your machine is not a SeeMeCNC 3D printer!

I have tried rebooting the pi and the printer a couple times.
Any suggestions?

Ditto rocky00717. Using the new master firmware and the plugin, I also get the NOT a SeeMeCNC printer message and the "Begin Delta Calibration" button is grayed out.

Try disconnecting and reconnecting again.

g.

geneb: disconnect and reconnect what? I've shut down and restarted both OctoPrint and the Rostock itself several times with no change. Do you mean to disconnect the RasPi from the Rambo and reconnect? Thanks!

So here's what I ended up doing,

Re-Downloaded the newest firmware for the printer at GitHub

Used the Previous version of Arduino and cleared the Eeprom, then loaded the firmware onto the printer

Did a G29

Then I held my breath and Ran the plugin

HOLY HELL MY PRINTER KNOW WORKS RIGHT AND DOESN'T HAVE BED TILT!!!!!!!!!!!!!!!!!!

ToddZilla wrote:geneb: disconnect and reconnect what? I've shut down and restarted both OctoPrint and the Rostock itself several times with no change. Do you mean to disconnect the RasPi from the Rambo and reconnect? Thanks!

You click the Disconnect button, give it a sec and then click the Connect button. I had the same issue and a single cycle of that cleared it up.

g.

DerStig wrote:So here's what I ended up doing,

Re-Downloaded the newest firmware for the printer at GitHub

Used the Previous version of Arduino and cleared the Eeprom, then loaded the firmware onto the printer

Did a G29

Then I held my breath and Ran the plugin

HOLY HELL MY PRINTER KNOW WORKS RIGHT AND DOESN'T HAVE BED TILT!!!!!!!!!!!!!!!!!!

#highfive

g.

Duh! lol

That did it. Thanks!

WOW! After getting the new firmware & OctoPrint plugin working, you can see the great results in the pictures. It's a single-layer 270 mm diameter disk. I still have a few slightly high and low spots, but overall DC42's least-squared calibration routine has made a MASSIVE improvement over what I had before (you can see my post in the Troubleshooting forum on my earlier troubles if you're that bored). The entire print bed is now usable, which was not the case before today. Kudos to DC and the SeeMeCNC crew! Thanks a ton!

Okay it's working, well it worked once I tired it a second time and it kicked apos error and disconnected.

Having said that what sort of accuracy are we looking for? My one time got me to .04mm error across the build surface

@ToddZilla - and this is why I've been promoting Duet and dc42 for over a year! I've been enjoying calibrations like that since migrating. And now, to correct those minor second order "defects" David has implemented grid based compensation. It's still in beta but is working amazingly well. That will require Duet and dc42 though as it has to modify every XYZ movement coordinate to compensate. In theory this could be done on the gcode - I actually did exactly that 18 months ago with my Barycentric Interpolation Compensation. But it is soooo dependent on the slicer's output and being able to generate code that can be reasonably parsed. The much better solution is to do it in firmware like dc42 and smoothieware have done.

It is great to see what can be done with a cheap/simple Raspberry Pi and an 8 bit Arduino based controller though.

DerStig wrote:Okay it's working, well it worked once I tired it a second time and it kicked apos error and disconnected.

Having said that what sort of accuracy are we looking for? My one time got me to .04mm error across the build surface

.04mm converts to .0015748". Human hair varies in diameter, but the average is around .07mm, or .0027559".

So the real question is, Are you happy with .04mm?