15.10.2019, 18:35
(This post was last modified: 15.10.2019, 18:36 by Erwin van der Zwart.)
Hi,
Looking at the EEP of both profiles I notice this:
D5-00-01 uses DB0.1 for open close and DB0.3 = for learn (pressed)
F6-01-02 uses DB0.1 and DB0.2 for 4 different states (value 0 to 3) but also reserved DB0.3, however this bit is not used in F6-01-02 according to the EEP, but is declared for "Rocker 2th Action", the documented profile values are only 0,1,2 and 3 so bit 3 will always be 0.
The telegram send by these 2 profiles are not the same, if your device is responding correct on a D5-00-01 telegram then the implementation of the profile is not correct in the device if it uses F6-01-02.
As you mentioned the D2-01-02 profile, this is a VLD (variable length) datagram and is not supported so what is the actual prescribed profile you need to use for your device?
As admin already stated, if you have a profile that works you can use it as its only a matter of picking the correct bit from the datagram that is handled by the profile..
BR,
Erwin
Looking at the EEP of both profiles I notice this:
D5-00-01 uses DB0.1 for open close and DB0.3 = for learn (pressed)
F6-01-02 uses DB0.1 and DB0.2 for 4 different states (value 0 to 3) but also reserved DB0.3, however this bit is not used in F6-01-02 according to the EEP, but is declared for "Rocker 2th Action", the documented profile values are only 0,1,2 and 3 so bit 3 will always be 0.
The telegram send by these 2 profiles are not the same, if your device is responding correct on a D5-00-01 telegram then the implementation of the profile is not correct in the device if it uses F6-01-02.
As you mentioned the D2-01-02 profile, this is a VLD (variable length) datagram and is not supported so what is the actual prescribed profile you need to use for your device?
As admin already stated, if you have a profile that works you can use it as its only a matter of picking the correct bit from the datagram that is handled by the profile..
BR,
Erwin