White Paper

5 Lessons Learned on

Inter Microcontroller Communication

Inter Microcontroller Communication

PRIVACY

I declare that I have read and fully understood the Privacy Notice and I hereby express my consent to the processing of my personal data by Reply SpA for marketing purposes, in particular to receive promotional and commercial communications or information regarding company events or webinars, using automated contact means (e.g. SMS, MMS, fax, email and web applications) or traditional methods (e.g. phone calls and paper mail).

Something went wrong with the form submit. Try again.

Industrial IoT

In the Internet of Things devices become connected to the Internet. However, in complex industrial environments devices also need to communicate with each other directly.

This means enabling Microcontrollers to send and receive messages as well as triggering tasks.

Direct Communication

Concept Reply was challenged with developing a solution for communication between two microcontrollers:
an existing application controller and an external Network Access Device powered by another microcontroller.

During This Process, the Team Learned Five Design Lessons:

Picture

Lesson #1:

How to avoid invalid message payload

Picture

Lesson #2:

How to fix uncoordinated responses

Picture

Lesson #3:

How to make sure, messages are delivered

Picture

Lesson #4:

How to avoid messages to be sent too often

Picture

Lesson #5:

How to handle limited memory sizes

Concept Reply

Picture

Concept Reply is an IoT software developer specializing in the research, development and validation of innovative solutions and supports its customers in the automotive, manufacturing, smart infrastructure and other industries in all matters relating to the Internet of Things (IoT) and cloud computing. The goal is to offer end-to-end solutions along the entire value chain: from the definition of an IoT strategy, through testing and quality assurance, to the implementation of a concrete solution.