specs/models/M_MDTS
Machine Data Source
Description, address and credentials for connecting to the data source so that data from the physical machine can be consumed by Tulip. This is used for defining a Machine in Tulip. The data source is created and/or managed by the customer or a 3rd Party, in a networked location accessible by a Tulip Connector Host. A Data Source can be deleted and can also be restored. There are 2 types of Machine data source :
- OPC UA - This is used for connecting to machines that transmit data over the OPC UA protocol
- Tulip API - This is a default machine data source which comes pre-configured in every Tulip instance. This is used for sending events to Tulip over Tulip's Machine API.
- MQTT - When
mqttMachineDataSourcefeaure flag is enabled, MQTT data sources can be connected to.
Fields - OPC-Ua
| Name | Description |
|---|---|
| Name | User defined name for the Data Source |
| Description | User defined text describing the Data Source |
| Running On | The Connector Host used to broker the data between the data source and Tulip |
| Type | The protocol that you are connecting to, MQTT or OPC-Ua |
| Agent URL | IP address or the host name for the data source. |
| Security Mode | Security mode required by the OPC UA server in order to encrypt the OPC UA traffic |
| Authentication Method | Option to choose a specific authentication method as required by the OPC UA server |
| Username | Username required by the data source to authenticate in case authentication method is User Name |
| Password | Password required by the data source to authenticate in case authentication method is User Name |
| Private Key & Certificate | Option that allows user to upload private key & certificate in order to authenticate using X509 |
| Image | User defined image to represent the Data Source |
| Deactivation Status | A boolean that indicates whether the machine is active or deactivated |
Fields - MQTT
| Name | Description |
|---|---|
| Name | User defined name for the Data Source |
| Description | User defined text describing the Data Source |
| Running On | The Connector Host used to broker the data between the data source and Tulip |
| Type | The protocol that you are connecting to, MQTT or OPC-Ua |
| Version | The MQTT version to be connected to |
| Host | IP address or the host name for the data source. |
| Poer | The port your connection will leverage for communication |
| Authentication Method | Option to choose a specific authentication method as required by the OPC UA server |
| Protocol | MQTT or MQTTS (MQTT over TLS) |
| Path | An optional path to connect to your broker |
| ClientID | The client ID that will connect to your broker, if Auto-generate is selected, a random client id will be used on connection |
| Path | An optional path to connect to your broker |
| Username and Password | An optional field where you can provide a username and password to be used for authentication |
| Keep Alive | An optional field that defines how long the client will wait before proving a heartbeat to the central broker |
| if MQTTS - Private Key | A private key is a cryptographic key that is kept secret and used to verify the identity of a client during the secure, encrypted communication process. |
| if MQTTS - Certificate | A certificate is a digital document that includes a public key and information about its owner, providing a means to establish trust and securely authenticate MQTT clients in a communication network. |
| if MQTTS - Trusted CA | A trusted CA (Certificate Authority) is a well-established and trusted entity responsible for issuing digital certificates, which are used to verify the authenticity of MQTT clients and ensure secure communication within the MQTT network. |
Requirements
No requirements