On Thu, Mar 29, 2018 at 10:27:36PM +0530, Aditya Xavier wrote:
> Thanks for the tip. Would try that too..
>
> However, I have tried few variations to check the BLE side ( whether it was
> responsible for truncating )
>
> 1. I am able to send the same message using encoding only.. i.e. if I trigg
Thanks for the tip. Would try that too..
However, I have tried few variations to check the BLE side ( whether it was
responsible for truncating )
1. I am able to send the same message using encoding only.. i.e. if I trigger
the same using a button to send over ble.
i.e. BLE Connection,
Hi Aditya,
On Thu, Mar 29, 2018 at 08:52:08PM +0530, Aditya Xavier wrote:
[...]
> And it doesn’t work when am trying to trigger it from BLE.
>
> Assuming it was a memory issue, I used a mem_pool, mbuf, allocating
> and reserving space. However, problem remains.
>
> It usually encodes and sends
Hi Mynewt Team,
Am facing some weird problem trying to use CBOR encoding and decoding.
The structure am trying to do is the following.
Decode :-
{“field1”:1, “field2”:2, “field3”:[{“field4”:4,”field5”:5}]}
Encode :-
{“field1”:1, “field2”:2, “field3”:[{“field4”:4,”field5”:[1,2,3,4,5]}]}
Decodin
Hi Łukasz,
One question about the beacon content: since the URI Harsh field is
optional and all zero in this case, shouldn't the field be removed entirely?
Cheers,
Lichun
2018-03-29 21:00 GMT+08:00 Łukasz Rymanowski
:
> Hi,
>
> On 29 March 2018 at 14:16, Li-Chun Ko wrote:
> > I hope it works
Hi,
On 29 March 2018 at 14:16, Li-Chun Ko wrote:
> I hope it works this time!
>
> https://imgur.com/ZsqnidG
Thanks. Well this looks good to me. You can verify with Mesh Profile
Specification chapter 3.9.2 Unprovisioned Device beacon
Probably Wireshark does not decode it well, but I have not clue
I hope it works this time!
https://imgur.com/ZsqnidG
Cheers,
Lichun
2018-03-29 19:39 GMT+08:00 Michał Narajowski
:
> Hi Li-Chun,
>
> We still didn't get the picture. Please try using some hosting website
> like Imgur and send us the link to the picture.
>
> Best regards
> Michał Narajowski
>
>
Hi Li-Chun,
We still didn't get the picture. Please try using some hosting website
like Imgur and send us the link to the picture.
Best regards
Michał Narajowski
2018-03-29 13:20 GMT+02:00 Li-Chun Ko :
> Attached it again here.
>
> Łukasz Rymanowski 於 2018年3月29日 週四 下午6:33 寫道:
>>
>> Hi Lichun
>>
Attached it again here.
Łukasz Rymanowski 於 2018年3月29日 週四 下午6:33 寫道:
> Hi Lichun
>
> On 29 March 2018 at 12:28, Li-Chun Ko wrote:
> > Hi Łukasz,
> >
> > I am using the ADV bearer.
> >
> > I don't have the log at hand but you should get all the information from
> > the picture I attached in my p
Hi Lichun
On 29 March 2018 at 12:28, Li-Chun Ko wrote:
> Hi Łukasz,
>
> I am using the ADV bearer.
>
> I don't have the log at hand but you should get all the information from
> the picture I attached in my previous email. It was captured by a low cost
> Nordic sniffer.
Could you resend picture
Hi Łukasz,
I am using the ADV bearer.
I don't have the log at hand but you should get all the information from
the picture I attached in my previous email. It was captured by a low cost
Nordic sniffer.
I used bascally the same steps that were mentioned in the BLE mesh tutroial
except I changed t
Hi Lichun,
On 29 March 2018 at 10:42, Li-Chun Ko wrote:
> Hi all,
>
> I am running blemesh with mynewt 1.3.0 on Nordics pca 10040. Here are two
> questions I have:
>
> 1. Is it correct that the current mynewt release doesn't support the
> Provisioner's role? I wasn't able to find a way to do so.
Hi all,
I am running blemesh with mynewt 1.3.0 on Nordics pca 10040. Here are two
questions I have:
1. Is it correct that the current mynewt release doesn't support the
Provisioner's role? I wasn't able to find a way to do so.
2. I tried to use the mesh stack from Noridc to play the Provisioner
13 matches
Mail list logo