Programming

M-PLC
Programming Interface

PLC programming interface according to

IEC 61131-3

M-PLC is a complete development environment for

programming the M1 controller in accordance with
IEC 61131-3. The M-PLC puts a simple approach to
the powerful IEC language at the disposal of the PLC
programmer. Use of the edit and debugging functions
is based on the proven development program
environments of advanced programming languages.

• Easy entry into IEC 61131-3

• All languages defined in IEC standard 61131-3
are supported (instruction list, structured text,
ladder diagram, function block diagram, continuous
function chart, sequential function chart).
• Editor and debugging functions
• Provided libraries with pre-finished and tested
functions

Programming
• Editors for programming in all IEC 61131-3
languages
IL Instruction List
ST Structured Text
LD Ladder Diagram
FBD Function Block Diagram
SFC Sequential Function Chart
CFC Continuous Function Chart
• Syntax highlighting for key words defined in
IEC 61131-3
• Graphic project navigation bar (based on Windows
Explorer)
• Support of all elementary IEC 61131-3 data types
to 64 bit
• Support of fields, structures and pointers
• Graphic controller and task configuration
• CAN objects from *.dcf files in M-PLC can be applied
as symbols
• PB objects from *.2bf files in M-PLC can be applied
as symbols
• Library management for creation and management
of libraries
• Watch manager and recipe manager (freely
definable variable monitoring)
• M-PLC can be started several times (multiple
Controller Controller projects open and online in parallel)
• Automatic project backup and creation of backup
IEC61131 IEC61131
SMI • Project archiving on the controller
• Password protection for projects
VxWorks

VxWorks
Tasks

Tasks
Tasks

Tasks
Tasks
Tasks

• Offline simulation
• Online help
VxWorks VxWorks
• Data exchange system-wide via SVI/SMI interface
394 programming

System Overview • Bachmann electronic GmbH • 05/2018 • Specification subject to change –

the product’s characteristics are exclusively governed by the data of the respective user manual.
 Programming

Runtime system Online functions

• Any number of running M-PLC projects on one
processor
• Every PLC project supports up to 16 separate
tasks
• Each task can be configured independently of
the others in terms of (priority, task call-up
mode [event, timetrigger, free running, sync],
watchdog)
• Actual multitasking via operating system tasks
(VxWorks)
• Communication between software modules (pre-
compiled units)
• Online change (exchange of blocks in running
operation) also for multitasking projects
• Monitoring of all project variables
• Writing and forcing of variables
• Single cycle, single step and break points
• Sequence control (program lines that have
been run through will be displayed)
• Recording and graphic presentation of
project variables – trace

SW module 1 SW module 2 SW module 3

C/C++ GD data
Simulink IEC61131 IEC61131

Global variables Global variables

VxWorks

VxWorks

VxWorks
Tasks

Tasks

Tasks
Tasks

Tasks

Tasks
Tasks

Tasks
Tasks

SMI/SVI

VxWorks

• Between different tasks of an IEC 61131

module: global variables or SMI/SVI
• Between IEC 61131 modules: GD flag range or
SMI/SVI
• Between IEC 61131 modules and other modules
(C/C++, Simulink): SMI/SVI
• Between any modules on different controllers:
SMI
• Interface to visualization/SCADA/BDE
• Standard protocols: OPC DA, IEC 61850
IEC 61400, Modbus etc.
• Libraries for integration into separate software
(for C/C++, C#.NET, Java)
• Support of battery-buffered data (RETAIN flag)

395

System Overview • Bachmann electronic GmbH • 05/2018 • Specification subject to change –

the product’s characteristics are exclusively governed by the data of the respective user manual.
 Programming

Manufacturer libraries • Display of the status "in error handling" (ERROR)

STANDARD IEC 61131-3 Standard functions in the interface
PLC 7 standard PID controllers • Implementation of the I/O modules of the process
MIO_PLC Functions for direct access image in the runtime system
to hardware I/Os • Optimized for performance, flexibility and
SMI_PLC Functions for fast combinability, shared use of an I/O module by
communication between modules multiple projects/SW modules possible
and controllers (SMI/SVI) • Saving/loading of the entire project including
EHD_PLC Functions for inputting and sources to/from the controller
managing errors in the EHD • Transparency of the global variables (flags,
UTIL_PLC Functions for access to RTC, symbolic variables, structures) controller- and
runtime system info, special visualization-wide
conversions 
FILE_PLC Functions for access to files,
directories and serial Integration in the SolutionCenter
interfaces (projects are SW modules)
CIA405 Functions for access to CAN Generation of an executable *.m file with
DN_PLC Functions for access to configuration information
device net • Task interval time measurement, can be queried in
PB_PLC Functions for access to Profibus the project itself and in Device Manager
USS_PLC Functions for communication • Watchdog integration
with "Micromaster" frequency • Execution possible in an application layer (memory
converters protection)
• Install, start, stop, reset and delete of PLC
projects in Device Manager
Extensions relative to CoDeSys • The state machine of a PLC project in the runtime
• Grouping possibility for I/O modules in the system always corresponds to the model defined
process image (controller configuration) runtime- for SW modules.
optimized process image (only channels being • Integration via M1 system debug mode and M1
used are processed) system logbook
• CAN objects with symbolic names in the process • Start of a project when booting through entry in
image MConfig.ini
• Addressing for inputs/outputs: undelayed access
that bypasses the process image
• Adjustment of the interval time and watchdog
time in the controller configuration
• Multiple, concurrently running PLC projects
on one CPU with different priorities / interval times
• Actual operating system tasks within the PLC
projects
• GD flag range for shared data from multiple
projects on one CPU
• RD flag range for remnant (battery-buffered) data
• Optionally, the normal flag range (MX .. MR) can
also be placed in the battery-buffered memory
area.
• Interface in the runtime system for libraries
• Initialization (C), deinitialization, version
check, memory management, management of
background tasks, provision for online change
• Support for exception handling in the runtime
system

396

System Overview • Bachmann electronic GmbH • 05/2018 • Specification subject to change –

the product’s characteristics are exclusively governed by the data of the respective user manual.