SoMachine Software
SoMachine V4.1 SP2

Release Notes
.

Software Version: V4.1 SP2

Build: 15.12.16.02
Release Date: 16.12.2015
Development Stage: Release

This document contains important information about the SoMachine software patch. 
Please read the complete document before you run the product.

This documentation is not intended as a substitute for and is not to be used for determining suitability or reliability of these products for specific user applications. It is the duty of any such user or integrator to perform the appropriate and complete risk analysis, evaluation and testing of the products with respect to the relevant specific application or use thereof. Neither Schneider Electric nor any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information contained herein. All pertinent state, regional, and local safety regulations must be observed when installing and using this product. When devices are used for applications with technical safety requirements, the relevant instructions must be followed. Failure to use Schneider Electric software or approved software with our hardware products may result in injury, harm, or improper operating results. Failure to observe this information can result in injury or equipment damage. If you have any suggestions for improvements or amendments or have found errors in this publication, please notify us. No part of this document may be reproduced in any form or by any means, electronic or mechanical, including photocopying, without express written permission of Schneider Electric.

© 2015 Schneider Electric. All rights reserved.

Table of contents
1.	System Requirements
1.1.	Supported Operating Systems
1.2.	PC Software Requirement
1.3.	PC Hardware Requirement
1.4.	Restrictions on 32 Bit systems
1.5.	Additional hints for reducing SoMachine's memory consumption:
1.6.	Increasing SoMachine's Build-Time performance:
2.	IMPORTANT INFORMATION
2.1.	Installation
2.2.	Changes compared to SoMachine V4.1 SP1 (DVD-Version)
2.2.1.	Improvements in SoMachine V4.1 SP1.1
2.2.2.	Improvements in SoMachine V4.1 SP1.2
2.2.3.	Improvements and changes in SoMachine V4.1 SP2
2.3.	Documentation changes for Altivar71_control
2.4.	Limitations and Restrictions
2.4.1.	SoMachine Central
2.4.2.	LogicBuilder
2.4.3.	VM usage
2.4.4.	DTM
2.4.5.	IO-Scanner
2.4.6.	Ethernet/IP
2.4.7.	TCP/UDP Library
2.4.8.	User rights
2.4.9.	Restrictions regarding compatibility of projects created with SoMachine V3.1 or earlier
2.4.10.	Compatibility
2.4.11.	Controller assistant
2.4.12.	OPC client
2.4.13.	Conversion of Twido and SoMachine-Basic Projects
2.4.14.	ATV-IMC
2.4.15.	Lexium 32 position gear mode
2.4.16.	LMC058 / M258
2.4.17.	M251
2.4.18.	M241 & M251
2.4.19.	M221
2.4.20.	LXM32 (EtherNet/IP and Modbus TCP) and Lexium ILA/ILE/ILS (EtherNet/IP)
2.4.21.	ATV32 & LXM32.
2.4.22.	LMC078
2.4.23.	Energy Efficiency Libraries
2.4.24.	Hoisting
2.4.25.	QUICK Key
2.4.26.	Vijeo Designer
2.5.	Web visualization
2.5.1.	Scope
2.5.2.	System Requirements
2.5.2.1.	Web browser
2.5.2.2.	Controllers
2.5.3.	Best Practices
2.5.3.1.	General Usage
2.5.3.2.	Data security
2.5.3.3.	Web browser
2.5.3.4.	Visualization
2.5.3.5.	Programming
2.5.3.6.	Download of Application using FTP
2.5.3.7.	Controller
2.5.3.8.	Network
2.6.	List of integrated components

1.	System Requirements
1.1.	Supported Operating Systems
This patch can be installed on the following operating systems:

•	Microsoft Windows 7 Professional Edition 32 Bit / 64 Bit
•	Microsoft Windows 8.1 Professional Edition 32 Bit / 64 Bit

SoMachine V4.1 SP2  is optimized for a 64 Bit Operating system 
(see 1.4. for details on 32 Bit systems).
1.2.	PC Software Requirement 
This software requires the following system components to run properly:
 
•	Microsoft .NET Framework 4.0

1.3.	PC Hardware Requirement 
EQUIPMENT	MINIMUM	RECOMMENDED	
Processor	Intel® Core™ 2 Duo*
or equivalent	Intel® Core™ I7
or equivalent	
RAM	3 GB	8 GB	
Free Hard Disk Space	8 GB including the memory space for the typical software installation, temporary space for execution and space for saving applications	15 GB for the full software installation, temporary space for execution and space for saving applications	
Display	Resolution: 1280 x 1024 pixel	Resolution: 1680 x 1050 pixel	
Peripherals	A mouse or compatible pointing device	
Peripherals	USB interface	
Web Access	Web registration requires internet access system	
*Might run with less performance CPUs, but with restrictions.

Virtual Machine usage
•	When using a VM running SoMachine V4.1 SP2, be sure to fulfill the minimal requirements especially for RAM, hard disk space and number of Cores inside the VM. Otherwise unexpected errors may occur (e.g. out of memory exception when installing SoMachine V4.1 SP2).

1.4.	Restrictions on 32 Bit systems
SoMachine is able to cope with large projects regarding the memory consumption. Nevertheless, there is a technical limit of memory usage by 32bit operating systems. You can encounter this technical limit with a large SoMachine project.

Remark: Categorizing a project as large is difficult. It might help having a look at the total count of "objects" (like devices, POUs and Actions, DUTs, GVLs, Visualizations) as seen in the 'Statistics' tab of the 'Project Information' dialog.  However, it could also be that one or several of these objects are extraordinarily large.

Note that 32 bit operating systems like Windows 7 32-bit have, by default, a maximum memory limit of 2GB assigned to user processes like SoMachine. You might consider increasing this limit to 3GB by using the /3GB boot option.

Before making this modification, be aware that this modification may not be compatible with your hardware or with other software installed on your system. It will probably not work with Video cards sharing memory with your computer as it is, for example, with an Intel HD Graphic Card.

If you experience any unintended, or what you may consider abnormal, behavior with the 3GB switch enabled, you may want to disable it and move to a 64 bit operating system.
Windows 7:
How to enable the 3GB switch:
1.	Start Menu -> All Programs -> Accessories
2.	Right-click Command Prompt and Click Run as Administrator.
3.	Enter "bcdedit /set IncreaseUserVa 3072"
4.	Restart the computer.
How to disable the 3GB switch:
1.	Start Menu -> All Programs -> Accessories
2.	Right-click Command Prompt and Click Run as Administrator.
3.	Enter "bcdedit /deletevalue IncreaseUserVa"
4.	Restart the computer.

1.5.	Additional hints for reducing SoMachine's memory consumption: 
In case your large project contains independent parts (like independent root devices), you might consider splitting it into several smaller projects.

Note also that by keeping several editors open, this will increase SoMachine's memory consumption, too. Consider closing unneeded editors for reducing memory consumption.

1.6.	Increasing SoMachine's Build-Time performance: 
To avoid a slow performance when working with SoMachine you can follow several recommendations to get the best user experience with our Software:

•	Verify that the hardware of the PC is matching the recommended system requirements described in chapter 1.3 
•	By using a Solid State Drive (SSD) and ensuring that you have enough memory. Please contact your IT administration if you are not sure what this means.
•	Please consider uninstalling unneeded components via SCM.
•	If you are using Vijeo Designer integrated in SoMachine you may want to activate "Disable automatic symbol export"  in the LogicBuilder Options / Vijeo Designer entry
•	Activate "Disable Undo after deleting DTMs" in the LogicBuilder Options / FDT entry if this function is less important for your daily work.
•	Avoid "oversized" POUs. SoMachine has no limit for the size of POUs programmed in graphical languages like LD, but it is recommended to make use of the possibility to call POUs in sequences instead of creating one big POU

