Media driver 4.6.0.0 download4/5/2024 ![]() SMC_MoveContinuousAbsolute, SMC_MoveContinuousRelative: Position jump when used in combination with MC_MoveSuperImposed SM3_Drive_ETC_SoE_Standard: errors of IDNRead/Write commands are not properly propagated and logged SMC_Interpolator: Internal error when computing the quadratic velocity profile Trigger: A trigger with an error that is projected to a blending loses the error condition Triggers with errors get enabled after a continue MC_SetPosition: documentation contains typo and is unclear SMC_GetCamSlaveSetPosition: not all errors are reported Misleading documentation for MC_ReadAxisError and TRIGGER_REF SMC_MoveContinuousAbsolute/Relative: Unexpected reversal when restarting the FB MC_MoveSuperimposed: Restarting the FB multiple times while it is Busy leads to a wrong Distance SMC_MoveContinuousAbsolute, SMC_MoveContinuousRelative: Possible jump in fSetPosition after homing SM3_Drive_ETC: Multiple device descriptions have the wrong parameter number for diActTorque FREE_ENCODER_REF: there is no input to pass the information that the position in increments is valid SMC_CamRegister: Documentation is unclear AXIS_REF_SM3: wrong parameter number for fSetTorque in documentation (1153 instead of 1160) MC_CamTableSelect: The checks for non-equidistant point tables do not use the correct offset and scale ![]() SMC_CP_TRAJECTORY_NOT_SMOOTH while jogging Tracking: Rotary axis jumps into a different period after MC_GroupContinue SM3_Depictor: error when using SMC_R_Depictor_Gantr圓 with SMC_R_Depictor_Wrist2 Multi axis slave: Invalid mapping when deleting the address of an object from the second or higher axes and activating automatic mapping afterwards SMC_MoveContinuousAbsolute/Relative: AdaptEndVelToAvoidOvershoot does not work correctly with trapezoidal velocity profile By replugging the CODESYS Key, the license can be used on any other controller. ![]() Alternatively, the license can be stored on a CODESYS Key (USB dongle). Licenses are activated on a software-based license container (soft container), which is permanently connected to the controller. Single device license: The license can be used on the target device/PLC on which the CODESYS runtime system is installed. Compatibility can be checked with the test project SML_Compatibilit圜heck_DS402.project SoftMotion Light works with CiA 402 compatible drives with CANopen or EtherCAT. SoftMotion CNC+Robotics requires CODESYS SoftMotion as a basis license. Real-time capable operating system platformsĬPU platforms with available FPU (Floating Point Unit)ĭevices with integrated fieldbus (EtherCAT, CAN/CANopen, or Sercos) CODESYS Development System V3.5.17.0 or higherĬODESYS Control Version 3.5.14.0 or higher
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |