Hello Guest it is September 27, 2023, 09:53:18 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 - Mauri

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 »
Mach4 General Discussion / Re: High GPU usage workaround
« on: January 19, 2017, 02:25:07 PM »
This only applies when you are not running the G-Code.
So if you load the file and view the toolpath display what you say is correct, but when you "Enable" and then "Cycle Start" it will go back to high GPU usage.
So what we need is another option on Toolpath display to only redo display when Toolpath is moved.
I tried 2.5D 3 Axis and 3D 4 Axis with the same result.

Mach4 General Discussion / Re: High GPU usage workaround
« on: January 15, 2017, 05:35:48 PM »
The file is too large for this site.
I have sent these files to Mach4 Programmers last year and they are aware of the issue, however they have not provided a solution.

You can contact me via email as long as you email provider allows files of over 16MB.

For those who do not understand this high graphics usage issue.
If you have medium to large files for 2.5D and 3D G-Codes the problem is not running/processing the Mach4 G-code, it is purely just displaying the pictorial representation of the G-Code in the Toolpath Display.
The reason for this must be that it is in a continual redraw loop on any Toolpath screen.
Most other OpenGL programs do not do this, only when you move the object do they redraw.
It does not matter if they are 32bit or 64bit programs.
For example Rhino5 is a 32bit (one Processor) and using OpenGL, however it can quite easily move a 1.5GB triangulated shaded files without heavy usage of GPU and it only redraws when you move it.
I am not aware of any program that continually redraws a stationary object on the screen.
The best way to do this is when you move/rotate the Toolpath then and only then should it be redrawn.
Another way would be is to be able to turn the looping redraw off.


Mach4 General Discussion / Re: High GPU usage workaround
« on: January 15, 2017, 02:37:26 PM »
Thanks for you info, however I tested many NVIDIA, AMD and INTEL and on my medium 4 Axis files size files ALL went to 100% as well as on large 2.5D files.
Yes NVIDIA on my smaller files will use more GPU than the other two.
You can have the fastest PC and Video card in the world and it will still go to 100% usage.

Mach4 General Discussion / Re: 4 Axis
« on: January 14, 2017, 10:38:25 PM »
This is the Offset G-code by 50% of the diameter.
The offset for axis was done on Rhino5/madCAM5 and NOT in Mach4, just the G-Code was used as it was produced in madCAM.
It shows an odd shape of the ball.

Mach4 General Discussion / 4 Axis
« on: January 14, 2017, 10:30:05 PM »
Below are what you see in Mach3 and madCAM Simulation, but not on Mach4 it appear in this example that only the XYZ have generated the image and not the A axis.
When doing just a circle it is also just a flat line.
If you offset the circle and then make the G-code on the Circle it will then make a circle, however if you do the to a full 3D like this Ball example it generates the G-Code incorrectly.
I will post the extra sample in the next post.

Mach4 General Discussion / High GPU usage workaround
« on: January 14, 2017, 06:35:50 PM »
For those using large Engraving/Carving files on 2.5D and medium files on 3D 4/5 Axis that are experiencing High Power, GPU% and Temperatures (no matter what type of Graphics or how powerful the PC is), you can stop this and have it use negligible usage by not displaying the Toolpath on the Screen.

On the industrial Screen set it is easy just keep it on the Program panel button (not Toolpath Panel button).

But on the Hobby Screen set you have to go to the "Probing" or "Offsets" tabs on the screen.

Alternately you can Turn Off the Toolpath display in the Edit Screen, click the toolpath panel.

Or another way would be to have an on screen button to turn off the Toolpath display feature.

If you toggle to back to the Toolpath screen just to look at the G-Code progress, it will then go back to high GPU usage just while you look, then just toggle back and it will revert back to low usage.

Hope this helps.


I have been advised that HiCON Integra Plugin can provide faster updates.

From Marc of VitalSystem a very helpfull Company with great CNC products.

Hz, or Hertz, is a unit for frequency (cycles/second).

To get the Poll interval:

PollInterval = 1000 / UpdateFrequency

This means, with an update frequency of 200Hz, you will effectively have 5ms update intervals.

I would really only recommend going up to 200Hz which is probably more than enough responsiveness as far as PC-based motion control goes. There are times when even more responsiveness is required, which is why we have the HiCON and DSPMC macros.

So since I had 100Hz that would have been equal to 10ms.
I will give the 200Hz a go and see what happens.


Thank you for the information, I had a feeling that this was happening.
On my Controller Plugin the Polling Frequency is 10Hz to 250Hz and I have the setting at 100Hz as recommended with the Controller information.
Previous versions of the Polling Frequency had 2Hz to 250Hz.
It talked about Significant Network Traffic and CPU load, however if my PC is fast and directly connected it should not be an issue.
I will enquire with the manufacturer of the card more about this setting.
At least now I can calculate a cut time that was close to Mach3 with its CV setting (CV Distance Tol = 0.01 and Stop CV on angles >49), which equates to about 75 on all CV 180 angles with Mach4 and this reports a reasonable good Toolpath finish using 30Degree 0.05mm Radius cutter on a 2.5D surface.
Thanks Steve,

I am having major differences between CV with Mach4 simulator and CV with Mach4 and Controller on the Toolpath Display and Timings to completion.
I have tried CV = 0/10/25/50/100 with the Mach4 and Controller running and have viewed each time the Toolpath Display and reported the time taken.
I have compared these against CV with Mach4 Simulation Mode on the Toolpath Display and recorded time taken to complete.
I have found that all CV’s are faster to completion with Mach4 and Controller, but are visually worse even comparing CV=0 with Controller and CV=100 with Mach4 Simulation mode on the Toolpath Display.

Could it be that the data is flowing faster to the Controller than the Toolpath Display and hence loosing data for display on the angles?
If not can anyone explain why?

I have many examples if some one needs them to explain.


Mach4 General Discussion / Re: CV G64 and Exact Stop G61
« on: January 03, 2017, 05:39:56 AM »
The jpg's CV50Accel1 above was with Z being different Acceleration to X/Y and was CV100 mislabeled , the other that looks good was CV50 the same Acceleration.
The letting example is 2mm high, it was very good with CV and Mach3, and in Simulation looks good with CV100 on all 180 angles.
As CV100 is in my examples 25% less time and that it simulates quite well it should be good for ant Lettering, 2.5D and 3D machining.

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 »