Good Ole VI Command is Not Working

[whermansen]

2003 Prt Standard 2 head
Installed Control Software Version 3.4.6 on new Computer (No Update) After upgrading to 4g board. Design Computer Separate. PartWizard 2.0,

OK I keep track of my cutting files with master files using the good ole VI command.(where you switch the 3 and 4). Now since the Control Software upgrade it doesn't work because of different parameters and such. So I went to Upgrade my VI commands to a syntax the control software would understand.
VI, 3,0,0,0,X,Y,A,B,4,Z,1 'Switches to Accesory Z.
VI, 3,0,0,0,X,Y,Z,B,4,A,1 'Switches Back to Primary Z
When I put this in my masterfile the machine goes through its offsets. (all changes are done at physical location 0,0,1.5)
Then shoots me up a message that says. "Could not correct location of Axis returning to original value" and keeps the primary z active.
Now I have been working on this and this is what I have found out. When I use the fill in sheet using the keyboard it allows me to control the second z with MZ and JZ commands and doesn't give me an error. But when I put it into a file or custom file It shoots me the error. Here is the simple file I have been using to troubleshoot this.
'Switching From Primary Z to Second Z with correct offset'
' date 03-04-04'
'Henderson
'Listed as Custom Cut #4"
'-----------------------------------
SA 'sets absolute setting'

MZ, 1.5 'moves Z to 1.5
M2, 0,0 'Moves to home
VI, 3,0,0,0,X,Y,A,B,4,Z,1 'Switch to Second Z with new syntax;
m2, -5.570, .245 'moves to the offset coordinates'
Z2 'Zeros x and y coordinates'

The control software will not execute this program without the message.
Now most of you are talented creative people. I am mass production no time for fill in sheets.
Any ideas? little help
Thanks in advance

[br928]

When VI is called in a custom program the results are only temporary and revert back when the program exits. Use the SV command before the program exits to make the changes permanent.

I had the same problem.

VI,,,,,X,Y,A,Z,4,B
SV

[zeykr]

Didn't realize you had a shopbot there in Cassville. Knew there was a novelty maker in the area but didn't know the name of the company. I sent you a catalog request.

[srwtlc]

Along with Stan's post, try leaving parameters 2,3, and 4 blank as they are obsolete and the 0's may cause problems.

Not exactly sure of what you're doing, but couldn't it be done with the new VO (Values Offset) command? Just thinkin'.

[br928]

Scott,
I think he is doing what I do and swap the two Z axis between Z and A by reassigning the channel (3 & 4) that writes to Z and A (ie. 3-Z 4-A or 3-A 4-Z). Toolpath software expects Z to be on channel 3.

All of my programs write to the Z axis. But a custom program I wrote determines which Z is the primary. In my case it's a spindle or drill. I never use both within the same cut file.

When you leave out the zeros be sure to leave the commas(,) as a place holder.

[garyc]

Wade & Stan...
Long gone are the days when it took custom programming or master files to enable using both the Z and A axis in a single file. Assuming that your offsets are in the system as per the 3.6.++ versions, simply post with the ShopBot TC arc (or inch) post processor. Tool numbers determine the active heads and proper offsets are in play. All offsets are off at file end.

Here is syntax from current MTC file to enable A (as 3rd axis): VI,,,,, X, Y, A, Z

Life is good. (And easier than it used to be)

[br928]

Thanks Gary,

I guess I never really looked into it since I only run one Z in any one cut file. I will try it on future files. With all my old files I run I will have to stay with the old school method.

Something about old dogs and new tricks comes to mind.....hmmmmm.

Well I still use my H-P calculator from college that has reverse polish notation. I still can't use a calculator that has a = sign on it! (JK)

[whermansen]

Stan your the Man!!! I think we have a winner. I didn't realize the control software viewed those vi commands as temporary. So can the SV command be tucked in behind the VI in a Custom File to make that permenant? Then a little c4 will do the Trick...(not that kind of C4...ka boom). All those wonderful files I have are not going to have to be redone before we can fire up again.

Gary....I had never tried different post processors before this problem arose and worked at it hard as a work around. I wanted to take maximum advantage of the control software upgrade. I think Partwizard 2.0 is getting dated and its posts wouldn't run right with the variables I inputed. And I was behind on the learning curve. yada yada yada
But that is another thread...

Thanks Guys I'll keep you posted

[whermansen]

Sad when your 42 with a 2003 shopbot and classified as old school. Getting to the age when change is resisted more.

[br928]

Wade,please...42?...I got t-shirts that old! (not really) Somewhere along the line of software improvements my custom files, that swapped axis, stopped working. That's when Ted or someone at SB figured out that I needed to add the SV command to my custom files. All is well after that. You should be able to use you old files now.

[whermansen]

SV Works.....Like manna from digital heaven. How sweet it is.
THANKS A TON

[br928]

Glad to hear that Wade. I was wondering if I was the only one to ever have that problem!

[ssflyer]

Stan,

Damn, I am getting old! I had to take college classes to learn the slide rule! :cool: I remember my first calculator - 4 functions, EL display and $79!
However, I still use my HP RP calculator - way faster input than normal ones! ;)

[br928]

Ron,

I had a slide rule too but luckily it was on the way out. Only 3 digits of precision at best (usually enough)! My first H-P cost over $400.

[MogulTx]

HAHAHAHAHAHA

My first HP was a 12C financial calculator in 1984-ish and then a used HP4C in about 1989 or 1990... I bought it used for about $100 and loved the RPN.

My next was in 1996... and I paid about $200... used again. It is a 48SX and still has marks where the kid -named "Riley"- engraved it.... (right before he probably disappointed his folks by dropping out of UT School of Engineering! And sold his calculator to some adult who could not use it nearly as well!) I have used his calculator for all these years with NO problems- and have loved it. I still can't use HALF the functions this old tank has... but it does well for me to this day. And nobody will steal it because they (1) don't want to have to carry it away and (2) most of them don't really know what "RPN" is about....

One of these days I will get to the level of programming the SB that you guys are. For now, I am content to make my files and run my 2D work... I just wish that the HP deskside - with all its memory and all its attributes-- would run my SB at HALF the reliability of this old calculator.... ! (There is a Dell in my near future, I think! Maybe Santa will bring it to me!)