subject:"\[dev\] Iotivity With ESP8266"

[dev] Iotivity with ESP8266

2016-12-29 Thread Matta Jayaram

Hi,

 Now I am Trying to create Multiple Resources with ESP8266 ( adding two
resources for same ESP8266 Device )

 From Eclipse Simulator I am unable to Discover these Resources and I
am getting 272 bytes of payload ,But for a Single Resource I am getting 209
bytes of payload & I am able to Discover it.

If I decrease the Payload size then I am able to Discover the Multiple
Resources.

I found this same issue is exists in previous version 1.1.0. and it fixed
in 1.1.1 version for Memory Constrained Devices like Arduino,ESP8266.

Case 1:I am able Discover multiple Resources by Decreasing the Payloadsize
(this is not a right way because I am unable to create resources with all
neccessary things )

Case 2: Even I tried to increasing the size of it before return
cborEncoderResult still I am unable to Discover Multiple resources from
Eclipse Simulator.

And one more thing that in Iotivity code I found these lines and I changed
it to other higher values

/* 320 is maximum size of a CoAP PDU for embedded
platforms...Arduino,ESP8266,...etc*/

/* 1400 is maximum size of a CoAP PDU for big platforms*/

then also I am unable to Discover Multiple Resources.

Please Suggest on it.


-- 

With Regard's'

Matta Jayaram

+91-9493952323

+91-8096796118
-- next part --
An HTML attachment was scrubbed...
URL:

[dev] Iotivity with ESP8266

2016-12-27 Thread Matta Jayaram

Dear Team ,

 Now I am Trying to create Multiple Resources with ESP8266 and I am
following Link referred & Provided by the Khaled Qorany and Khaled Elsayed.

While Creating Multiple Resources like light,fan,..etc .

>From Eclipse Simulator I am unable to Discover these Resources and I am
getting 272 bytes of payload ,But for a Single Resource I am getting 209
bytes of payload & I am able to Discover it.

File:/resource/csdk/security/src/pstatresource.c

Line Nums : 38 to 43

/** Default cbor payload size. This value is increased in case of
CborErrorOutOfMemory.

* The value of payload size is increased until reaching below max cbor
size. */

static const uint16_t CBOR_SIZE = 512;//***I changed it to 1024 & 2200
&4400***//

// Max cbor size payload.

static const uint16_t CBOR_MAX_SIZE = 4400;

Even still I am unable to Discover Multiple Resources when I clicking
FindResource option on Eclipse Simulator.

Please Suggest on it.


-- 

With Regard's'

Matta Jayaram

+91-9493952323

+91-8096796118
-- next part --
An HTML attachment was scrubbed...
URL:

[dev] Iotivity With ESP8266

2016-12-13 Thread Matta Jayaram

Dear Team,

I ported Iotivity to ESP8266 & I am able to control it From
Iotivity Ported Ubuntu PC. Now I want to control it from Iotivity based
Android App.That App has to Work Similar to Generic Eclipse Simulator
Iotivity Client Plugin to Initiate GET,PUT with Different Payloads, POST,
OBSERVE Queries. If any of you find Sample Iotivity Android Client App or
Web Interface please suggest it .



-- 

With Regard's'

Matta Jayaram

+91-9493952323

+91-8096796118
-- next part --
An HTML attachment was scrubbed...
URL:

[dev] Iotivity with Esp8266

2016-11-10 Thread Matta Jayaram

Dear Developers,

Ported Iotivity to ESP8266 Device.Now I am Trying To Control Esp8266
(Server) Device.

*CASE1:*Using one Esp8266 Device as Client and Another Esp8266 Device as
Server   *Device Discovery,GET,PUT...etc are Working **fine.*

*CASE2:*Now I am Trying To Control Esp8266 (Server) Device by Running the
occlient/simple client on Iotivity Ported Ubuntu PC.

  Here the Strict rule is that I am Not allowed to change anything on
ClientSide .cpp file (Ubuntu PC).

