Job offer (CoAP protocol integration)

Go To Last Post
10 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Dears, I got commissioned to develop a prototype for a company, that during last months was already built and tested in many versions.

So they decided to "move" the device in a network system, upgrading the tech level and enabling it with the CoAP protocol (JSON messages replies, with a linux proxy client).

 

The problem: I am not skilled enough to write a firmware that implements CoAP and ethernet libraries, I am more an hardware engineer, to put it simple.
Moreover, I don't know how to deal with CoAP and I have not enough time to go back to study.

 

So, the job: I already posted on upwork the job but I'm getting difficulties to find people that knows MCU / embedded firmware design, on AtMel products.
To ease things I described the job about arduino, but seems with no real search improvement. The project can be developed this way too, thus I'm not a fan of it for professional products. 

The already made firmware is quite simple, so my idea is to let work an engineer on a completely blank project developing the CoAP structure, later on I will take care to prosecute adding the rest of the classes.

 

If someone is interested, please PM me, this should be a short project, and of course, I pay.
In case someone of you will accept and want to feel safer, you can join the project on upwork so protection from the organization is offered to both, up to you.

 

Thanks, 
B.Regards, 

D.

 

PS: Additional note about hardware: The hardware chosen from the commissioner is an arduino (for prototyping, they loves modular design).
The version used up today were many, the latest prototypes used Arduino Due and Arduino Mega Adk, connected on a custom PCB.
The wiser thing to do is to choose an MCU that is suitable for this hardware, I own the JTAGICE3 so I can download the firmware on this processors. So, the choice is yours for this actual development phase.
Lately I may develop the hardware keeping the processor type or moving on a different one. Another option is the SAM4S Xplained.
Let's interact.  

 

The only way of discovering the limits of the possible is to venture a little way past them into the impossible - Arthur C. Clarke

Last Edited: Wed. Oct 18, 2017 - 08:59 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

"CoAP" was new to me. For the benefit of others:

 

http://coap.technology/

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I never heard of this either, though in my case that doesn't mean much... my knowledge of networking protocols is minimal.

Here is the spec: https://tools.ietf.org/pdf/rfc72...

Seems complicated.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It's another networking stack.

 

Contiki: The Open Source OS for the Internet of Things

http://www.contiki-os.org/

...

 

6lowpan, RPL, CoAP

Contiki supports the recently standardized IETF protocols for low-power IPv6 networking, including the 6lowpan adaptation layer, the RPL IPv6 multi-hop routing protocol, and the CoAP RESTful application-layer protocol.

Find the code in ...

 

...

https://github.com/contiki-os/contiki/blob/master/apps/er-coap/er-coap.h 

...

/**
* \file
* An implementation of the Constrained Application Protocol (RFC).
* \author
* Matthias Kovatsch <kovatsch@inf.ethz.ch>

*/

...

Calipso Gateway - A HTTP/CoAP proxy and cache

https://github.com/sics-iot/calipso/tree/master/gateway

 

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Uhm, I was reading about Contiki but it seems projected on a wifi - ipv6 LowPan - bluetooth comm.

In this very project, the connection is only wired eth., anyway it may be a good approach.

 

About CoAP complexity, I read the relative source code of arduino libs and sketches, and it doesn't look very complex.
I may be wrong though...

The only way of discovering the limits of the possible is to venture a little way past them into the impossible - Arthur C. Clarke

Last Edited: Thu. Oct 19, 2017 - 04:13 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

El Tangas wrote:
Seems complicated

As the name suggests, it is specifically designed for "constrained" devices.

 

It is quite widely used on so-called "IoT" nodes - surprised that people haven't heard of it.

 

gchapman wrote:
It's another networking stack.

No, it's not a Stack - it would form (part of) one layer of a stack

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:
surprised that people haven't heard of it.
I guess that would depend on whether your day job is involved in IoT or not? For example my day job involves "Lucas-Kanade". Without looking it up would you know what that was if you are not involved in computer vision? Anyone doing CV will undoubtedly know what it is. (or AdaBoost or many other such things!). We all know "small areas" of computing.

Last Edited: Fri. Oct 20, 2017 - 08:30 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
I guess that would depend on whether your day job is involved in IoT or not?

Yes, of course.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The OP might post to the IoT community

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Indeed.

 

Another example of how the "communities" organisation is not fit for purpose.