We have our own Freescale K60 microcontroller board running MQX RTOS. We can POST (and most likely GET) data to Xively via TCP but our data plan is limited and TCP resends and chews up a ton of overhead. I have heard that UDP seems to be our best solution. We are having difficulty knowing how to GET and POST via UDP to Xively. We know we would have to write our own layer, any get tips? Also, are there any tricks to getting Xively to ack back to the microcontroller client?
Send 500 bytes to Xively via UDP (low data plan), using C on an MCU
353 Views Asked by Stephen West At
1
There are 1 best solutions below
Related Questions in C
- docker compose, vagrant and insecure Repository
- The docker compose will remain legacy volumes and couldn't now clear them
- Docker: how to set up file ownership in a data-only container?
- How could I launch multiple container at a time shared one Dockerfile
- Using docker-compose volumes_from option does not work
- Docker Compose with one Terminating Container
- Failed to limit memory with docker compose
- docker-compose error - unable to read file
- docker-compose get ID of a docker
- Can docker compose build image from different Dockerfiles at the same folder
Related Questions in TCP
- docker compose, vagrant and insecure Repository
- The docker compose will remain legacy volumes and couldn't now clear them
- Docker: how to set up file ownership in a data-only container?
- How could I launch multiple container at a time shared one Dockerfile
- Using docker-compose volumes_from option does not work
- Docker Compose with one Terminating Container
- Failed to limit memory with docker compose
- docker-compose error - unable to read file
- docker-compose get ID of a docker
- Can docker compose build image from different Dockerfiles at the same folder
Related Questions in UDP
- docker compose, vagrant and insecure Repository
- The docker compose will remain legacy volumes and couldn't now clear them
- Docker: how to set up file ownership in a data-only container?
- How could I launch multiple container at a time shared one Dockerfile
- Using docker-compose volumes_from option does not work
- Docker Compose with one Terminating Container
- Failed to limit memory with docker compose
- docker-compose error - unable to read file
- docker-compose get ID of a docker
- Can docker compose build image from different Dockerfiles at the same folder
Related Questions in EMBEDDED
- docker compose, vagrant and insecure Repository
- The docker compose will remain legacy volumes and couldn't now clear them
- Docker: how to set up file ownership in a data-only container?
- How could I launch multiple container at a time shared one Dockerfile
- Using docker-compose volumes_from option does not work
- Docker Compose with one Terminating Container
- Failed to limit memory with docker compose
- docker-compose error - unable to read file
- docker-compose get ID of a docker
- Can docker compose build image from different Dockerfiles at the same folder
Related Questions in XIVELY
- docker compose, vagrant and insecure Repository
- The docker compose will remain legacy volumes and couldn't now clear them
- Docker: how to set up file ownership in a data-only container?
- How could I launch multiple container at a time shared one Dockerfile
- Using docker-compose volumes_from option does not work
- Docker Compose with one Terminating Container
- Failed to limit memory with docker compose
- docker-compose error - unable to read file
- docker-compose get ID of a docker
- Can docker compose build image from different Dockerfiles at the same folder
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Xively currently supports only TCP-based protocols, which are:
You should try using HTTP with CSV data format first, it's very likely that the TCP payload will end up being small enough. For this purpose you can use Xively C library which is very portable. I have checked Freescale Application Note AN3907 and it looks lik porting of C library should be trivial, as "MQX RTCS sockets are compatible with Unix BSD 4.4". So you should be able to use existing POSIX communication layer, although you might need to include some different headers and make sure you have initialised the stack as well as configured the device either with a static IP or using DHCP. To account for amount of data being sent, please refer to the RX/TX counters provided by RTCS.
You could, however opt to use MQTT instead. You will end-up sending much smaller packets. Basic functionality for MQTT should be added to the Xively C library pretty soon.
If you are saying that you need a way of what you call "ack back to our controller", then MQTT is what you need for this. It's a publish/subscribe protocol, although you will need to keep a persistent connection.