Issue with Sending generic level messages from main()

RE: Issue with Sending generic level messages from main()

rmarques — Wed, 12 Jun 2019 15:49:43 GMT

Hello, I am using the nRF SDK version 15.2 and nRF Mesh SDK 3.1.0.

I could not get this patch working. While it does compile and program a DK, when trying to provision I get a Mesh assert error:

app_error_weak.c, 108, Mesh assert at 0x0002B0A0 (:0)

I suspect this is happening because either the mesh stack or a softdevice event is triggering in the wrong priority level, but I thought this patch solved it.

Just to be sure, what I did was the following:

1 - Replace the content of the light switch client example main with the content of this patch

2 - Add app_scheduler.c to the Application project folder on Embedded Studio

3 - Add $(SDK_ROOT:../../../../nRF5_SDK_15.2.0_9412b96)/components/libraries/scheduler; to c_user_include_directories

4 - Edit sdk_config.h line number 5792 #define APP_SCHEDULER_ENABLED 0 changed to 1

This should be enough right? But it still triggers the Mesh assert error when trying to provision.

RE: Issue with Sending generic level messages from main()

Mttrinh — Tue, 26 Feb 2019 17:18:37 GMT

I have attached the main for the client example. Most of the modification are the same as the patch for the server except for how the publishing is done. Look at the main to see how to send messages from main loop. You can also search for "MODFIED" to see all the modifcation done.

devzone.nordicsemi.com/.../main.c

RE: Issue with Sending generic level messages from main()

BubDev — Mon, 18 Feb 2019 19:07:52 GMT

I am also running into the same problem when using the client models. It would be greatly appreciated if a patch could be created for the client models.

RE: Issue with Sending generic level messages from main()

DeveloperZ — Mon, 18 Feb 2019 13:33:57 GMT

Hi,

Any chance that I could get a patch for the onoff client model because the clients and servers are so different in publishing the information that I am unable to write a patch for the client models.

Thank you.

RE: Issue with Sending generic level messages from main()

Mttrinh — Mon, 18 Feb 2019 09:54:19 GMT

Unfortunately, there are no patch for the client.

RE: Issue with Sending generic level messages from main()

DeveloperZ — Fri, 15 Feb 2019 19:20:32 GMT

Okay, Onoff/Level server messages are being published successfully.

Can I ask if there is any such patch for the client models either generic on off/client?

Thank you.

RE: Issue with Sending generic level messages from main()

Mttrinh — Thu, 14 Feb 2019 15:00:34 GMT

Hi,

Yes, that is correct.

RE: Issue with Sending generic level messages from main()

DeveloperZ — Thu, 14 Feb 2019 13:50:08 GMT

Hi,

I have an update. I have this patch up and running. You suggest writing similar functions for the generic level messages that I am willing to publish?

RE: Issue with Sending generic level messages from main()

DeveloperZ — Wed, 13 Feb 2019 14:17:52 GMT

I have applied the patch by making changes in various files suggested but now, I can't provision the board and assign a publishing/subscribing address as the board has all the LED's ON when I flash it whereas flashing the code should blink the LED's twice and turn them OFF.

Even the RTT viewer isn't showing any error when I flash the board. Reset button resets the board but it enters the same state again. Buttons on the board have no effect on the application.

RE: Issue with Sending generic level messages from main()

Mttrinh — Mon, 11 Feb 2019 16:35:51 GMT

Hi,

One of our developers from the Mesh team have made a patch to help you with this issue:

The mesh stack will assert if Mesh APIs are not called from correct priority. In the thread mode of operation, it is not sufficient to only change the priority setting during mesh stack initialization. The application also needs to use app scheduler and ensure that softdevice events are dispatched using app scheduler.

Apply this patch on the 3.1.0 release source. This patch will modify the example (light-switch-server) and model files to show following things:

How to use thread mode of operation in the examples?:

1. Adds app scheduler to the application (adds necessary sources/headers to cmakelists and initialization code)

2. Sends a mesh message from main loop as a demonstration (periodically turns off the LED on the server and publishes a status).

3. Modifications required to handle button press events to correctly call mesh APIs from the thread priority. Shows the use of app scheduler.

devzone.nordicsemi.com/.../patch_2D00_thread_5F00_mode_5F00_delayed_5F00_reply.diff

RE: Issue with Sending generic level messages from main()

DeveloperZ — Thu, 07 Feb 2019 15:03:52 GMT

[quote userid="15475" url="~/f/nordic-q-a/42915/issue-with-sending-generic-level-messages-from-main/169958"]instead of running it in the for-loop you could create an interrupt that triggers whenever the sensor detects motion.[/quote]

That was the first thing that I did if you can see the question that I posted, I tried to send a generic level message upon receiving an indication from the sensor using UART that motion is detected.

[quote userid="15475" url="~/f/nordic-q-a/42915/issue-with-sending-generic-level-messages-from-main/169958"]Might be that the messages are being sent too fast, can you try waiting for the NRF_MESH_EVT_TX_COMPLETE before sending a new message?[/quote]

I might have taken it that way already if the program crashes while sending the second message after successfully transmitting the first. But, I am unable to transfer the first message itself.

I also tried another thing, used the EnOcean switch example, instead of sending generic OnOff messages, I tried sending generic Level messages. They are transmitted without any error inside the app_switch_debounce().

Why can these messages be transmitted from app_switch_debounce() in EnOcean example, but not from the main() in any example?

RE: Issue with Sending generic level messages from main()

