In the P2P mode, the following settings can be configured in the Settings page:
Transmission mode
The P2P mode uses the 32Mbit ibaNet protocol. In the transmission mode field, you define how this protocol is assigned. You can choose from the following transmission modes:
-
4: 1024 Integer + 1024 Digital in 800 µs
-
A: 512 Real + 512 Digital in 800 µs
-
C: 2872 bytes in 1000 µs
The setting has to correspond with the setting in the 32Mbit communication partner (e. g. ibaLink-VME).
For each slave: bus number, address and active
The data from the ibaNet telegrams are mapped in send and receive direction on up to 8 slaves (A - H). For each slave, you can choose, on which bus it is to be activated, which PROFIBUS address should be assigned and if you want to use this slave at all.
Digital
The Slave H can be used in the transmission modes 4 and A, either for the analog value range or the digital value range. If you want to use the slave H for the digital values, then activate the "Digital" setting.
Submit
You activate changed settings by clicking on <Submit>.
Refresh
With a click on <Refresh>, the mask will be updated.
The colored bar visualizes the mapped data from the ibaNet-telegram. The mapping of the data is always identically for both directions.
|
Mode |
|||
|---|---|---|---|
|
4: 1024 Integer + 1024 Digital |
A: 512 Real + 512 Digital |
C: 2872 bytes |
|
|
Slave A |
Integer 0 – 121 |
Real 0 -60 |
Bytes 0 – 243 |
|
Slave B |
Integer 122 – 243 |
Real 61 – 121 |
Bytes 244 – 487 |
|
Slave C |
Integer 244 – 365 |
Real 122 – 182 |
Bytes 488 – 731 |
|
Slave D |
Integer 366 – 487 |
Real 183 – 243 |
Bytes 732 – 975 |
|
Slave E |
Integer 488 – 609 |
Real 244 - 304 |
Bytes 976 – 1219 |
|
Slave F |
Integer 610 – 731 |
Real 305 – 365 |
Bytes 1220 - 1463 |
|
Slave G |
Integer 732 – 853 |
Real 366 – 426 |
Bytes 1464 – 1707 |
|
Slave H |
Integer 854 – 975 or digital values 0 - 1023 |
Real 427 – 487 or digital values 0 - 512 |
Bytes 1708 – 1951 |
|
Not to be used |
Integer 976 - 1023 |
Real 488 - 512 |
Bytes 1952 - 2872 |
Note |
|
|---|---|
|
In total, the ibaNet-telegram always contains more data than can be mapped on 8 slaves (each with 244 bytes). This is why a part of the telegram cannot be used. |
|
Under Actual length you can see the length of the inputs and outputs in the web dialog that has been detected for the respective slave. This corresponds to the configured length in the PROFIBUS configuration (e. g. Step 7 HWConfig).
Note |
|
|---|---|
|
In the PROFIBUS configuration, there are limitations for the maximum length to be configured for the inputs and outputs. Under Step 7, for example, the sum of the configured inputs and outputs of a slave may not exceed a maximum length of 256 bytes. |
|
