What's the difference from running mesh sdk on SES to on board?

RE: What's the difference from running mesh sdk on SES to on board?

run_ar — Fri, 07 Dec 2018 09:54:12 GMT

ok, so what board are you using to measure RSSI? is it located and oriented in the exact same way when it is connected to the pc and when it is not? What is the variation in RSSI measurements you are seeing?

RE: What's the difference from running mesh sdk on SES to on board?

zzzh — Thu, 06 Dec 2018 14:17:08 GMT

I'm sure it's not sleeping.

It looks like there's big difference in the rssi value it detceted.

RE: What's the difference from running mesh sdk on SES to on board?

run_ar — Thu, 06 Dec 2018 12:23:12 GMT

Can you please elaborate on what it is you are doing?

If it only work when you have connected a debugger I would guess your application would be sleeping when the the debugger is not connected. which is why it "almost works", not sure what "alomst works" means, though...

RE: What's the difference from running mesh sdk on SES to on board?

zzzh — Thu, 06 Dec 2018 08:04:13 GMT

It's like what's the difference between car and truck, details are always the more the better, but not a must..

RE: What's the difference from running mesh sdk on SES to on board?

awneil — Thu, 06 Dec 2018 07:53:21 GMT

Too little detail to comment!

Describe fully what you mean by, "almost don't work"

Remember: we can't read your mind; we don't know what you're doing; we can't see what you have on your bench; we can't see your screen; we can't see your code; etc, etc...