Hi,

You probably didn't initialize the mesh test class so you got that error. Call the gecko_bgapi_class_mesh_test_init to initialize it then you can use all the mesh test class APIs.

Thanks,

Kevin

Hi,

What's your question here? You only put your code, but does it succeed or? Please share more information otherwise we cannot help you.

Thanks,

Kevin

Hi,

This is not possible because we currently don't support L2CAP connection oriented channels which is a requirement for this.

Thanks,

Kevin

Hi,

You can refer to the SPP example, https://docs.silabs.com/bluetooth/latest/code-examples/applications/spp-serial-port-profile-over-ble, and make modification to adjust your use case.

Thanks,

Kevin

Hi,

You need to use the le_gap_end_procedure to stop the ongoing connection request which hasn't succeeded in establishing a connection. The API can also be used for stopping scanning, but they are not conflicted, you can stop scanning after you find the device you want to connect to, or you can just ignore it. Just remember to start scanning again if you call le_gap_end_procedure.

The le_connection_closed event won't be raised since connection has never been established successfully. This event indicates that a connection is dropped.

Thanks,

Kevin

Hi,

After connection established, you can try to discover the services on your phone. Then you will probably find the current time service (0x1805), which contains the time information. Then you can read out the current time characteristic (0x2a2b) for the time.

Thanks,

Kevin

Hi，

Bluetooth Mesh is not based on connection, so most of the nodes are not connected to each other, they are just following the same rules (keys, sequence number, etc. ) to communicate with each others. There won't be any event indicating that nodes are getting far away, however, you could use the heart beat feature to determine the network topology and get the necessary hops to reach out to one specific node. Please go through the heart beat feature in the Mesh Profile.

The higher the tx power is, the longer the signal can be transmitted, assuming the same environment factors and RX sensitivity, the longer the receiver can be. You can use that API to set the tx power for the specified advertiser, or you can use the gecko_cmd_system_set_tx_power to set for all advertisers. Note, do the setting below starting advertising, the best location to call it should be right after receiving the system_boot_evt.

Thanks,

Kevin

Hi,

I would like to suggest you to start with a soc-empty project, then port your code (USART, ADC, GPIO) to that project. This is the easiest way you get all the project settings align with our Bluetooth SDK.

Thanks,

Kevin

Hi,

I just used the Thunderboard BG22 to capture the trace in Network Analyzer, it works fine, the packets are shown in the content. You can just use a micro USB cable to connect to it and start capture.

Thanks,

Kevin

Hi,

From the Bluetooth LE perspective, 20m distance is quite easy to meet. However, the latency requirement is not, the minimal interval for BLE to communicate with each other is 7.5ms and it's not allowed to send any packets if the 7.5ms interval doesn't expire, you don't have the timing control for sending packets, you can only push the packets to link layer and link layer will schedule sending the packets. So, it's hard to meet the latency requirement, the real latency could be varies from 0ms to 7.5ms depending on when you push the packets.

Thanks,

Kevin