2.	IMPORTANT INFORMATION
2.1.	Installation
SoMachine V4.1 SP2 is an update for the following installed versions: SoMachine V4.1 SP1, V4.1 SP1.1, V4.1 SP1.2. It replaces the previous version on your PC. 

The installation of SoMachine V4.1 SP2 requires administrator privileges to start.

2.2.	Changes compared to SoMachine V4.1 SP1 (DVD-Version)
All changes (features and bugfixes) implemented in SoMachine V4.1 SP1.1 and SoMachine V4.1 SP1.2 are also included in SoMachine V4.1 SP2. 

2.2.1.	Improvements in SoMachine V4.1 SP1.1

•	New ModbusTCP Slave library for HMISCU devices
•	Performance improvements in several use cases (depending on the project):
-	General Ladder performance on opening and editing POUs
-	AutoDeclare 
-	Open projects
-	Build (All)
-	Clean (All) 
•	Memory consumption optimized
•	Ladder Editor: Fixed an issue with function calls in parallel branches
•	Performance improvement on opening projects with many libraries
•	Direct Addressing in Network Variable List is now possible
•	Softmotion: Fixed an issue on scaling factor with non-integral modulo value

2.2.2.	Improvements in SoMachine V4.1 SP1.2

•	Fixed an issue with writing/forcing variables without address information in online mode
•	Support for Vijeo Designer 6.2 SP3
-	New HMIGTU device family
-	New iPC devices
-	Fix for HMISCU
•	Fix for Altivar71 (see below 2.3)
•	Corrections for OnlineHelp TM3 Safety
•	Fix for TM3 Thermocoupler
•	Improvement of performances after a modification of GVL
•	Fixed an issue that after update device the device is in simulation mode
•	Fixed an issue that after creating a NVL SoMachine is not responding
•	Fixed an issue with the device filter inside the new project assistant
•	Global variables can now be published using the software catalog

ATTENTION
Vijeo Designer 6.2 SP3 or higher is absolutely necessary to connect the above mentioned HMIGTU and iPC devices.

2.2.3.	Improvements and changes in SoMachine V4.1 SP2
New devices:
•	M251 Controller as EtherNet/IP Master (M251MESE)
•	Altivar 71 for EtherNet/IP (Variable speed drive)
•	Altivar 32 for EtherNet/IP (Variable speed drive)
•	Lexium 32 M for EtherNet/IP (Servo drive)
•	Lexium ILA for Modbus TCP and EtherNet/IP (Servo drive)
•	Lexium ILE for Modbus TCP and EtherNet/IP (Servo drive)
•	Lexium ILS for Modbus TCP and EtherNet/IP (Stepper drive)
•	OsiSense XGCS for Modbus TCP and EtherNet/IP (RFID sensor)
•	OsiSense XUW for EtherNet/IP (Vision sensor)
•	Preventa XPS MCM for EtherNet/IP (Programmable safety controller)
•	Generic EtherNet/IP slave device
•	Generic TCP/UDP device without protocol (to be used along with the library dedicated to TCP/UDP) 
•	New Industrial Ethernet Manager
-	Implements DHCP Server configuration
-	Implements Ethernet/IP and ModbusTCP IO Scanner

Libraries:
•	New TCP/UDP_Communication  Library
-	Provides the core functionality for the implementation of socket-based network communication protocols using TCP (client/server) or UDP
•	New PackML Library
-	Contains objects to support the creation of an application in compliance with the PackML standard
•	General Motion Control (GMC) Libraries
•	EtherNetIP Support Libraries
•	Altivar library V4.5.0.0
-	function block "Altivar_Startup" is no longer blocked (iq_iCMD=-1), when the drive is switched off and then on.
•	Toolbox library Vx.y.z.a
-	the function block "MonoStable_Valve" has been improved, to show an error when the feedback signal supervision is active and the valve is closed
•	Lexium library V3.5.4.0
-	the function block "Servo_Startup" of can now reset and start the drive again, after an error E1300 has occured and the drive was  controlled by the application (i_iControlMode=1)

	TVDA
•	Update - TVDA
All TVDA project templates have been updated to this SoMachine version. The TVDA Device Module Library has been split into 5 separate libraries:
•	TVDA Device Module Library – CANopen
•	TVDA Device Module Library – CANmotion 
•	TVDA Device Module Library – Hardwired
•	TVDA Device Module Library – ModbusSL
•	TVDA Device Module Library – ModbusTCP

•	New - TVDA for EtherNetIP
This component introduces a new Tested Validated and Documented Architecture (TVDA) based on the Logic Controller M251. With the component TVDA for EtherNetIP a SoMachine project template together with its associated System User Guide is installed on your system. In addition the function template library TVDA Device Module Library – EtherNetIP is installed into the template repository.

	SoMachine Central:
•	For a parallel installation of SoMachine V3.1 and V4.1 SP2 on Windows7 32bit, when double-clicking on a project file from Windows Explorer, this project file will be opened by the right SoMachine version (V3.1 or V4.1 respectively), i.e. the one with which the project was created.
•	SoMachine Central can now open / convert CoDeSys V2.3 .pro files (like LMC020 projects; including the application part, like POUs, visualizations, CAN and CNC elements; excluding the device part, like controller configuration, axis, IOs,...).
* SoMachine V4.1 SP2 is now able to import a Vjieo Designer .vdz file, even if the control part (present in the SoMachine project before the import) has build errors.
•	When updating a SoMachine V3.1 project, that was protected with the legacy user management mechanism, this protection can now be cleared by disabling the user management in SoMachine V4.1 SP2.
•	SoMachine Central can now also save archives with DTM modules, containing trailing blanks in their module (type) name
•	Download Source: please note that the "Download Information files" project setting is now turned on by default within new projects, thus simplifying the "Upload source" scenario. 
•	Export SoMachine Basic Project: in case of several embedded M221 controllers, it is now possible to select the controller to export 
•	New Menu-Items: 
-	Convert TWIDO Project to SoMachine
-	Convert SoMachine Basic Project to SoMachine
•	Improved startup performance of Vijeo Designer when symbol configuration is unchanged

	LogicBuilder:
•	TM258 / LMC058 and TM241 / TM251:
•	 Periodic task number up to 5
•	 Up to 8 simultaneous controller connections (from SoMachine, HMI,…) 
•	 Ethernet/IP adapter assembly sizes are extended to 120 words
•	 ModbusTCP salve register sizes are extended to 120 words
•	TM241 / TM251:
•	 TM2 / TM3 modules can now configured as optional devices
•	 It is now possible to start LogicBuilder via Desktop/Start Menu icon without SoMachine Central (installation option, deactivated by default)
•	SoMachine V4.1 SP2 will now create warnings in new projects, if they don't contain an implicit check POU.
For details regarding implicit check POU, refer to the Online Help chapter "POUs for Implicit Checks" and in particular the subchapter "CheckBounds".
To disable this warning, go to Project Settings > Implicit checks and unset the check_bounds checkbox.
•	“Late adding" of  DTMs with ModbusTCP devices (see Online Help chapter "Using DTMs to Configure Devices on Modbus TCP or EtherNet/IP).
•	Device type information is shown when using Drag'n'Drop function from the Hardware Catalog to the Device Tree
•	Drag'n'Drop from the Hardware Catalog to the Device Tree is taking into account the preferred protocol configured inside a network manager (like in the Industrial Ethernet Manager)
•	The controller type is also shown in the Application and Tools view for the Application node
•	Verify and enforce single Profibus DPV1 master devices
•	Naming of I/O in OTB IO configuration tab modified
•	Support of SVG graphics in visualizations
•	Drag'n'Drop of modem into Navigator views improved to function reliability
•	A project containing calls of HSC function blocks can now be built also when the controller device is in simulation mode,
•	You can configure more than 28 PDOs for a CANopen slave (in this case all configured SDOs will be sent).
•	Function blocks using one of their IN_OUT parameters of type REAL as divisor now behave correctly, even if the implicit CheckDivDInt function is used in the project

