nes-proj/examples/coap
2018-01-12 01:20:53 +01:00
..
resources renamed coap packet to coap message - for naming closer to RFC 2018-01-12 01:20:53 +01:00
resources-plugtest renamed coap packet to coap message - for naming closer to RFC 2018-01-12 01:20:53 +01:00
coap-example-client.c renamed coap packet to coap message - for naming closer to RFC 2018-01-12 01:20:53 +01:00
coap-example-observe-client.c CoAP: Various minor updates in CoAP example 2018-01-12 01:20:52 +01:00
coap-example-server.c CoAP: Various minor updates in CoAP example 2018-01-12 01:20:52 +01:00
in6addr.patch Move 'examples/coap-example' to 'examples/coap' 2017-11-01 09:31:20 +01:00
Makefile CoAP: Various minor updates in CoAP example 2018-01-12 01:20:52 +01:00
plugtest-server.c COAP: adapted CoAP examples to new API 2018-01-12 01:18:41 +01:00
plugtest.h CoAP: Various minor updates in CoAP example 2018-01-12 01:20:52 +01:00
project-conf.h CoAP: Various minor updates in CoAP example 2018-01-12 01:20:52 +01:00
README.md CoAP: Various minor updates in CoAP example 2018-01-12 01:20:52 +01:00
server-client-native.csc Move 'examples/coap-example' to 'examples/coap' 2017-11-01 09:31:20 +01:00
server-client-observe.csc Move 'examples/coap-example' to 'examples/coap' 2017-11-01 09:31:20 +01:00
server-client.csc Move 'examples/coap-example' to 'examples/coap' 2017-11-01 09:31:20 +01:00
server-only.csc Move 'examples/coap-example' to 'examples/coap' 2017-11-01 09:31:20 +01:00

A Quick Introduction to the Erbium (Er) CoAP Engine

EXAMPLE FILES

  • coap-example-server.c: A CoAP server example showing how to use the CoAP layer to develop server-side applications.
  • coap-example-client.c: A CoAP client that polls the /actuators/toggle resource every 10 seconds and cycles through 4 resources on button press (target address is hard-coded).
  • plugtest-server.c: The server used for draft compliance testing at ETSI IoT CoAP Plugtests. Erbium (Er) participated in Paris, France, March 2012 and Sophia-Antipolis, France, November 2012 (configured for native).

PRELIMINARIES

  • Make sure rpl-border-router has the same network stack and fits into mote memory.
  • Alternatively, you can use the native rpl-border-router together with the slip-radio.
  • For convenience, define the Cooja addresses in /etc/hosts fd00::0212:7401:0001:0101 cooja1 fd00::0212:7402:0002:0202 cooja2 ...
  • Get the Copper (Cu) CoAP user-agent from https://addons.mozilla.org/en-US/firefox/addon/copper-270430
  • Optional: Save your target as default target make TARGET=sky savetarget

COOJA HOWTO

###Server only:

make TARGET=cooja server-only.csc

Open new terminal

make connect-router-cooja
  • Start Copper and discover resources at coap://cooja2:5683/
  • Choose "Click button on Sky 2" from the context menu of mote 2 (server) after requesting /test/separate
  • Do the same when observing /test/event

###With client:

make TARGET=cooja server-client.csc

Open new terminal

make connect-router-cooja
  • Wait until red LED toggles on mote 2 (server)
  • Choose "Click button on Sky 3" from the context menu of mote 3 (client) and watch serial output

TMOTE SKY HOWTO

###Server:

  1. Connect two Tmote Skys (check with $ make TARGET=sky sky-motelist)

     make TARGET=sky coap-example-server.upload MOTE=2
     make TARGET=sky login MOTE=2
    
  2. Press reset button, get address, abort with Ctrl+C: Line: "Tentative link-local IPv6 address fe80:0000:0000:0000::::"

     cd ../rpl-border-router/
     make TARGET=sky border-router.upload MOTE=1
     make connect-router
    

    For a BR tty other than USB0:

     make connect-router-port PORT=X
    
  3. Start Copper and discover resources at:

     coap://[fd00::____:____:____:____]:5683/
    

Add a client:

  1. Change the hard-coded server address in coap-example-client.c to fd00:::::

  2. Connect a third Tmote Sky

     make TARGET=sky coap-example-client.upload MOTE=3
    

NATIVE HOWTO

With the target native you can test your CoAP applications without constraints, i.e., with large buffers, debug output, memory protection, etc. The plugtest-server is thought for the native platform, as it requires an 1280-byte IP buffer and 1024-byte blocks.

    make TARGET=native plugtest-server
    sudo ./plugtest-server.native

Open new terminal

    make connect-native
  • Start Copper and discover resources at coap://[fdfd::ff:fe00:10]:5683/
  • You can enable the ETSI Plugtest menu in Copper's preferences

Under Windows/Cygwin, WPCAP might need a patch in \usr\include\w32api\in6addr.h:

21,23c21
< #ifdef __INSIDE_CYGWIN__
<     uint32_t __s6_addr32[4];
< #endif
---
>     u_int __s6_addr32[4];
36d33
< #ifdef __INSIDE_CYGWIN__
39d35
< #endif

DETAILS

Erbium implements the Proposed Standard of CoAP. Central features are commented in coap-example-server.c. In general, coap supports:

  • All draft-18 header options
  • CON Retransmissions (note COAP_MAX_OPEN_TRANSACTIONS)
  • Blockwise Transfers (note COAP_MAX_CHUNK_SIZE, see plugtest-server.c for Block1 uploads)
  • Separate Responses (no rest_set_pre_handler() required anymore, note coap_separate_accept(), _reject(), and _resume())
  • Resource Discovery
  • Observing Resources (see EVENT_ and PRERIODIC_RESOURCE, note COAP_MAX_OBSERVERS)

TODOs

  • Dedicated Observe buffers
  • Optimize message struct variable access (directly access struct without copying)
  • Observe client
  • Multiple If-Match ETags
  • (Message deduplication)