KONNEKTING Protocol Specification: Difference between revisions

From KONNEKTING Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
* [[ KONNEKTING Protocol Specification 1.0.0 beta4 ]]
The programming protocol uses group telegrams with the mostly unused group address 15/7/255. Those telegrams use DPT 60000.000, which is unreserved for manufacturer specific extensions. The used Property Data Type is PDT_GENERIC_14, which is 14 bytes of raw data.
* [[ KONNEKTING Protocol Specification 1.0.0 beta5 ]]
 
'''!!! It's required that no other device is using this address. Otherwise it may conflict with KONNEKTING Devices !!!'''
 
{| class="wikitable" style="text-align:center"
!Byte no#:
!0
!1
!2
!...
!13
|-
!Used for:
|colspan="2"|Header, 2 bytes
|colspan="3"|Body, 12 Bytes
|-
!Description:
|Protocolversion
|Message-Type-ID
|colspan="3" rowspan="2"|depends on Message-Type-ID
|-
!Range:
|0x00..0xFF
|0x00..0xFF
|}
 
There are several message types for all kind of purposes. As we have one byte for the Message-Type-ID, we have up to 256 possible messages. That should be enough for our purposes. Same for version: Up to 256 versions should be enough for the ''near'' future.
 
 
 
== Protocol Versions ==
 
Here is a list of currently developed protocol versions
 
* [[ KONNEKTING Protocol Specification 0x00 ]]
* [[ KONNEKTING Protocol Specification 0x01 ]]

Revision as of 15:19, 5 March 2018

The programming protocol uses group telegrams with the mostly unused group address 15/7/255. Those telegrams use DPT 60000.000, which is unreserved for manufacturer specific extensions. The used Property Data Type is PDT_GENERIC_14, which is 14 bytes of raw data.

!!! It's required that no other device is using this address. Otherwise it may conflict with KONNEKTING Devices !!!

Byte no#: 0 1 2 ... 13
Used for: Header, 2 bytes Body, 12 Bytes
Description: Protocolversion Message-Type-ID depends on Message-Type-ID
Range: 0x00..0xFF 0x00..0xFF

There are several message types for all kind of purposes. As we have one byte for the Message-Type-ID, we have up to 256 possible messages. That should be enough for our purposes. Same for version: Up to 256 versions should be enough for the near future.


Protocol Versions

Here is a list of currently developed protocol versions