Sven Wesley pravi: > 2010/4/23 yann <[email protected]> > > >> Le lundi 19 avril 2010 16:21:18, Slavko Kocjancic a écrit : >> >>> Like instead 2 hour's machining showed in >>> Property dialog the actual time is over 3 hrs. I know that my file has a >>> lot of short segments and machine need to accelerate/decelerate but all >>> >> You pointed it out. This is the problem. >> >> >>> that parameters are known to emc so I think it can calculate near >>> perfect time (..until speed override) >>> >> Seems to be not as simple as it looks like. >> There was a big discussion on this a few weeks or months ago. Have a look >> in >> the list's archives. >> >> >> > My "simple" suggestion from that discussion was to count executed steps > compared to the total number of steps. But someone's got to do it though... > >
Hmm probably nobody. Why? That solution can report percentage of execution. and works only in stepper sistem. The solution should be steper and servo friendly. If we want that "precision" then assuming coherent file we can just calculate percentage from CurrentLine/TotalLinesInFile*100 % And from that and already elapsed time we can get ETA time pretty good. Ie if we are in 10% and for that needed 10 minutes we know that 90 minutes is time to go. But the files are no coherent so the output will wary. The question is just how much? If half of file is roughting and other half is finishing then at 50% the report can be pretty wrong (the feedrates are not calculated) The better way can be to calculate "normalised" lenght of path (to acount feedrate) and calculate percentage of that. A lot of different way to solution. But have no knowledge to programming to do that. Slavko. ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
