The download page has no settings, and instead allows the final check before the jobs are sent to the cell controller and become active. When you click the "Download to machines" button, OrderLink connects to FMS Insight and sends the jobs. One of several things can happen:
OrderLink can't communicate with FMS Insight. (For example, there is a firewall or network problem or FMS Insight is not running.) In this case, OrderLink will display an error message and allow you to re-attempt the download.
OrderLink communicates with FMS Insight, but FMS Insight rejects the jobs as invalid. As an example, OrderLink might specify a job uses program
12345but FMS Insight sees that the program
12345does not exist in the cell controller. Or a job might specify a pallet or combination of pallets that is not allowed by the cell controller. In this case, FMS Insight rejects the entire schedule and nothing is added to the cell controller. OrderLink will display an error message describing the problem. You must fix the problem before attempting to download again (for example, if the program
12345is missing it must be added to the cell controller).
OrderLink communicates with FMS Insight and FMS Insight accepts and stores it as a valid schedule. In this case, OrderLink displays a success message and you can exit OrderLink.
Note that for some cell controllers, it might take up to 10 minutes for the jobs to appear in the cell controller (due to the communication technique). Once OrderLink receives and displays a success message from FMS Insight, the jobs are safely stored inside FMS Insight. FMS Insight takes care of feeding the jobs into the cell controller over the next few minutes, and FMS Insight will retry if any error in communication occurs (and also add messages in the FMS Insight error log). If OrderLink shows a success message but the jobs are not appearing in the cell controller, check the FMS Insight error log for errors in the communication between FMS Insight and the cell controller. Note that the jobs are safely stored in FMS Insight so as soon as the communication resumes the jobs will be sent.
OrderLink successfully sends the jobs to FMS Insight but errors when reporting the scheduled bookings to the ERP system. (For example, the ERP server is down for maintenance or is offline.) In this case, you can still exit OrderLink since the jobs will be copied into the cell controller and become active. The next time OrderLink runs, OrderLink will notice that the scheduled bookings from the previous schedule were not reported properly to the ERP and re-attempt to report the scheduled bookings to the ERP. In this way, OrderLink will not attempt to machine a booking more than once.