To achieve it I made some Changes in ocserver.cpp (Esp8266 server)file.

*Device Discovery is Working ,When I issueing the GET Request from Eclipse
Simulator or ./occlient -t 9 From Ubuntu terminal My ESP8266(Server) not
Responding to it and I am also verified even it is not entering into
the(**OCEntityHandlerCb
function)*

OCEntityHandlerResult OCEntityHandlerCb(OCEntityHandlerFlag flag,
OCEntityHandlerRequest * entityHandlerRequest, void */*callbackParam*/)

*{*

// This is the entity handler for the registered resource.

// This is invoked by OCStack whenever it recevies a request for this
resource.

*}*

Please Suggest on it,


-- 

With Regards,

Matta Jayaram,

Software Engineer

+91-8096796118
-- next part --
An HTML attachment was scrubbed...
URL:

[dev] Iotivity with ESP8266

2016-11-04 Thread Matta Jayaram

Dear Developers,

 I have Ported Iotivity to the ESP8266. I have also gone through
Aurdino sample programs and wrote simple server program for ESP8266.

For this Discovery method is working properly  but facing issues with
GET,PUT,etc.. methods as getting OC_STACK_COMM_ERROR.

If any of you working on this, please suggest.




-- 

  Thanks & Regards,

Matta Jayaram,

Software Engineer

+91-8096796118
-- next part --
An HTML attachment was scrubbed...
URL:

[dev] Iotivity with ESP8266

2016-11-04 Thread ASHOKBABU CHANNA

An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: 201602111742151_N3WZA6X7.png
Type: image/png
Size: 33527 bytes
Desc: not available
URL:

[dev] IoTivity on ESP8266

2015-09-02 Thread Damian Rakowski

@Rees, Kevron

Hello!

At the moment support code isn't in upstream IoTivity.

For more details, please refer to my answer to Morrow, Joseph L's question.

Regards,
Damian Rakowski
d.rakowski at samsung.com 
Samsung R Poland

@Morrow, Joseph L

Hi!

We are willing to provide all the required assistance to help setting up 
IoTivity on ESP8266 on your machines.
Regarding directly uploading source code to IoTivity, due to external 
constraints we cannot share it right now. It is however possible we will 
be able to in near future.
We plan to release an article, a how-to, explaining the finer details 
and issues arising when porting ESP8266 to IoTivity.

Regards,
Damian Rakowski
d.rakowski at samsung.com 
Samsung R Poland






PS: I'm sorry if You got this message twice. I have sent it yesterday, 
but I believe it didn't reach the destination.

On 08/31/2015 06:55 PM, Rees, Kevron wrote:
> That's awesome news.  Is the support code in upstream iotivity now?
>
> On Mon, Aug 31, 2015 at 9:16 AM, Damian Rakowski 
> mailto:d.rakowski at samsung.com>> wrote:
>
> Hi Everyone!
>
> We have noticed some room for growing the pool of WiFi-enabled
> platforms in IoTivity. During our prototyping activity, we decided
> to port ESP8266!
>
> I have included some photos, to let you know how it looks like.
> You can find the at the end of this e-mail.
>
>   * The small chip is ESP8266-12 itself.
>   * The small device is just an ESP8266 with power input and some
> pins to reprogram it. We use it for ex. proxy'ing non-IoTivity
> devices to IoTivity.
>   * The big one is a motion detector, which can be seen in work on
> the nearby photo.
>
> It was developed using ESP8266 port to Arduino
> , so almost all the code
> written for Arduino can be easily reused with ESP8266.
>
> For the technical minded, here are ESP8266 parameters. Please note
> there are various variants, so we chose one of the most common
> options (ESP8266-12)
>
> CPU Speed Flash Memory size   Instruction RAM sizeData RAM
> size  Number of GPIO portsDimensions  Price
> 80MHz 512kB   32kB80kB9   24mm * 16mm about $3
>
> It has some other nice features, such as
>
>   * The option of being either an Access Point or WiFi Station (or
> even both at once!).
>   * HTTP Server functionality
>   * DNS/mDNS support, which means it will automatically appear in
> a network with a nice hostname, instead of having to enter the
> IP address
>   * EEPROM memory, as well as a File System
>   * Support for the most common communication protocols, such as
> I2C, SPI, Serial
>   * Interrupts via GPIO pins
>   * ADC pin
>
> If you have any questions, please contact me.
>
> Regards,
> Damian Rakowski
> d.rakowski at samsung.com 
> Samsung R Poland
>
> ___
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> 
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
>
>

