I want to develop a KNX Stack.

[kervanaslan]

Hi All,

I want to develop a knx stack, and planing to share it free to use after registering this stack. Yes a big dream :)

I can currently write and read group address values, and wrote many of DTP's.
But there isn't a ETS compatibility. And I don't know how to start, as I am a KNX member diving into KNX.org documentations but can't find any useful information.

For example, how individial address programing works and how its diagram.
Or, how to generate a S19 file and what is the valid format for Manufacturer tool.

Are there a resource which I can study?

Thanks all.

[nanosonde]

Hi @kervanaslan !
Indeed a big dream...

I suggest that you read the whole KNX specs.

Reading and writing to group addresses is the minimum and possibly the easiest part of the KNX stack.
However, there is really so much more to do.

Study the provided source code here to estimate how much you would have to do.

May I ask why you want to create your own KNX stack instead of contributing to this one?

IMHO it is the most advanced open source stack.

[GeminiServer]

There is already a full software KNX stack that was implemented 10-12 years ago and, to my knowledge, is still supported. You can find it here: https://github.com/selfbus/software-arm-lib/tree/5fea151f4b3491d0579802bd43e3fde28a625732/sblib

I completely agree with @nanosonde. Today, I believe there’s no need for a full software KNX stack, as the hardware BCU already contains everything that is necessary.
It’s also become more cost-effective nowadays. While having your own stack would be nice, it would also require your own hardware. As mentioned, if you're interested, check out the links. Otherwise, OpenKNX is a great choice and will serve you well.

[kervanaslan]

@GeminiServer @nanosonde

First of all, thank you for taking the time to respond.

Actually, there are three reasons why we want to develop a stack:

1- We already have devices that we’ve developed for our company, and we want to make them ETS-compatible.
2- In the future, we plan to sell our startup, and we believe having our own stack will add significant value.
3- Also, I don’t want to depend on a third-party stack. Having our own registered stack with full control would be ideal.

Yes, I know it’s difficult, but we can do it.

Right now, my main problem is this:

If we take an example scenario—for individual address programming, ETS and the KNX device exchange a series of packets. I can say that I’ve gone through all the documents provided by the KNX Association, but I couldn’t find any documentation explaining how this is actually done.

Of course, I could try to figure it out by reading the code of open-source projects that have done this before me. But the real question is: How did the first companies did do this (like Tapko)?