Jam Detection Thread

RE: Jam Detection Thread

Verena — Mon, 25 Apr 2022 07:08:08 GMT

Hello Edvin,

your answer solved my problem. Thank you very much for your help!

Best regards

Verena

RE: Jam Detection Thread

Edvin — Fri, 22 Apr 2022 06:26:00 GMT

[quote user="Edvin Holmseth"]

What SDK version do you use? Do you use NCS or nRF5 SDK? The reason I ask is that I can't find any references to otStartJamDetection(), but I can find otJamDetectionStart() in our SDK.

[/quote]

Can you please specify this?

[quote user="Verena"]In the instruction it is written to enable the jam detection in the openthread/src/core/config/openthread-core-default-config.h[/quote]

This link, nor the first link in your previous reply is leading anywhere. Can you please check both your links?

[quote user="Verena"]This is out of the instruction, but I don't know how to give aCallback in this function[/quote]

You need to look up the definition of this parameter. otJamDetectionCallback is defined in openthread\include\openthread\jam_detection (at least in the openthread instance that is used in the nRF5 SDk for Thread and Zigbee. If this is not what you are using, please specify what SDK you are using.

typedef void (*otJamDetectionCallback)(bool aJamState, void *aContext);

This means that you need to define a callback looking something like this:

void my_jam_detection_callback(bool aJamState, void *aContext)
{
    NRF_LOG_INFO("Jam state %d", aJamState);
}

and then pass my_jam_detection_callback instead of aCallback when you call otJamDetectionStart():

otError err_code;

otInstance my_instance = ...;

err_code = otJamDetectionStart(&my_instance, my_jam_detection_callback, NULL);
NRF_LOG_INFO("otJamDetectionStart returned %d", err_code);

RE: Jam Detection Thread

Verena — Wed, 20 Apr 2022 14:19:07 GMT

I enabled the Jam detection in openthread/src/core/config/openthread-core-config-check.h and also in the sdk_config.h .
But if I am calling the method otJamDetectionIsEnabled(thread_ot_instance_get())) i am always getting 0 back. The thread_ot_instance_get is a method which is getting the actuall instance. The instance is required as an argument for the function *** bool otJamDetectionIsEnabled( otInstance *aInstance ) ***.

In the instruction it is written to enable the jam detection in the openthread/src/core/config/openthread-core-default-config.h , but there is no such file in my openthread repository.

Where should I enable this to solve this problem?

My second problem is that I don't know how to call the starting function.

otError otJamDetectionStart(
  otInstance *aInstance,
  otJamDetectionCallback aCallback,
  void *aContext
)

This is out of the instruction, but I don't know how to give aCallback in this function. ainstance and aContext are already defined in some example code snippets, so I know these. Should I define my own function ? Or what should I place there.

I would be glad about some help.

Best regards

Verena

RE: Jam Detection Thread

Edvin — Tue, 12 Apr 2022 13:57:33 GMT

Hello,

Did you enable the jam detection through the CONFIGs?

When you call otStartJamDetection(..., otJamDetectioncallback, ...);, what is otJamDetectionCallback in your case? Is it a function that you have defined? I couldn't see this from your snippet.

I don't think this callback should fire unless there is actually something jamming your network, so I guess it is a bit difficult to test unless you have a jammer.

According to jam_detection.h, the otJamDetectionIsEnabled() should return true (1) if it is enabled. From where do you call this function? And what does thread_ot_instance_get() return?

You should also check the return values of the ot... function calls that you do, that return something, like otStartJamDetection()

What SDK version do you use? Do you use NCS or nRF5 SDK? The reason I ask is that I can't find any references to otStartJamDetection(), but I can find otJamDetectionStart() in our SDK.

Please note that we are very short staffed here in Norway due to Easter Holidays this week (and Monday next week). This will lead to a longer than usual response time. I am sorry for the inconvenience.

Best regards,
Edvin