-- next part --
An HTML attachment was scrubbed...
URL:

[dev] IoTivity on ESP8266

2015-09-01 Thread Damian Rakowski

@Rees, Kevron

Hello!

At the moment support code isn't in upstream IoTivity.

For more details, please refer to my answer to Morrow, Joseph L's question.

Regards,
Damian Rakowski
d.rakowski at samsung.com <mailto:d.rakowski at samsung.com>
Samsung R Poland

@Morrow, Joseph L

Hi!

We are willing to provide all the required assistance to help setting up 
IoTivity on ESP8266 on your machines.
Regarding directly uploading source code to IoTivity, due to external 
constraints we cannot share it right now. It is however possible we will 
be able to in near future.
We plan to release an article, a how-to, explaining the finer details 
and issues arising when porting ESP8266 to IoTivity.

Regards,
Damian Rakowski
d.rakowski at samsung.com <mailto:d.rakowski at samsung.com>
Samsung R Poland

On 08/31/2015 06:55 PM, Rees, Kevron wrote:
> That's awesome news.  Is the support code in upstream iotivity now?
>
> On Mon, Aug 31, 2015 at 9:16 AM, Damian Rakowski 
> mailto:d.rakowski at samsung.com>> wrote:
>
> Hi Everyone!
>
> We have noticed some room for growing the pool of WiFi-enabled
> platforms in IoTivity. During our prototyping activity, we decided
> to port ESP8266!
>
> I have included some photos, to let you know how it looks like.
> You can find the at the end of this e-mail.
>
>   * The small chip is ESP8266-12 itself.
>   * The small device is just an ESP8266 with power input and some
> pins to reprogram it. We use it for ex. proxy'ing non-IoTivity
> devices to IoTivity.
>   * The big one is a motion detector, which can be seen in work on
> the nearby photo.
>
> It was developed using ESP8266 port to Arduino
> <https://github.com/esp8266/Arduino/>, so almost all the code
> written for Arduino can be easily reused with ESP8266.
>
> For the technical minded, here are ESP8266 parameters. Please note
> there are various variants, so we chose one of the most common
> options (ESP8266-12)
>
> CPU Speed Flash Memory size   Instruction RAM sizeData RAM
> size  Number of GPIO portsDimensions  Price
> 80MHz 512kB   32kB80kB9   24mm * 16mm about $3
>
> It has some other nice features, such as
>
>   * The option of being either an Access Point or WiFi Station (or
> even both at once!).
>   * HTTP Server functionality
>   * DNS/mDNS support, which means it will automatically appear in
> a network with a nice hostname, instead of having to enter the
> IP address
>   * EEPROM memory, as well as a File System
>   * Support for the most common communication protocols, such as
> I2C, SPI, Serial
>   * Interrupts via GPIO pins
>   * ADC pin
>
> If you have any questions, please contact me.
>
> Regards,
> Damian Rakowski
> d.rakowski at samsung.com <mailto:d.rakowski at samsung.com>
> Samsung R Poland
>
> ESP8266 photoSmall device based on ESP8266Motion detector based on
> ESP8266
> ESP8266 in action
>
> ___
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> <mailto:iotivity-dev at lists.iotivity.org>
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
>
>

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150901/386b290f/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 347960 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150901/386b290f/attachment.jpe>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 799406 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150901/386b290f/attachment-0001.jpe>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 724802 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150901/386b290f/attachment-0002.jpe>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1467624 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150901/386b290f/attachment.png>

