Messages

3251

Mach4 General Discussion / Re: Mach4 Printer Port Discussions

« on: June 20, 2014, 03:10:51 AM »

Looks like I will have to wait until a build is released which runs with XP then. 

I think the Mcode issue is quite deep rooted as it appears that just one Mcode in a short program is OK but put two Mcodes (almost any Mcodes) in the program and the smooth motion is destroyed for the duration of the program run between the two Mcodes. 

I presume that external motion controllers, such as the ESS, will not suffer from this issue ?

Tweakie.

3252

Mach4 General Discussion / Re: Mach4 Printer Port Discussions

« on: June 19, 2014, 12:00:45 PM »

Hi Art,

Yes I am using WinXP sp3 -  I can't run v.1817 either 

Tweakie.

3253

Mach4 General Discussion / Re: Mach4 Printer Port Discussions

« on: June 19, 2014, 10:21:59 AM »

Hi Art,

Thank you for the information and taking the time to look at the problem.

I have now found that it has nothing to do with the spindle and think I can confirm what you have said. The following runs with rough motion until the M9 is encountered then it runs just fine (so it looks like it's a Mach4 problem).

code
m7
code
m9
code

Tweakie.

3254

Mach4 General Discussion / Re: Mach4 Printer Port Discussions

« on: June 19, 2014, 07:29:40 AM »

Hi Art,

I am having troubles running a simple code such as:-

G1 F300
M3
X10
Y10
X0
Y0
M5
%

I had to delete the M3, M5 macros from the Mach4 macros folder on order to get these commands to operate the spindle but now the motion is lumpy (almost single step mode). If I leave out the M5 then it runs just fine (starting the spindle at the M3) but of course the spindle is not stopped at program end.
I have a similar problem if ending a program with M30 (for the last few lines it runs lumpy) and I put this down to my PC being antique but now I am not so sure.

Does using the M3 / M5 combination alter the output stream from Mach4 in some way?

Any advice greatly appreciated as this issue has me stumped at the present.

Tweakie.

3255

Mach4 General Discussion / Re: Laser Cutting.

« on: June 19, 2014, 04:36:12 AM »

Thanks Brett.

A few of the challenges I encountered with Mach4 v.1767 which may be of interest to others…
 
Initially my machine PC graphics card was not up to the task and had to be replaced with one that makes a better job of handling OpenGL. It’s a 10 year old PC and getting hold of a suitable AGP card was not that easy but where there is a will…

I work in metric so selected Metric Units in Mach4. As it turned out the Counts per Unit / Acceleration and Velocity for the X,Y & Z axes all had to be entered in Imperial units in motor tuning in order to get correct operation and axis movement distance. The A axis behaves differently and settings for this were entered in metric units.

Overall, setting up Mach4 is very easy to do but getting the M3 / M5 commands to talk to my VFD control was, to say the least, a real challenge. I got it working fine in about 5 minutes but did not record the settings, changed something else, it stopped working and then took me a few hours to get it working again (I have now written down my settings for future reference).

I forgot (read about it often enough on the forum but still forgot) to delete the M6 macro and the tool change ‘dance of honour’ tested my reactions – God bless E-Stop.

My old PC does not appear to have the computing power to handle the M30 command (stalling all motors during the GCode rewind operation) so M30 had to be deleted from my GCode programs to get them to run correctly towards the end. This needs further investigation on my part.

The Imperial / Metric bug, mentioned above, may have already been rectified in v.1817 but overall Mach4 v.1767 is just brilliant to use and it operated faultlessly during the couple of test runs I have been able to do so far.

Art’s ‘Darwin’, parallel port driver, performed beautifully during the tests with no faults or bugs to report. It is very easy to set-up and the motion produced is just so smooth it is difficult to describe the difference from Mach3.

As yet we do not have a dedicated control method for laser switching (the old M11P1/M10P1 commands have gone) but Art is working on it and I am sure he will think up something good once he starts using his Synrad. 

As soon as I get more ‘play time’ I will delve a bit deeper and see what I can and can’t do with the new toy. 

Tweakie.

3256

G-Code, CAD, and CAM discussions / Re: G-Code scaling program, mm to Inches and back

« on: June 18, 2014, 11:52:11 AM »

I am pleased that you got it sorted Greg. 

Tweakie.

3257

Mach4 General Discussion / Laser Cutting.

« on: June 18, 2014, 10:05:09 AM »

I have said it before but I just can’t say it enough – my congratulations go out to the Mach4 team and of course, Art for the excellent Darwin driver.

Just couldn't resist making a short video of Mach4 (build.1767) with Darwin laser cutting.  http://www.graytel.talktalk.net/Mach4.wmv

Tweakie.

Addition;

This is the video of the latest test engraving and cutting  http://www.graytel.talktalk.net/Darwin 2.wmv

3258

Mach4 General Discussion / Re: Mach4 Printer Port Discussions

« on: June 18, 2014, 02:18:57 AM »

Thanks Art.

Another issue which is probably just M4 v.1767 related and maybe not of interest here but I am just reporting as I find.

In Imperial mode everything is OK but in Metric mode G00 X1 Y1 Z1 moves X,Y,Z axis 1mm whereas G00 A1 moves the A axis 25.4mm (all DRO’s reflect the correct physical movement).

Tweakie.

3259

Mach4 General Discussion / Re: Mach4 Printer Port Discussions

« on: June 17, 2014, 01:58:26 PM »

Just thought I should mention this...

I don’t know if this is a Mach4 v.1767 issue or a Darwin issue but for those like me, that work in metric, the motors Counts per Unit : Velocity and Acceleration all have to be entered in Imperial units irrespective if metric is selected in general config. Not a problem once you know but it was puzzling initially.

Tweakie.

3260

G-Code, CAD, and CAM discussions / Re: G-Code scaling program, mm to Inches and back

« on: June 17, 2014, 12:22:26 PM »

Hi Greg,

Just one point of note - if your part origin (X0,Y0) is centre of the work then it's OK but if your part origin is bottom left then by changing the scale DRO to a negative value the origin will become bottom right (the GCode for the work has been flipped horizontally so has the starting point X0,Y0).
Not sure if this makes sense but you will see what I mean when you do it.

Tweakie.