On 04/17/2018 04:11 AM, 구자훈 wrote:
Hello, and Thanks to your answer.
I think I lacked my current environment and explanation of the
questions. Sorry..
I followed the instructions in the
[IoTivity Development on Raspberry Pi* 3] document and
confirmed that turning the LED on and off using
Hello, and Thanks to your answer.
I think I lacked my current environment and explanation of the questions.
Sorry..
I followed the instructions in the
[IoTivity Development on Raspberry Pi* 3] document and
confirmed that turning the LED on and off using server and client from the
raspberry
Hi All,
We've resolved the issue with Windows builders connecting and brought
Jenkins out of shutdown mode.
You should see Windows verification votes coming in shortly.
Thanks for your patience!
Regards,
Trevor Bramwell
On Mon, Apr 16, 2018 at 10:37:50AM -0700, Trevor Bramwell wrote:
> Hi All,
Hi All,
We're seeing several windows builders being spun up but unable to
connect to Jenkins, which has created a backlog of Windows jobs.
Jenkins is currently in shutdown mode to flush out the queue while we
work on diagnosing the connection issues.
Once we've identified the issue and gotten Wi
An architectural correction: the local OCF servers typically discover RD
and register with it not the other way around.
On Mon, Apr 16, 2018 at 3:37 PM, Khaled Elsayed
wrote:
> If the devices have public IP addresses (not recommended), they can be
> accessed with the help of a resource direct
If the devices have public IP addresses (not recommended), they can be
accessed with the help of a resource directory RD server. The RD should
perform local discovery of the devices and can share this information with
external end points.
If devices have non-routable addresses, then proxy+RD is t
Try this guide here and see if things work out
https://openconnectivity.org/wp-content/uploads/2017/12/OCF-IoTivity-RPi3-GSG.pdf
On Mon, Apr 16, 2018 at 3:33 AM, 구자훈 wrote:
> Hello,
>
> I don't know if it's right to ask a question here.
>
>
>
> I am trying to implement about [IoTivity Developme
Hi Greg,
There are two ways. Either use a BLE stack that has some port of
iotivity-lite or devise some proxy to interface with a native BLE device
using its own stack that has no OCF support.
For the first case, mynewt is one option and the other is Zephyr. Also for
Nordic modules, RIOT with its
There are lots of examples in the iotivity code base.
In resource/examples, there is a simpleclientserver.cpp which is a unified
example - but in the same directory there is also a simpleclient.cpp and a
simpleserver.cpp which show a divided approach. There are many other
examples in that directo
Hi,
In my tests, it takes IoTivity 1.3.1 about 40 seconds to report an error,
when a resource gets physically disconnected following the discovery.
My sequence:
- Client and server are on the same WiFi network.
- A client discovers a server resource, and keeps the resource "proxy"
(OcRe
10 matches
Mail list logo
