At the risk of the blind leading the blind, to my knowledge the time estimate is generated by parsing the gcode (job) file, determining how far and at what speed each move is performed and adding all these times up. Acceleration and rapid movement speed are parameters that are not specified in gcode so a time estimate applies a âfudge factorâ to account for that and the scale factor is a secondary fudge factor to try and improve the accuracy of the time estimate with the particular equipment being used.
The time a job takes is an ESTIMATE to give you a rough idea - it is not meant to be an accurate value.
More info. Changed Vectric scaling factor to 1.45 and estimate for cut was 3:20. Downloaded gcode and loaded file. gSender estimate is 2:20, ie., same as Vectric at Scaling factor of 1.0 . Coincidence?
Seems gS does not get time estimate from Vectric, so, how does it calculate the time? Like Jens indicates? Still the large disconnect between gS cut time on the visualiser and REAL time.
Just stumbled on this. Am surprised after various threads. I posted âreal timeâ vs âdisplayed timeâ, as well as well as yellow display. All related issues - the visualizer is far from accurate and can be on either side re time and cut. Surely Sienci can do better. I live in hope
@Retiree for gSender-specific questions and feedback this Category is used - I noticed your previous ones are in the âCommunity Supportâ category so have not gone as noticed. Regarding your prior posts I understand what your two issues are:
Discrepancy in stated line number versus resumed line number using âStart from lineâ
Discrepancy in estimated cutting time while cutting
Your first issue is currently resolved in the new Edge releases and will soon be available in the new 1.6.0 gSender release. It was a matter of incorrect line counting based on the incoming file versus the âcleaned upâ file weâd send to the machine. Your second issue is exactly what Grant has reported in this thread and is the reason for my resurrecting it, since weâve made some further changes and are now looking for feedback. If youâd like to try to download the new Edge version and report back then thatâd be appreciated
Regarding behaviour of the yellow line and the broader conversation of how we spend our time, understand that we get unique queries for specific tweaks, new features, and opinions on changes about 10 times per week, and we usually canât implement them at the rate they come in. Because of this, itâs important we prioritize the most mentioned items first (alongside some other aspects that go into decision-making) so I hope that gives more context when it seems like the items youâre mentioning arenât immediately being addressed.
EDIT: Iâve linked your other posts to this thread for easier finding in the future, though Iâve since moved one to the gSender Category
