One thing that would be really nice is if motion would list time to next bit change.
The problem is that it would always be wrong, and everyone would complain about that too. The time to run a job is based on estimates of time for executing commands, and the number of commands left, not how long it actually takes to do each of those commands (because acceleration and decel are different, etc, etc, etc) So, you can probably get an estimate, but it’ll be wrong…which might be ok (it’s better than nothing), but then they’ll have to deal with all the people complaining that in this case or that the estimate is wrong by and order of magnitude.
This topic was automatically closed after 30 days. New replies are no longer allowed.