[dev] IoTivity on ESP8266

2015-08-31 Thread Damian Rakowski

Hi Everyone!

We have noticed some room for growing the pool of WiFi-enabled platforms 
in IoTivity. During our prototyping activity, we decided to port ESP8266!

I have included some photos, to let you know how it looks like. You can 
find the at the end of this e-mail.

  * The small chip is ESP8266-12 itself.
  * The small device is just an ESP8266 with power input and some pins
to reprogram it. We use it for ex. proxy'ing non-IoTivity devices to
IoTivity.
  * The big one is a motion detector, which can be seen in work on the
nearby photo.

It was developed using ESP8266 port to Arduino 
, so almost all the code written 
for Arduino can be easily reused with ESP8266.

For the technical minded, here are ESP8266 parameters. Please note there 
are various variants, so we chose one of the most common options 
(ESP8266-12)

CPU Speed   Flash Memory size   Instruction RAM sizeData RAM size 
Number of GPIO portsDimensions  Price
80MHz   512kB   32kB80kB9   24mm * 16mm about $3

It has some other nice features, such as

  * The option of being either an Access Point or WiFi Station (or even
both at once!).
  * HTTP Server functionality
  * DNS/mDNS support, which means it will automatically appear in a
network with a nice hostname, instead of having to enter the IP address
  * EEPROM memory, as well as a File System
  * Support for the most common communication protocols, such as I2C,
SPI, Serial
  * Interrupts via GPIO pins
  * ADC pin

If you have any questions, please contact me.

Regards,
Damian Rakowski
d.rakowski at samsung.com 
Samsung R Poland

ESP8266 photoSmall device based on ESP8266Motion detector based on ESP8266
ESP8266 in action
-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: esp8266.jpg
Type: image/jpeg
Size: 347960 bytes
Desc: not available
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: proxy.jpg
Type: image/jpeg
Size: 799406 bytes
Desc: not available
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: motion.jpg
Type: image/jpeg
Size: 724802 bytes
Desc: not available
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: freeze.png
Type: image/png
Size: 1467624 bytes
Desc: not available
URL:

[dev] IoTivity on ESP8266

2015-08-31 Thread Morrow, Joseph L

Hi Damian,

This is great!

Will you be officially adding this support to the IoTivity repo?

Thanks,

Joey Morrow

From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Damian Rakowski
Sent: Monday, August 31, 2015 9:17 AM
To: iotivity-dev at lists.iotivity.org
Subject: [dev] IoTivity on ESP8266


Hi Everyone!

We have noticed some room for growing the pool of WiFi-enabled platforms in 
IoTivity. During our prototyping activity, we decided to port ESP8266!

I have included some photos, to let you know how it looks like. You can find 
the at the end of this e-mail.

  *   The small chip is ESP8266-12 itself.
  *   The small device is just an ESP8266 with power input and some pins to 
reprogram it. We use it for ex. proxy'ing non-IoTivity devices to IoTivity.
  *   The big one is a motion detector, which can be seen in work on the nearby 
photo.

It was developed using ESP8266 port to 
Arduino<https://github.com/esp8266/Arduino/>, so almost all the code written 
for Arduino can be easily reused with ESP8266.

For the technical minded, here are ESP8266 parameters. Please note there are 
various variants, so we chose one of the most common options (ESP8266-12)
CPU Speed

Flash Memory size

Instruction RAM size

Data RAM size

Number of GPIO ports

Dimensions

Price

80MHz

512kB

32kB

80kB

9

24mm * 16mm

about $3


It has some other nice features, such as

  *   The option of being either an Access Point or WiFi Station (or even both 
at once!).
  *   HTTP Server functionality
  *   DNS/mDNS support, which means it will automatically appear in a network 
with a nice hostname, instead of having to enter the IP address
  *   EEPROM memory, as well as a File System
  *   Support for the most common communication protocols, such as I2C, SPI, 
Serial
  *   Interrupts via GPIO pins
  *   ADC pin

If you have any questions, please contact me.

