If you get the error ' Cannot start a new OEE run because the operation previously started has not been indexed to the next cell', this article explains how to fix this.
This situation can arise if cells or cell groups were added or modified to the line in the production model while an OEE run was active. It is strongly recommended to end any runs before making changes to the production model, but if you find yourself in this situation, the following steps can be taken to correct the entries in the database to fix this error.
For most cases, the scripts below are sufficient in solving the issue.
Fix with Scripting
Run this script first. It will print the Operation UUID, Product Code, Work Order, and Mode for the line and all the cells, and then return an Ignition Dataset with the same info.
This will bruteforce fix the issue, aborting all runs, and updating the Operation UUID, Product Code, Work Order, and Mode to reflect a run that has ended right when you run this script. Please note that this script assumes that your "Idle" mode is 3.
Check and Abort any Active Runs
- Check if there are any active operations on the line and abort them if necessary. You can do this in the script console by typing ...
Add Necessary Entries to New Production Items
There are entries in the database table for the existing cells/cell groups that need to copied over to the new cells/cell groups that were added.
Repeat the above steps for all new cells and cellgroups and for the Equipment Operation UUID, Equipment Product Code and Equipment Work Order Tag Collector Type fields.
Alternatively, you can download the following project files to be imported in the Designer
(new !! Perspective version available now !!)
How to use DnF ?
There is no content with the specified labels