ANT extended device numbers

RE: ANT extended device numbers

Toyman — Fri, 13 Apr 2018 11:48:13 GMT

Here is what happens: when adding Transmission type, you have to know not only the upper nibble, but also the lower nibble. There is no way to wildcard lower nibble while hard coding upper one.

That's the limitation of current library implementation, because if I want to set the extended device id (i.e. Device ID + upper nibble of the Transmission type) I should also set transmission type set by lower nibble.

In my example I was searching for device ID (0x13D6 + 0x2) with transmission type 0x1, while my sensor had different transmision type.

The not_so_ideal workaround I am using is to search for ID 0x13D6, while wildcarding transmission type (0), but that means that devices with extended ID consisting of 0x13D6 + 0x1, 0x2...0xF will be able to connect as well.

RE: ANT extended device numbers

Kenneth — Tue, 10 Apr 2018 14:42:26 GMT

Have you tried read out the channel ID after aquire channel using wildcards with sd_ant_channel_id_get()?

RE: ANT extended device numbers

Toyman — Mon, 09 Apr 2018 17:08:52 GMT

Sure. Everything is working fine with either wildcards or with non-extended Device Numbers (uint16t), e.g. 60922

RE: ANT extended device numbers

Kenneth — Mon, 09 Apr 2018 16:10:49 GMT

Have you added the actual ANT+ network key in ant_key_manager_config.h:

#define ANT_PLUS_NETWORK_KEY {0, 0, 0, 0, 0, 0, 0, 0} /**< The ANT+ network key. */