Regards,
Damian Rakowski
d.rakowski at samsung.com<mailto:d.rakowski at samsung.com>
Samsung R Poland
[ESP8266 photo][Small device based on ESP8266][Motion detector based on ESP8266]
[ESP8266 in action]
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150831/efc7f639/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4084 bytes
Desc: image002.jpg
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150831/efc7f639/attachment.jpg>
-- next part --
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 4535 bytes
Desc: image004.jpg
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150831/efc7f639/attachment-0001.jpg>
-- next part --
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 7005 bytes
Desc: image006.jpg
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150831/efc7f639/attachment-0002.jpg>
-- next part --
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 60570 bytes
Desc: image008.jpg
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150831/efc7f639/attachment-0003.jpg>

[dev] IoTivity on ESP8266

2015-08-31 Thread Rees, Kevron

That's awesome news.  Is the support code in upstream iotivity now?

On Mon, Aug 31, 2015 at 9:16 AM, Damian Rakowski 
wrote:

> Hi Everyone!
>
> We have noticed some room for growing the pool of WiFi-enabled platforms
> in IoTivity. During our prototyping activity, we decided to port ESP8266!
>
> I have included some photos, to let you know how it looks like. You can
> find the at the end of this e-mail.
>
>- The small chip is ESP8266-12 itself.
>- The small device is just an ESP8266 with power input and some pins
>to reprogram it. We use it for ex. proxy'ing non-IoTivity devices to
>IoTivity.
>- The big one is a motion detector, which can be seen in work on the
>nearby photo.
>
> It was developed using ESP8266 port to Arduino
> <https://github.com/esp8266/Arduino/>, so almost all the code written for
> Arduino can be easily reused with ESP8266.
>
> For the technical minded, here are ESP8266 parameters. Please note there
> are various variants, so we chose one of the most common options
> (ESP8266-12)
> CPU Speed Flash Memory size Instruction RAM size Data RAM size Number of
> GPIO ports Dimensions Price 80MHz 512kB 32kB 80kB 9 24mm * 16mm about $3
>
> It has some other nice features, such as
>
>- The option of being either an Access Point or WiFi Station (or even
>both at once!).
>- HTTP Server functionality
>- DNS/mDNS support, which means it will automatically appear in a
>network with a nice hostname, instead of having to enter the IP address
>- EEPROM memory, as well as a File System
>- Support for the most common communication protocols, such as I2C,
>SPI, Serial
>- Interrupts via GPIO pins
>- ADC pin
>
> If you have any questions, please contact me.
>
> Regards,
> Damian Rakowski
> d.rakowski at samsung.com
> Samsung R Poland
> [image: ESP8266 photo][image: Small device based on ESP8266][image:
> Motion detector based on ESP8266]
> [image: ESP8266 in action]
>
> ___
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150831/8d0e37d5/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: proxy.jpg
Type: image/jpeg
Size: 799406 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150831/8d0e37d5/attachment.jpg>
-- next part --
A non-text attachment was scrubbed...
Name: freeze.png
Type: image/png
Size: 1467624 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150831/8d0e37d5/attachment.png>
-- next part --
A non-text attachment was scrubbed...
Name: motion.jpg
Type: image/jpeg
Size: 724802 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150831/8d0e37d5/attachment-0001.jpg>
-- next part --
A non-text attachment was scrubbed...
Name: esp8266.jpg
Type: image/jpeg
Size: 347960 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150831/8d0e37d5/attachment-0002.jpg>

[dev] Iotivity with ESP8266

[dev] Iotivity with ESP8266

[dev] Iotivity With ESP8266

[dev] Iotivity with Esp8266

[dev] Iotivity with ESP8266

[dev] Iotivity with ESP8266

[dev] IoTivity on ESP8266

[dev] IoTivity on ESP8266

[dev] IoTivity on ESP8266

[dev] IoTivity on ESP8266

[dev] IoTivity on ESP8266

11 matches

Site Navigation

Mail list logo

Footer information