Report on Job stats
Posted: Fri Sep 13, 2019 1:39 pm
(Hopefully I didn't miss this in the docs, if it already exists)
It would be useful to get an optional report of the job stats, at the end of each Job, as follows:
- output to file only, to avoid cluttering the GUI
- Number of parts placed
- list of parts placed (footprint, tape ID etc without any potentially confidential details)
- # nozzle changes, with nozzle #
- Total duration of Job HH:MM:SS.mmm
- CPH number
- Option to enable/disable this reporting feature via a popup context menu(right click) on the Job tab.
- Opt in option to automatically upload stats to LP, might prove useful for future roadmaps?
- Bonus option would be timestamps at when each part is placed - allows better analysis of making a change impacting only one component.
Reason for this is that I saw in the docs that CPH in the range of 500-800 cph can be achieved (expected?). However, in my tests I am seeing around 250 cph on average - using place fast on tapes..with 1 nozzle change & duration of about 15 mins. So If I make a change, it would be nice to be able to quickly see if there was a performance boost. Might also be useful in comparing different software releases...such that a release with performance improvements can be published with a number for a particular reference job or jobs along with the PC spec.
I understand that we are not looking to have a 'Pro' machine and that the tape position, motor config, vision etc etc all impact placement pick & place job run-times.
Finally, the times I am currently achieving for test jobs is acceptable to me, even if slower than expected....but always a nice bonus if I could get between 500-800 cph or more.
PS: I am running on a 10 year old laptop which may slow the vision a bit. However, I did notice that when I upped the run-time priority of the LitePlacer application I got about a 10% job time boost (Obviously, if I had this feature I could have an exact measurement!). That is something that could be built into the application as an option to apply at run-time (needs admin privileges). Alternatively, can be done manually thru the Task Manger.
It would be useful to get an optional report of the job stats, at the end of each Job, as follows:
- output to file only, to avoid cluttering the GUI
- Number of parts placed
- list of parts placed (footprint, tape ID etc without any potentially confidential details)
- # nozzle changes, with nozzle #
- Total duration of Job HH:MM:SS.mmm
- CPH number
- Option to enable/disable this reporting feature via a popup context menu(right click) on the Job tab.
- Opt in option to automatically upload stats to LP, might prove useful for future roadmaps?
- Bonus option would be timestamps at when each part is placed - allows better analysis of making a change impacting only one component.
Reason for this is that I saw in the docs that CPH in the range of 500-800 cph can be achieved (expected?). However, in my tests I am seeing around 250 cph on average - using place fast on tapes..with 1 nozzle change & duration of about 15 mins. So If I make a change, it would be nice to be able to quickly see if there was a performance boost. Might also be useful in comparing different software releases...such that a release with performance improvements can be published with a number for a particular reference job or jobs along with the PC spec.
I understand that we are not looking to have a 'Pro' machine and that the tape position, motor config, vision etc etc all impact placement pick & place job run-times.
Finally, the times I am currently achieving for test jobs is acceptable to me, even if slower than expected....but always a nice bonus if I could get between 500-800 cph or more.
PS: I am running on a 10 year old laptop which may slow the vision a bit. However, I did notice that when I upped the run-time priority of the LitePlacer application I got about a 10% job time boost (Obviously, if I had this feature I could have an exact measurement!). That is something that could be built into the application as an option to apply at run-time (needs admin privileges). Alternatively, can be done manually thru the Task Manger.