Messages

1

Brains Development / Re: Delay Reading DRO's

« on: March 05, 2010, 02:16:05 PM »

RC,

Great idea.....that should have worked.
But when I tired it there is a split second before the dwell takes active that the spindle is 0 rpm and throws a true.
So the brain runs thru too fast to see the dwell active.

Somehow I have to have time to get the spindle past 0 rpm before comparing that it is 0 rpm.  

Thanks for the idea!!

Jim

2

VB and the development of wizards / Re: Latest Mach Ver .038 tool change

« on: March 05, 2010, 12:33:42 PM »

To All,

Dave's response was right on......DoButton(0) worked perfectly.

Also I removed the DoButton(0) in the m6end file so now it's empty.
The problem has been solved and works great.

Thanks again Dave!!

Jim

3

Brains Development / Delay Reading DRO's

« on: March 05, 2010, 12:30:24 PM »

I am making a brain to watch spindle rpm and e-stop if the feedback from the VFD is 0 while spindle led is on.

Problem.....When the spindle on command is given, at that point the spindle feedback is 0 for a split second so there is a failure.
Question.....How can I delay the reading of the feedback RPM after the spindle led in on so I can wait so many seconds for the spindle to be at speed, then start checking the RPM feedback to make sure the spindle actually came on?

I have tried for several hours to use a timer to delay the reading, my assumption is that you can't use timers to delay the reading.

Thanks in advance!

Jim

4

VB and the development of wizards / Re: Latest Mach Ver .038 tool change

« on: March 04, 2010, 10:04:56 PM »

Dave,

Thanks for your time and support.

The version I was using before this was 2.xx.xx something.
I have tried to update my versions in the past and something else is always broken so
I have been using that version since it seemed the most stable.

The main problem with that version is the spindle not always starting up and crashing parts.
So I decided it was time to update and hope that is fixed. Then the tool change problem.

I will try the DoButton(0) command. That seems easy enough. Because it is on the old functions list I never tried it.
I did notice that if I did a standard cycle start it worked like it's supposed to. It was just heck having to hit cycle start 2 or 3 times when there should be no tool change.

I am just thinking about how I have been using this in the past.
Step 1  m6start has a check to see if there is a tool change needed. No tool change needed so issue a cycle start.
Step 2  m6end issue a cycle start to get out of the macro and start program.
So during normal run it looks like you hit cycle start call tool and no change needed so continue running.

If there was a tool change needed....
Step 1  m6start has the tool number update and wait for a change.... user changes tool cycle start...
Step 2  m6end still has issue cycle start to end macro and continue running.

I can't remember off hand... if there was nothing in the m6start and m6end does mach require 2 cycle starts to get the program running again?
Also does the programmed cycle start interfere with the manual cycle start in the m6end. Seems like it may be a double cycle start.
I do know double cycle starts have caused serious problems. Especially while in the middle of a macro.
I have seen many times the program takes off running and the macro isn't even done yet and always results in a machine crash.

Do you have any idea about spindles not starting up all the time in previous versions?
I read in the update list about 3 or 4 versions ago something was fixed with regards to spindle not starting up...
That is the main reason I updated to this version.

Thanks again Dave, I will try your idea tomorrow and report back for future references.


Jim

5

VB and the development of wizards / Latest Mach Ver .038 tool change

« on: March 04, 2010, 04:31:13 PM »

Just installed ver .038 and now have tool change problem.

I have manual tool changer so must use Stop Spindle & Wait option in config.

If I have T1 in the spindle and is current tool and read T1M06 how do I get the tool changer to ignore the command to change tool.
I used to check if tool selected = current tool and then issue a DoOEMButton(1000) in the m6start file.
Then it would jump to m6end file and I would issue another DoOEMButton(1000).
Program worked and continued on......

Well now issuing a DoOEMButton(1000) does not work. It starts the cycle timer but nothing happens in the program.

I also tried doing Auto Tool Changer in the config and in the m6start file did a SystemWaitFor(55) or (start) and nothing happens.
So that command doesn't seem to work anymore.

Any Ideas???

The problem seems simple enough....if tool selected = current tool ....do nothing.

Thanks!!

Jim