Hi Aditya,
On Wed, 23 May 2018 at 09:43, Aditya Xavier wrote:
> Hi Łukasz,
>
>
> Just saw a PR which you raised, does this fix the problem we were
> discussing ?
>
I don't think it fixes it. I will put info on the issue you created once
it is done.
>
> Also, the example I
Hi Łukasz,
Just saw a PR which you raised, does this fix the problem we were discussing ?
Also, the example I gave you has Device Address being generated Randomly. Is it
possible to use Mesh with a Public BLE Address ?
Thanks,
Aditya Xavier.
> On 19-May-2018, at 7:41 PM, Aditya Xavier
Hi Łukasz,
Thanks for looking into it.
Have raised an issue in Github for the same.
Thanks,
Aditya Xavier.
> On 19-May-2018, at 6:05 PM, Łukasz Rymanowski
> wrote:
>
> Hi,
>
>
> On Sat, May 19, 2018, 14:21 Aditya Xavier wrote:
>
>> Hi
Hi,
On Sat, May 19, 2018, 14:21 Aditya Xavier wrote:
> Hi Michał / Łukasz,
>
> Were you able to identify the issue ? Do let me know if you need any
> further testing from my end.
>
We found one issue. Not yet PR bit you can apply patch for you to test
Hi Michał,
Sorry fo the confusion. I have done some more testing on the same, please find
the test results in the xl file.
Please note, the test results are of Device A; wherein the Device B is kept in
the same state ( with all the mentioned flags turned off)
Also, test cases 2 - 5 have an
Hi Aditya,
BLE_ROLE_BROADCASTER should not have an impact on this. There is only one
place in the code where this is used:
include/nimble/nimble_opt_auto.h:37:#define NIMBLE_BLE_ADVERTISE
\
(MYNEWT_VAL(BLE_ROLE_BROADCASTER) || MYNEWT_VAL(BLE_ROLE_PERIPHERAL))
Best regards
Hi Michał,
Yes, that is what you should be seeing, because the message is being sent to
the GROUP; originator receives it as well.
If you change it to the destination / target address, you wouldn’t see Received.
To test this, you would require two devices.
Assuming Device A and B.
With all
Hi Aditya,
I enabled these flags:
BLE_ROLE_BROADCASTER: 1
BLE_ROLE_PERIPHERAL: 1
BLE_EXT_ADV: 1
And this is what i see after pushing the button a few times:
045120 #mesh-onoff STATUS
045121 #mesh-onoff STATUS: Sent !
045123 Received
045263 #mesh-onoff STATUS
045264
Hi Łukasz,
Disabling only the following flags in syscfg.yml allows the device to receive
but not send mesh messages.
BLE_ROLE_BROADCASTER: 1
BLE_ROLE_PERIPHERAL: 1
Disabling BLE_EXT_ADV: 1, flag allows the device to send and receive mesh
messages.
And as I said earlier
Hi Łukasz,
Am actually sending it to the Group Address.
In main.c :- Line 27
void button_cb(struct os_event *ev)
{
mesh_msg_send(MODEL_ID_CBOR_ACTION, GROUP_ADDR, "HELLO WORLD", 12);
}
And its relevant method :-
In mesh_init.c :- Line 138.
void mesh_msg_send(uint16_t model_id,
Hi Łukasz,
Thanks for looking into it.
As per the documentation,
To make use of it application needs to set BLE_EXT_ADV and
BLE_MULTI_ADV_INSTANCES at least to 1. Mesh will use last available
advertising instance for PB-ADV and second to last for PB-GATT and
PROXY
What would happen when the
Hi,
We found the issue which was related to latest controller changes.
Basically controller does not allow now to mix legacy HCI with ext adv HCI
which of course is good. The PR
https://github.com/apache/mynewt-nimble/pull/8 is fixed now.
I removed RFC and I plan to merge it soon.
@Aditya -
Hi Aditya,
Sorry for late answer.
Could you please provide btmon logs along with console logs so we can help
you to analyze what is going on?
Here is instruction how to get btmon logs:
https://www.codecoup.pl/blog/support-for-btmon-in-mynewt/
Thanks and best regards
Łukasz
On Fri, 27 Apr 2018
Hi Łukasz,
Any update on it? Were you able to check this ?
Bt_mesh_model_send does not work after enabling BLE_EXT_ADV..
Or, can you give me a sample code where it works so that I can check if there
is something am doing wrong.
Thanks,
Aditya Xavier.
> On 20-Apr-2018, at 3:56 PM, Aditya
Hi Łukasz,
Thanks, was able to build btshell + blemesh into nrf52832.
I think I found an issue with regards to bt_mesh_model_send method.
It seems bt_mesh_model_send is no longer working.
In my test app, I have remove all ble code, and using only blemesh ( auto
provisioning ) and send a
Hi Aditya,
I suggest to hack around flash map instead of removing code.
I would do something like this (hopefully calculations are OK).
+++ b/hw/bsp/nrf52dk/bsp.yml
@@ -41,11 +41,11 @@ bsp.flash_map:
FLASH_AREA_IMAGE_0:
device: 0
offset: 0x8000
-
Hi Łukasz,
Am using nrf52832, hence the problem of flash overflow.
Would create a test app, using btshell + blemesh + the flags which you
recommended, and test again.
Thanks,
Aditya Xavier.
> On 18-Apr-2018, at 12:29 PM, Łukasz Rymanowski
> wrote:
>
> Hi
Hi Aditya,
If there is flash overflow consider removing some features from the
configuration.
What HW are you using? We are running on nrf52840
BTW There is no special application. It is btshell plus those 4 flags (
BLE_EXT_ADV, BLE_MULTI_ADV_INSTANCES, BLE_MESH, BLE_MESH_SHELL) . Of
course you
Hi Michał, Aditya,
I just upload a new version of PR:
https://github.com/apache/mynewt-nimble/pull/8
It contains fixes for the problem mentioned above, however solution is bit
different from what Michał suggested.
@MIchał, could you take a look?
@Aditya, Could you be able to test it and give us
Hi Aditya,
Mesh is using Adv extensions under the hood if you have Łukasz's patch
and enable BLE_EXT_ADV and set BLE_MULTI_ADV_INSTANCES to at least 1.
Blemesh_shell has a command "init" which initializes mesh stack and
starts advertising Unprovisioned Mesh Beacon.
I tested this now and I
Hi Michał / Łukasz,
I have been trying to understand the blemesh_shell, and I fail to understand
how / where it is using the Advertisement extensions.
Basically, could you point me towards the difference if I need to implement, in
order to use blemesh instead.
From what I gathered /
Hi Aditya,
Please set BLE_MESH: 1 and BLE_MESH_SHELL: 1 and you should be able to
use both btshell and mesh shell. Let us know how that works for you.
Best regards
Michał
2018-04-03 7:56 GMT+02:00 Aditya Xavier :
> Hi Łukasz,
>
> Any pointers, as to what needs to be
Hi Łukasz,
Any pointers, as to what needs to be implemented from the blemesh_shell app ?
Thanks,
Aditya Xavier.
> On 02-Apr-2018, at 11:34 PM, Łukasz Rymanowski
> wrote:
>
> Second thought
>
> Aditya,
> Since I did not test it a lot, would it be possible to
Hi Aditya.
On Mon, Apr 2, 2018, 19:14 Aditya Xavier wrote:
> Hi Łukasz,
>
> Is there anything special required to get this working along with BLE ?
> For e.g. would the btshell app code for ADV_EXT work along with mesh with
> the provided patches ?
>
In addition to
Hi Łukasz,
Is there anything special required to get this working along with BLE ?
For e.g. would the btshell app code for ADV_EXT work along with mesh with the
provided patches ?
Mesh and BLE seems to compile however, am currently unable to get Mesh working.
Also, any reason why this was not
+1 - this is great, thanks Lukasz!
On 19 Mar 2018, at 6:36, Łukasz Rymanowski wrote:
> Hi All,
>
> I saw people asking around about possibility to advertise with non-mesh
> data while mesh is running on Mynewt. Well this is possible to do but of
> course it brings a lot of risk for mesh
Hi All,
I saw people asking around about possibility to advertise with non-mesh
data while mesh is running on Mynewt. Well this is possible to do but of
course it brings a lot of risk for mesh operations and especially for
friendship scenario. However I went ahead and added support for this in
27 matches
Mail list logo