FDT/DTM: 
•	"Edit Connection" is now available for several DTMs
•	The UI is no longer closed when DTMs disallow it to be closed
•	EtherNet/IP DTMs are now available, Lexium 32 M, Altivar 32 and Altivar 71
•	Overview Editor is available for DTMs in EtherNet/IP and Modbus TCP. This Editor will check if a DTM is installed and instantiate a DTM on demand

Gateway and Gateway Management Component
•	SoMachine V4.1SP2 uses a new Gateway component. This versions supports the activation and de-activation of USB connections to LMC078
•	Bluetooth support for M241/M251
•	New Online Help for the Gateway Management Console
•	Selection/Deselection of certain network adapters on a PC
•	Enable/disable of forwarding devices scanned by one Gateway to other Gateways in the same subnet

OnlineHelp
•	Contextual Online Help has been improved to better support finding functions and function blocks 
•	Operators and keywords have been added to the Online Help Index
•	the Online Help index will now be prepared only once (not at every call of Online Help)
2.3.	Documentation changes for Altivar71_control
General Purpose:

The already existing function BRH4 implemented in the Altivar 71 device can help to prevent suspended loads from falling for the rare case when the holding brake fails (see documentation of the Altivar 71 device).

The BRH4 function uses the encoder feedback to detect movement of the axis, after the brake should have been closed. If a movement is detected, the drive applies current to the motor in order to hold the load.

However, when Altivar71 is controlled via communication, the BRH4 function works only, if the drive is in state "Operation Enabled".

Modification of Altivar71_Control Function Block

Normally, the Altivar71_Control function block sets the drive to state "Switched On" as soon as there is no any direction command applied (i_xFwd = FALSE and i_xRev = FALSE) and the actual velocity and actual current decrease to zero, and thus the BRH4 function does not work.

The improvement of the Altivar71_Control function block consists in a new input i_xKeepOpEn, which allows keeping the Altivar 71 in state "Operation Enabled", in order that the BRH4 function can work.

The new behavior becomes active after the first direction command (i_xFwd = TRUE or i_xRev = TRUE) until the Function Block is disabled with i_xEn = FALSE.

The default value for the new input i_xKeepOpEn is FALSE, which means the default behavior of the Altivar71_Control FB is the same as in the past.

To get the new behavior (i.e. keeping Altivar71 in state "Operation Enabled" and making use of the BRH4 function) two steps have to be performed:

1.	activate the BRH4 function, e.g. HMI, SoMove or within the application

2.	set the new input i_xKeepOpEn of the Altivar71_Control to TRUE

NOTE: In case you were updating a project, the new input of the Altivar71_Control FB will not be initially visible. To make it visible use the contextual ResetPins command on the box in CFC and the UpdateParameters command in FBD/LD respectively.
2.4.	Limitations and Restrictions
2.4.1.	SoMachine Central
•	When the Windows operating system is configured to use large fonts, SoMachine or Vijeo Designer can have unintended behavior. 
To correct this, the screen resolution of a PC running SoMachine must be set to 100% (96 dpi). 
•	Within Windows 7, classic theme should not be used.  Aero theme should be used.
•	When opening a project archive file from Central, the "Options" that might be part of the archive should not be selected for extraction. Otherwise, Central might not open the project archive successfully.
•	To avoid problems when opening an archive, the LogicBuilder should be launched before opening the archive. (If the LogicBuilder has already been used during the current session, it is not necessary to open it again.)
There are the following alternatives to do this:
•	Create a new project, open the LogicBuilder, switch to Central, close the project (no need to save it) and then open the archive
•	Open an existing project, open the LogicBuilder, switch to Central, close the project and then open the archive
The same preparation is needed before uploading a project from a controller, as uploaded projects are always archives.

