Hardcode unicast address?

RE: Hardcode unicast address?

Mttrinh — Fri, 30 Oct 2020 15:04:15 GMT

Hi,

I understand. Like I mentioned the unicast addresses of the device cannot be changed. NFC would be a good alternative. It is hard to give a solution without knowing the specific use-case.

RE: Hardcode unicast address?

JVKran — Wed, 28 Oct 2020 15:29:22 GMT

Nope, unfortunately an external party determined that would be the technology that's going to be used. It's for interacting with objects in a room. And those objects contains RFID readers.

Don't know the ins- and outs of the pros and cons of the chosen path, but hey; I trust that was the best option they had available.

RE: Hardcode unicast address?

Mttrinh — Wed, 28 Oct 2020 15:26:31 GMT

What I meant is why do you want to use RFID? What is the use-case?

Is it to know which device is which when getting close to it?

RE: Hardcode unicast address?

JVKran — Wed, 28 Oct 2020 09:51:39 GMT

Hi Mttrinh,

Well, let's say RFID tag 5 broadcasts 0x0005. Then the device that's physically connected to RFID tag 5 should have unicast address 0x0005.

I hope that clears thing up a bit.

RE: Hardcode unicast address?

Mttrinh — Wed, 28 Oct 2020 09:46:01 GMT

Hi,

When a device is added to a network, it is assigned a range of unicast addresses that represents it. This is done by the provisioner. A device's unicast addresses cannot be changed.

[quote user=""]Every device will contain an RFID tag and the RFID tag number has to be equal to the address of the device it's connected to.[/quote]

Could you give me more details/explain to me why you want to do this?

[quote user=""]Just let a provisioner run and assign addresses and keys to devices and let the provisionee broadcast the address through NFC.[/quote]

Yes, as you say this alternative should solve the problem.