...
The following station protocol parameters can be defined:
| Keyword | Full name | Meaning | Unit | Default value |
|---|
| Change Baudrate | Value Yes means that communication will be switched between modes 1 and 2 (only Serial line).
Value No means that communication will be performed using the mode 1 (300 Bauds). | - | No |
| Send SND_NKE as Broadcast | The Yes value means that the SND_NKE (slave device initialization) command is sent as Broadcast before reading from the first station on the line.
The No value means that the SND_NKE command is sent to each device individually before the start of the reading.
Note: if the parameter is set to Yes, after sending Broadcast, there is a delay configurable by parameter WAI. | - | Yes |
| Kotva |
|---|
| komunikacna_stanica |
|---|
| komunikacna_stanica |
|---|
|
Communication station configuration
...
The following station protocol parameters can be defined:
| Keyword | Full name | Meaning | Unit | Default value |
|---|
| Address Scan Mode | Each reading of values increments the station address. This mode can be used to find a device with an unknown address. | - | No |
| Retry Count | Poll repetition count in case of a communication error. | - | 2 |
| Retry Timeout | Delay between poll repetition in case of a communication error. | ms | 100 ms |
| Wait First Timeout | First waiting for response after sending the poll. | ms | 800 ms |
| Wait Timeout | Delay after transmitting the poll before reading the response. | ms | 500 ms |
| Max Wait Retry | Repetition count of response readings till its finalization. | - | 40 |
| Wait After SND_NKE Broadcast | Delay after sending a broadcast SND_NKE, before reading from the first station on a communication line. | ms | 8000 ms |
| Wait before REQ_UD2 Request | Delay before sending the REQ_UD2 poll request to a slave. | ms | 4000 ms |
| Set FCB Bit after SND_NKE | Parameter specifies whether an FCB bit in a poll request after sending SND_NKE shoult be ste to 1 (YES) or 0 (NO). | - | YES |
| Accept Following Records (0=disable,255=read all) | If the slave station has Variable Data available, the parameter specifies the number of records read during one polling of the station. A value of 255 means that all available records will be read. | - | 0 |
| Send Application Reset before REQ_UD2 | Optional sending of "application reset" message (50h) prior to reading the values from the station. | - | NO |
| WakeUp Length | Length (given in characters) of so-called wake-up message sent before each poll. Value 0 disables sending of wake-up message. | bytes | 0 |
| WakeUp Delay | Delay between wake-up message and poll. | ms | 400 |
| Full Debug | Enables debug logs on the communication and acquired data. | - | NO |
| Multical III | Enables decoding the Manufacture specific data of Multical III device. | - | NO |
String containing the protocol parameters is being defined as follows:
...
- Simple address: a number that is an index of value in M-Bus data packet. To get detailed information on unknown device activate debug logs using the parameter FULL_DEBUG.
An example of debug log (individual rows correspond with addresses 1 to 9, value is displayed at the end of listing after the text "Val"):
>> Adr.1,DF:0CH (8 digit BCD)(inst. val),VIF:05H=Energy 0*10^2 [Wh],VIFE:7DH=Multiplicative corr. factor 10^3,Val:0
>> Adr.2,DF:0CH (8 digit BCD)(inst. val),VIF:15H=Volume 0*10^-1 [m3],Val:0
>> Adr.3,DF:0CH (8 digit BCD)(inst. val),VIF:3DH=Volume Flow 0*10^-1 [m3/h],Val:0
>> Adr.4,DF:0CH (8 digit BCD)(inst. val),VIF:2DH=Power 0*10^2 [W],Val:0
>> Adr.5,DF:02H (16 bit int)(val during err),VIF:5AH=Flow temperature 0*10^-1 [C],Val:0
>> Adr.6,DF:02H (16 bit int)(val during err),VIF:5EH=Return temperature 0*10^-1 [C],Val:0
>> Adr.7,DF:03H (24 bit int)(val during err),VIF:60H=Temperature difference 0*10^-3 [K],Val:0
>> Adr.8,DF:0CH (8 digit BCD)(inst. val),VIF:78H=Fabrication No.,Val:53155203
>> Adr.9,DF:0CH (8 digit BCD)(inst. val),VIF:7DH=Extension of VIF-codes,VIFE:10H=Customer location,Val:53155203
Address of header objects: in format 0.subadr enables to address objects located in a header of an answer. A device can answer using a fixed or variable respond that have different header contents. Following table lists header objects and their addresses for fix and variable respond.
| Object | Value type | Address in fix respond | Address in variable respond |
|---|
| Identification No. | Ci, TxtI | 0.0 | 0.0 |
| Manufacturer | TxtI (3 characters) | - | 0.1 |
| Version | Ci | - | 0.2 |
| Medium | Ci | - | 0.3 |
| Access No. | Ci | 0.1 | 0.4 |
| Status | Ci | 0.2 | 0.5 |
| Signature | Ci | - | 0.6 |
An example of debug log for variable respond:
Variable data respond CI=0x72 mode 1 from St:'B.MBUS_SENSUS'(0) detected.
>> Adr.0.0,Identification No.,Val=53155203
>> Adr.0.1,Manufacturer,Val='SEN'
>> Adr.0.2,Version,Val=12
>> Adr.0.3,Medium,Val=4
>> Adr.0.4,Access Nr.,Val=50
>> Adr.0.5,Status,Val=16
>> Adr.0.6,Signature,Val=0
...
Multical III device sends extended "manufacture specific data". Activating the parameter MULTICALIII allows to configure I/O tags according to the following table:
| Address | Value description | Type |
|---|
| 12 | Access counter | Ci |
| 13 | Number of customer 1 | Ci |
| 14 | Number of customer 2 | Ci |
| 15 | Info | Ci |
| 16 | TAR2 | Ci |
| 17 | TL2 | Ci |
| 18 | TAR3 | Ci |
| 19 | TL3 | Ci |
| 20 | AUX1 | Ai |
| 21 | AUX2 | Ai |
| 22 | Prog_No | Ci |
| 23 | Config | Ci |
| 24 | Date | TiA |
| 25 | Date* | TiA |
Parameters settings and data acquisition method
...
Changes and modifications
...