2.4.2.	LogicBuilder
•	Overlapping keyboard shortcut assignment in Windows7:
In SoMachine the keyboard shortcut Ctrl+Shift+0 is reserved for inserting a TON into a Ladder POU. But in Windows 7, Ctrl+Shift is assigned to the "Switch Keyboard Layout" feature. To enable the SoMachine shortcut the Windows 7 feature has to be turned off via the control Panel. (refer to http://support.microsoft.com/kb/967893)
•	Importing of dcf files inside LogicBuilder may lead to information data loss. If you want to transfer
Data between different SoMachine projects we recommend to use DTM Export / Import.
•	Watchdog can not be used in simulation mode.
If watchdog is active and a simulation is started a program exception can occur randomly.
•	When a Modbus Serial IOScanner is configured on a controller, if one of the Modbus slaves is disconnected, the application may go to exception state just after the download or after a reset of the controller. Please verify the integrity of your cable, and that your cable is correctly connected between the controller and the Modbus Serial slave. You should then reset your controller.
•	If an error is detected while using Modbus Serial IOScanner, the xError flag associated to the slave generating or causing the error is set to TRUE and the communication is NOT stopped (the controller will still try to connect the slave). By detection of this error uiNumberOfCommunicatingSlaves is decreased and xAllSlavesOK is set to False.
When the communication is re-established to this slave a rising edge on xReset entry of the slave is needed to reset xError and to update values of uiNumberOfCommunicatingSlaves and xAllSlavesOK.
•	NVL communication might be suspended after an online change. In such a case, a reboot of the target should be performed.
•	MultipleDownload might not work the first time if you use a HMI controller with an outdated firmware. In this case please start it a second time or use the “Download firmware HMI” button in Central instead.
•	Conversion from Non-HMI controller to a HMI controller is not available in SoMachine V4.1.
•	CAA File, sysFile and sysDir library must not be used as user libraries in SoMachine. These libraries are intended for internal purposes only, and therefore are not fully documented in SoMachine. Usage of the Function Blocks and functions located inside these libraries may provoke unintended consequences.
•	As part of SoMachine V4.1 SP1, two versions of the "CAA File" library are installed: V3.5.3.132 is dedicated for usage with LMC078 controller, V3.5.3.0 is dedicated for the other controllers. As for this library a placeholder is existing (and also not a FCL library), the recommended way is to add the library (via the Library Manager) to your device as placeholder. Thus, SoMachine will add the right library version to your device. (This is in sync with the procedure described in chapter "Adding Libraries to a SoMachine Project" of Online Help.)
•	Closing editors by clicking "X" is not possible after the first start of SoMachine after installation. You have to right click on the editor and select "Close Editor".
From the second start of SoMachine Editors can be closed as expected by clicking "X". 
•	The hardware catalog is not updated nor is the new device visible until you restart SoMachine after import of an eds file.	

2.4.3.	VM usage
•	When using a VM for SoMachine V4.1, please make sure to fulfill the minimal requirements especially for RAM, hard disk space and number of Cores inside the VM. Otherwise, errors can occur. An error that may occur, for example, is an out of memory exception when extracting a large project archive.

2.4.4.	DTM
•	After updating a project made in SoMachine 3.1 to SoMachine 4.1 SP1 the Advantys OTB DTM and the TM5-7 DTM may be unresponsive or unreliable. If this happens, copy and paste the same DTM. The new node will work fine. You can then remove the old one.
•	For Import/Export the explicit DTM Import (ContextMenu->Configuration->Import/Export DTM) should be used.
•	The tab "CANopen Configuration" is displayed when opening the DTM of the TM5 or TM7 CANopen Interface. This editor allows you to configure CANopen parameters. It is intended for use only by CANopen experts. The parameters are reset to default value after modification of the island (add module, delete module..).
•	When using Altivar 32 and Altivar 71 DTMs, the Command Panel should be deactivated before closing the DTM Editor. If the user decides to force the closing of the Editor while the Command Panel is still active, the DTM internal state will be unreliable. In this case, reopen the project.
•	After Uploading parameters on the Altivar DTMs, if the hardware configuration changes (e.g. Option Board), the changes might be incompatible with the current DTM configuration. In such a case, the user will receive an information message, "The configuration file is not compatible with this drive". Add a new 'Advanced Settings' device and execute the 'Upload Parameters' command to get the current Hardware Configuration
•	When Altivar 61 or 71 have an option card for  EtherNet/IP communication, then the DTM cannot be used in CANopen. The following Option boards are impacted:
•	VW3A3310  Ethernet Card
•	VW3A3316  Ethernet/IP Card
•	VW3A3320  Ethernet RSTP Card
•	When executing a function in CANopen make sure to be Logged to the PL
•	For the Lexium 32 DTMs, "File open" dialog from special folders in scope
•	Several Help button exists in dialog boxes but have no action, for the Lexium 32 DTMs
•	Oscilloscope: Lexium 32M: Selecting an empty Slot in the Channel select dialog may lead to 
unresponsive equipment either hardware or software.
•	Sporadic connection loss may occur due to incorrect timing behavior of USB to RS485 dongles

2.4.5.	IO-Scanner
•	Modbus TCP IOScanner may send some requests before the first application cycle, even if the function IOS_STOP() is called during the first application cycle. Take this into account for operating the application.
•	Lexium32 IO-Scanner slave may not get reconnected after a Lexium power cycle: If the LXM32MU45M2 FW VERSION 1.12.XX, and if you are using the Ethernet accessory VW3A3616 labeled “Made in Sweden”, the connection may not restart after power cycle. Use VW3A3616 labeled  V1.07 IE03 ( Made in China).

2.4.6.	Ethernet/IP
•	Ethernet IP Adapter implementation of M251MESE (Firmware version V4.0.4.x) differs from the implementation in M241 and M251MESC. In case of communication loss with the Ethernet/IP Scanner (The Scanner is powered off, or the cable is disconnected), the Inputs of M251 MESE adapter (Originator to Target) will fall back to 0. In the same situations, the Inputs of M241 and M251MESC adapters will keep their last state.
2.4.7.	TCP/UDP Library
•	The TCPUDPCommunication library uses system functions and resources which are not supported by each controller platform available in SoMachine. The table below lists all supported controllers
o	M251, M241*, M258, LMC058, LMC078.
* controller must be equipped with an Ethernet interface, can be either embedded Ethernet or from the TM4ES4 expansion module
2.4.8.	User rights

•	When applying user rights configuration on a target, the new configuration might not be taken in account for connections that are already open. In order to be sure the configuration is fully applied, you should close all connections to this target by either rebooting the target or disconnecting all cables (Ethernet and Serial) for at least 1 minute.
•	If you set Engineering Access to “Operate”, "Program" or "Administrate" for a specific user, it will also activate Data Access for this user.
•	Currently, it is not intended that the User Rights feature be used to protect the SoMachine project against malicious access, but rather to help prevent mistakes from trusted users. If you want to protect your entire project, use the project encryption option instead. If you want to protect only a part of your code inside the project, the best option is to put this code inside a compiled library.

2.4.9.	Restrictions regarding compatibility of projects created with SoMachine V3.1 or earlier

•	Firmware versions included in SoMachine V4 are not compatible with prior versions of SoMachine, like V3.1 for example. If you want to use a SoMachine V3.1 project, you must ensure that your runtime version of the controller corresponds to a SoMachine V3.1 firmware version. If this is not the case, either you downgrade your firmware to the correct version, or you upgrade your SoMachine V3.1 project to SoMachine V4. Please refer to the “SoMachine Compatibility and Migration” guide for more details.
•	Some critical hotfixes were provided to libraries in SoMachine 3.1. If you use a project from SoMachine 3.1 which use the library versions without the critical hotfix you will get a compiler error. In this case you can find the corrected version of the library in the Folder “C:\Program Files(x86)\Schneider Electric\SoMachine Software\4.1\LogicBuilder\Support”. Please install this library version using the Library Repository dialog inside LogicBuilder from the Tools menu. You need to restart SoMachine afterwards to apply this changes.
•	Some compatibility problems with old projects of SoMachine V1.1 still exist. Please update your projects to the SoMachine V3.1 before updating to SoMachine V4.1.
•	When loading a SoMachine V3.1 project in SoMachine V4.1 several update dialogs may appear. Please confirm all dialogs to update your project. If any errors occur, they can be viewed in LogicBuilder.
•	When updating a SoMachine V3.1 project in SoMachine V4.1 you may get compiler errors because the extension for libraries is missing. You need to add this extension to fix the compiler errors (e.g. GET_STATE -> CIA405.GET_STATE).
•	The new feature to map variables on single bits is only offered for devices that are created with version SoMachine V4 or later.
If a SoMachine project was updated from an older version, this feature is not available for the existing / updated devices. To make it available, you have to create a new device and delete the old one.
•	In SoMachine V3.1, it was possible to use internal variables implicitly created when adding a CANopen slave to access some information on the current state of the device. For example, MyOTB.nStatus or MyOTB.bSlaveAvailable. These internal structures are no longer supported in V4. Instead, use the GET_STATE function blocks of the CIA405 library to retrieve the state of your CANopen slaves.
•	While using the '3S CanOpenStack' library inside you project you might encounter the build error "C0035: Program name or function block instance expected instead of 'xxx'.", where 'xxx' is a POU inside your project (for example a POU named 'START' or 'STOP'). 
•	As the library '3S CanOpenStack' is of the category 'Intern" (i.e. not intended for direct usage), we recommend setting the checkbox "Only allow qualified access to all identifiers" in the "Properties" dialog of this library for overcoming those build errors. While updating a project from SoMachine V3.1 with HMISCU/XBTGC device and containing the HSC and PTO_PWM modules, the update leaves modules in error with red crosses. To fix it, you should update the device by right-clicking on the HMISCU/XBTGC node and select "Update Device..."
•	When updating an application from SoMachine V3.1, it may be that variables defined in a GVL of a library are not correctly shared in Symbol Configuration editor. In this case, a message will appear in the build message box: "The POU xxx is no longer available within your compiled application but it is still configured in the symbol configuration". To be able to share again this variable in the symbol configuration, you can open the symbol configuration editor inside the updated project in SoMachine V4.1, deselect the variable that cause(s) the problem(s), close symbol configuration editor, reopen it, build the application and select the variable again.
•	In SoMachine 3.1 a "Remote Connection" tool was available for connecting to controllers in remote subnets. In SoMachine V4.1 this can be performed via the "Controller Selection" dialog (by using the "Remote TCP" connection modes). Especially for connections via OPC, the "Diagnostics" tool may be used for establishing a remote brigde connection to a controller.  
•	When building a legacy application (from SoM V3.1 or earlier) with SoM V4.1 you might encounter "Internal Error in Statement" messages if you use direct addresses of the form "myvar AT %Mn : BOOL" in your variable declarations. You can skip this message by selecting "Ignore". However, build errors are generated for this usage. To overcome those, replace the address declaration, using the form "myvar AT %MXn.0 : BOOL".

2.4.10.	Compatibility
•	M251 MESE projects containing Modbus TCP IOScanner are converted to Industrial Ethernet Manager. A user is informed by a message that the namespaces of Libraries PLCopen, ATV and LXM have changed and have to be adapted manually. Refer to “SoMachine Compatibility and Migration – User Guide” in Online Help for more details.
•	M251 MESE Ethernet IP Adapter function must be defined on Ethernet#1 connector. Converting an application built with SoMachine V4.1 SP1 or older to V4.1 SP2 will lead to delete the Ethernet IP adapter previously configured.
•	Modbus Serial IOScanner: Read/Write (FUNC23) is no longer transformed automatically to Read (FUNC03) and Write (FUNC16) when the slave does not support the Read/Write function. The application needs to be modified to manually separate the Read/Write function into one Read and one Write.
•	While updating a legacy project file containing devices for which no new device description files are installed in the current SoMachine device repository, these devices will not be recognized by SoMachine.
In particular, this might be the case for (customer) devices imported from EDS files.
To avoid this, install these devices prior to updating your project.
Generally, refer to the chapter "Migrations Considerations" in the "SoMachine Compatibility and Migration User Guide".
•	When updating an application to SoMachine V4.1 SP2 the following may apply:
•	if choosing YES in the "Project Update" dialog and un-selecting "Update All libraries", this will lead to an update of placeholder libraries. 
•	if for a library parameters of a POU were renamed between versions, still the old parameters names will be used in the POU code. For using the new parameter names the command "Update Parameters" has to be executed manually on the corresponding POU call usage. 
•	In SoMachine 3.1 a "Remote Connection" tool was available for connecting to controllers in remote subnets. In SoMachine V4.1 this can be performed via the "Controller Selection" dialog (by using the "Remote TCP" connection modes). Especially for connections via OPC, the "Diagnostics" tool may be used for establishing a remote brigde connection to a controller.  

2.4.11.	Controller assistant
•	Controller assistant “Write on controller” functionality is not available for all M258/LMC058 firmware versions. “Write on controller” can be used only if both current PLC firmware and firmware to install are:
•	Either, at least v2.0.31.29 or v4.0.2.8
•	Or, v4.0.X.X older than v4.0.2.8
For all other cases, controller assistant will popup a message to notify you of the incompatibility. You must then use a USB key to perform the firmware update (the USB key can be generated using “Write to” functionality of controller assistant).

2.4.12.	OPC client
•	Variables mapped to %I selected in a SymbolConfiguration are not available automatically inside an OPC client. It is necessary to add the path to the variable manually, For example: 
M251.Application.IOCONFIG_GLOBALS_MAPPING.temperatureLabo

2.4.13.	Conversion of Twido and SoMachine-Basic Projects
•	Compatibility: The SoMachine Basic Converter can convert SoMachine Basic projects created with SoMachine Basic V1.4 and all previous versions. The conversion of a SoMachine Basic project created with a newer version is possible, but the conversion may lead to errors that need manual adaptation.
•	The power cycle behavior of the converted controller differs from the behavior of the original Twido or M221 controller. A Twido or M221 controller keeps the values of all variables after a power cycle. The converted controller initializes all variables to their initial value. If your application requires some or all variables to keep their value after a power cycle, you can define these variables as Remanent variables by using the RETAIN attribute.
•	In Twido and SoMachine-Basic a cold start / warm start can be triggered by the application program (by writing to the system bit %S0 / %S1). In both cases the controller restarts after executing the start procedure. In SoMachine the converted controller does not restart after the execution of the cold start / warm start procedure.
•	The functionality of pulse generators and high-speed counters in the converted controller differs from the functionality in a Twido or M221 controller. Depending on the usage of pulse generators and high-speed counters the converted application may have to be adapted.
•	The following features of SoMachine Basic V1.4 cannot be converted and an warning will be generated during conversion process to inform the user:
•	SMS function block SEND_RECV_SMS
•	Motion Task function block MC_MOTIONTASK_PTO
•	Some System Words and System Bits (the list of supported system words and bits is documented in the online help)
•	Additional limitations may exist depending on the supported features of the destination controller
•	Occasionally the conversion of a SoMachine-Basic project created by an older version of SoMachine-Basic fails with the error message "The project cannot be converted, because it is not valid and may contain programming errors". This problem can be fixed by opening the project with the latest version of SoMachine-Basic (V1.3 or later) and saving the project again.
•	Occasionally the conversion of a SoMachine-Basic project created by an older version of SoMachine-Basic reports the error "Project File does not contain IL instructions for LD network". In this case an incomplete description of an LD network in the SoMachine-Basic project file was encountered and the LD network could not be converted. The problem can be fixed through the following steps:
1) Check the error message in the message view to find the POU that contains the unconverted LD network.
2) Open the SoMachine-Basic project and switch the POU from LD to IL and then back to LD. Then save the project again.
The saved project now contains a complete description of the LD network and can be correctly converted.
2.4.14.	ATV-IMC
•	In the Devices tree location: Local --> Drive--> I/O Mapping, the column ‘Default Value’ is not taken into account for fallback mode, i.e., when Behaviour for outputs in Stop = ‘Set all outputs to default’.
•	To add an Option Board, use the right click button and then select "Plug Device".
2.4.15.	Lexium 32 position gear mode
•	The output InGear of the function block GearInPos_LXM32 is not implemented in the present version, and therefore should not be used. The Lexium32 is synchronized to the master encoder as long as the output Busy of the function block is TRUE.
2.4.16.	LMC058 / M258
•	When upgrading application from SoMachine V3.1 or SoMachine V4.0 to SoMachine V4.1, if the jerk configuration parameter was used together with sin² ramp velocity, then this jerk parameter is suppressed and is automatically set to 0. To use this jerk parameter for sin² ramp, use the jerk input of SoftMotion Function Block (like in MC_Stop, MC_MoveVelocity ...). Refer to “SoftMotion” documentation in the online help of SoMachine for further information about jerk and sin² ramp.
•	When a M258 with PCI slots configured is converted to another M258 or LMC058 reference with PCI slots, the result is incorrect when the PCI module is inserted in the second slot and the first slot is empty. After the conversion, the PCI module moves from the second to the first position. So when you download the application and go online, a red triangle appears in front of the module. To fix this issue, after the conversion you should move the modules to the converted position.
•	For M258 targets, accesses to recipe files (create, read, write and delete) should be performed in a dedicated low priority task in order to avoid impact on the cycle time of the application. No watchdog should be defined for this dedicated task.
•	When updating M258 firmware using USB key, LEDs of controller might be temporary switched off. In such a case user must not power off PLC until “USB Host” LED is back on and no more blinking. This applies to clone USB keys as well.
•	After updating M258 firmware with USB key, PLC might restart with no LEDs. In such a case, user should perform the FW update with same USB key again. During this second firmware update, LEDs can be off for a while, user should not power off PLC until “USB Host” LED is back on and no more blinking. This applies to clone USB keys as well.
•	It is not possible to directly install firmware v2.0.31.15 on M258 if the M258 current firmware is at least v2.0.31.29 or v4.0.2.8. User should first update the M258 firmware using v2.0.31.X (X between 16 and 27).
2.4.17.	M251
•	There is no verification that TM2 modules connected to Advantys OTB Distributed I/O modules match those configured in the IOscanner.  Therefore, it is possible to write data incorrectly in case of a configuration mismatch.
•	The FBs IOSCN_Start and IOSCN_Stop are synchronous calls. In some cases they can block the IEC calling task until the next repetitive rate fires. In the case that of all the repetitive rates are slow (for example, on the order of 500ms), the IEC calling task can stay locked for 500ms, and this could trigger a watchdog exception.
•	An Advantys OTB Distributed I/O module may not reconnect after a M251MESE power cycle. To remedy this issue, you should always power cycle the OTB after the power cycling the M251.
•	Ethernet_2 Post Configuration will not be applied if the IOScanner function is configured.
2.4.18.	M241 & M251
•	The NVL-GVL service in mode "Unpacked Variables" may not work as expected, and may generate a controller exception or otherwise make for degraded performance.
•	"Latched" inputs are not detected when they are used in a task other than the MAST task.
•	For M241 & M251 targets, accesses to recipe files (create, read, write and delete) should be performed in a dedicated low priority task in order to avoid impact on the cycle time of application. No watchdog should be defined for this dedicated task.
•	If Alarm output is used, avoid using the same output in the application. This conflict may not be detected at build time. 
2.4.19.	M221	
•	During a controller reset, when the controller first enters an EMPTY state, all outputs are set to zero for the first cycle of the controller.  If you set the default (fallback) value of an output to one in the configuration, it will not take effect until after this first cycle, the duration of which is dependent on your application (size, communications, etc.).  You may, given you intend a default (fallback) value of 1 for any or all outputs, take this into consideration.  Thoroughly test your application and ascertain whether a reset of the controller, followed by an EMPTY state and the setting of outputs to zero, would cause your machine or process to react in ways that would have adverse consequences.
•	Forced I/O are maintained in case of warm start and cleared in case of cold start
•	Some controller input LEDs are ON during a USB Powered Download
•	On overloaded networks (more than 300 frames per seconds received by the controller), the error led may not be ON to signal a duplicate IP address
•	When there is mismatch between physical configuration and SoMachine Basic configuration, the bit 13 of %SW118 is set to 0, indicating an "I/O expansion configuration error". In this case the expansion bus is not started. The bit in %SW120 corresponding to the modules which do not match are set to 1.
•	If there are more modules in the physical configuration than in SoMachine Basic, only the bit corresponding to the first module missing is set to 1.
•	When at least one module does not answer correctly to the M221 during runtime (meaning the configuration step succeeded) the corresponding bit in %SW120 is set to 1 and the bit 13 of the %SW118 is set to 0. Even if it is the same error information as for configuration mismatch, the behavior is different in that the expansion bus is still refreshed by the M221.
•	The INIT command may disconnect the Ethernet connection with SoMachine Basic.
•	If a defective USB cable is connected, after a power cycle, the controller may stay locked in boot phase. This is usually due to a short between pins 4 & 5. Replace the cable or at least disconnect the cable during a power cycle.
2.4.20.	LXM32 (EtherNet/IP and Modbus TCP) and Lexium ILA/ILE/ILS (EtherNet/IP)
The following list of PLCopen motion function blocks use library-specific acceleration and deceleration values for LXM32 (EtherNet/IP and Modbus TCP) and Lexium ILA/ILE/ILS (EtherNet/IP) implementations.  This means that pre-configured values for these parameters (for example, via the commissioning tool or the local HMI on the drive) are overwritten when one of the motion function blocks is executed.

