I have attached the gcode file for this job. It is a simple pocketing and profile cutting toolpath.
I have also attached two screencaps. The first - timevslines - is a point in time when I paused the job to take the screencap. It shows that the job had run for 1h02m, it was 84% complete, but still had 1h02m23secs/4083 lines left to run. It was then that I believed something was wrong in that I didnāt see how the job could be 84% done and still have the same amount of time left to run as it had run until then.
The second screencap - timevslines_2 - shows that the job finished 8 minutes later. Total time was 1h10m. There are 0 lines left to run, but the time remaining still shows 1h02m23sec.
I realize that this is not a new issue. I have reported it before. But, this is the first time that I have seen it using gSender 1.4.6.
I know the team has made some changes to time estimation and Iāve provided a couple files for the Vortex runs too. We may see another release come out next week sometime.
The gSender team got to wire up and run a 4th axis job on the Vortex on Friday, it was amazing to see the Y axis move while running.
Iāve been reading up on 4 axis projects, but have not seen any that did not turn on āhand-madeā gcode. How did your team create the gcode for the project? Do you see Sienci offering a plug and play 4th axis package any time soon?
We hand-rolled it from a file exported for A/B axes (I think from Snapmaker Luban) converting them to the actual axes because their rotary is not on Y. Unfortunately the CAM side just isnāt there yet for the hobbyist.
Iām not really allowed to definitively say what weāre developing but the answer for 4-axis package is āprobably eventuallyā once the SLB/Altmill development dust has settled - itās definitely been talked about. Itās relatively low barrier to entry and honesty having a consistent motor driver with a known labelling will go a long way for both support and the customer experience.
@KGN Tks, Kevin. This topic has gotten a bit off track. Iāll take some blame for that and put some on @StephenCampbell for mentioning the Vortex projects that you have been playing with.
The run time/time remaining issue is not related to rotary.
On-topic, we will have a couple tweaks in the next release looking at addressing the outstanding issues with time remaining for both rotary and regular jobs.
I have some more info on the job progress with gSender 1.4.7 on Windows 10.
It seems to really mess up when it recalculates due to a feed override. Here you see I have negative progress and at this rate my job will never finish.
@_Michael, weāve made several improvements to the job progress area since then. Are you still experiencing any weirdness with the latest version of gSender, 1.4.10?
I didnāt have an actual job to run to test the accuracy of the estimate versus actual run time. I did create a job with the surfacing tool and played around with it running in the main visualizer.
All of the weirdness with the overrides is gone. My job was estimated at ~22 minutes. Override at 200% estimate drops to ~11 minutes, override at 50% and estimate increases to ~44 minutes. Those overrides and more were done in the same run and everything looks good.
