Automation / Engineering Software / 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 sym-
bols
• 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 projects open and
online in parallel)
• Automatic project backup and creation of backup
• Project archiving on the controller
• Password protection for projects
Controller Controller
• Offline simulation
• Online help
IEC61131
SMI
IEC61131
• Data exchange system-wide via SVI/SMI interface programming
VxWorks

VxWorks
Tasks

Tasks
Tasks

Tasks
Tasks
Tasks

VxWorks VxWorks

Bachmann electronic GmbH • 08/2021 • Specification subject to change – the product’s characteristics are exclusively governed by the data of the respective user manual.
 Automation / Engineering Software / Programming

Runtime system • Between any modules on different controllers: SMI

• Any number of running M-PLC projects on one processor1) • Interface to visualization/SCADA/BDE
• Every PLC project supports up to 16 separate tasks • Standard protocols: OPC DA, IEC 61850 IEC 61400,
• Each task can be configured independently of the others Modbus etc.
in terms of (priority, task call-up mode [event, timetrigger, • Libraries for integration into separate software
free running, sync], watchdog) (for C/C++, C#.NET, Java)
• Actual multitasking via operating system tasks (VxWorks) • Support of battery-buffered data (RETAIN flag)
• Communication between software modules
(pre-compiled units)
• 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
1) Maximum 256 user software modules

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

Online functions
• 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

Bachmann electronic GmbH • 08/2021 • Specification subject to change – the product’s characteristics are exclusively governed by the data of the respective user manual.
Automation / Engineering Software / Programming

Herstellerbibliotheken • Display of the status „in error handling“ (ERROR) in the

• STANDARD IEC 61131-3 Standard functions interface
• SMI_PLC Functions for fast ommunication between • Implementation of the I/O modules of the process image
modules and controllers (SMI/SVI) in the runtime system
• PLC 7 standard PID controllers • Optimized for performance, flexibility and c­ ombinability,
• MIO_PLC Functions for direct access to hardware I/Os shared use of an I/O module by multiple projects/SW
• EHD_PLC Functions for inputting and managing errors modules possible
in the EHD • Saving/loading of the entire project including sources to/
• UTIL_PLC Functions for access to RTC, runtime system from the controller
info, special conversions • Transparency of the global variables (flags, symbolic
• FILE_PLC Functions for access to files, directories and ­variables, structures) controller- and visualization-wide
serial interfaces 
• CIA405 Functions for access to CAN
• DN_PLC Functions for access to device net Integration in the SolutionCenter
• PB_PLC Functions for access to Profibus (projects are SW modules)
• USS_PLC Functions for communication with • Generation of an executable *.m file with configuration
­„Micromaster“ frequency converters information
• Task interval time measurement, can be queried in the
project itself and in Device Manager
Extensions relative to CoDeSys • Watchdog integration
• process image (controller configuration) runtime- • Execution possible in an application layer
optimized process image (only channels being used are (memory protection)
processed) • Install, start, stop, reset and delete of PLC projects in
• CAN objects with symbolic names in the process image Device Manager
• Addressing for inputs/outputs: undelayed access that • The state machine of a PLC project in the runtime system
bypasses the process image always corresponds to the model defined for SW modules.
• Adjustment of the interval time and watchdog time in the • Integration via M1 system debug mode and M1 system
controller configuration logbook
• Multiple, concurrently running PLC projects on one CPU • Start of a project when booting through entry in MConfig.
with different priorities / interval times ini
• 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

Bachmann electronic GmbH • 08/2021 • Specification subject to change – the product’s characteristics are exclusively governed by the data of the respective user manual.