Codesys Compatible Plc

[Athina Dollison]

cansomeone tell me where I can find a Codesys 3.5 list of supported devices? In fact I think about programming a Schneider Modicon M241. Due to a few problems with SoMachine (or EcoStruxure Machine Expert) I am searching for an alternative. I am wondering if its possible to configure TM3/TM4 modules with "standard" codesys and if its possible to use the SoMachine Protocol and libraries?

Several million CODESYS-compatible devices and approximately 1,000 different device types from over 500 manufacturers make CODESYS the leading manufacturer-independent IEC 61131-3 automation suite. The following table lists a selection of companies that offer CODESYS-compatible devices. It also provides an overview of which CODESYS products and functionalities the named manufacturers offer on their devices. Several million CODESYS-compatible devices and approximately 1,000 different device types from over 500 manufacturers make CODESYS the leading manufacturer-independent IEC 61131-3 automation suite. The following table lists a selection of companies that use CODESYS-compatible devices. It also provides an overview of which CODESYS products and functionalities the named manufacturers use on their devices.

The CODESYS Group is the manufacturer of CODESYS, the leading hardware-independent IEC 61131-3 automation software for developing and engineering controller applications.

CODESYS is a registered trademark.

CODESYS SoftMotion is an additional option for CODESYS compatible SoftPLC systems. CODESYS SoftMotion extends the functional scope of these systems from a purely logical controller to a motion controller, optionally also with CNC and robotics support.

The CODESYS Depictor allows creating and displaying 3D models and linking their geometrical relations (i.e. axis angles) to CODESYS applications. It is possible to display and animate machine parts (e.g. robots) or entire production lines in CODESYS.

Separation of application development from drive configuration. The drives in the device tree are accessed symbolically (by name) from the application. Changes in the drive configuration are possible without changing the application.

A note on SoftMotion Light: In contrast to SoftMotion and SoftMotion CNC+Robotics, the calculation of the axis movements is not done within the controller. With SoftMotion Light movements of the drive are just commanded and supervised (status) by the PLC and executed by the drive. The trajectory calculation is done in the drive.

Licenses are activated on a software-based license container (soft container), which is permanently connected to the controller. Alternatively, the license can be stored on a CODESYS Key (USB dongle). By replugging the CODESYS Key, the license can be used on any other controller.

To submit such a technical support request after purchase, a CODESYS Store account is required. After logging in, please use the "My Support Authorizations" list in your account or use the "My Question" contact form. After you have described and submitted your problem, the message will be forwarded to our technical support. They will contact you immediately to determine the next steps.

For general error messages or pre-sales inquiries, please also use the "My Question" contact form and select the appropriate department. This type of request can be used without logging in. A list of alternative support options can be found in the support section of the CODESYS Group website.

This product includes a free addition to an otherwise paid support entitlement of one hour of support. The redemption must be made within from the date of purchase. After this time, the support entitlement expires.

For general error messages or pre-sales inquiries, please use the "My Question" contact form directly, which can also be used without logging in. A list of alternative support resources can be found in the support section of the CODESYS Group website.

CODESYS SoftMotion 4.16.0.0 introduces override functionality for single axis function blocks in the form of the function block MC_SetOverride. In addition, there are new examples for interrupt/continue and override and numerous small improvements and bug fixes.

CODESYS SoftMotion 4.15.0.0 adds support for trigger points on the path to Robotics, similar to h-functions in our CNC product. Trigger points can be created for movements using a relative position, an absolute distance, or the intersection with a plane. Within a configurable forecast-duration, the trigger can be queried in advance. The precise remaining duration until the trigger is reached is reported.

The dJerkMax input of SMC_Interpolator can now be changed while the interpolator is running. The value will become active - at the start of the interpolator - or once a standstill has been reached (between two G-code commands, due to a stop or caused by a override value of 0),

Setting the maximum brake duration with SMC_TuneCPKernel has been deprecated. The limitation to a maximum brake duration has been removed from the robotics trajectory planning. As a result, movements with a brake duration of more than 1 second can now be commanded without any tuning.

As the Id of the Staubli uniVAL device descriptions has been changed, an update to the newest version is not automatically proposed for existing projects. Please update the uniVAL devices in the device tree to the new Id and version. (The device dialog will show both the old device in version 4.12.0.0 and the new device in version 4.13.0.0 with the same name, as the Ids are different.)

CODESYS SoftMotion 4.12.0.0 brings support for modulo axes to robotics and improved support for continuing after a MC_GroupStop/MC_GroupHalt, as well as new example projects for CNC (use of additional axes and use of tool length correction).

The default values of the inputs VelFactor, AccFactor, and JerkFactor of SMC_GroupJog2 have been changed from 1 to 0. Applications that are using SMC_GroupJog2 and did not change the default of these inputs need to be adapted. The reason for the change is that certain jogging movements may be very fast when all factors are 1. For example when jogging in the ACS, the full global axis limtis may be used for the jogging movements.

In previous versions, the non-cartesian elements were inserted into the queue after the correction arc. However, the position of the non-cartesian elements was set to the start position of the arc. This was a bug and could lead to jumps if no subsequent path processing FB corrected the error (set the position of the non-cartesian elements to the end postion of the arc).

Important: when upgrading to 4.12.0.0, make sure all SoftMotion drives have suitable software limits set before moving the robot. Existing motion programs must be tested again, preferably with reduced velocity.

For authors of kinematic function blocks, the handling of axis limits has been simplified. The interface ISMKinematicAxisSettings no longer needs to be implemented, except for the rare cases where the axis limits are needed for the kinematic transformation. In the method GetAxisProperties, which is still required if the kinematics contains rotary joints, no limits should be returned, except for the rare case that the rotary joint should be limited to a specific range. (Note that such a limit will make it impossible to connect a modulo axis to the joint.)

SoftMotion 4.11.0.0 brings improved tracking of conveyor belts and rotary tables for Robotics, several new and improved functions for single axes, new drivers for servo drives as well es many bug fixes.

The position and velocity filter of the logical axis has been reworked and improved. For the same settings, it should produce better results. In particular, the fActVelocity now better matches the fActPosition and noise on fActPosition is reduced effectively. For existing applications that use the logical axis to filter e.g. encoder values, please check your filtered signals using the trace to make sure you get the desired behavior with the improved filters.

The input MovementType of MC_MoveDirectAbsolute and MC_MoveDirectRelative has been deprecated. It will be removed in a future version. The movement type SMC_PTP_MOVEMENT_TYPE.Fast is no longer supported. Only the movement type SMC_PTP_MOVEMENT_TYPE.PTP_PI is supported.

The function block SMC_GroupJog has been deprecated and is superseded by SMC_GroupJog2. It is strongly recommended to use SMC_GroupJog2 for new projects and to change existing applications from SMC_GroupJog to SMC_GroupJog2.

Robotics: The blending between movements has been changed. The same shape of blending is now applied, no matter what kind of movement (tracking or static, orientation mode axis or great circle). This means that the path of the TCP may (slightly) change during blending compared to previous versions of SoftMotion. Please test your application carefully when updating to this version.

3a8082e126