Simulation timer

[Tarasevih]

Hi Tom.
Is it possible to add a simulation timer?
This is a very useful function if you need to know the exact execution time.

Regards,
Taras.

[TomKerekes]

Hi Taras,

I assume you mean machine time if ran. I suppose something could be added. It wouldn't always be accurate based on Spindle operations, tool changes, and so forth.

An approximation based on feed lengths and feed rates that ignore velocity/acceleration limits would be easier and faster than full trajectory planning the whole job. In some cases it would be quite accurate and sometimes not.

[Tarasevih]

Hi Tom.
Is it possible to do like Weihong?
[youtube]https://www.youtube.com/shorts/UgTfcLdFBNA[/youtube]
Regards,
Taras.

[Tarasevih]

Hi Tom.
How quickly can changes be made?
I need to know which control system to use for my machine.
My machine is ready and it remains only to find the controller.
I need 4 axes and the NCstudio available to me only supports 3 axes.
How much can it cost?
Regards,
Taras.

[TomKerekes]

Hi Taras,

We are looking into it. It will likely take some. A significant issue is changing the main GUI screen has to be compatible with legacy screen scripts and such. No promises.

If added it will be included in KMotionCNC for free.

[Tarasevih]

Tom you have the best feedback I know.
С уважением,
Тарас.

[Tarasevih]

If I can help you in any way, I'm ready.
I really want to make your product as convenient as possible, this should attract a lot of interest.
Regards,
Taras.

[Tarasevih]

Hi Tom.
Can I do something similar from a C user program?
Ie by clicking on the user button to read the g-code and knowing the acceleration of the machine to calculate the execution time.
After calculation, display this time as a message.
If it's possible can you help me Tom ?
Regards,
Taras.

[Tarasevih]

I'll probably start.
Am I reading g-code correctly;

Code: Select all

 #include "KMotionDef.h"
 #define TMP 10 
 #include "KflopToKMotionCNCFunctions.c"
 #define NVARS 6

main()
{
        // Download Variables from GCode #1 to persists 
	GetVars(1,NVARS,TMP); 
}

Regards,
Taras.

[Tarasevih]

I discarded the option to calculate processing time by g-code.
You were right that an approximation based on feed lengths and feed rates with increased speed and acceleration would be much easier.

The logic of work should be like this;
1 We create a Timer that will be tied to the FRO value and will be launched when the g-code is executed
2 By pressing the simulation button, we start the program for execution by turning off the generation of step and direction signals.
3 Increase the FRO, as well as the speed and acceleration in the trajectory planner by 200%, while the timer will also count 200% faster.
4 At the end of the g-code, stop the timer and return the speeds and accelerations to those that were at the beginning.
As a result, we have the execution time of the g-code.