Mttrinh — Thu, 07 Feb 2019 14:50:34 GMT

Might be that the messages are being sent too fast, can you try waiting for the NRF_MESH_EVT_TX_COMPLETE before sending a new message?

Also, instead of running it in the for-loop you could create an interrupt that triggers whenever the sensor detects motion.

RE: Issue with Sending generic level messages from main()

DeveloperZ — Mon, 04 Feb 2019 14:46:32 GMT

If I made any error in adding the lines to the code, kindly correct me.

Thank you.

RE: Issue with Sending generic level messages from main()

DeveloperZ — Mon, 04 Feb 2019 14:41:09 GMT

Hi,

Thanks for the reply. I tried making the changes to the mesh_stack.c file mentioned in the links above. I even tried calling mesh_opt_core_adv_set() function inside static void start(void) function only before mesh_stack_start() call and also in the mesh_stack.c between calls sd_nvic_critical_region_enter()/_exit().

Adding these lines results in a Forbidden Command error 15 as shown below:

I also added following lines in mesh_stack.c

uint8_t is_nested;
ERROR_CHECK(sd_nvic_critical_region_enter(&is_nested));

mesh_opt_core_adv_set(CORE_TX_ROLE_ORIGINATOR, &net);

ERROR_CHECK(sd_nvic_critical_region_exit(is_nested));

Because I am using Mesh SDK 3.0.0, this solution isn't applicable. May be the support team know a better way to fix this issue.

Thanks for your response pirast.

RE: Issue with Sending generic level messages from main()

pirast — Sat, 02 Feb 2019 15:41:43 GMT

FYI I think I have found a solution; I am using Mesh SDK 2.2. Tracking down the mesh assert address, I found NRF_MESH_ASSERT_DEBUG(bearer_event_in_correct_irq_priority()); in timer_scheduler.c to be the critical section. After some research, I found https://devzone.nordicsemi.com/f/nordic-q-a/41645/error-nrf_error_invalid_state-when-send-data-via-mesh-3-0/163725 respectively https://devzone.nordicsemi.com/f/nordic-q-a/38479/mesh-sdk-2-2-0-bug-in-mesh_opt_core_adv_set/148935#148935 . Nesting the message publish code in sd_nvic_critical_region_enter (answer at the bottom) solves this for me.

RE: Issue with Sending generic level messages from main()

pirast — Fri, 01 Feb 2019 17:10:28 GMT

Actually, I am running into the same issue. I want to shoot off button_event_handler(1) not from rtt_input_handler callback but from another function (e.g. main). When I do that, I get the same mesh assert. Interestingly, the first time it works (after provisioning). But after power cycling it (settings are loaded), this does not work and it gives the mesh error.

I have tracked it down to net_state_seqnum_alloc where m_net_state.seqnum is = m_net_state.seqnum_max_available. Possibly this appears based on from which context the send function is run?

RE: Issue with Sending generic level messages from main()

Mttrinh — Thu, 31 Jan 2019 17:23:14 GMT

I'm not too sure why this error occurs. I will try this and update you as soon as possible.

RE: Issue with Sending generic level messages from main()

DeveloperZ — Tue, 29 Jan 2019 19:50:01 GMT

Hi,

I was trying a similar thing with light_switch example. In the light switch client, I did something similar:

int main(void)
{
    initialize();
    start();

    for (;;)
    {
        button_event_handler(1);
        nrf_delay_ms(2000);
        (void)sd_app_evt_wait();
    }
}

Initially, I already setup a mesh with a Mesh switch(CLIENT) publishing to an address and Mesh light(SERVER) subscribed to that address. When I run the example after adding button_event_handler in the main(), I see the following forbidden command error:

Any idea on why this error is occuring?

RE: Issue with Sending generic level messages from main()

DeveloperZ — Tue, 29 Jan 2019 16:18:03 GMT

May be you can try this issue by just calling button_event_handler() function in the main() of the dimming client example something like this:

for (;;)
    {
        
        button_event_handler(1);

        (void)sd_app_evt_wait();
    }

Later after provisioning using app and applying a publication address,

I was getting a mesh_assert when sending acknowledged messages and mesh error 15 when sending unacknowledged messages.

RE: Issue with Sending generic level messages from main()

Mttrinh — Tue, 29 Jan 2019 15:19:41 GMT

I'm little bit confused. Which error code do you get from access_model_reliable_publish()? Or do you get mesh error 15 from this function? You should be able to send messages from main(), seems like the issue is elsewhere.

RE: Issue with Sending generic level messages from main()

DeveloperZ — Mon, 28 Jan 2019 15:01:26 GMT

Hi Martin,

I have been using 15.2.0 SDK and 3.0.0 Mesh SDK.

[quote userid="15475" url="~/f/nordic-q-a/42915/issue-with-sending-generic-level-messages-from-main/168286"]Which function are giving you this error?[/quote]

I have been trying to debug the error but it was showing an error from the access_model_reliable_publish() function that is executed before sending the generic level message. If I dig deep into the function, it shows an error at a different function each time I start a new debug stint.

If I try to send an unacknowledged generic level delta_set message, it results in a mesh error 15 i.e, forbidden command.

Can't we send the generic level messages from the main() but send them by pressing the buttons on the board? How?

Thank you.

RE: Issue with Sending generic level messages from main()

Mttrinh — Mon, 28 Jan 2019 14:43:40 GMT

Hi,

Which function are giving you this error? Which nRF5 SDK and Mesh SDK are you using?