You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -35,16 +35,15 @@ This connector uses a Simple Network Management Protocol (SNMP) connection and r
35
35
36
36
SNMP CONNECTION:
37
37
38
-
-**IP address/host**: [The polling IP or URL of the destination.]
39
-
-**Device address**: [Indicate if required or not. If it is, specify default value and range.]
38
+
-**IP address/host**: The polling IP or URL of the destination.
39
+
-**Device address**: Indicate if required or not. If it is, specify default value and range.
40
40
41
41
SNMP Settings:
42
42
43
-
-**Port number**: [The port of the connected device, by default 161.]
44
-
-**Get community string**: [The community string used when reading values from the device (default: *public*).]
45
-
-**Set community string**: [The community string used when setting values on the device (default: *private*).]
43
+
-**Port number**: The port of the connected device, by default 161.
44
+
-**Get community string**: The community string used when reading values from the device (default: *public*).
45
+
-**Set community string**: The community string used when setting values on the device (default: *private*).
46
46
47
47
## How to use
48
48
49
-
In the connector there are 5 pages. The **General** contains the most important status parameters. Next to this, there is an **Audio** and **Video** page. The **Faults** page enables the user to let the device send traps on certain situations. **Configuration** at last contains information about the slot and master jumper.
50
-
49
+
The element created with this connector will have 5 data pages. The **General** page contains the most important status parameters. Next to this, there is an **Audio** and **Video** page. On the **Faults** page, you can make the device send traps in certain situations. The **Configuration** page contains information about the slot and master jumper.
The beIN GPIO Mapping is a protocol that allows to show Frame PSU State parameters, which are destinations connected to source parameters via Element Connections.
6
+
With the beIN GPIO Mapping connector, you can view Frame PSU State parameters, which are destinations connected to source parameters via [DataMiner Element Connections](https://aka.dataminer.services/virtual-elements-used-for-element-connections).
7
7
8
8
## About
9
9
10
10
### Version Info
11
11
12
-
| Range | Key Features | Based on | System Impact |
@@ -35,8 +35,8 @@ This connector uses a virtual connection and does not require any input during e
35
35
36
36
### Initialization
37
37
38
-
For this element and parameters to show relevant data, you need to connect the 11 parameters (that serve as destinations) with sources. This can be done via **Element Connections**. An element running the protocol *Advantech ADAM5050* could e.g. provide parameters that can serve as sources.
38
+
For this element and parameters to show relevant data, you need to connect the 11 parameters (which serve as destinations) with sources. This can be done via [Element Connections](https://aka.dataminer.services/virtual-elements-used-for-element-connections). An element running the protocol *Advantech ADAM5050* could e.g. provide parameters that can serve as sources.
39
39
40
40
## How to use
41
41
42
-
In the connector there is 1 page **Frame PSU States** with 11 parameters that can be monitored. Discreet values are preconfigured as *Fault (0)* and *Healthy (1)*.
42
+
The connector has one data page,**Frame PSU States**, with 11 parameters that can be monitored. Discrete values are preconfigured as *Fault (0)* and *Healthy (1)*.
0 commit comments