Search

44 result(s) for FileType

• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.12 AddressSpaceFileType
  BrowseName AddressSpaceFileType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the FileType defined in OPC 10000-20 HasComponent Method ExportNamespace The method has no parameters. Optional Conformance ... file and then access the file with the Methods defined in the FileType . Servers might provide some vendor-specific mechanisms importing parts of an address space as subtype of this
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.36 UABinaryFileDataType
  base type for the UABinaryFileDataType Structure . If the file is provided through a FileType Object , the MimeType Property of the Object shall have the value application/opcua+uabinary. If the file
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.1 TrustListType
  TrustListType This type defines a FileType that can be used to access a TrustList . The CertificateManager uses this type to implement the Pull Model. Servers use this type when implementing ... encoded structure is not wrapped in an ExtensionObject . The Size Property inherited from FileType has no meaning for TrustList and returns the error code defined in OPC 10000-20 . When
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.2 Open
  Open The Open Method is inherited from FileType which is defined in OPC 10000-5 . The Open Method shall not support modes other than Read (0x01) and the Write + EraseExisting
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.4 Read
  Read The Read Method is inherited from FileType which is defined in OPC 10000-5 . If the Server is able to detect out of band changes to the TrustList before
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.5.1 ConfigurationFileType
  ConfigurationFileType This type defines a FileType that can be used to access the configuration associated with an Object . The file is a stream containing an instance of UABinaryFileDataType serialized using ... writing, the Client shall follow the following steps. Read the existing configuration with the FileType Read Method . Set the position to the beginning of the file with the FileType SetPosition
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.2 Configuration behaviours
  access to the complete PubSub configuration. Both read and write access are handled through FileType functionality. The related functionality is defined in 9.1.3.7 . Modifications of the PubSub configuration can happen ... through different mechanisms like FileType access or sequences of Method calls defined in other information models. The PubSub application should ensure that all mechanisms coordinate access to the configuration
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.2 PublishSubscribeType
  write access to the PubSub configuration through a PubSubConfigurationType with is a subtype of FileType . The read access is to the complete configuration. The write access allows add, modify
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.7.1 PubSubConfigurationType
  PubSubConfigurationType This ObjectType represents a FileType the can be used to access a PubSub configuration. The PubSubConfigurationType is formally defined in Table 238 . The PubSubConfigurationType file is a UA Binary ... NamespaceArray in the OPC UA Server for a Session with the Server . The FileType functionality is used instead of passing the PubSubConfiguration2DataType to read and write Methods to overcome potential
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.1 Overview
  client is reading the array while others are manipulating it. Therefore, the ObjectType FileType is defined representing a file with Methods to access the file. The life-cycle ... file stored on a hard disk and an instance of the FileType representing the file in an OPC UA AddressSpace can be independent. In addition to representing individual files this
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.3.1 FileDirectoryType
  Organizes Object <FileDirectoryName> FileDirectoryType OptionalPlaceholder Organizes Object <FileName> FileType OptionalPlaceholder HasComponent Method CreateDirectory Defined in 4.3.3 Mandatory HasComponent Method CreateFile Defined in 4.3.4 Mandatory HasComponent Method ... instance of this ObjectType . Instances of the ObjectType contain a list of FileType Objects representing the files in the file directory represented by the instance of this ObjectType
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.3.4 CreateFile
  CreateFile CreateFile is used to create a new FileType Object organized by this Object . The created file can be written using the Write Method of the FileType . Signature CreateFile ... fileNodeId and the fileHandle can be used to access the new file through the FileType Object representing the new file. If requestFileOpen is set to False, the returned value shall
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.4.1 TemporaryFileTransferType
  formally defined in Table 13 . The Methods GenerateFileForRead or GenerateFileForWrite generate a temporary FileType Object that is not browsable in the AddressSpace and can only be accessed with the NodeId ... Method calls to read or write the file content from the virtual temporary FileType Object . If the Client exceeds the timeout between Method calls, the Server may close the file
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.4.2 File transfer sequences
  Client reads the file content by calling the Method Read defined by the FileType until the whole file is transferred from the Server to the Client . The transaction is completed ... calling the Method Close defined by the FileType . The sequence of Method calls necessary to execute a write file transfer transaction is illustrated in Figure 3 . Figure 3 - Write file
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.4.3 GenerateFileForRead
  start the read file transaction. A successful call of this Method creates a temporary FileType Object with the file content and returns the NodeId of this Object and the file ... UserAccessDenied See OPC 10000-4 for a general description. Bad_NotReadable The temporary FileType Object is writeonly and can not be generated for read. Table 14 specifies the AddressSpace representation
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.4.4 GenerateFileForWrite
  start the write file transaction. A successful call of this Method creates a temporary FileType Object and returns the NodeId of this Object and the file handle to access ... UserAccessDenied See OPC 10000-4 for a general description. Bad_NotWritable The temporary FileType Object is readonly and can not be generated for wirting. Table 15 specifies the AddressSpace representation
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.3.1 ConnectionManagerConfigurationType definition
  F.3.1 ConnectionManagerConfigurationType definition This ObjectType represents a FileType that can be used to maintain ConnectionConfigurationSets . The content of this File shall correspond to F.2 . Reading the File allows the retrieval ... Value BrowseName 4:ConnectionManagerConfigurationType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of FileType defined in OPC 10000-20 . HasComponent Method 4:CloseAndUpdate Defined in F.3.2 . Mandatory Conformance Units
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.5.6 SupportInfo Interface
  ByteString 0:BaseDataVariableType MP 1:DocumentationFiles 0:HasComponent Object 1:<DocumentFileId> 0:FileType MP 1:ProtocolSupport 0:HasComponent Variable 1:<ProtocolSupportIdentifier> 0:ByteString 0:BaseDataVariableType ... cases will represent a product manual. They can be exposed as Variables or as FileType instances. Files are useful in particular for large documents. Documents as Variables are represented
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.3.5 WriteBlockSize
  client shall write the Software Package in chunks of this size to the FileType object (the last Block can be smaller
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.4.4 WriteTimeout
  Client about the maximum duration of the call to the Write Method of FileType (maximum time the write of a block of data can take). If the write operation takes
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.6.3 GetUpdateBehavior Method
  files. The files are identified by the NodeId of their FileType instance in the FileSystem . Signature GetUpdateBehavior( [in] 0:NodeId[] NodeIds, [out] UpdateBehavior UpdateBehavior); Table 86 - GetUpdateBehavior Method Arguments Argument
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.9.5 InstallFiles Method
  more files. The files are identified by the NodeId of their FileType instance in the FileSystem . If the installation succeeds but the software cannot run properly this should
• OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-95
  7.2 Test Specification Information
  Specification Information For example, the subtype of test specification might have an Object of FileType (defined in OPC 10000-5 ) that indicates a file for the document that describes
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  6.3.10.1 Definition
  WoTAssetFileType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the 0: FileType defined in OPC 10000-5 . 0:HasComponent Method CloseAndUpdate Defined in 6.3.10.2 Mandatory Conformance Units
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  6.2.3.2 Object Images
  deliver the expected results. The Images Object when available shall contain the list of FileType Objects (see Table 10 ) with the images taken by the OCR reader. The MIME type ... image is provided through the MimeType Property of the FileType
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  6.3.3.2 Object Images
  deliver the expected results. The Images Object when available shall contain the list of FileType Objects (see Table 12 ) with the images taken by the optical reader. The MIME type ... image is provided through the MimeType Property of the FileType
• OPC-30020 – MDIS OPC UA Companion Specification
  6.8.3 MDISValveObjectType Definition
  HasProperty Variable CloseTimeDuration 0:Duration 0:PropertyType O, RO HasSignature Object <ValveSignature> FileType OP ConformanceUnits MDIS Valve Base The following items describe status information from the valve: SignatureRequestStatus ... Move commands]. <ValveSignature> - The reference shall point to an instance of FileType , where the file contains valve signature information. The name of this object is project or vendor
