Messages

41

General Mach Discussion / Re: Haas VF1 Conversion

« on: July 06, 2016, 10:06:26 AM »

Thanks Hood.  The persistent tool seems do what I need.
CSLabs got back and is pretty sure it is a Mach issue.  They were able to dupilcate the issue using GetUserLed so it's not just when their hardware is called.  Using the If ....=0 seems to take the place of IF NOT just fine so I'm good.  Wonder if Mach 4 has similar issue?

42

General Mach Discussion / Re: Haas VF1 Conversion

« on: July 04, 2016, 01:44:16 PM »

Just an update.  I have the gear change working well.  Its funny, I figured I would start learning the scripts with Gear change thinking it would be much easier than the tool changer.  It actually is more difficult because of the way SpinSpeed and M3/M4 are tied together is not so obvious way.  But it ended up being a great learning experience.

I ran into a problem where anytime I used an "IF NOT GetInBit(?) THEN" statement, it always returned true irregardless of the input state.  Had no clue what was making my programs do silly stuff.  Finally narrowed it down to a plug-in issue I'm pretty sure.  If I use the "IF NOT GetOEMLed(?) THEN", this works as expected so it's not likely a mach issue.  But if I call on CSLABS hardware, it never worked.  A regular "IF GetInBit(?) THEN" statement does work correctly.  I emailed CSLABS support and waiting on reply.  As a workaround, I can do this.
"IF GeTInBit(?)=0 THEN" and this works inplace of using the IF NOT.

So I moved on to the tool changer and found it to be rather straight forward so far.  I am able to orient the spindle with no speed or timing issues straight from the CSLABS I/O.  Tool carosel seems to have no issue landing on the correct tool with the geneva cam setup.  Never really paid attention to how they work and now I get it.  Awesome design.  Instead of trying to land within 1 degree or less, you now get to just land within 180 degrees and you are good.  Clever solution.

So I have it where the Z, Carosel in/out, and Carosel tool select all work in harmony.  I want it to work as close to the original machine as I can.  On power up and Homing, the Haas always homed the z, then x and y and then it would go put the existing tool in the current pocket.  Raise Z to safe and run carosel to tool 1 and load that tool.

I like this and it makes perfect sense to me.  It seems Mach likes to just load up with tool 0 and its up to the operator to not forget to fix this.
So couple of questions:
What would be the best way to add carosel and tool 1 selection when homing all?
Can I eliminate mach displaying a tool zero.  Instead, all tools are 1 through 16.
Thanks,
Mike

43

General Mach Discussion / Re: Haas VF1 Conversion

« on: June 26, 2016, 01:07:01 PM »

Okay,  Don't know why I didn't figure it out yesterday while on the machine.  Playing around today, It looks like I have to Catch the speed request inside of SpindleSpeed.m1s.
Just as Dave pointed out.  I think I tried to be smart and failed.  Figured I didn't need to go into SpindleSpeed if I was doing an M3.  Clearly an  M3 (which has a S???) goes through the SpindleSpeed call first and then runs the M3 call.  If the returned value from SpindleSpeed exceeds the current Pulley max, Mach changes it to Max and then runs M3.  I get it.  I knew there was no way that I write my first script and run into some fundamental bug.  I will try to dumb myself down moving forward.
Thanks Guys.

Feeling like the tool change is going to be very manageable.  Been a little nervous throughout the re-wire that I wouldn't be able to complete the changer and would end up with a basic knee mill.  This stuff ain't bad at all once you dig in a bit.

44

General Mach Discussion / Re: Haas VF1 Conversion

« on: June 25, 2016, 07:59:41 PM »

I think the number one question is

Did they throw the data away (the original speed request) or can it be plucked from somewhere?

45

General Mach Discussion / Re: Haas VF1 Conversion

« on: June 25, 2016, 07:18:44 PM »

Got the gear change working just fine.  First VB code I ever wrote.  But now I have a problem that is Mach related.

If I am running or was running in low gear at 500rpm and stop the spindle with M5.  My current pulley is Number 2
I now enter M3 S2500 (my threshold for gear change is 999rpm.

Mach looks at my pulley 2 max rpm and figures out it is too high.  It throws a warning and reset my speed command to the max in the pulley setting.  Then it calls M3 macro.

So the problem is, I have the code in the M3 macro to look at requested speed (Mach just changed it) and decide if gear change is needed.  Also, as part of that macro, we set the new pulley to number 1.

I can't just change the pulley max rpm as that is directly tied to the analog out that runs the drive.  Right now, at all speeds in any gear, I'm within .5%.

Is there a way to tell Mach to ignore max speed?  Or is there a place it puts the original request that I could go get?

The issue is that when it finally shifts gears, runs the spindle up- I'm stuck at the low gear maximum.  That ain't cool at all.  Easy way to break a tool when I requested 4000rpm and in runs into the material at 1300rpm with only a note at the bottom of the screen. Hoping there is something in there to fix this.

46

General Mach Discussion / Re: Haas VF1 Conversion

« on: June 24, 2016, 06:48:16 PM »

My new panel

47

General Mach Discussion / Re: Haas VF1 Conversion

« on: June 24, 2016, 06:46:29 PM »

Have some issues with home and limits.  Homing is perfect.  But if i jog onto a limit, it is issueing an estop and disabling everything.  Have to turn on emulate for that switch in order to jog off.  Cslabs has a smart limits setting that seems to do nothing.  I'll get it figured.  Writing first script for gear change.

I have figured out how to get the requested speed and I get the idea of slowing down to change gears.  Issue I have is how to catch a simple S200 entered into mdi.  Thats not a M03 command that I can edit in the m3 script.
  Idea would be we are running 2500 rpm on pulley one.  Threshold for gear change is 900.  A S500 shows up in mdi or in gcode program.  How do I catch that.

48

General Mach Discussion / Re: Haas VF1 Conversion

« on: June 24, 2016, 09:01:32 AM »

I got the x,y,z and spindle going yesterday.  I used Demo version of Mach 3 for now.

Was able to get about 500 inches/minute which is smoking fast.  I turned everything back to 300 in/min just because 500 will scare the heck out of you.

Gonna get the spindle gearing setup correctly today in high gear.  Then I will start working on the gear change.  This is where I'm hoping you guys can help.  

49

General Mach Discussion / Re: Haas VF1 Conversion

« on: June 20, 2016, 10:52:34 AM »

So things are coming along.  Panel is just about wired.  Haven't settled on a new spindle drive yet but figure I can play with X,Y and Z before worrying about spindle and tool changer.
Now to setting up software.

Mach 3 or Mach 4??

I'm familiar with Mach 3 so probably leaning that way.  Thoughts?

50

General Mach Discussion / Re: Haas VF1 Conversion

« on: June 01, 2016, 02:26:57 PM »

Never mind Hood.  I found that CS Labs has exactly what I need. 

Finally, I think I have a combination that will work.