I have some questions regarding
the difference between FTD and FED.
By default, when the system is compiled in ‘FTD mode’, if I play the standard
use case shown in the readme (panid 0x1234, ifconfig up, thread start) between
two devices , the first one will become ‘Leader’ and the second one will become
‘Child’ and then ‘Router’.
1) If I want my second board to act as an ‘EndDevice, this ‘device’ should not
go to the ‘router’ state but should stay ‘child’. (OK/KO)
(Note : How is configured the time managing
the transition child-> router? otSetRouterSelectionJitter ?)
2) Even if I compile my code in
FTD, it will always be possible to use my device as an FED (OK/KO).
(Note : I hope the response is OK, otherwise it means that I need to define my
use case at compilation time !!)
3) Using simple ‘cli commands’, how can I have my first board becoming single ‘router’
or ‘leader’ and my second board acts as an ‘end device’ and not as a ‘router’ ?
4) Sleep mode on an End Device :
Once I have configured my device in FED, I will be able to put this device in
sleep mode rather easily.
For example, we could have such a device being able to sleep all the time and to
wake up only from time to time for a very short period (For example once every
5 seconds), to send some sensors data. In this case, when it will wake up, this
device will also be able to catch any specific previous pending request coming from
the router on which it is connected. (OK/KO) ?
5) Sleep mode on an Full Thread Device
If I use my device as an FTD and if I use it as a ‘router’ or a ‘leader’, it will be possible to put it in sleep mode only for very short period of time (for instance maximum 10ms every 1 seconds)
6) Apart from gaining ‘memory space’,
what it the real added value for compiling OpenThread stack in FED mode ?
Thanks a lot.
I have some questions regarding the difference between FTD and FED.
By default, when the system is compiled in ‘FTD mode’, if I play the standard use case shown in the readme (panid 0x1234, ifconfig up, thread start) between two devices , the first one will become ‘Leader’ and the second one will become ‘Child’ and then ‘Router’.
1) If I want my second board to act as an ‘EndDevice, this ‘device’ should not go to the ‘router’ state but should stay ‘child’. (OK/KO)
(Note : How is configured the time managing the transition child-> router? otSetRouterSelectionJitter ?)
2) Even if I compile my code in FTD, it will always be possible to use my device as an FED (OK/KO).
(Note : I hope the response is OK, otherwise it means that I need to define my use case at compilation time !!)
3) Using simple ‘cli commands’, how can I have my first board becoming single ‘router’ or ‘leader’ and my second board acts as an ‘end device’ and not as a ‘router’ ?
4) Sleep mode on an End Device :
Once I have configured my device in FED, I will be able to put this device in sleep mode rather easily.
For example, we could have such a device being able to sleep all the time and to wake up only from time to time for a very short period (For example once every 5 seconds), to send some sensors data. In this case, when it will wake up, this device will also be able to catch any specific previous pending request coming from the router on which it is connected. (OK/KO) ?
5) Sleep mode on an Full Thread Device
If I use my device as an FTD and if I use it as a ‘router’ or a ‘leader’, it will be possible to put it in sleep mode only for very short period of time (for instance maximum 10ms every 1 seconds)
6) Apart from gaining ‘memory space’, what it the real added value for compiling OpenThread stack in FED mode ?