• OPC-30020 – MDIS OPC UA Companion Specification
  9.3 HasSignature ReferenceType
  SourceNode is deleted. The TargetNode of this ReferenceType shall be an instance of FileType . The FileType instance shall contain valve signature information. The SourceNode shall be an instance of MDISValveObjectType
• OPC-30020 – MDIS OPC UA Companion Specification
  14.2.2 Server
  version information for the MDIS Server Server MDIS Information Signatures Supports providing Signatures as FileType Objects Server MDIS Information Signature Validation Supports the JSON schema for the Signature file objects
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  7.6.2 FdtDocumentFile
  Node Class BrowseName DataType TypeDefinition Other Subtype of FdtDocumentType 0:HasComponent Object File 0:FileType M The FdtDocumentFile is a concrete type and can be used directly. The document ... retrieved from the server by using the methods related to the object of type FileType
• OPC-30260 – OPC UA for OPEN-SCS - Serialization Object Model: OPEN-SCS
  6.3.2.1 EPCISStream Object
  start the write file transaction. A successful call of this Method creates a temporary FileType Object and returns the NodeId of this Object and the file handle to access ... Object. (From OPC 10000-5 ). The returned FileType object is not browsable in the AddressSpace and can only be accessed with the NodeId and FileHandle returned by the method
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  5.1 General rules for the mapping of the AAS metamodel to the OPC UA information model
  SubmodelElements : Specific for the Blob SubmodelElement type (AASBlobType) the predefined OPC UA type definition FileType is used for the value. References of type FileType are components of the ObjectType ... File". The mime type is part of the OPC UA FileType and therefore not added. In contrast to the OPC UA FileType , the mime type is mandatory
