Hi,
Thank you very much for your response.
I managed to get a system with N-tags versus M-anchors running, but it still requires significant optimization. Below, I’ve outlined a few additional questions:

Regarding the IRQs: During the initialization phase, I needed to enable them by calling (on the ESP target) two additional functions compared to your reference example:

dw3000_hw_init_interrupt();
dw3000_hw_interrupt_enable();

From my understanding, these functions are not called anywhere else. Is that correct?

Where can I catch an event for TWR completion on the tag side when no REPO packet is used?
Reviewing the code, it seems that when no REPO is expected, the twr_handle_result function is invoked with dist == TWR_OK_VALUE. In this condition, no twr_callback is triggered.
Would it be acceptable to simply add the twr_callback as follows to invoke the observer callback, or is there a better approach?

} else if (dist == TWR_OK_VALUE) {
    // This is on the initiator side when no reports are expected; the distance is unknown
    LOG_INF("#%d " LADDR_FMT " -> " LADDR_FMT ": OK", cnum, LADDR_PAR(src),
            LADDR_PAR(dst));
    // >>>
    twr_callback(src, dst, dist, cnum);
    // <<<

I’m still encountering issues with MAC filtering.
After calling dwmac_set_frame_filter(), I stop receiving any packets. Do you have any advice on resolving this?

Thank you!

Ranging with multiple anchors #3

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions