Danfoss MCO 305 Design Manual

Also see for MCO 305: Operating instructions Operating instructions Design guide

MCO 305 Design Guide__ PC Software Interface __MG.33.L5.02 – VLT® is a registered Danfoss trademark 61 File MenuThe File menu contains all the commands necessaryto create, open, save and print programs. File →Close, Save, Save as, Print, and Print setup areused in the usual way.In depend on the operating mode – MCT online,MCT offline or APOSS stand-alone – differentfunctions are enabled:MCT online MCT offline APOSS stand-aloneFile → NewNew files must be created via MCT10 or in APOSS stand-alone with File → New.An APOSS Window is opened with the name “Untitled” and you can begin to write your program.File → OpenSelect the file via the MCT10. APOSS and with that the file is opened automatically. In APOSS stand-aloneuse File → Open.File → Save asPlease use the features of the MCT 10 to rename a program file (*.m) or to copy it. Or use → Save as inAPOSS stand-alone.APOSS program files always have the extension “.m”.Write to driveClicking on → Write to drive will compile the current file being edited, make a connection to the drive anddownload the compiled file to temporary memory on the controller.If the download was successful, then the program is saved in permanent memory. If MCT 10 requests it,then the source code is also downloaded to the drive. SampleAPOSS contains several sample programs. Any of these sample programs may be freely used, modified, orincorporated into other programs by the user. File → Sample can be used to edit any of these sampleprograms. Please see Program Samples for a list of the available sample programs. Exit ProgramThe APOSS application can be ended by clicking on Exit Program or on the ⌧ icon in the far upper rightcorner of the window. If you have not yet saved a new file, or saved changes to an old file, then you willhave the chance to do this.NB!:Exit Program does not end a program running in the controller. You can only abort or end aprogram with [Esc] or with Development → Break. In order to do this the file which is linked withthe controller must be open or re-opened.NB!:Disconnecting from very early versions of controllers (for example, as a result of File → ExitProgram), may cause the controller to stop executing if the controller is using PRINT commands tosend messages to the PC. This happens once the controller's internal print buffer becomes full.This is not a problem for all newer controllers. Newer controllers will continue to execute even after theprint buffer becomes full; print messages will simple be discarded once the buffer is full.