yes, we have used the same code provided with the configuration in the anchor as:
cfg_anchor.initiator = 1;
cfg_anchor.bridge = 0;
cfg_anchor.common.led_en = 1;
cfg_anchor.common.ble_en = 1;
cfg_anchor.common.uwb_mode = DWM_UWB_MODE_OFF;
cfg_anchor.common.fw_update_en = 1;
and in the tag as:
HAL_Print(“Setting to tag: dev%d.\n”, HAL_DevNum());
cfg_tag.low_power_en = 0;
cfg_tag.meas_mode = DWM_MEAS_MODE_TWR;
cfg_tag.loc_engine_en = 1;
cfg_tag.common.led_en = 1;
cfg_tag.common.ble_en = 1;
cfg_tag.common.uwb_mode = DWM_UWB_MODE_ACTIVE;
cfg_tag.common.fw_update_en = 0;
One of the DMW1001-DEV in the RP3 is runing as anchor and the other MW1001-DEV in the RP3 is runing as tag without changes in the location computed.
Thanks in advance
I found this post https://devzone.nordicsemi.com/f/nordic-q-a/36439/spi-connection-between-nrf52832-and-raspberry-3-pi
where indicate maybe some connections are changed in DMW1001-DEV from default code, is it possible? how could I change them to check?
nrf_drv_spis_config_t spis_config = NRF_DRV_SPIS_DEFAULT_CONFIG;
spis_config.csn_pin = 3; // GPIO8/SPI_CE0 on RPi
spis_config.miso_pin = 7; // GPIO9/SPI_MISO on RPi
spis_config.mosi_pin = 6; // GPIO10/SPI_MOSI on RPi
spis_config.sck_pin = 4; // GPIO11/SPI_SCLK on RPi
spis_config.mode = NRF_DRV_SPIS_MODE_1;
Many thanks Yves,
I have successfully conected to one tag to raspberry and I obtain the location (by C++ code at the page 40 from api-guide) from the 3 anchors (one used as active) previously configured by android app.
My issue is that I would like to have one or more tags in the sytems “free” of raspberry, just one tag connected to RP3 to process the information as “listener”. Is it possible to obtain other tag locations by C++ code?
Event, I just needed the distance from one tag to other anchors.
If not, how could I obtain this information?