The default  acceleration and deceleration values written by these motion function blocks are as follows:

The default values for acceleration are 600 [user-defined units]  for LXM32 and 600 [user defined units]  for Lexium ILA/ILE/ILS.   
The default values for deceleration are 600 [user-defined units]  for LXM32 and 750 [user defined units]  for Lexium ILA/ILE/ILS.   

If you require other acceleration and/or deceleration values, you must use the vendor specific function blocks to do so.  Use the vendor specific function blocks SetDriveRamp_LXM32 and SetDriveRamp_ILX in the GMC Independent Lexium library to define the deceleration and acceleration.  The function block has to be executed only once if a change of the ramp values is required. 

List of affected PLCopen motion function blocks:
•	MC_MoveAbsolute
•	MC_MoveRelative
•	MC_MoveAdditive
•	MC_MoveVelocity
•	MC_Jog
•	MC_Home
2.4.21.	ATV32 & LXM32.
•	To be able to use the web server of the Ethernet module VW3A3616 of the ATV32 or LXM32 drives with Java version 1.8, you need at least firmware version 1.11IE01 of the Ethernet module VW3A3616.
2.4.22.	LMC078
•	When a  USB memory key is inserted in the connector CN2 of the LMC078 controller and the controller is booting, the boot is unsuccessful. The controller will present the message "!ERR: SD-Card" in the display. To avoid this issue, please remove USB memory key before rebooting the controller.
•	When resetting the user rights on an LMC078 with the operation "reset origin", it is necessary to reboot the controller for the action to be affected. To avoid this issue, please reboot the controller after resetting the user rights to complete the operation.
•	The documented function FC_PrgResetAndStart is not available in this version of the LMC078.
•	The LMC078 only allows to configure its IP address mode in SoMachine on the ethernet connector object. To switch between DHCP, BOOTP and fixed IP address (default), please:
1.	 select the ethernet connector object inside SoMachine
2.	change the setting
3.	download the project to your controller
•	When converting a LMC058 project to LMC078, the ethernet connector can contain configuration data for the IP address in grayed out fields.

After the conversion those fields are not editable. The data shown in the fields has no effect. The IP address is configured using the process communication settings command in the controller selection tab on the LMC078 object. Only the IP mode (DHCP/BOOTP/fixed IP Address) is set in the on the ethernet connector.
Ignore the displayed values.
•	When LMC078s Ethernet connection is configured as DCHP it does not activate the gateway address it receives from the DHCP server. Instead it operates with the gateway address configured on the SD card. This does not affect communication between the controller and devices in the same subnet (e.g. on the same switch).

Workaround:
•	for devices in same subnet (e.g. PC attached to same switch): no action necessary
•	for communication with devices in other subnets (e.g. maintenance via remote PC): set gateway address via the process communication settings command in the controller selection tab on the LMC078 object.
•	By default the LMC 078 (via USB) is turned off by Gateway Management console.
•	When activating LMC 078 (via USB) the port specified by “Device name starts with:” is reserved for LMC078 communication. If other non SoMachine applications try to use the same USB Port it will lead to conflicts.
•	Downloading a project to the LMC078 via an indirect connection (e.g. SoMachine connection via usb other to another controller that in turn is connected via RS232 to an LMC078) might be unsuccessful. Use direct communication between your PC and the LMC078 to avoid this issue.
E.g. by attaching the LMC078 to an ethernet network your PC is connected to and selecting IP connection mode, connecting your PC directly via ethernet to the LMC078 or by using a USB cable between the LMC078 or your PC. 
•	Sercos phase up is unsuccessful if any unconfigured LXM32S are present on the Sercos network (ring/line). The Sercos master (LMC078) shows the diagnosis code 8506 "SERCOS Master comm. not possible" with the extended diagnosis "Err:0x00020021". The LXM32S does not support inactive participation in the Sercos network. To resolve the issue either:
1.	physically remove unconfigured LMX32S from the Sercos network by rewiring the Sercos cables
or
2.	configure all LXM32S connected to the Sercos network in your application so that the master actively communicates with them
•	LXM32S does not support ring break (continued operation when disconnecting one of the redundant cables in a Sercos ring during operation) if the Sercos cables don't respect the following connection order. The connection order to respect is: Master P1 - Drive 1 P1, Drive 1 P2 - Drive 2 P1, Drive 2 P2 - Drive 3 P1, .... Drive x P2 - Master P2. In case this order is reversed at any LXM32S, a ring break will result in a communication error. To avoid this issue connect Sercos cables always in the connection order specified above.
•	If you chose to declare variables as Persistent, the Read / Write of the those variables increase the cycle time of the controller.  Configure the minimum number of persistent variables required for your application to help avoid degradation of controller performance.
•	The switching of the Operation mode between the Velocity mode and the Position mode may lead to a small, rapid movement of the motor.
 WARNING	
UNINTENDED MACHINE OPERATION

Do not switch the Operation Mode from Velocity mode to Position mode with the drive in STANDSTILL.
Failure to follow these instructions can result in death, serious injury, or equipment damage.	

•	The bus cycle task of TM5 IOs on Sercos cannot be configured on the TM5 device.The only means to set the bus cycle task for TM5 IOs on sercos is via the PLC settings tab on the LMC078. The setting on the controller level is applied to all devices that don't specify a bus cycle task explicitly.

•	Though the probability is low, there is the possibility that, after power cycle, with only one of the single axis (LXM32S) powered on the Sercos bus, the servo drive can stay in Phase 0. To resolve this issue, you need to power on all the servo drives.
•	Though the probability is low, there is the possibility that the error B109 (communication error between the Sercos Module and drive) may occur in case of using all LXM32S functionalities with the trace function. To resolve this issue you, need to power off the servo drive.

2.4.23.	Energy Efficiency Libraries
•	ModbusEnergyEfficiencyToolbox library does not support Modbus IO scanner for HMISCUxA5 & HMISCUxB5. 
•	Modbus Manager with Baud rate 9600 may not work properly with HMISCUxA5 & HMISCUxB5. In this case, increase the baud rate to 19200 or 38400.

