OpenDACT(Delta Automatic Calibration Tool) - For Repetier

[mhackney]

We keep cross posting!

Ok, I will focus on using the windows version on the Kossel with the RAMBo card. That is what I reported in my previous post above. Just hangs after requesting eeprom

[RollieRowland]

Ok, I figured out how to uninstall and reinstalled the new version on Win8. I am running into the same issue as on the Mac:

Connected
Request to read EEPROM sent


and then it hangs. I have to ctrl-alt-del to kill from task manager

I made a change real quick, and removed a Thread.Sleep after that command is sent. I'm not sure if it sleeps for 1000 milliseconds or 1000 seconds. New .exe - https://drive.google.com/file/d/0B06WCA ... sp=sharing

If this doesn't work, this may be difficult for me to do while not in front of a printer....

But since it is hanging, would you want to debug the build and see where it hangs at?

[mhackney]

Ok, I was actually looking at that exact code too. I divided the timeout by 10 but that had no effect. I also set a breakpoint at private void parsedata_event(object sender, EventArgs e) but never got the break. Isn't that the thread entry for handling a response from the printer?

[mhackney]

I set a breakpoint at the read eprom line just to make sure my dev environment is ok. It is, I break properly and single step through. I just need to figure out where the thread entry point is after the button2_Click completes.

[RollieRowland]

Ok, I was actually looking at that exact code too. I divided the timeout by 10 but that had no effect. I also set a breakpoint at private void parsedata_event(object sender, EventArgs e) but never got the break. Isn't that the thread entry for handling a response from the printer?

Yes that is the entry point for handling the responses. Since this is the case, I am wondering if it is connecting to your printer at all? That could be causing the hang-up. Check the log in the advanced tab. Watch for any response coming from the printer. If there is no response, then it isn't connected(properly).

And after button2_Click is completed, it relies on a response from the printer to go any further. Go to line 227

[mhackney]

Ok, on the Kossel/RAMBo when I connect the advanced Printer Console shows a bunch of goblet gook ???/?? stuff that continues to add/scroll fairly regularly

[RollieRowland]

Ok, on the Kossel/RAMBo when I connect the advanced Printer Console shows a bunch of goblet gook ???/?? stuff that continues to add/scroll fairly regularly

Sometimes when I connect to the port it shows any combination of w, a , i, and t ("iatw", "aiat"). It has never caused a problem but I am not sure why it does that.

[mhackney]

Hmm, looking at the source I may have found the issue:

//port.BaudRate = int.Parse(textBox5.Text);//250000

In button2_Click

The baud rate is the default 9600. But explicitly setting that to my 250000 is still not connecting. I'll spend some time on the connection code.

[RollieRowland]

Hmm, looking at the source I may have found the issue:

//port.BaudRate = int.Parse(textBox5.Text);//250000

In button2_Click

The baud rate is the default 9600. But explicitly setting that to my 250000 is still not connecting. I'll spend some time on the connection code.

Well then.... I must've gotten distracted while "fixing" that. There may also be other settings that pertain to connection that need modified that I may not have included in the connection i.e. parity, flow control, stop bits, data bits, etc.

[mhackney]

Just out of curiosity, has anyone been able to calibrate with any version of the application?

[RollieRowland]

Just out of curiosity, has anyone been able to calibrate with any version of the application?

I haven't heard that anyone has used the automatic version yet, other than me. I have calibrated with version 2.0.0 (+/-0.015mm tolerance) but haven't been near my printer to test 2.0.1. If you have a decent calibration currently it may be best to wait for me to test it on Monday.

Although with the manual HTML version several people have and the calibration code is essentially the same.

[mhackney]

Thanks, I'm just trying to figure out if anyone has been able to connect to their printer with the application.

[RollieRowland]

Thanks, I'm just trying to figure out if anyone has been able to connect to their printer with the application.

I would assume that it has only been me so far, unless others have used it and didn't say anything.

[RollieRowland]

https://drive.google.com/file/d/0B06WCA ... sp=sharing
Here are the source files from 2.0.0, I just tested it and it connects. I also tested the version we are working on and it is NOT working. I cannot connect to my printer either on this version.

[mhackney]

Ok, one step forward...

I'll take a look at the 2.0.0 stuff

[mhackney]

in 2.0.0 the kossel/RAMBo is in a loop displaying Resend:822 after I connect. Any idea what that is?

[RollieRowland]

in 2.0.0 the kossel/RAMBo is in a loop displaying Resend:822 after I connect. Any idea what that is?

I did notice my printer do this once, it just replaced "ok" or "wait" with "Resend:". I just restarted my printer to get it to display "wait again."

[mhackney]

Ok, restarting the printer did the trick. I can now connect and run the calibration and send Gcode. It completes the calibration routine and then crashes so I am not sure if stuff is being written to the eeprom, I'll have to conduct a test.

[RollieRowland]

I tried copying the button2_Click code from V2.0.0 to the V2.0.1, it connected and started to read the EEProm. However, it froze and instantly crashed. I can't debug from here, I was using Teamviewer to connect to my Dads desktop where the printer is.

Your new post just came in. Now did you run the advanced or normal calibration? Check the M206 command, it is what I am using to send the values back to the printer.

[mhackney]

Ah, when I issue M206, that's when it crashes. I did this several times including immediately before calibrating and it crashed when I entered M206.

[RollieRowland]

Ah, when I issue M206, that's when it crashes. I did this several times including immediately before calibrating and it crashed when I entered M206.

Try sending this to your printer in a single line. It will just set your probing speed to 20mm/s. If that crashes, try it in your host software or V2.0.0
"M206 T3 P812 X15"

[mhackney]

I'm doing all this in 2.0.0 - that's where the M206 is crashing. The code you posted above also crashes immediately.

[RollieRowland]

I'm doing all this in 2.0.0 - that's where the M206 is crashing. The code you posted above also crashes immediately.

Try to send that code via mattercontrol/repetier/etc.

[mhackney]

Ok, after issuing the M206 command above in RH and then re-running v2.0.0, it hangs immediately every time I click Calibrate. I rebooted the printer and tried several times.

[mhackney]

Ok, I rebooted both the laptop and the printer and tried it again. This time it worked and did not hang after calibration - v2.0.0
Not sure how good the calibration is but it went to completion.