Hi, On Fri, Jun 3, 2022 at 2:34 PM Miquel Raynal <miquel.raynal@xxxxxxxxxxx> wrote: > > The current enum is wrong. A device can either be an RFD, an RFD-RX, an > RFD-TX or an FFD. If it is an FFD, it can also be a coordinator. While > defining a node type might make sense from a strict software point of > view, opposing node and coordinator seems meaningless in the ieee > 802.15.4 world. As this enumeration is not used anywhere, let's just > drop it. We will in a second time add a new "node type" enumeration > which apply only to nodes, and does differentiates the type of devices > mentioned above. > First you cannot say if this is not used anywhere else. Second I have a different opinion here that you cannot just "switch" the role from RFD, FFD, whatever. You are mixing things here with "role in the network" and what the transceiver capability (RFD, FFD) is, which are two different things. You should use those defines and the user needs to create a new interface type and probably have a different extended address to act as a coordinator. - Alex
