Page 1 of 1

Auto-calibration options using FSRs?

Posted: Sun May 22, 2016 9:32 pm
by HumanLiberty
I installed FSRs on my Max v2 some time ago with the intention of using RollyRowland's OpenDACT auto-calibration software.
Though the FSRs all trigger correctly and I was able to implement commands on the printer via the software, The FSRs' signal never had an effect ad the nozzle would always crash into the bed. Was not able to fix this and have moved on.

I understand 626Pilot has an auto-calibration script out there, but that it requires a smoothiboard to run - which I don't have. Not sure of it's compatibility with FSRs either.

Does anyone know of a reliable way to auto-calibrate with FSRs?

I run MC on a mac, but have access to an old Windows XP machine if need be.

I'm printing all the way at/around the edge of the platform I already suffered the indignity of having to buy the part I need from a guy on 3dHubs - it broke due to insufficient infill for its application, and I'm really hoping to do the replacement myself, but the calibration issue has been the kiss of death.

Many thanks for any help!

Re: Auto-calibration options using FSRs?

Posted: Sun May 22, 2016 9:54 pm
by IMBoring25
As I understand it, the 626Pilot script and the stock Duet autocalibration routines both work with FSRs, but I don't have them so I'd suggest a thorough search.

What are the dimensions you're trying to make?

Re: Auto-calibration options using FSRs?

Posted: Sun May 22, 2016 11:37 pm
by HumanLiberty
10.73" circle. Man it's been a bitch.

Re: Auto-calibration options using FSRs?

Posted: Mon May 23, 2016 12:11 am
by IMBoring25
10.73 inches is 272.5 mm. Are you sure it will go that far at the level of your bed? I've made a 270mm turntable disk on mine, manually leveled, but attempting 275mm caused the Cheapskates to hit the base when it got opposite one of the towers.

Re: Auto-calibration options using FSRs?

Posted: Mon May 23, 2016 1:01 am
by HumanLiberty
Yes, I had that problem at fist too - ultimately fixed it by upgrading to tricklaser's 325mm CF arms.

Re: Auto-calibration options using FSRs?

Posted: Tue May 24, 2016 10:17 am
by geneb
Or you could spend half that and get the 290mm ball & socket arms from SeeMeCNC that will allow you to easily print to the full 280mm diameter of the bed. :)

g.

Re: Auto-calibration options using FSRs?

Posted: Tue May 24, 2016 12:56 pm
by ccavanaugh
HumanLiberty wrote:I installed FSRs on my Max v2 some time ago with the intention of using RollyRowland's OpenDACT auto-calibration software.
Though the FSRs all trigger correctly and I was able to implement commands on the printer via the software, The FSRs' signal never had an effect ad the nozzle would always crash into the bed. Was not able to fix this and have moved on.

I understand 626Pilot has an auto-calibration script out there, but that it requires a smoothiboard to run - which I don't have. Not sure of it's compatibility with FSRs either.

Does anyone know of a reliable way to auto-calibrate with FSRs?

I run MC on a mac, but have access to an old Windows XP machine if need be.

I'm printing all the way at/around the edge of the platform I already suffered the indignity of having to buy the part I need from a guy on 3dHubs - it broke due to insufficient infill for its application, and I'm really hoping to do the replacement myself, but the calibration issue has been the kiss of death.

Many thanks for any help!
Did you add a jumper to the FSR board to make it normally closed? I learned the hard way and peened my nozzle closed by thunking it too many times... I was in too much of a hurry and didn't slow down and read through the documentation closely.

Re: Auto-calibration options using FSRs?

Posted: Tue May 24, 2016 2:14 pm
by HumanLiberty
Ccavanaugh - good question. No jumper. My FSR kit didn't come with any documentation - had to figure it out from whatever I could find online - I think there was something in these forums. Jumpers were mentioned, but didn't appear applicable to me at the time. So no, they're default is open, I believe. You're saying it should be the reverse?

Gene - Those weren't available at that time - this was right when TL came out with the longer arms - maybe at least partly in response to my squeekywheelifying. Anyway, I wouldn't have come out of pocket to bring something I bought up to advertised spec - that's supposed to be for improvements beyond spec - anything else is on the company.

Re: Auto-calibration options using FSRs?

Posted: Sat May 28, 2016 6:24 am
by ccavanaugh
HumanLiberty wrote:Ccavanaugh - good question. No jumper. My FSR kit didn't come with any documentation - had to figure it out from whatever I could find online - I think there was something in these forums. Jumpers were mentioned, but didn't appear applicable to me at the time. So no, they're default is open, I believe. You're saying it should be the reverse?

Gene - Those weren't available at that time - this was right when TL came out with the longer arms - maybe at least partly in response to my squeekywheelifying. Anyway, I wouldn't have come out of pocket to bring something I bought up to advertised spec - that's supposed to be for improvements beyond spec - anything else is on the company.
A Duet controller/firmware expects it to be jumpered. but I'm not sure of the other boards.

Re: Auto-calibration options using FSRs?

Posted: Sat May 28, 2016 10:33 am
by HumanLiberty
Gotchya - thanks ccavanaugh.

Re: Auto-calibration options using FSRs?

Posted: Wed Jun 08, 2016 3:47 pm
by Howler
I know I'm kind of late here, but I recently installed FSRs and had a similar issue with OpenDACT. It was because of the Z Height. OpenDACT fast moves to Max Z - 10 mm; then it moves slowly and listens for the FSRs to activate. My Max Z height was set way too high (FSRs plus mounts removed Z height).

I'm going off memory here, but if you go to the advanced section and hit "read values from EEPROM" and set max z height to whatver it is minus like 50mm, it should be safe. Then hit "save to EEPROM". I also set a book on top of my build plate for the first run to make sure I didn't hurt the build plate. Finger on the off switch until I saw it was going to behave.

I keep meaning to issue an update for OpenDACT to have an option to figure out the current max Z before calibrating to eliminate this issue. It's on my list... maybe I'll bump up the priority ;)