OpenDACT(Delta Automatic Calibration Tool) - For Repetier

[CaptainMerica]

It seems like it's working about the same. hasnt given any crazy numbers yet though. I have my webcam set up so you can see the console and printer if you wish, i have to do some chores around the house.

Tinyurl.com/printerviewer3

EDIT
eek it was going good, luckily i was in the room when it decided to crash, it went down 6 inches, almost back up to home, then HA-ZAAA into the plate. this is a screengrab

[RollieRowland]

It seems like it's working about the same. hasnt given any crazy numbers yet though. I have my webcam set up so you can see the console and printer if you wish, i have to do some chores around the house.

Tinyurl.com/printerviewer3

EDIT
eek it was going good, luckily i was in the room when it decided to crash, it went down 6 inches, almost back up to home, then HA-ZAAA into the plate. this is a screengrab

crash.png

Well, your tower offsets are about 5 times what they should be in the first column. Why may you ask? Not the slightest - this is a first. However, it definitely is caused by increasingly bad XYZ offset values - impart from the left column of the Tower correction. I would recommend using the default values for the time being, it will just take longer to calibrate. (I will have a new version up tonight - will work a lot better)

[CaptainMerica]

hmm. How do those tower offset values get adjusted like that? I didnt touch them at all, i will retry it with a fresh open of the app.

[RollieRowland]

hmm. How do those tower offset values get adjusted like that? I didnt touch them at all, i will retry it with a fresh open of the app.

Those are adjusted in the AI and HAI calibration modes

[CaptainMerica]

ah, gotcha. I reset everything and am currently running the standard calibration. so far so good.

edit. nope. same thing. screen grab below. I think i'll just wait and try later haha.

[dkaustin]

I just offer the following for information purposes, don't know how significant or helpful it may be...

Running OpenDACT v2.1.1 Basic Calibration in Win7 in compatibility mode for XP SP2 with Administrator rights:

At 9600 baud, OpenDACT connects, printer responds to request for EEPROM info, OpenDACT does not respond. OpenDACT does not hang at this point, it's still running but does not proceed any further.

At 19200 baud, OpenDACT connects, printer responds to request for EEPROM info, OpenDACT acknowldges EEPROM capture, says "Beginning Calibration" but nothing further happens. Again OpenDACT does not hang, it just doesn't proceed any further.

At 38400 baud, OpenDACT runs normally, although it does not converge to a solution. Diagonal Rod length changes slightly from input 269mm to about 267mm. Horizontal Radius changes slightly from input 129mm to about 128mm.

Again, don't know if this is significant, just thought I would share it in case someone sees a pattern.

[Micael]

Have you changed the baud on the firmware, or just the opendact, because if you just change the baud on the opendact, it is normal that it doesn't work properly.

[geneb]

There's no reason to run OpenDACT under XP compatibility mode. It was built with Visual Studio 2015, which is about as current as you can get when compiling programs.
In fact, the only reason to EVER use compatibility mode is if you've got a 16 bit application that predates Windows 7.

Why are you changing the baud rate? It should operate at the default Rambo speed of 115200.

g.

[Micael]

Why are you changing the baud rate? It should operate at the default Rambo speed of 115200.

If he has a rostock max v2 with the repetier firmware provided by seemecnc on their website, it's set at 250000, which is the default value on version 2.0.5A of opendact.

[keith elliott]

Quick question for anyone who used the manual calc with the new seemecnc cheapskates. If I set the hoz rad to 140 the probe will go out side the print area. If I leave it at the default 130 it will run fine, but when I try and run it a second time it will go outside the print area since the calc figured a 139ish hor rad. Any help would be appreciated.

[geneb]

Why are you changing the baud rate? It should operate at the default Rambo speed of 115200.

If he has a rostock max v2 with the repetier firmware provided by seemecnc on their website, it's set at 250000, which is the default value on version 2.0.5A of opendact.

I was tired and mis-typed. You're absolutely correct. I should know better. I wrote the manual. *laughs*

