VUM_EditType (ENUM) ¶ TYPE VUM_EditType : InOut: Name Initial VUM_NONE 0 VUM_ADD 1 VUM_INSERT 2 VUM_MODIFY 3 VUM_REMOVE 4 VUM_CHECKPASSWORD 5 VUM_CHANGEPASSWORD 6 VUM_CHECKPASSWORD_AND_GROUPID 7
VUM_ReturnValues (ENUM) ¶ TYPE VUM_ReturnValues : InOut: Name Initial Comment ERR_OK 16#0 Standard return values ERR_FAILED 16#1 The operation failed ERR_PARAMETER 16#2 Wrong parameter ERR_VUM_FILE_NOT_FOUND 16#5000 Range for VisuUserMan Errors 16#5000 until 16#50FF ERR_VUM_TEMP_FILE_CANNOT_BE_OPENED 16#5001 The user management temp file cannot be opened ERR_VUM_FILE_READ_FAILED 16#5002 The user management file cannot be read ERR_VUM_FILE_WRITE_FAILED 16#5003 The user management file cannot be written ERR_VUM_INVALID_FILE_CONTENT 16#5004 The user management file has a invalid content ERR_VUM_USERNAME_ALREADY_EXIST 16#5005 The user name must be unique ERR_VUM_WRONG_PASSWORD 16#5006 The password is wrong ERR_VUM_UNEQUAL_PASSWORD 16#5007 The password isn’t equal to the acknowledge password ERR_VUM_NEW_USER_DB_CANNOT_BE_STORED 16#5008 The new user db file cannot be stored ERR_VUM_ONLY_VISIBLE_USERS_CAN_BE_REMOVED 16#5009 Only visible users can be removed ERR_VUM_EMPTY_PASSWORD_NOT_ALLOWED 16#500A An empty password is not allowed ERR_VUM_ANOTHER_CLIENT_EDITS_UM 16#500B Only one client can edit user management entries ERR_VUM_SYSFILE_ERROR 16#500C Error during working with SysFile ERR_VUM_SETNEWUSERDB_FAILED 16#500D Set new user database failed ERR_VUM_PROXY_IS_NOT_IN_IDLE_MODE 16#500E Proxy is not in idle mode ERR_VUM_DATASERVER_ERROR 16#500F DataServer ProcessDataServerRequest error ERR_VUM_DATASERVER_ERROR_USERS 16#5010 The user list cannot be read from the remote system ERR_VUM_MAX_GROUP_LIMIT 16#5011 The maximum number of possible groups is exceeded ERR_VUM_USER_DOES_NOT_EXIST 16#5012 The user does not exist ERR_VUM_USER_IS_INACTIVE 16#5013 The user is inactive ERR_VUM_NO_LOGIN_PROVIDER_AVAILABLE 16#5014 The login dialog cannot be opened because the maximum number of login dialogs is reached ERR_VUM_NO_CLIENT_MEMORY 16#5015 No client memory ERR_VUM_NO_USER_LOGGED_IN 16#5016 No user logged in ERR_VUM_NO_VALID_USERGROUP_SET 16#5017 No valid user group set ERR_VUM_NO_RIGHT_TO_CHANGE_USERS 16#5018 No right to change users ERR_VUM_NO_USER_MANAGEMENT 16#5019 No user management ERR_VUM_USER_NOT_IN_USER_GROUP 16#501A The user does not belong to the user group
File and Project Information ¶ Scope Name Type Content FileHeader creationDateTime date 13.12.2023, 11:15:40 companyName string 3S-Smart Software Solutions GmbH libraryFile Visu_Itfs.library primaryProject True productName CODESYS productProfile CODESYS V3.5 SP16 Patch 3 contentFile Visu_Itfs.clean.json version version 2.0.0.0 ProjectInformation IsInterfaceLibrary bool True Released True LastModificationDateTime date 13.12.2023, 11:15:39 LibraryCategories library-category-list Intern|Visu Author string CODESYS Development GmbH Company System CompiledLibraryCompatibilityVersion CODESYS V3.5 SP15 DefaultNamespace Visu_Interfaces Description See: Description Project Visu_Itfs Title Visu Interfaces Version version 4.5.0.0
Library Reference ¶ This is a dictionary of all referenced libraries and their name spaces.
3S CANopenSafety Library Documentation ¶ Company 3S - Smart Software Solutions GmbH Title 3S CANopenSafety Version 3.5.14.0 Categories Intern|CANbus; Docs|Fieldbus|CAN Namespace _3SCOSS Author 3S - Smart Software Solutions GmbH Placeholder 3S CANopenSafety Description 1 ¶ CANopenSafety stack provided by 3S Smart Software Solutions GmbH. The stack uses the the unsecure CANopenStack as grey communication channel. Contents: ¶ _3SCANopenSafety BufferSizes (ParamList) Function Blocks Indices and tables ¶ 1 Based on _3SCANopenSafety.library, last modified 11.12.2018, 09:18:30. LibDoc 4.4.0.0-b.27 The content file _3SCANopenSafety.clean.json was generated with CODESYS V3.5 SP14 on 11.12.2018, 09:18:32.
_3SCANopenSafety ¶ BufferSizes (ParamList) Function Blocks CANRemoteDeviceSafe (FunctionBlock) Cyclic-Methods-state-independent Initialization State-Machine State Transitions States CheckConfiguration CheckConfiguration and Stopped Operational CANopenManagerSIL2 (FunctionBlock)
BufferSizes (PARAMS) ¶ Library parameters for Tx and RxSRDO buffer sizes. High Limit defines the highest array index. Values will be set by the configurator. InOut: Scope Name Type Initial Comment Constant gc_TXSRDOBUFFER_HIGH_LIMIT BYTE 63 maximal number of TxSRDOs = gc_TXSRDOBUFFER_HIGH_LIMIT + 1 gc_RXSRDOBUFFER_HIGH_LIMIT BYTE 63 maximal number of RxSRDOs = gc_RXSRDOBUFFER_HIGH_LIMIT + 1
Function Blocks ¶ CANRemoteDeviceSafe (FunctionBlock) Cyclic-Methods-state-independent Initialization State-Machine State Transitions States CheckConfiguration CheckConfiguration and Stopped Operational CANopenManagerSIL2 (FunctionBlock)
CANRemoteDeviceSafe (FB) ¶ FUNCTION_BLOCK CANRemoteDeviceSafe This function block implements the logic of a CANopen Safety Remote Device. All instances are managed by the CANopenManagerSIL2 in a simple chained list and called on StartBusCycle. The function block gets its SRDO config in SetupSDROs and has its own pointer to the Safety Exchange. Function block can be enabled/disabled by S_xEnable. When S_xEnable gets TRUE the function block checks every bus cycle all conditions for safe communication: Unsafe stack is in OPERATIONAL state CRCs read back from device are correct Consistency of SRDO configuration data If a configuration error is detected (e.g. CRC mismatch) S_eError changes from NO_ERROR to a corresponding error code. If every condition is fulfilled the function block tries starting safe communication. S_xActive gets TRUE if all SRDOs are sent/received at least one time without any error. When communication error occurs (SCT/SRVT timeout, data mismatch, …), all SRDO communication is stopped: S_xActive = FALSE, S_eError <> NO_ERROR Errors can be acknowledged by a rising edge of S_xErrorAck. Safe communication will be continued. InOut: Scope Name Type Initial Comment Input S_xEnable BOOL TRUE TRUE: SRDO communication enabled; FALSE: SRDO communication stopped S_xErrorAck BOOL FALSE Pending error (S_eError <> NO_ERROR) will be acknowledged on rising edge. Output S_xActive BOOL FALSE TRUE: safe communication active; FALSE: safe communication inactive (in case of error or S_xEnable = FALSE) S_eError CST.ERROR CST.ERROR.NO_ERROR pending error Structure: Cyclic-Methods-state-independent Initialization State-Machine State Transitions States CheckConfiguration CheckConfiguration and Stopped Operational
Cyclic Methods (state independent) ¶ Methods called every cycle independent of state.
