BLE_Gateway mesh device will not broadcast

RE: BLE_Gateway mesh device will not broadcast

Ignacio Lopez — Tue, 03 May 2016 11:28:03 GMT

That's correct Trond. Ta!

RE: BLE_Gateway mesh device will not broadcast

Trond Einar Snekvik — Mon, 02 May 2016 08:28:45 GMT

The 4th byte should set the length of the data you're sending, and the command you mention in the 5th step sets the value with zero length, while your data is 1 byte. If you don't check this length in your nRF51 application, you might see corrupted data. Building the BLE_gateway from the 0.8.3 version of the mesh, the command 00-00-00-01-01 works on my setup, with a 20ms connection interval, slave latency 0, connection supervision timeout at 3000ms, auto-accept connection update enabled in MCP 3.10.0.14. In MCP, I select a mesh device, connect, discover services and enable services, before writing the command as a hex-value to the last characteristic in the list (UUID 2A1E0005-...).

RE: BLE_Gateway mesh device will not broadcast

David Edwin — Fri, 29 Apr 2016 15:21:46 GMT

Lets first do it without the Photon and test the mesh first as there are some issues on the Photon interface. You can try the github.com/.../BLE_Gateway and see if it works.

RE: BLE_Gateway mesh device will not broadcast

Ignacio Lopez — Fri, 29 Apr 2016 15:18:34 GMT

Trond, Thanks for the quick response. I have increased the connection interval to 100ms on the MCP as suggested. The message does not propagate between devices.

I am also testing with the serial connection via particle.io api. It reaches the PCA10028 board that it is connected via SPI but it does not propagate to the next one.

RE: BLE_Gateway mesh device will not broadcast

Trond Einar Snekvik — Fri, 29 Apr 2016 15:13:45 GMT

Hi,

Go to File->Options in MCP. The third setting from the top should allow you to set the connection interval. I think it's at 7.5ms by default. Anything below 10-15ms would block the mesh activity on the chip, and it won't be able to broadcast its new values. I recommend setting it to 100ms, although it should work with everything above 20ms. Does this fix your issue?