Log in

View Full Version : Help with Z Zero going from inch to metric



Bob Eustace
04-09-2013, 06:32 AM
In deep poo with this one. We work in inches but every couple of months we get a long run job in metric. No problems BUT running 3.8 we get these extra messages we didnt get in the past (apart from changing to metric) asking us to reconfigure the machine. Simple job calling for 3 pockets 12mm deep. We are getting 9.12mm??? Looked at the reconfigure menu for plate thickness and it currently reads 0.121 BUT it doesnt say what units. Could some clever person point us in the right direction please as I dont want to create more problems???? Using the mm arc speed PP.

What would happen in Aspire if we designed in mm then clicked the convert button to imperial and used the inch PP??

Thanks

adrianm
04-09-2013, 06:57 AM
You can design in any unit size you like in Aspire and the Post Processor will take care of all the conversion to whatever unit is specified in the PP.

I mix units all the time in my files but always output using a metric PP.

There are automatic calculation features in Aspire that help out as well. Entering 100*i= will convert 100mm to inches and entering 4*m= will convert 4 inches to millimetres.

Looks like the z-zero routine has changed with the latest release so it now expects the plate thickness to be in the same units as SB3 is running in. Previous versions did conversions. Presumably there were issues with that.


11/15/12 Routine no longer tries to swap between measurement systems. If Setup (under tools in ShopBot)
' ... has configured my_variable.sbc file for inches, ZZERO will expect inches; if mm then mm

gerryv
04-09-2013, 10:48 AM
Sounds like a bit of a nightmare for Canadian users as we're metric but with our markets being so integrated with the Americans we constantly are having to switch. I wonder if there will be any kind of "For Dummies" tutorial made available for those of us who do not get into any programming at all?

adrianm
04-09-2013, 11:08 AM
If you're getting actual SBP files from customers to cut I can see it being a bit awkward but if you're generating PartWorks/VCarve/Aspire files it shouldn't be an issue.

You can work in whatever units you like just make sure that the Post Processor you use matches the unit setting in SB3.

We have the same issue in the UK regarding metric and imperial. Probably half the work I get is specified in inches despite us being metric for forty years!

I do suffer from a bit myself as although I always prefer to design in metric I specify all my feed rates in inches per second.

myxpykalix
04-09-2013, 02:38 PM
Hey Bob!
Here is a clumsy alternative that works. This is a small app that does the conversions from one to another and you could just input the conversion numbers till you get this fixed:

http://joshmadison.com/convert-for-windows/

Bob Eustace
04-09-2013, 05:51 PM
Thanks all - it is very reassuring to be able to draw on the vast bank of knowledge on this very unique forum. Thanks for the life line!

So Adrian if we occasionally design in metric using the select units in Aspire, then save to the inch/arc PP and then cut on the bot using SB 3.8 set to imperial as normal, all should be OK?

Bob Eustace
04-09-2013, 09:38 PM
OK, Adrians suggestion of doing file in metric, saving to inch pp and cutting with 3.8.2 set to inch works EXCEPT it is deducting the thickness of the zero plate from the pocket depth. Other dimensions are just fine. Should there perhaps be a minus sign in front of the 0.121 in the plate thickness. Cautiously looked in my variables and it just has =0.121.

Any suggestions greatly appreciated!!

myxpykalix
04-09-2013, 11:30 PM
I can't answer your question directly and regarding the plate thickness being .121 I think rathewr then simply putting a minus sign in front of the .121 I think it might be more reasonable to put the metric equivilent of .121 ?:confused:

I can tell you that you are probably going to forget to change it back and going to screw something up.:eek:

Bob Eustace
04-10-2013, 12:20 AM
Jack it as me stumped. It is 3mm shy. Of course I could go the daft way and tell sb3 that thebsero plate measures nothing. It did the customer sample with zero probs now it has gone spastic.

adrianm
04-10-2013, 05:02 AM
Sounds like something is screwed up from the previous attempts.

Designing in metric, saving as inches and then running SB3 also set to inches should work fine.

I'd run through the setup routine again to make sure everything is as it should be.

Once you've zeroed to the plate check that the Z readout is actually 0 and do a MZ,0 to see that the bit moves to zero.

If it doesn't then something is definitely amiss with the SB3 side of things.

zeykr
04-10-2013, 07:19 AM
How about going back to the previous version of zzero.sbp?

Should be a backup copy of sbparts directory when new version was installed. Looks like the also changed how safe_z pullup is determined, but if it worked in past for you, probably still will.

Bob Eustace
04-10-2013, 07:10 PM
Adrian - Thanks for the MZ 000 tip - the bleeding obvious and totally fuzzy thinking on my part. Have three urgent jobs and definitely not focussing on one at a time. Well doing a MZ 000 puts the bit on the surface perfectly. The X and Y dimensions are also perfect. Initially the file cut fine on the test piece. On the first production one we got a comms failure about 30 seconds into the job. Rebooted everything and all three pockets then came out at 9mm instead of 12???????

Ken - yes I'm almost at the point of going back to 3.6. In desperation I have sent all files to Shopbot but nothing back as yet.

srwtlc
04-10-2013, 07:26 PM
Bob, did you rezero the z axis after rebooting? Position can get messed up after a comm error. Good idea to reset all axes when that happens.

Bob Eustace
04-10-2013, 07:54 PM
Scott - yes I did and have tried several times since.

Simops
04-11-2013, 06:58 AM
Hey Bob.....I stayed with 3.6.44 and have no issue, no comms failures, all good.....there just is too much negativity about 3.8.x that I was not prepared to take the chance mucking about with a driver that appers simply not to be robust enough compared to 3.6.44. I guess it's just not universal enough for everyone! Those that have it working OK are lucky, others are not. This hit and miss driver is not up to my standard to bother with......I'll wait and see how it goes.

Change back to 3.6.44 Bob and de-stress:p

Cheers