nvt on develop
tests: update csc files to late… Merge pull request #2287 from p… (compare)
nfi on develop
Fix style and misleading commen… Avoid log-warning every time de… Log human-readable TSCH link op… and 1 more (compare)
nvt on develop
Fix include of random-lib in rp… Merge pull request #2389 from a… (compare)
dependabot[bot] on github_actions
nfi on develop
build(deps): bump hendrikmuhs/c… Merge pull request #2383 from c… (compare)
guys, can someone help me to convert this C code to .sky file so it can be applied on cooja mote, thank you
(CoAP_Clinet.c & CoAP_Client.h)
https://drive.google.com/file/d/1wqOXc2sExr2QFxqUBuHfQcGqJwoEtkhv/view?usp=sharing
and the dependent file
https://drive.google.com/file/d/1KXByL1Yb2C5Gvt8OGBrB_yhsa02rbWpi/view?usp=sharing
Thinking aloud to open a discussion regarding metrics (PDR):
I have been researching TSCH scheduling and realized that PDR might hide network issues; for example, disconnections may occur in TSCH networks, and after a while the queue is full, and the S.O. notifies the app that it cannot generate data (at least until the link is restored). Disconnections may happen due to failure in node synchronization(IEEE Std 802.15.4 - Section 6.5.4.2). But, the PDR calculus is only performed over the generated and sent data. IMHO, PDR is an excellent measure to assess links, paths, etc. But, it could hide some TSCH issues as MAC disconnections. That's why I relate the PDR with the Expected Generated Packages: Simulation Time, Warmup time and the nodes sending interval (All nodes except root generates).
I don't know if I have explained my point clearly or if my reasoning is correct, but I think it is interesting.