2.4.24.	Hoisting
•	Part of the delivery of two of the three Hoisting Templates, which are:
i.	Hoisting_Industrial Crane_CANopen_M241
ii.	Hoisting_Industrial Crane_CANopen_M241_Safety,
the project file for the safety controller is to be uploaded to the Preventa XPSMC controller.

The file is called: M241_Safety_XPSMC_V2.mcc.

To be able to load this project to the Preventa XPSMC controller, the corresponding Preventa software XPSMCWIN must be obtained. This software is not a standard part of SoMachine V4.1.  You can obtain the XPSMCWIN software from your local Schneider-Electric sales representative or your ADE.

2.4.25.	QUICK Key
•	QUICK KEY ref:TM2USBABDEV1
The Quick Key with a FW version ≤ V0.08 does not work with M218 and M238 controllers (firmware V4.0.1.xx) when there is no application already present in the controller.  

2.4.26.	Vijeo Designer
•	For remote download (VPN, NAT ...) of HMI targets, the connection needs first to be established using the Diagnostics tool
•	If the main CPU of an HMISCU controller processes invalid instructions (application corruption or invalid commands) or does not respond for 10 seconds, the Hardware Watchdog will be triggered. A software reset of the Vijeo Designer Runtime will be triggered. After the reset, no controller application will be loaded and the Vijeo Designer will be in a "Ready for Download" state. To recover an HMISCU controller in this state, the user must download a new valid application from Vijeo Designer via Ethernet, USB cable or USB memory device.
•	A second real-time clock chip in addition to the original was added to newer hardware revisions of the HMISCU controller in hardware revision “PV 02, RL 02, SV 2.0”. This hardware revision and later revisions must be used with SoMachine V3.1 with Vijeo Designer V6.1 SP3.1 or later versions (including SoMachine V4.0).
•	Multiple Download used to download an application to an HMI or HMI controller that has an older Vijeo Designer Runtime on it will not automatically update the Runtime
The user must manually upgrade Vijeo Designer Runtime by using Vijeo Designer Runtime Installer. This tool can be launched from the "Maintenace" button of SoMachine Central -> select "Download Firmware HMI" to launch.
•	After downloading the HMI Application and HMI controller Application via "Multiple Download", "COM Port Open Failed" system error message will appear on the HMI screen. Logging into the controller will show that the PLC Communication Library Modbus function block (WRITE_VAR, READ_VAR, WRITE_READ_VAR) is returning Oper Error #2. A reboot will bring the Modbus functionality back to normal.
•	When HMISCU is put into Offline Configuration, the PTO axis will be put into Dec. Fast Stop. However, the deceleration will be interrupted at 6 seconds and the PTO output will cease activity. For motor control that requires Dec. Fast Stop to be longer than 6 seconds, DO NOT put the HMISCU into Offline configuration.  In any case, you must ensure that there are other safety systems in place for this situation.

 WARNING	
UNINTENDED MACHINE OPERATION

•	Do not put the HMISCU into Offline Configuration during a PTO axis movement.
•	Be sure that the proper functional safety systems are installed and operating during operation.

Failure to follow these instructions can result in death, serious injury, or equipment damage.	

•	HMISCU using PLC Communication Library's Modbus Requests do not work at 9600 Baud or less. For HMISCU controllers, Modbus request function blocks from the PLC Communication Library require a specific Time between Frames based on the baud rate in order for communication at lower baud rates. This "Time between Frames" can be set in the Configuration Tab of the Modbus_Manager node panel.
Use the following formula to determine an appropriate Baud rate:
Time between Frames (rounded up to the nearest millisecond) = 35000 / Baud rate
•	When logged into an HMI Controller application that uses Modbus Manager on a COM port, a red triangle will indicate that the Modbus Manager is not functioning. The Status Tab of the Modbus Manager will show "No driver found". Nonetheless, Modbus communication will still be functional.
•	For HMI controllers, do not use the same Embedded Output byte or Input byte in multiple Tasks. This can cause high jitter for Tasks. The SoMachine Editor does not validate for this invalid circumstance on HMI Controllers.
•	The variables from the PLC_R structures from the PLC System Library cannot be shared via Symbol Configuration to the Vijeo Designer application of HMI targets (including HMI controllers).
•	Input configuration parameters can change when converting XBTGC to any controller. 
Please verify your input configuration parameters after converting XBTGC to any controller.
•	The SoMachine Log Viewer feature inside Vijeo Designer is not supported. Instead use for this purpose the Log tab of the controller view inside SoMachine.
•	 HMISCU and XBTGC download ceases operation if a runtime update is required during the download.
Please use RuntimeLoader (C:\Program Files\Schneider Electric\Vijeo-Frame\RuntimeLoader.exe) to update your HMISCU or XBTGC before downloading an application
•	On HMI Controllers, when downloading a new Controller application, the outputs may be driven to the configured Default Values for some time before they are turned to OFF.
The system designer must consider this and prevent unintended equipment operation due to these signals during the download phase.
•	For HMI Controllers, the surrounding area of the lamps in the ComboController_for_color ToolChest object may appear in pink on the HMI screen. Other objects using bitmap images with transparent background may also exhibit this symptom.
To solve this issue, you can ungroup the objects and choose Primitive object style for these lamps to avoid the pink color. You can also choose a different background color for the transparent color for any bitmap images used.
•	When a project using an HMISCU is updated from SoMachine V3.1 to SoMachine V4.1, the HSC and PTO_PWM nodes may display as red "X". This means that the devices are outdated. 
To solve this issue, right click on the nodes select "Update Device" and select the same device type.
•	When using Multiple Download to HMI Controllers, if the WRITE_VAR or READ_VAR function blocks are included in the Controller application, they may not operate correctly on startup after the download is completed.
The HMI may stop functioning, and SoMachine may lose connection with the device for 2 to 3 minutes.
For HMI Controllers, whenever the READ_VAR or WRITE_VAR function blocks are used, if the conditions above occur, reboot the HMI Controller once again or wait for the HMI to recover.
•	When installing Vijeo Designer Standalone on a PC that already has Vijeo Designer installed as part of Somachine, if the installation source drive (for example D:) of Vijeo Designer Standalone is not the same as the original installation source drive (for example E:) of SoMachine, the Vijeo Designer Standalone installer will not execute correctly.
There are 2 possible solutions to this issue:
1. Install Vijeo Designer Standalone from the same source drive as that which you installed SoMachine.
2. If solution #1 above is not possible, you need to perform the following operations:
     - manually uninstall the Vijeo Designer version installed by SoMachine (by going to the
 Windows Control Panel)
     - install Vijeo Designer Standalone
•	HMI targets using the Modbus TCP/IP Slave driver freeze (commands are not taken into account and comnunication fails) after a STOP command on the Modbus TCP IO-Scanner.
In this situation, the HMI target must be rebooted.
•	When using a symbol configuration inside LogicBuilder, do not use the setting "Include Comments in XML". Otherwise, Vijeo Designer will not operate properly and may cease to function entirely.
•	Instructions for Plugging and Unplugging two-piece Target Machines for the two-piece Magelis target machines, HMISCU (HMISAC and HMISBC) and HMISTU (HMISTU855 and HMISTU655, HMIS5T/HMIS65, HMIS5T/HMIS85):

 WARNING	
UNINTENDED MACHINE OPERATION

•	Do not attach or detach the front display module while the back module is connected to power.
•	Do not connect or disconnect the HMISURDPxx display module separation cable while the back module is connected to power.
•	Ensure the front module is securely attached before applying power to the back module.

Failure to follow these instructions can result in death, serious injury, or equipment damage.	

•	Do not share variables native to Function Blocks in the Symbol Configuration window. Their values will be displayed incorrectly on the HMI.