• OPC-40001-101 – OPC UA for Machinery - Part 101: Result Transfer
  7.2.2 GenerateFileForRead
  start the read file transaction. A successful call of this Method creates a temporary FileType Object with the file content and returns the NodeId of this Object and the file
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  7.16.2 LoadByNodeId Method
  Table 71 - LoadByNodeId Method Arguments Argument Description Id ExpandedNodeId pointing to an instance of FileType representing a task control program or module Status 0 - OK - Everything
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  7.4.2.1 GenerateFileForRead
  start the read file transaction. A successful call of this method creates a temporary FileType Object with the file content and returns the NodeId of this Object and the file
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  7.4.2.2 GenerateFileForWrite
  start the write file transaction. A successful call of this method creates a temporary FileType Object with the file content and returns the NodeId of this Object and the file
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  7.5.1 Overview
  Address Space (see Section B.1.3.3 ) using the Recipes folder of this type, the FileType object component of the RecipeType objects in this folder can also be used directly
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  7.6.2.1 GenerateFileForRead
  start the read file transaction. A successful call of this method creates a temporary FileType Object with the file content and returns the NodeId of this Object and the file
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  7.6.2.2 GenerateFileForWrite
  start the write file transaction. A successful call of this method creates a temporary FileType Object with the file content and returns the NodeId of this Object and the file
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  7.7.1 Overview
  Variable LastModified UtcTime PropertyType Mandatory HasProperty Variable LinkedProducts ProductIdDataType [] PropertyType Optional HasComponent Object Handle -- FileType Optional HasComponent Method LinkProduct -- -- Optional HasComponent Method UnlinkProduct -- -- Optional HasComponent Method Prepare -- -- Mandatory HasComponent Method ... LinkedProducts Array of ProductIds which this recipe is linked to. May be empty. Handle FileType object for handling transfer of recipe data between client and server. The data is treated
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  7.7.2.1 Overview
  RecipeType object as well as on he RecipeManagement object. For data transfer, the FileType object contained in the RecipeType object can be used directly. Therefore, there is no need
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  7.7.2.6 Recipe transfer
  There are no dedicated transfer methods on the RecipeType because it already contains a FileType object representing the content of the actual recipe in the vision system. Thus, transfer ... carried out using the standard Open , Read , Write , Close methods of the FileType object
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  7.12.2.1 GenerateFileForRead
  start the read file transaction. A successful call of this method creates a temporary FileType Object with the file content and returns the NodeId of this Object and the file
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  B.1.7.3 Address Space-based recipe management
  recipe entry and uses the returned NodeId. It uses Open method of the FileType component of the detected Recipe object to open the pertaining file object for reading or writing