It's those poor schmucks that bought maggotboxen (macs) that have to slog along at 115200.

I need a drink.

g.

[lordgort]

no luck with it @RollieRowland?

[derzaubererer]

well after i got my fsr setup i cant get it to calibrate properly its about 0.2 mm off and i have not a single idea how to fix it:(

[geneb]

I suspect he'll answer when he's got time and no sooner.

g.

[RollieRowland]

I suspect he'll answer when he's got time and no sooner.

g.

Yeah, I haven't had much time this week.

For the baudrate, use what your printer is set at. There is no huge benefit to changing baudrate except for a slight speed increase and less data loss - which normally isn't an issue.

For the calibration, I might be able to finish enough of the new version tonight to upload it and have everyone test it - as long as nothing else happens that prevents me from doing so.

[Paxy]

Great job guys,
Until this program, I have used to manually calibrate printer with just XYZ offsets which took me 3-4 hours for each calibration.
Now, job is done automatically in less then hour.

Here is mine full calibration video:
https://www.youtube.com/watch?v=cQ1uTnZpUzM

I have designed and used Z probe module that is mounted only during calibration.
http://www.thingiverse.com/thing:892717

Also, I like to thank derzaubererer to point me to your calibration solution.

[derzaubererer]

Great job guys,
Until this program, I have used to manually calibrate printer with just XYZ offsets which took me 3-4 hours for each calibration.
Now, job is done automatically in less then hour.

Here is mine full calibration video:
https://www.youtube.com/watch?v=cQ1uTnZpUzM

I have designed and used Z probe module that is mounted only during calibration.
http://www.thingiverse.com/thing:892717

Also, I like to thank derzaubererer to point me to your calibration solution.

glad you got your system figured out:)

[duvdev]

Hi

I am trying to use the z probe.

after the first 6 points when in going down fo the second round it always hits the glass.
can some please tell me y?

thanks

[Paxy]

Hi

I am trying to use the z probe.

after the first 6 points when in going down fo the second round it always hits the glass.
can some please tell me y?

thanks

I had similar problem when Max. z-probe - bed dist was set too low. It should be maximum distance (more then Z max).

[lordgort]

"I had similar problem when Max. z-probe - bed dist was set too low. It should be maximum distance (more then Z max)."

how did you exactly do to solve this problem? sorry, english is not my mother language and the names for the parameter in the programm are not well enough described for me.
z-probe-bed distance?

@RolliRowland
maybe im thinking wrong, but in my university we "see" everythink from the base coordinate system (x:0,y:0,z:0) so im a little confused with these ^^
from the default values i believe you are using the "noozle coordinate system" is that right?

everything i write is meant to sound friendly, i appreciate every help i can get

[Paxy]

how did you exactly do to solve this problem? sorry, english is not my mother language and the names for the parameter in the programm are not well enough described for me.
z-probe-bed distance?

If your Z probe max bed distance is too low, for ex. 10mm, maximum distance firmware measure is 10mm even if z probe had traveled 300 or more mm.
Just put same large value in this firmware settings, greater then distance between bed and heatend, and you should get correct reading of Z probe distance after first measurement.
If this value is too low, after first measurement program decrease Z max to very low value so Z probe is ignored and heatend crush to bed.

[lordgort]

so i should try z-probe start heigh : 310mm?

[Paxy]

so i should try z-probe start heigh : 310mm?

No !
Go in Repetier-Host and Firmware Settings (if your firmware is EEPROM based) and change Z probe max bed sistance to at least 310mm.
Then close Repetier-Host and try with OpenDACT.

[lordgort]

wow thanks XD

//

but now it sets my Z max lenght to 708.975 after the first bed measuring :-/

[duvdev]

so after a few iteratons the head slamed in the glass
digonal rod gor the value -1023
and drom the eeprom the hor radios was abou 700
[img]http://i.imgur.com/bxOU0E6.png[/img]
why is that ?
how can i fix it?