Progrm Upload to Controller in Somachine Basic

Converting Projects

Converting SoMachine Basic and Twido Projects

Introduction

With EcoStruxure Motorcar Expert, you can convert a SoMachine Basic or TwidoSoft/TwidoSuite project and the configured controller to a selectable EcoStruxure Machine Expert logic controller . The controller and the respective logic are converted and integrated in the EcoStruxure Auto Expert project.

For the conversion process, execute the File > Convert SoMachine Basic Project or the File > Convert Twido Project control. The Convert SoMachine Basic Project dialog box or Convert Twido Project dialog box opens. If the commands are not available, y'all tin insert them in a menu of your choice by using the Tools > Customizedialog box.

The SoMachine Basic versions supported past this conversion mechanism are listed in the release notes of EcoStruxure Machine Expert. If you convert a SoMachine Basic project that was created with a SoMachine Basic version that is newer than the latest supported version, this is indicated past a message in the Messagesview. You can then proceed or abolish the conversion. If yous continue, the application will exist converted, but it may not be possible to exercise so without encountering errors that will need to be rectified. In this instance, review and verify both the message view and your application before attempting to put it into service.

Note: Verify that the SoMachine Bones or Twido project is valid earlier you convert it into EcoStruxure Machine Proficient.

Note: It is non possible to convert countersign-protected projects.

To help to avert unintended behavior subsequently a project was converted, verify that the target controller supports the functions and communication ports that are required in your project.

WARNING

UNINTENDED EQUIPMENT Functioning

o Verify that the program for the target controller contains the intended configurations and provides the intended functions after you have converted the project. o Fully debug, verify, and validate the functionality of the converted program before putting it into service. o Before converting a program, verify that the source program is valid, i.due east., is downloadable to the source controller.

Failure to follow these instructions can result in expiry, serious injury, or equipment harm.

NOTE: For more than information, communication and important safety information concerning importing projects into EcoStruxure Machine Good, see the Compatibility and Migration User Guide.

Converting a SoMachine Bones or a Twido Projection

Step	Action
1	To start the conversion process, perform i of the three actions in the EcoStruxure Machine Expert Logic Builder (as listed in the Introduction block of this chapter ). Outcome: The Convert SoMachine Bones Project dialog box or Convert Twido Project dialog box opens:
2	Enter a proper name for the controller in the Device Proper name field.
3	Enter the path to the SoMachine Basic or Twido project file in the Project File box, or click the ... button to browse for the file. NOTE: If you already browsed for your SoMachine Basic or Twido project in the Open project dialog box, the path has been entered automatically in the Project File field and cannot be edited.
4	Select the programming language in which the logic volition be converted from the Implementation Language list. The following programming languages are supported: o Ladder diagram (LD) o Function block diagram (FBD) o Educational activity listing (IL) o Continuous office chart (Cfc)
v	Select the target controller from the Devices listing in which yous want to convert your SoMachine Basic or Twido controller. Further information on the selected device is displayed in the Information area of the dialog box.
half-dozen	Click Convert to outset the conversion. Effect: The SoMachine Bones or Twido project is converted and integrated in the open EcoStruxure Auto Expert project. Modifications or configurations that could non be converted are listed in the Messagesview.
7	Consult the category Project Conversion of the Letters view and verify the errors and alerts detected and listed.
8	Verify whether the converted projection contains the intended configurations and provides the intended functions. If not, adapt the configuration.

IEC Compatibility of Object and Variable Names

Object names and variable names in EcoStruxure Machine Skillful projects accept to comply with the naming conventions defined in the IEC standard. Any names in your SoMachine Basic or Twido project that exercise non comply with the standard are automatically adjusted to IEC conventions past the converter.

If you lot want to preserve names that are not IEC-uniform in the converted EcoStruxure Machine Expert project, activate the option Allow unicode characters for identifiers in the Project Settings > Compile optionsdialog box.

TwidoEmulationSupport Library

The TwidoEmulationSupport library contains functions and function blocks that provide SoMachine Basic and TwidoSoft/TwidoSuite functionality in a EcoStruxure Machine Skillful application. The TwidoEmulationSupport library is automatically integrated in the EcoStruxure Auto Expert project with the converted controller.

Conversion of the Application Plan

