Hello Guest it is April 23, 2024, 05:10:42 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - H2

Pages: 1 2 3 »
1
Mach SDK plugin questions and answers. / Re: Impact engraving plugin
« on: November 11, 2010, 12:26:07 PM »
Art -

Thank you that is what I was looking for, I feared it but thought it would not be fast enough either and defer to your opinion.  I will look into how to add an additional drive.  I am running a Campbell board with all axes full.

Great thread and fantsatic information. Thanks for paving the way Andrea!
All the best, Henry

2
Mach SDK plugin questions and answers. / Re: Impact engraving plugin
« on: November 11, 2010, 11:52:07 AM »
Tweakie,

I am still trying to figure this out so bear with me.  The solenoid needs something to make it fire.  I am under the impression that Andrea was using a drive to fire the solenoid. IE gecko or....  I have all 4 axes in use so I was wondering if I could use my PLC (it is set up for a toolchanger with outputs to spare) to fire the solenoid.  This of course is if my assumptions on how this works is correct.... ?

all the best, Henry




3
Mach SDK plugin questions and answers. / Re: Impact engraving plugin
« on: November 11, 2010, 10:38:07 AM »
Tweakie or Art  do you think that a PLC would control the impact head effectively?
All the best, Henry

4
LazyTurn / Re: LazyTurn
« on: March 05, 2010, 08:59:30 PM »
Ouch - sorry to be stupid but where can I find the update?
All the bset, Henry

5
LazyTurn / Re: LazyTurn
« on: March 05, 2010, 05:36:02 PM »
Thanks Rich - I will go back and check it out again AAAAAAAAAAHhhhhhhhhhhhh!
All the best, Henry

6
LazyTurn / Re: LazyTurn
« on: March 05, 2010, 05:20:54 PM »
Lurker here and downloaded the March5 exe of lazy turn.  When it's in the Mach directory I got a lost DLL error on start up.  The previous exe ran fine.. is it me ?

Thanks! all the best, Henry

7
General Mach Discussion / Re: End VB ! (script that is)
« on: March 22, 2009, 06:12:27 PM »
jimpinder,

Apologies for the delay getting back to you - I have been trying to get my head around the information you provided and waiting for the light to come on but the room is still dark ;-)

If the following was added to the toolchanger code after the variables - it would work?

Stillgoing = 1
 While Stillgoing
 Stillgoing = Not GetOEMLed(800)
 Wend
 Code "(Reset pressed)"

The VB appears simple but I am missing something basic to understand it just yet ;-)

I appreciate your help, Henry

8
General Mach Discussion / Re: End VB ! (script that is)
« on: March 20, 2009, 05:56:04 PM »
jimpinder - Excellent!

Your theory and M1100 worked on my mill. 

Now the question is - is it possible that you can explain how your M1100 code translates to something I can learn from and put into my code?

Thank you!, Henry

9
General Mach Discussion / Re: End VB ! (script that is)
« on: March 20, 2009, 05:28:57 PM »
Wow - Thank you , I will try the M1100 script and see if it works on my mill.

I looked at the M1100 code and to be honest I haven't got a clue what it does ;-)I  am a babe in the woods on the VB.

Hood -
The macro pump idea is interesting...

I will report back Thanks again!  Henry 

10
General Mach Discussion / Re: End VB ! (script that is)
« on: March 19, 2009, 10:30:32 AM »
Thank you for the response.  My ability at the moment to use VB is VERY limited - just getting started and I thought the retrofit was tough!

I understand what you are saying about adding the G code to the script but maybe I phrased something wrong - what happened is while the machine was in the tool change script the machine lost some steps and started to take a walk on me so I hit the e-stop.  When I reset Mach and came out of the physical e-stop the VB script continued running where it left off - taking a walk! What would be nice in the script if possible is.

During the running script if an e-stop, reset or limit occurs abort / end the vb script.

Looking over some of the VB information - and correct me if I am wrong - the VB seems to execute each line of code similar to G code and not have a running memory to keep track of a potential E-stop or limit?

On the second issue I think it solved itself with your clarification of the DRO remembering information even after being shut off.... that will accomplish the same goal.

Thank you for your help
All the best, Henry 



Pages: 1 2 3 »