Hello Guest it is September 29, 2022, 02:29:40 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 - Steve Stallings

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 »
Mach4 General Discussion / Re: Editing loaded GCode???
« on: September 28, 2022, 09:08:19 AM »
On the standard screen sets look in the lower right corner for the Ops panel. Select the File Ops tab and select the Edit G-code button in the left column.

Mach4 General Discussion / Re: Question on upgrade
« on: September 17, 2022, 03:54:59 PM »
Version 2 has been out for several years and you almost certainly are running it already.

If you go to >Help >About you will get a screen that shows Version 4.2.0. x x x x where
the 4 means means the product is Mach4, the 2 means version 2 in the Mach4 series,
0 is the sub-version, and x x x x is the build number of the software that you are running.

If you are not having any problems, there is no need to update your software.

There are production releases that are available on the Download page for Mach4, and
also beta versions on a separate FTP server.

There are normally no update charges for Mach software within a product series,
i.e. product 4 for Mach4.

Note: Mach4GUIR.exe is part of the standard Mach4 install and will be found in the regular Mach4Hobby folder.

Mach4 General Discussion / Re: Mech4 Velocity Calibration
« on: August 29, 2022, 06:40:59 PM »
The Velocity and Acceleration parameters on your Motors page are for adjusting the maximum velocity and acceleration that Mach4 will attempt to utilize while running your motors. Changing these would affect your feed rate only if the maximum allowed here was less than the feed rate requested by your G code. Feedrate also changes dynamically to keep the acceleration within the requested maximum.

Feed rate itself does not need calibration as it is computed automatically using the other parameters provided to Mach4. If you have the steps per unit calibrated correctly, Mach4 will produce accurate feed rates. Before evaluating feed rates, make sure the steps per unit are correct.

There are three other things that can affect the actual feed rate that occurs.

1) G0 commands are "rapid" move commands and ignore the F word in G code for setting feed rate. G1 commands should be used when needing controlled feed rate.

2) The user GUI has a provision for feed rate override. This is in the lower left area of the screens supplied with Mach4 and is labeled "FRO%". If the value is other than 100% the actual feed rate will be affected accordingly.

3) Feed rate control in G code is understood to be the vector sum of the feed rate of the individual axes and can cause the speed of individual axes to be reduced when the vector sum would exceed the requested rate.

Also be sure that your CAM software is inserting meaningful F words in the G code that it produces.

Mach4 General Discussion / Re: what is wrong with this g code
« on: August 17, 2022, 08:56:06 AM »
He already did. See the link to a zip file in the first message.

Mach4 General Discussion / Re: what is wrong with this g code
« on: August 16, 2022, 02:46:09 PM »
I have not figured out what is wrong, but I did get different preview results from you.

For me the Mach4 preview looks to match the Vectric one.

I happen to be running build 4818.

My only issue with the ESS is that their plugin configuration takes over many functions that are normally done in the standard Mach configuration screens. This is, for me, confusing. Overall the ESS is an excellent product and I do not think it is the cause of your problems.

Yes, the on screen jog buttons can be modified, but it is far more common to find that users change the keyboard ones without understanding the system. I was trying to find a way to avoid Gcode issues and prove that Mach4 was working correctly. Comparing DRO readouts to observed machine motion was the critical part.

I guess it is possible that the old setup had the Y axis misconfigured and original poster did not realize that he had worked around it by changing the Gcode. The replacement PMDX-411 is on the way to him and maybe he can reload his old configuration to check that. The testing with using the on screen jog buttons to verify that the DROs and machine moved in the correct direction convinced me that Mach4 was driving the machine correctly in this case. Sometimes people get confused when one axis moves the cutter and the other axis moves the table. I wonder if that could be the source of the problem.

This case is more than just configuring the motor direction correctly.

The DROs and machine run correctly if you use the on screen jog keys.

When Gcode is run, one axis moves backwards. The Gcode itself has been supposedly been validated on his older setup with a PMDX-411. We have been trying to figure out if a G51 parameter is stuck somewhere. Adding a G51 Y-1.0 to the Initialization string in Mach4 makes things work correctly.

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 »