When sharing variables to HMI, the data for variables native to Function Blocks are incorrectly displayed on the HMI. Variables native to Function Blocks in a POU assigned to a Task are normally available to be used in Vijeo Designer when they are shared from Symbol Configuration. However, the PLC will not send the correct data of the variables to the HMI.

NOTICE	

INCORRECT DATA DISPLAYED

Do not directly share function block variables for HMI displays.

Failure to follow these instructions can result in equipment damage.	

Example:  The WRITE_READ_VAR function block from the PLCCommunication Library.

If a function block of type "WRITE_READ_VAR" named "MyBlock" were used in a POU in a Task:

MyBlock(
    Execute:= , 
    Abort:= , 
    Addr:= Address1, 
    Timeout:= 10, 
    ObjType:= 0, 
    FirstWriteObj:= 80, 
    WriteQuantity:= 10, 
    WriteBuffer:= ADR(WRITE_Buffer), 
    FirstReadObj:= 80, 
    ReadQuantity:= 10, 
    ReadBuffer:= ADR(READ_Buffer), 
    Done=> , 
    Busy=> , 
    Aborted=> , 
    Error=> , 
    CommError=> , 
    OperError=> );

and the Application.POU.MyBlock is shared in the Symbol Configuration:

MyBlock.Execute, MyBlock.Abort, MyBlock.Done, MyBlock.Busy, MyBlock.Aborted, MyBlock.Error, MyBlock.CommError, and MyBlock.OperError variables will be shareable to Vijeo Designer via Symbol Configuration and a user can assign them to Data Displays in Vijeo Designer.
The actual data that is shared in Vijeo Designer's Runtime from the PLC is incorrect and the HMI does not display the correct values.

•	To share variables native to Function Blocks in the Symbol Configuration window with an HMI an update to Vjieo Designer V6.2.SP3.1 HotFix1 or later is needed. Their values will be displayed incorrectly on the HMI when using an older Vijeo Designer version.
•	Do not share single(!) elements of a structured variable in the Symbol Configuration window, as their values will be displayed incorrecly on the HMI. In case you need to share an element of a structured variable, you should share all(!) elements of this structured variable.
•	To share single(!) elements of a structured variable in the Symbol Configuration window with an HMI use Vijeo Designer V6.2SP3.1Hotfix1 or later. Otherwise their values will be displayed incorrecly on the HMI.
•	Do not share references to a structured variable in the Symbol Configuration window, as their values will be displayed incorrecly on the HMI.
•	A certain number of pre-requisites are necessary for Intelligent Data Services (IDS) to function properly. These pre-requisites are available on the installation DVD, in the "IDS\ISSetupPrerequisites" subfolder.
•	In order to have the compatible versions of the pre-requisites and to avoid any future IDS functional issue, it is mandatory to install the pre-requisites from the DVD.SoMachine Basic
•	When updating M221 firmware with "Firmware Update" tool, ensure to be offline in SoMachine Basic (fixed in SoMachine Basic 1.4)
•	Avoid having more than 200 rungs in one POU: separate them between different POUs to increase performance and avoid unrecoverable errors in SoMachine Basic
•	The following online modifications will force you to download your application after disconnection: (fixed in SoMachine Basic 1.4)
•	Add/remove a line in Instruction List
•	When an output is reserved by an I/O function block (HSC reflex output, PLS or PWM):
Its value is not refreshed (program part and animation table)
A force action has no effect
•	In order to operate SoMachine Basic simulation together with Vijeo Designer simulation, you should start SoMachine Basic simulation first and then launch Vijeo Designer simulation. Vijeo Designer simulation execution is limited by time. So please re-launch it if it ceases to function.
•	When using an M221 controller with I/O cartridges, the values of the I/Os from the cartridges cannot be directly accessed by the HMI.
The solution to this issue is to write the values of the I/Os from the cartridges into PLC 
memory addresses so that they can be accessed by the HMI.

2.5.	Web visualization

2.5.1.	Scope
The goal of this chapter is to describe the limitations and restriction of the web visualization.

The CODESYS WebVisu is a client based on a HTLM5 and javascript which communicates with the web server integrated in controller and displays the visualization in any given visualization systems. 

It can be used if there is a WebVisu object inserted below the visualization manager, in the application. 

Then to access to the webvisu thanks to web browser, the following address should be entered in the web browser:

http://<IP_address of controller>:8080/<webvisu>.htm 

<webvisu>.htm is the HTM file defined in the Visualization Manager, as Visualization Entry page - Thereafter the visualization can be operated in the browser.

This document describes the limitation of the webvisu for the following components since version:

Component	Version	
SoMachine	V4.1	
M258/LMC058	V4.0.2.32	
M241/M251	V4.0.2.36	
LMC078	V1.51.10.4	

2.5.2.	System Requirements

2.5.2.1.	Web browser
Web visualization is supported on any browser that supports java script and HTML5 (Firefox, Chrome …)

2.5.2.2.	Controllers
Only M241, M251, M258, LMC058 and LMC078 controllers support this feature

2.5.3.	Best Practices

2.5.3.1.	General Usage
Webvisu feature should be used to monitor variables in a controller.
Webvisu should not be used to commission a machine.

2.5.3.2.	Data security 
In order to minimize the risk of data security breaches, consider the following technical and organizational measurements for the system running your applications: 

As far as possible avoid exposing PLCs and PLC networks to public networks and the Internet. For protection, use additional security layers like, for example, VPN for remote access, and install firewall mechanisms. Restrict access to authorized people. If available, please change default passwords at start-up and modify them frequently. Check regularly and frequently the effect of these measurements. 

If you nevertheless want to publish your Web Visualization, give it at least a simple password protection to prevent access to the functionality of your PLC over the Internet. This can be done by the general User Right configuration of the application.

2.5.3.3.	Web browser
•	On Windows PCs, some problems can occur with Internet Explorer and HTML-Canvas 5. Mozilla Firefox or Google Chrome operate normally with HTML-Canvas 5.
•	On Android systems, Chrome is the preferred browser.
•	Sometimes the web browser can have difficulties to display the visualization. Please flush the cache of your web browser in this case.
•	Web browser zoom factor should be set to 100%.

2.5.3.4.	Visualization
•	    Some scaling problems can appear in your browser. To fix this issue, you can use a rectangle and put the visualization objects inside this rectangle.
•	    Use less than 50 variables in a visualization page; otherwise it might have an impact on the application load and can provoke a watchdog timeout exception.
•	    If there are issues concerning the performance of the webvisu display, try to adjust the “size of memory for Visu” or the “size for Paint Buffer”, in the "extended settings" in the visualization manager configuration screen.
•	    If some photos are used in the visualization, please use photos that are compressed. Uncompressed photos, like bitmap photos, have a negative impact on the performance.
•	    When building visualization, you should avoid using the zooming feature.
	
2.5.3.5.	Programming
•	    A new task VISU_TASK is added automatically when using webvisu. Please make sure that your application is not overloaded with this new, low priority task. If after adding WebVisu, the PLC application encounters "Exceptions", you should adjust the Cycle time of the applicative tasks.
•	    The FreeWheeling tasks must not be used together with the WebVisu because freewheeling mode does not leave spare time for WebVisu to run.
•	    Adding the WebVisu service to the application will significantly increase the size of the application.
•	    The configured "Maximum number of visualization clients", Visualization Manager/Expert settings must not be over 3 

2.5.3.6.	Download of Application using FTP
•	    When downloading application and Webvisualization files to PLC using FTP, FTP transfer type must be set to binary.

2.5.3.7.	Controller
•	    In some situations during intensive processing while using WebVisu, SoMachine connection problems can be encountered. It is recommended to quit the browsing of WebVisu when you want to connect SoMachine to the controller. 

2.5.3.8.	Network
•	    The webvisu connection should be established through local Ethernet network or through reliable Wireless networks. Any connection through the Internet can provoke some difficulties to display the visualization in the web browser

2.6.	List of integrated components