Reliable data from field to system

IoT, communication and automation integration

We develop systems that transmit sensor and device data to the automation infrastructure or server application in IoT, that is, internet of things, projects. We evaluate LoRa, 4G/5G, BLE, Wi-Fi and wired communication according to distance, delay, energy and site conditions. We test custom boards, gateways, embedded software and data transfer end-to-end.

Describe your project Explore the technical scope
Testing of external sensor, encased IoT device and electronic circuit board gateway together
Representative application image.
WirelessLoRa, 4G/5G, BLE, Wi-Fi
IntegrationDevice + automation + server
SelectionAccording to site and energy needs

Your project, your product

Developed confidentially and delivered with source files.

We may work with a confidentiality agreement (NDA) before sharing technical details. At the end of the project, we deliver the source codes, design files and technical documents we have developed to you.

  • NDA before sharing technical information
  • Clear deliverables agreed at the outset
  • Source and technical files at the end of the project
Our confidentiality and delivery process

VOMRO engineering approach

We first ask what the connection is supposed to accomplish.

Technology selection in an IoT project cannot be made only by looking at the communication distance. How often will data be sent, will the device be battery operated, will it receive commands, where will it be installed and what will it do when disconnected? These questions affect hardware, antenna, protocol and server architecture together. VOMRO conceives the connection as a system that complements the function of the product.

Collecting production data from a machine, monitoring field sensors and configuring a product through a phone involve different connectivity requirements. Where an existing PLC, control cabinet or business software is involved, its interfaces are reviewed. How off-the-shelf modules are combined with custom electronics and software depends on the project's requirements and long-term maintainability.

01

LoRa, cellular connection, BLE or Wi-Fi

LoRa may suit field nodes with low data volumes and energy requirements; network topology and message frequency follow the use case. LoRa and LoRaWAN have different scopes: choosing LoRaWAN also brings the network server, gateway and device joining procedure into the design. The appropriate approach is determined for the complete system to be installed.

For 4G/5G, operator coverage, modem capabilities, antenna and energy consumption are examined together. BLE may suit nearby setup and device interaction, while Wi-Fi may provide access to an existing local network. Field performance is not promised solely from a module's catalogue range; connection checks are planned in the actual environment.

  • Data amount, latency and power budget
  • Antenna, coverage and installation conditions
  • Network topology and device connection method
Terminal and sensor connections on a custom DIN-rail-mounted interface board
Representative application image.
02

Interface development suitable for existing automation

The system in the field does not consist only of wireless devices. It may be necessary to receive data via RS485/Modbus, CAN, Ethernet, digital input output or analog signals. Signal levels, isolation, grounding and noise conditions are taken into account in the design of the electronic interface. If there is a gateway requirement, data mapping between different protocols is clearly defined.

Reading data from a machine and sending control commands to the machine carry different responsibilities. Authorizations, command confirmation, behavior on communication loss and local control priority are determined by the application. Automation connection is not activated without evaluating the effects on the protection and safety functions of the existing machine.

  • Data exchange with PLC and control systems
  • Protocol converter and gateway development
  • Isolation, signal compatibility and command limits

Industry 4.0 infrastructure to collect production data from the machine

Measuring table with oscilloscope and power supplies in electronics laboratory
Signal and supply measurement in laboratory environment for electronic systems.
03

Outage, maintenance and server integration

A data stream is established that can track the time of the measurement, the identity of the device, and the processing status of the message. Local buffer, retry, connection state recording and remote parameter management are developed as needed. Connection protection and device authentication are planned in line with the selected hardware and network capabilities.

Pilot testing checks weak connections, restarting and recovery after interruptions as well as confirming data arrival. End-to-end checks use the server dashboard or existing API. Deliverables may include protocol documentation, connection settings, device software and technical information for field installation; mobile operator and network service requirements are stated separately.

  • Offline recording and data completion approach
  • Device ID and connection status tracking
  • Pilot field and end-to-end communication testing

API, database and monitoring panel development for IoT devices

Devices connected to automation and server via LoRa, cellular connection, BLE and Wi-Fi
Conceptual representation of the technical process.

How it works

A clear process from start to delivery.

Not every project looks the same; however, the measurable requirement, controlled revision, and field verification steps remain unchanged.

  1. 01

    We define the field

    We evaluate distance, data flow, power supply and existing infrastructure.

  2. 02

    We choose the link

    We compare wireless and wired options with the actual requirements of the product.

  3. 03

    We combine the layers

    We develop the electronic interface, firmware and server protocol together.

  4. 04

    We test it in the field

    We verify the coverage, interruption, and reconnection behavior in the pilot scenario.

Frequently asked questions

Before starting the project

The technical scope, deliverables and test plan are clarified together according to the requirements of your project.

Should we use LoRa or 4G/5G?

The decision depends on data volume, transmission frequency, coverage, power supply and network cost. No single technology is the best choice for every project; it is assessed alongside field conditions.

Can you import data from our existing PLC or machine?

A suitable interface can be developed after examining the accessible protocol, port and usage rights. The scope and risks of monitoring alone and remote control are assessed separately.

Can you give the exact distance for wireless communication?

Range depends on the antenna, placement, obstacles, interference and selected technology. Target coverage is defined for the project, and results are assessed through field or representative pilot testing.

Can we work with NDA before sharing technical details?

Yes. We can complete the NDA arrangements together before you share your project's technical details.

Do you deliver source codes and technical files at the end of the project?

Yes. We deliver the source codes, design files and technical documents we developed within the scope of the project to you at the end of the project. The delivery list and file formats are clarified at the beginning.

Related content

We design the behavior of the device

Embedded software and embedded system development

 From device to management panel

Server software and device management

 Technical capability

Industry 4.0 and industrial IoT infrastructure development

 Technical decision guide · Connected products

How to plan device management and OTA updates for connected products

All product development services

Let's start with your idea

Let's talk about the product you dream of and the need you want to solve.

Submit a project request +90 534 487 98 02