Development Menu - Danfoss MCO 305 Design Manual

MCO 305 Design Guide

Development Menu

This menu provides various functions used during
the program development phase of applications.
This includes functions to compile, execute, break,
and debug programs. It also includes functions that
allow controllers to be connected and disconnected.
Many of these functions require a controller or the
FC 300 to be connected before the function can be
executed. A controller can be connected either by
pressing [Esc] to connect to the default controller or
by using Development → Select Controller to con-
nect to a specific controller if more than one control-
ler is present. If no controller has yet been connec-
ted when a function is executed, then most of these
functions will automatically connect to the default
controller.
In offline mode, all functions which require access to
the drive can not be used. Most of the Development
menu items are disabled. APOSS will use the drive
connection that MCT 10 has already established.
For information on debugging programs, please see Debugging Programs at the end of this chapter.
Execute [F5]
This will execute the program currently being edited. This involves the following steps:
1. If a controller is not currently open and connected to the APOSS Window, then an attempt is made to
connect to the currently defined default controller. If no controller is connected, then the Execute is
aborted.
2. A check is made to see if the controller is already executing a program. If so, then the user is asked if
the existing program can be stopped. The controller can only execute one program at a time. If the
controller is not "idle", then the Execute is aborted.
3. If the user has made changes to the program being edited, then the changes are automatically saved to
the PC disk. If this is a "new" program, then the user is requested to enter a filename for the program.
Note that it is not necessary to enter a filename at this time. If no filename is given, then a temporary
file is used.
4. The program being edited is then "compiled". This produces a "machine code" version of the program
that is customized for that particular controller. Note that this "machine code" is not human-readable
and cannot be edited. If the compile fails for any reason, then the Execute is aborted.
5. The "machine code" (i.e. not the original text file being edited) is then downloaded to the controller and
placed in the controller's temporary memory. Note that this temporary memory will be lost if the
controller is powered off. To save a program permanently in the controller, use Controller → Programs.
6. After the download completes, the controller will start to execute the program.
Each subsequent time that Execute is used, the previously downloaded program will be overwritten with the
newly downloaded program. This allows you to quickly and easily make changes and re-test during
debugging.
Run Programs in Several Controllers
You can execute different programs on different controllers all at the same time simply by opening each
program in a different APOSS Window. Then use Development → Select Controller in each window to select
the desired controller for that program. Finally, use Development → Execute in each window to download
and start the programs.
Note that you must use Select to open the controllers before using Execute since Execute will always
connect to the default controller if no controller is yet connected.
64
__ PC Software Interface __
®
MG.33.L5.02 – VLT is a registered Danfoss trademark