This information may be of help to other Epilog Mini users.
Last week I discovered a small bug in the firmware for my Epilog Mini 18. I confirmed the bug with my dealer who has a model 24 and have also notified Epilog. As of this morning, Epilog is investigating the issue. I have also verified the problem on my own Mini 18 with firmware versions from 1.0.0.4 to the current 1.0.1.2 all with the same results.
The issue occurs when multiple jobs are sent to the laser with different frequencies. Jobs will only run at the frequency which was last sent to the laser. If you use the control panel on the laser to switch to a previous job, that job will run at the frequency which was most recently sent to the laser (i.e. highest job number) instead of the frequency which was specified when that job was originally submitted.
This example might explain more clearly:
1. Job #1 is sent to the laser with settings Power=30, Speed=100, Frequency=10
2. Job #1 is run. It runs properly at the settings specified.
3. Job #2 is sent to the laser with settings Power=20, Speed=50, Frequency=1500
4. Job #2 is run. It runs properly at the settings specified for it.
5. On the laser’s front control panel, you use the up/down arrow keys to change back to Job #1 to re-run that job.
6. Job #1 now runs incorrectly. It runs with Power=30, Speed=100, Frequency=1500. Notice the power and speed settings are correct as specified when Job #1 was submitted, however the frequency is running at Job #2’s frequency.
This issue will naturally only affect people who send multiple jobs to the laser with different frequencies and also later switch between those queued jobs to re-run them.
The problem is most clearly demonstrated when running very low frequency jobs (e.g. perforating paper) since it’s easy to distinguish with your eyes the difference between frequency=10 and frequency=1500. Frequency=10 will produce wide perforated dashes, while 1500 would cut a sheet of paper.
Hopefully this information can be helpful for a few other Mini owners until a fix is released. Again, Epilog was only made aware of this issue as of this morning. I’ll post again if I hear more or if I find this is somehow isolated.