In the target EcoStruxure Machine Expert project, separate programs are created for each SoMachine Basic POU and free POU and for each Twido subroutine and program section. The programming language that is used for these programs is determined by the Implementation Language selected in the Convert SoMachine Basic Project / Convert Twido Projection dialog box. An exception is made for POUs that were programmed in graphical Grafcet . They are converted to an SFC  programme. For detailed information, refer to the Grafcet section in this affiliate .

For each language object (such as retention objects or role blocks) being used by the application program, one global variable is created. Separate global variable lists  for the dissimilar object categories (i for memory bits, i for memory words and so forth) are created.

The following restrictions employ for the conversion of the awarding plan concerning the programme structure:

o In EcoStruxure Motorcar Expert, it is not possible to bound to a label in another program.

o It is non possible to define Grafcet steps in a subprogram.

o Information technology is not possible to activate or conciliate Grafcet steps (per # and D# instruction) in a subprogram.

Conversion of Retentivity Objects

The areas provided for memory objects in SoMachine Basic and Twido differ from EcoStruxure Machine Practiced.

In SoMachine Bones and Twido, there are three distinct areas for retentiveness objects:

Area	Retentiveness objects included
retentivity chip area	memory bits (%M)
memory give-and-take expanse	o retentivity words (%MW) o double words (%Doc) o floating point values (%MF)
constant area	o constant words (%KW) o double words (%KD) o floating signal values (%KF)

In EcoStruxure Machine Expert, there is simply the retention word area for retention objects:

Area	Memory objects included
memory word area	o memory words (%MW) o double words (%Physician) o floating indicate values At that place is no specific addressing format for floating indicate values. Floating point variables tin be mapped on a %MD accost.

The graphic provides an overview of the different layouts of %Doctor and %MF addresses in SoMachine Basic / Twido and EcoStruxure Machine Adept.

ane Retentiveness addresses in SoMachine Basic / Twido

2 Retention addresses in EcoStruxure Machine Skillful

Memory objects are converted every bit follows:

Source memory objects	Target retentiveness object	Further information
%MW	Mapped to the same %MW address Instance %MW2 is mapped on %MW2.	For each %MW object, a global variable of type INT is created.
%MD  and %MF with even addresses	Mapped such that they are located on the same %MW accost equally before. Example %MD4 / %MF4 are mapped on %MD2.	For each %Md object, a global variable of type DINT is created. For each used %MF object, a global variable of type Existent is created.
%Dr.  and %MF with uneven addresses	Cannot be mapped considering a DINT variable cannot be located on an odd give-and-take address.	A variable is created to assistance ensure that the converted application can be congenital. Even so, you need to examine the effect that such variable creation has on the overall functionality of your plan.
%G	Mapped as a packed bit field to a fix location in the %MW area.	For each %M object, a global variable of type BOOL is created.
%KW	Mapped to consecutive addresses of the %MW area.	For each used %KW object, a global variable of type INT is created.

The human relationship between %KW, %KD, and %KF objects is the same as for %MW, %Doc, and %MF objects. For instance, %KD4 / %KF4 are mapped on the same location as %KW4. Uneven %KD / %KF addresses cannot be mapped.

Remote Access

Memory objects (%MW, %MD, %MF, and %Grand) can be accessed by a remote device through Modbus services:

o If a remote device accesses %MW, %Md or %MF objects in the source application, this admission volition all the same be bachelor in the EcoStruxure Machine Skillful application.

o If a remote device accesses %M objects in the source application, this admission will no longer be available in the EcoStruxure Auto Expert application.

Handling Ascension and Falling Edges

A ascension/falling edge contact is converted as follows:

ane. An additional global variable with the suffix _Rise/_Fall is created (for example, M1_Rise for a rising border contact for %M1).

2. This variable is set via an R_TRIG/F_TRIG example in the SystemFunctions program.

Edge detection is performed at the beginning of the controller cycle.

A FALLING/RISING education is straight converted into an R_TRIG/F_TRIG instance.

Edge detection is performed at the aforementioned place of the execution sequence as in the original application.

Conversion of Function Blocks

For the following function blocks in SoMachine Basic / Twido, the TwidoEmulationSupport library provides office blocks with uniform functions:

SoMachine Basic / Twido function block	TwidoEmulationSupport library function block
Timers %TM	FB_Timer
Counters %C	FB_Counter
Register %R	FB_FiFo / FB_LiFo
Drum %DR	FB_Drum
Shift bit register %SBR	FB_ShiftBitRegister
Step counter %SC	FB_StepCounter
Schedule %SCH	FB_ScheduleBlock
PID	FB_PID
Exchange / message %MSG	FB_EXCH
High-speed counter %HSC / %VFC	They are converted as described in the department Conversion of Fast Counters, High-speed Counters (Twido: Very Fast Counters) and Pulse Generators  of this chapter.
Fast counter %FC
PLS pulse generator %PLS
PWM pulse generator %PWM
PTO function blocks %PTO, %MC_xxx_PTO
Frequency generator %FREQGEN
Advice part blocks READ_VAR, WRITE_VAR, WRITE_READ_VAR , and SEND_RECV_MSG	FB_ReadVar, FB_WriteVar, FB_WriteReadVar, and FB_SendRecvMsg
SMS function block SEND_RECV_SMS	They are not converted.
MC_MotionTask_PTO
Drive function blocks %MC_xxx_ATV
%DATALOG

For the conversion of function blocks, note the following:

o The TwidoEmulationSupport library does not provide whatsoever function blocks for hardware-related functions, such every bit high-speed counters, fast counters, and the pulse generators. They must be controlled through office blocks provided by the platform-specific HSC and PTO_PWM libraries. These part blocks are non compatible with the source part blocks. In short, a full conversion is not possible if the source program contains functions based on controller hardware resource. For farther information, refer to the description Conversion of Fast Counters, High-speed Counters (Twido: Very Fast Counters) and Pulse Generators .

o In SoMachine Basic / Twido, the messaging function is provided past the EXCHx educational activity and the %MSGx function cake. In the EcoStruxure Motorcar Expert application, this role is performed by a single function block FB_EXCH.

o In SoMachine Basic / Twido, sure part blocks can be configured using special configuration dialog boxes. This configuration information is provided to the function blocks of the TwidoEmulationSupport library by dedicated parameters.

o If a rung  contains multiple function blocks, the converter may split the rung into multiple logic networks.

Conversion of Network Objects

The table indicates the network object types that are supported by the conversion:

Network object	Object part	Supported
%QWE	Input associates (EtherNet/IP)	Yes
%IWE	Output assembly (EtherNet/IP)	Yes
%QWM	Input registers (Modbus TCP)	Yes
%IWM	Output registers (Modbus TCP)	Yeah
%IN	Digital inputs (IO scanner)	Only Serial IO scanner
%QN	Digital outputs (IO scanner)	Merely Serial IO scanner
%IWN	Input registers (IO scanner)	Only Serial IO scanner
%QWN	Output registers (IO scanner)	Only Serial IO scanner
%IWNS	(IO scanner Diagnostics)	Just Serial IO scanner

Conversion of Arrangement Variables

The post-obit system bits and words are converted:

System bit / word	Farther information
%S0	Is set to 1 in the offset cycle after a cold start. NOTE: It is not possible to trigger a common cold start by writing to this arrangement bit.
%S1	Is set to 1 in the first cycle after a warm start. Note: It is not possible to trigger a warm start by writing to this system bit.
%S4	Pulse with the time base 10 ms.
%S5	Pulse with the time base 100 ms.
%S6	Pulse with the time base 1 southward.
%S7	Pulse with the time base of operations 1 min.
%S13	Is ready to 1 in the get-go cycle after the controller was started.
%S18	Is set to ane if an arithmetic overflow occurs. NOTE: This flag is provided by the TwidoEmulationSupport library and is simply set by functions provided by this library.
%S21 , %S22	Are just written. Reading is not supported for these variables.
%S113	Stops the Modbus Serial IOScanner on serial line one.
%S114	Stops the Modbus Serial IOScanner on serial line two.
%SW63...65	Mistake code of the MSG blocks 1...3.
%SW114	Enable flags for the schedule blocks.

Other arrangement variables are not supported by the conversion. If an unsupported system variable is used by the source awarding plan, a message is generated in the category Project Conversion of the Messagesview.

Conversion of Retain Behavior

The variables and function blocks in SoMachine Basic / Twido are retain variables. This means, they keep their values and states fifty-fifty after an unanticipated shutdown of the controller besides as after a normal power cycle of the controller.

This retain behavior is not conserved during conversion. In EcoStruxure Motorcar Expert, the converted variables and function blocks are regular, which means that they are initialized during unanticipated shutdown and ability cycle of the controller. If you demand retain variables in your EcoStruxure Auto Practiced awarding, yous have to declare this aspect keyword manually.

Conversion of Animation Tables

Management of animation tables differs in the source and target applications:

o SoMachine Basic / Twido let you to ascertain multiple animation lists identified past name. Each animation list tin can incorporate multiple entries for objects to exist animated. For each variable, y'all can select the option Trace.

o In EcoStruxure Machine Proficient, in that location are 4 predefined watchlists (Watch one...Scout 4). Each watchlist can contain multiple variables to be blithe. Ane watchlist can contain variables from dissimilar controllers.

For those variables that have the option Trace selected in SoMachine Basic / Twido, EcoStruxure Machine Practiced creates a trace object. Yous tin can view these variables in the trace editor .

During the conversion process, the entries of the source blitheness tables are added at the end of watchlist Spotter 1.

Conversion of Symbols

Symbols defined in a SoMachine Basic / Twido project are automatically transferred into the EcoStruxure Machine Expert projection.

The following restrictions use to the naming of symbols:

If...	So ...
a symbol name does non comply with the naming rules of EcoStruxure Machine Expert,	the name of the symbol is modified.
a symbol proper name is equal to a keyword of EcoStruxure Auto Good,	the name of the symbol is modified.
no variable is created for a language object,	the name of the symbol is discarded.
a symbol is non used anywhere in the application program,	the name of the symbol may be discarded.

For the complete list of symbol modifications that were required, refer to the Letters view.

Conversion of Fast Counters, High-Speed Counters (Twido: Very Fast Counters) and Pulse Generators

The function blocks provided by EcoStruxure Machine Expert differ from the function blocks provided by SoMachine Bones / Twido. However, the configuration of fast counters, high-speed counters, and pulse generators is converted every bit far every bit possible. The post-obit sections provide an overview of the restrictions that apply.

General Restrictions

The following general restrictions apply:

Restriction	Solution
The inputs and outputs used by the converted loftier-speed counters and pulse generators may differ from the used inputs and outputs of the source application.	Take this into account in the wiring of the converted controller. The reassignment of inputs and outputs is reported in the Messagesview.
The SoMachine Basic controller may support a unlike number of counters and pulse generators than the selected target controller. The conversion part but converts the counters and pulse generators that are supported past the target controller.	Y'all have to adapt your application manually.

Constraints Pertaining to the Conversion of%FC, %HSC / %VFC, %PLS, and %PWM

For each %FC, %HSC / %VFC, %PLS, and %PWM part block being used in the SoMachine Basic / Twido application, a single program is created in EcoStruxure Machine Expert. You lot can meliorate this basic implementation according to the needs of your application.

The following restrictions apply:

Restriction	Solution
The access to role block parameters is performed differently in SoMachine Basic and EcoStruxure Machine Practiced. In SoMachine Basic, the parameters of a role cake tin can exist accessed directly by the application program, for example, %HSC.P = 100. In EcoStruxure Machine Skilful, a controller-specific function block (for case, EXPERTSetParam) has to be used to access a parameter.	If the source application accesses parameters of the function block, you accept to extend the converted application accordingly.
The beliefs of counters differs in EcoStruxure Machine Expert from SoMachine Bones / Twido when the preset value is ready. In Twido: o The downwards counter continues counting if nothing is reached. o The up counter continues counting if the preset value is reached. In EcoStruxure Motorcar Skilful: o The downwards counter stops counting if goose egg is reached. o The up counter starts to count from the beginning if the preset value is reached.	You accept to adapt your application manually.
The post-obit parameters of SoMachine Basic function blocks cannot be converted to EcoStruxure Auto Expert: Office cake %PLS: o Output parameter D [Done] o Parameter R [Duty Cycle] Function block %PWM: o Parameter R [Duty Cycle] Function block %HSC: o Output parameter U [Counting Management]	You have to adapt your application manually.

Constraints Pertaining to the Conversion of PTO Function Blocks%PTO and %MC_xxxx

For M241:

The PTO function blocks provided by EcoStruxure Machine Proficient for M241 controllers are compatible with the PTO function blocks provided by SoMachine Basic. PTO part blocks are converted without restrictions. The only exception is the MC_MotionTask_PTO function block. The MC_MotionTask_PTO is not converted.

For HMISCU:

The PTO function blocks provided by EcoStruxure Machine Expert for HMISCU controllers are not compatible with the PTO function blocks provided by SoMachine Basic. PTO function blocks are not converted.

Constraints Pertaining to the Conversion of Frequency Generator Function Block%FREQGEN

The frequency generator function block %FREQGEN is converted without restrictions for both M241 and HMISCU controllers.

Conversion of Loop Elements (FOR / ENDFOR)

The destination languages for the conversion practice not back up loops. For that reason, a FOR loop is broken up into a functionally equivalent sequence of logical networks using label and bound elements.

Conversion of Conditional Elements (IF / ELSE / ENDIF)

The destination languages for the conversion exercise non back up provisional statements (except EN / ENO, which are already used for other purposes). For that reason, an IF construction is broken upwards into a functionally equivalent sequence of logical networks using label and spring elements.

Conversion of a Grafcet Program

You lot can write a Grafcet program in a textual or in a graphical fashion.

Grafcet blazon	Description	Supported by
Textual	Diverse IL  and LD  programming elements are available for the definition, activation, and deactivation of Grafcet states.	o TwidoSoft/TwidoSuite o SoMachine Basic
Graphical	Allows you to draw the layout of steps, transitions, and branches in a graphical way.	Just SoMachine Bones V1.4 and later versions.

Conversion of Textual Grafcet

The programming languages of EcoStruxure Machine Expert do not back up the programming with Grafcet.

For that reason, a converted Grafcet application contains additional linguistic communication elements that implement the Grafcet management.

Additional chemical element	Description
binder Grafcet	This binder contains the following language elements used for the management of the Grafcet country machine.
data construction GRAFCET_STATES	This data structure has one chip element for each immune Grafcet country. If it is an initial state, the element is initialized to True, otherwise it is FALSE.
global variable list GrafcetVariables	This global variable list contains the following variables: o 1 variable STATES that contains 1 fleck for each Grafcet state. Each bit represents the present value of the respective Grafcet state (%Xi object). o 1 variable ACTIVATE_STATES that contains 1 bit for each Grafcet state. If the bit is True, the Grafcet state is activated in the side by side cycle. o one variable DEACTIVATE_STATES that contains 1 bit for each Grafcet country. If the bit is TRUE, the Grafcet state is deactivated in the next cycle.
programme Grafcet	This program implements the Grafcet land automobile. It contains the logic for the activation and deactivation of Grafcet steps. The program contains the post-obit actions: o Init initializes the Grafcet steps to their initial states. It is executed when the system chip %S21 is gear up past the application program. o Reset resets the Grafcet steps to Imitation. It is executed when the system scrap %S22 is set past the application plan.

The Grafcet instructions in the awarding program are converted every bit follows:

o The beginning of each Grafcet step is marked by a characterization with the name of the step.

The starting time statement inside the Grafcet footstep checks if the step is agile. If not, it jumps to the label of the next Grafcet footstep.

o The access to the %Xi is converted to an access to the STATES.Xi variable.

o A Grafcet activation instruction #i is converted to setting the activation bit of state i and the deactivation bit of the present state.

o A Grafcet deactivation instruction #Di is converted to setting the deactivation bit of country i and the deactivation bit of the present state.

Y'all tin can extend the converted Grafcet program if you consider the information given in this section.

Conversion of graphical Grafcet

Graphical Grafcet is similar to the programming language SFC  provided by EcoStruxure Machine Expert. For this reason, a graphical Grafcet POU is converted to an SFC program, as far as possible.

There are the following differences between graphical Grafcet and SFC:

Graphical Grafcet	SFC	Further information
Can accept an arbitrary number of initial steps.	Must have exactly ane initial step.	If the graphical Grafcet POU has several initial steps, then the converter creates several initial steps in SFC. This has the effect, that the converted application cannot exist built without errors being detected. Carefully adapt the converted program.
Activation of multiple steps of an alternative branch is allowed.	Only ane step of an alternative branch can be activated.	Carefully verify that the converted program is working as expected.
The output transitions of a stride are evaluated right after the pace has been executed.	The transitions of the SFC program are evaluated after all agile steps have been executed.	Carefully verify that the converted program is working equally expected.
The layout of steps, transitions, and branches is relatively costless.	The layout of steps, transitions, and branches is more than restricted.	The graphical layout is converted to SFC as far equally possible. The incompatibilities encountered during the conversion are reported in the Letters view. The step actions and transition sections are fully converted. Complete the created SFC as necessary.

A graphical Grafcet POU can be initialized by setting the system bit %S21. If this fleck is set in the SoMachine Basic projection, the converter activates the implicit variable SFCInit and uses information technology to initialize the SFC plan.

Conversion of TM2 Expansion Modules to TM3 Expansion Modules

Twido controllers only use TM2 expansion modules. Even though M221 and M241 Logic Controllers can handle TM2 as well every bit TM3 modules, information technology is a practiced practise to use TM3 modules. To catechumen the TM2 modules used in your Twido project into TM3 modules for the EcoStruxure Machine Expert project, the option Upgrade TM2 Modules to TM3 is by default selected.

The TM2 expansion modules are converted into TM3 expansion modules as listed in the table:

Source TM2 expansion module	Target TM3 expansion module	Further information
TM2DDI8DT	TM3DI8	–
TM2DAI8DT	TM3DI8A	–
TM2DDO8UT	TM3DQ8U	–
TM2DDO8TT	TM3DQ8T	–
TM2DRA8RT	TM3DQ8R	–
TM2DDI16DT	TM3DI16	–
TM2DDI16DK	TM3DI16K	–
TM2DRA16RT	TM3DQ16R	–
TM2DDO16UK	TM3DQ16UK	–
TM2DDO16TK	TM3DQ16TK	–
TM2DDI32DK	TM3DI32K	–
TM2DDO32UK	TM3DQ32UK	–
TM2DDO32TK	TM3DQ32TK	–
TM2DMM8DRT	TM3DM8R	–
TM2DMM24DRF	TM3DM24R	–
TM2AMI2HT	TM3AI2H	–
TM2AMI4LT	TM3TI4	It is possible that the behavior of the converted temperature module differs from the original module. Advisedly verify the converted module.
TM2AMI8HT	TM3AI8	–
TM2ARI8HT	–	The TM2 modules TM2ARI8HT, TM2ARI8LRJ, and TM2ARI8LT are non converted because in that location is no corresponding TM3 expansion module. You can replace this module by ii TM3TI4 modules.
TM2AMO1HT	TM3AQ2	The target TM3 expansion module has more I/O channels than the source TM2 module.
TM2AVO2HT		–
TM2AMM3HT	TM3TM3	–
TM2ALM3LT		Information technology is possible that the behavior of the converted temperature module differs from the original module. Advisedly verify the converted module.
TM2AMI2LT	TM3TI4	The target TM3 expansion module has more I/O channels than the source TM2 module. It is possible that the behavior of the converted temperature module differs from the original module. Carefully verify the converted module.
TM2AMM6HT	TM3AM6	–
TM2ARI8LRJ	–	The TM2 modules TM2ARI8HT, TM2ARI8LRJ, and TM2ARI8LT are not converted considering there is no corresponding TM3 expansion module. You can replace this module past two TM3TI4 modules.
TM2ARI8LT	–	The TM2 modules TM2ARI8HT, TM2ARI8LRJ, and TM2ARI8LT are not converted because there is no corresponding TM3 expansion module. You can replace this module by two TM3TI4 modules.

Note: If you are using TM2 as well every bit TM3 expansion modules in your EcoStruxure Machine Good project, note their position in the tree structure: If TM3 nodes are located below TM2 nodes in the tree structure, this is reported every bit a detected Build error in the Messages view.

Conversion of Modbus Series IOScanner

Due to the differences betwixt controller platforms, and specially for connected controller equipment that depend on the proper functioning of the converted program, you must verify the results of the conversion process. Whether or non errors or alerts are detected during the conversion, information technology is imperative that you thoroughly test and validate your entire system inside your machine or process.

WARNING

UNINTENDED EQUIPMENT Performance

o Verify that the programme for the target controller contains the intended configurations and provides the intended functions after you have converted the project. o Fully debug, verify, and validate the functionality of the converted program before putting it into service. o Before converting a programme, verify that the source plan is valid, i.e., is downloadable to the source controller.

Failure to follow these instructions tin issue in decease, serious injury, or equipment damage.

Configuration

The IOScanner configuration is completely converted:

o The devices are converted to the Generic Modbus Slave device. The source device blazon is non preserved.

o The device configuration is completely converted. This includes initialization requests, channel settings, and reset variable.

Function Blocks

The drive function blocks for the control of Altivar drives over the Modbus IOScanner (MC_xxx_ATV) are not converted.

Status Handling

Since the IOScanner status handling differs for SoMachine Basic and EcoStruxure Machine Expert, these features can only be partly converted. If your application uses IOScanner condition information, verify that this logic still works.

IOScanner Condition	Further information
Device Status (%IWNSx)	Both SoMachine Bones and EcoStruxure Machine Skillful provide condition information for a slave device, but the status values are different. The status logic is partly converted.
Channel Status (%IWNSx.y)	EcoStruxure Automobile Expert does not provide status information for single channels. The channel status is converted to the device status.
Organisation words and $.25:
%S110/%S111 (IOScanner reset)	They are non converted.
%S113/%S114 (IOScanner stop)	They are converted.
%SW210/%SW211 (IOScanner status)	They are not converted.

Conversion of Modbus TCP IO Scanner

The configuration of the Modbus TCP IO Scanner is not converted.

Immediate I/O Access

The instructions READ_IMM_IN and WRITE_IMM_OUT of SoMachine Basic for immediate access to digital local I/O channels are non converted.

For M241 controllers, yous tin can use the functions GetImmediateFastInput and Physical­WriteFastOutputs provided past the PLCSystem library, but consider the following differences:

READ_IMM_IN  and WRITE_IMM_OUT  instructions (M221 controllers)	GetImmediateFastInput and PhysicalWriteFastOutputs functions (M241 controllers)
Admission to all local inputs and outputs.	Admission simply to fast inputs and outputs.
WRITE_IMM_OUT writes a single bit (like to the read function). WRITE_IMM_OUT returns an error code.	PhysicalWriteFastOutputs writes fast outputs at the aforementioned time. PhysicalWriteFastOutputs only returns the information on which outputs have actually been written.
The error codes of READ_IMM_IN and GetImmediateFastInput differ.
READ_IMM_IN updates the input object (%I0.x).	GetImmediateFastInput only returns the read value but does non update the input channel.

NOTE: For HMISCU controllers, no equivalent function exists.

Twido Communication Features

The following advice features of Twido are not converted:

o AS Interface

o CANopen

o remote link

If yous use these communication features in your Twido application, yous have to conform the EcoStruxure Machine Proficient application manually.

During conversion, 1 variable is created for each related I/O object in order to allow the EcoStruxure Machine Expert application to be built successfully. These variables are collected in separate global variable lists. This helps you in identifying the variables to be replaced.

Detected Errors and Alerts Indicated in the Letters View

If errors or alerts are detected during the conversion process, a message box is displayed, indicating the number of errors and alerts detected. For further information, consult the category Project Conversion of the Lettersview. Verify each entry carefully to see whether you have to adapt your application.

Warning

UNINTENDED EQUIPMENT OPERATION

o Verify that the program for the target controller contains the intended configurations and provides the intended functions later on yous have converted the project. o Fully debug, verify, and validate the functionality of the converted program earlier putting it into service. o Earlier converting a program, verify that the source program is valid, i.e., is downloadable to the source controller.

Failure to follow these instructions can upshot in death, serious injury, or equipment harm.

o A warning message indicates that the conversion process made some adjustments that, in all likelihood, do not take bear on on the functions of your application.

o An error bulletin indicates that some parts of the awarding could not be fully converted. In this case, you have to adapt the application manually in club to preserve the same functionality in the target application.

o If the application programme makes utilise of functionality that cannot be completely converted, the converter creates variables for the unsupported language objects. This allows you to compile your application successfully. However, verify this unsupported functionality after the conversion.

To save the information displayed in the Messages view, you tin re-create it to the Clipboard (press CTRL + C) and paste it to a data file (press CTRL + V).

devrieswhickeenet.blogspot.com

Source: https://product-help.schneider-electric.com/Machine%20Expert/V1.1/en/SoMProg/SoMProg/Managing_Devices/Managing_Devices-11.htm

Share this post