Messages

3981

General Mach Discussion / Re: Skipped Parts

« on: February 07, 2013, 10:11:19 AM »

Did you really do a real-life test run ? I mean on a real machine ?

Hi Wilfried,

I only ran the tool-path (engraved into a piece of scrap) mainly because I was most interested in the efficiency of your GCode and how so much was accomplished within the 500 line limit. ( and I spotted the deliberate mistake  ).

I was using version R3.043.066 so, in retrospect, your problem may be to do with a possible restriction placed on the demo version but Graham is much more of an expert than I am so hope he can shed some light on the issue.

Tweakie.

3982

General Mach Discussion / Re: Skipped Parts

« on: February 07, 2013, 07:20:33 AM »

Hi Wilfried,

I appreciate that is not much help in resolving your problem but all 4 fuse cut-outs were executed when I test ran your code here.

Which version of Mach3 are you using ?

Tweakie.

3983

VB and the development of wizards / Re: Mach3 machine material surface ZERO script

« on: February 07, 2013, 06:39:43 AM »

Hi Andre,

If it is of any help to you this is the button script that I use (second half of page) and how I have implemented it   http://www.cooperman.talktalk.net/files/17.htm

Tweakie.

3984

VB and the development of wizards / Re: Mach3 machine material surface ZERO script

« on: February 07, 2013, 05:43:19 AM »

Which Mach screen .set are you using ?

Tweakie.

3985

Share Your GCode / Re: How to speed up simple G Code

« on: February 07, 2013, 03:05:57 AM »

Hi Jack,

I think John has described the operation of these commands perfectly and I can only repeat what he has already said.

The M and E commands perform exactly the same function (M10P1 = E1P0 and M11P1 = E1P1) so to avoid confusion I will just stick with the M commands.

A typical GCode sequence could be something like this;

G0 B0   (zero imaginary Axis B)
M11P1 
G0 B1   (Output #1 switched on at this point)
M11P2 
G0 B0   (Outputs #2 switched on at this point)
M10 P1
G0 B1   (Output #1 switched off at this point)
M10 P2
G0 B0   (Output #2 switched off at this point)

Etc.

There has to be an axis movement following the M10 / M11 command in order for it to execute and I often use an ‘imaginary’ axis B which has been configured at minimal steps per unit with maximum Velocity and Acceleration if there is no ‘real’ axis movement to follow the M command (this may sound a bit strange but some software (such as DotG) requires a trigger point whilst the X,Y & Z axes are all stationary).

Execution time differences, measured some while ago, was 100mS for the M3 command and 2mS for the M11P1 command so there could be some advantage for your application and the best bet would be to just try it and see if you can achieve any improved results.

Tweakie.

3986

Share Your GCode / Re: How to speed up simple G Code

« on: February 06, 2013, 02:29:38 AM »

Hi Jack,

It is as John has said - these commands are indeed faster but the M11P*/ M10P* command set execute in a different way and are perhaps primarily intended for laser switching.

The M3/M7/M8 are ‘stand alone’ commands (they will execute when called).

The M11P1 (turn on Output #1), M11P2 (turn on Output #2) etc. are ‘linked’ commands (they will only execute after an axis has started it’s movement).

So it may be possible to increase speed by using these commands but it would depend on the design of your machine and the speed of the solenoid operation etc. etc.

Tweakie.

3987

General Mach Discussion / Re: Skipped Parts

« on: February 04, 2013, 08:07:16 AM »

Hi Wilfried,

As far as I am aware – if it shows in the toolpath window then Mach3 will output the correct step and direction signals to follow that display.

My guess is that you are either loosing communication between your PC and the machine or else that your PC is off doing another task whilst it is running the Mach3 GCode.

Tweakie.

3988

Show"N"Tell ( What you have made with your CNC machine.) / Re: Isolation Routing PCB's and Local System Rotate.

« on: February 03, 2013, 01:35:58 AM »

Hi Richard,

I am pleased that you have managed to resolve the problem. 

Tweakie.

3989

Show"N"Tell ( Your Machines) / Re: The Laser Project.

« on: February 02, 2013, 07:23:49 AM »

At the risk of rambling on a bit, I have been closely following the absolutely excellent and quite pioneering work which is being done with low power diode lasers by John, Jeff, Dave and others in different parts of the world - for those that may be interested these threads relate;

http://www.machsupport.com/forum/index.php/topic,23456.0.html
http://www.machsupport.com/forum/index.php/topic,23584.0.html

Whilst I am quite certain that it can be done, replicating their work using a CO2 laser is not without it’s difficulties (cracking a nut with a lump hammer comes to mind) but, hopefully, I will get there.  

Tweakie.

3990

General Mach Discussion / Re: Z Height Setting Woes

« on: February 02, 2013, 03:11:01 AM »

Hi Gerry,

I am absolutely certain that there is no fault or problem with your Probing code - the issue I am suspecting lies with later versions of mach3.

I do a lot of engraving work which necessitates my use of a probing script after every tool change or when engraving different thickness laminates and I noticed a similar problem (to the one mentioned here) at the beginning of last year.

It appears that one of the Mach3 feed-hold flags is not cleared by the ‘Cycle Start’ or ‘Reset’ buttons, it becomes persistent but it can be cleared by the ‘Stop’ button. This particular flag does not affect the running of Program GCode but it does affect the way in which CB scripts perform.

My solution / work-around was to include the stop command within my probing script and this magically resolved the problem I was encountering.

I have no idea if the problem mentioned in this thread will be resolved by the same course of action but CNCjunky now has ‘DoOemButton(1003)’ added to his script and I await the results of his tests.

Tweakie.