problem with DPT 3.7 about knx HOT 5 CLOSED

same goes for DPT 18.1 and valueToBusValueSceneControl().

from knx.

The logic of the index is as follows:
DPT 3.7 consists of two parts:

• c 1 bit Increase/Decrease (index 0)
• bbb 3 bit Stepcode (000b - 111b) (index 1)

The whole DPT-Encoding stuff was taken from a knxd branch. It would probably b easier to understand if every complex dpt would get a struct.
In case of DPT 3.7 a signed char would do the job just fine.

Feel free this ;)

from knx.

oh, so I've got to create 2 group object to handle a, for example "scene control" DTP? something like this?

	GroupObject& sceneLearn = knx.getGroupObject(2);
	sceneLearn.dataPointType(Dpt(18, 1, 0));
	GroupObject& sceneNumber = knx.getGroupObject(2);
	sceneLearn.dataPointType(Dpt(18, 1, 1));
	sceneLearn.value(1);
	sceneNumber.value(5);

right?

and, if i want to manage it myself i can just use another DTP? like 5.10 ?

	GroupObject& scene = knx.getGroupObject(2);
	scene.dataPointType(Dpt(5,10));
	scene.value(0x85);

would it be alright? (I donno much about KNX protocol so im not sure if its okey to use another DPT there)

from knx.

No the group object is the same.
Something like:

GroupObject& scene = knx.getGroupObject(2);
learn = scene.value(Dpt(18,1,0));
number = scene.value(Dpt(18,1,1));

should work.

When you write a group object you have to set the first components with GroupObject::valueNoSend and only the last component with GroupObject::value.

GroupObject& scene = knx.getGroupObject(2);
scene.valueNoSend(1, Dpt(18,1,0));
scene.value(37, Dpt(18,1,1));

If you want to decode the data yourself,, you can get a raw pointer with GroupObject::valueRef and the size of the data with GroupObject::valueSize.

The better way would be custom structs for complex datapoints.

from knx.

Thanks!

from knx.