IEC-104 Server Application development +Mysql DB store

₹37500-75000 INR

Posted 1 minute ago

•

Ends in 6 days

₹37500-75000 INR

Paid on delivery

I need a compact IEC 60870-5-104 server application that listens for client connections, accepts live measurement traffic, and writes every incoming value directly into a MySQL database. The scope is intentionally narrow: no dashboards, alarms, or status screens—just reliable capture and storage of live measurement values. Each record must carry the originating device name together with its IEC 104 point number so I can unambiguously identify the source later. Performance matters: the service should cope with simultaneous connections from several field devices without losing data or blocking. You are free to pick the implementation language and library—lib60870-C/C++, j60870, Python wrappers, Node IEC 104, or another proven stack—as long as it runs on Ubuntu 22.04 (headless) and connects cleanly to MySQL 8.0. Deliverables • Source code with clear in-line comments • systemd service file or equivalent start-up script • SQL script creating required tables and indexes • README with build steps, configuration parameters, and a quick test procedure using a sample IEC 104 client Acceptance criteria 1. When I send live measurement ASDU frames from a test client, every value appears in the database with correct device name and point number. 2. The service withstands a 24-hour soak test without memory leaks or dropped packets. 3. Rebooting the host auto-starts the server and resumes logging seamlessly. That’s the entire job—straightforward but must be rock-solid.

Project ID: 40816366

About the project

15 proposals

Open for bidding

Remote project

Active 6 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

15 freelancers are bidding on average ₹46,990 INR for this job

User Avatar
Flag of INDIA

Your IEC 60870-5-104 capture-and-store service on Ubuntu 22.04 is exactly the kind of narrow, well-scoped work I build well. I will use lib60870-C as the protocol core rather than a Python wrapper, because the C library handles concurrent APDU parsing with far lower per-connection overhead — critical when several field devices are sending spontaneous measurement traffic simultaneously and you cannot afford a slow parser blocking socket reads. Database layer: SQL schema with a composite index on device_name and point_number, plus an insert queue that batches commits under load so your 24-hour soak test produces zero dropped values. One problem your description does not mention: MySQL 8.0 default transaction isolation can cause write contention when multiple device threads commit simultaneously. I will set the table engine to InnoDB with explicit row-level locking in the insert path to prevent that. Deliverables match your list exactly: commented source, systemd unit file with Restart=always, SQL creation script, and a ready-to-run test client you can fire immediately to verify frame-to-row accuracy before sign-off. Delivery: 5 days, 52,500 INR. One question: are your field devices sending spontaneous data only (COT 3), or do you also need the server to respond to general interrogation commands (COT 6/7)?

User Avatar
Flag of TANZANIA, UNITED REPUBLIC OF

Hello, Your scope is clear: a lean IEC 60870-5-104 listener that never drops a measurement and stores every value in MySQL with device name plus point number so you can trace it later. I would split the receive path from the database writes so a slow insert never stalls the sockets. On Ubuntu 22.04 I would stand up a small service (Python or C with lib60870, after a quick spike to see which stays cleaner) that accepts several clients at once, parses live ASDUs, and pushes rows through a short queue into MySQL 8 with batched inserts and a solid unique key on device plus IOA. That way concurrent field traffic stays smooth and nothing gets lost under load. You get commented source, a systemd unit so a reboot brings logging back up on its own, the SQL for tables and indexes, and a README with build steps, config knobs, and a sample-client smoke test. Before handoff I would run a multi-client load check and a full-day soak so we catch leaks or dropped frames early. Happy to keep this tight around capture and storage only. No dashboards, just reliable logging that holds up in the field.

User Avatar
Flag of INDIA

Reliable real-time data capture is central to the business systems I develop, and my skills in Node.js, Python, MySQL, Linux, database programming, and system administration align well with this IEC 60870-5-104 server requirement. I can build a focused headless Ubuntu service that receives measurement values from concurrent field-device connections and stores each record with its device name and IEC 104 point number. My background in software architecture and database management supports a robust implementation rather than a dashboard-heavy solution. I can provide the complete source code, MySQL schema with suitable indexes, systemd startup configuration, inline comments, and a README covering setup, configuration, and testing. My experience with realtime systems and background processing is also relevant to handling incoming traffic without blocking database writes. I am ready to deliver a compact, maintainable application designed for reliable long-running operation and automatic restart after reboot. Choose me to build this IEC-104-to-MySQL service.

User Avatar
Flag of MOROCCO

Hi Vembaiyan, I will deliver an IEC‑104 server on Ubuntu 22.04 that captures measurements and stores device name, point number and value into MySQL 8 with systemd service, SQL schema and README. I can finish in 7 days and send a sample. Shall I start now?

User Avatar
Flag of INDIA

Hello Sir, I can develop the IEC 60870-5-104 server application you need, ensuring it reliably captures and stores live measurement values in MySQL. Using Python on Ubuntu 22.04, I will implement a solution that efficiently handles multiple simultaneous connections without data loss. I will provide detailed documentation, including build steps and a SQL script for table creation. I'm ready to start right away. Could you clarify if there are specific performance benchmarks you have in mind? Thanks, Deepak

User Avatar
Flag of UNITED STATES

Hi there, our senior engineering team at InvisionOne (Auroinfo LLC, Official Google Cloud & Shopify Partner) can architect and build your IEC-104 Server Application development +Mysql DB store solution (specifically covering Source code with clear in-line comments and systemd service file or equivalent start-up script) across 3 structured milestones: Milestone 1 delivers the core system architecture, data model, and working staging prototype; Milestone 2 completes end-to-end API, backend workflow, and UI integration; Milestone 3 covers automated QA, deployment, documentation, and long-term milestone support. Could you share any existing specs or workflow details so we can finalize the Milestone 1 plan?

User Avatar
Flag of INDIA

Hello, You need a lightweight IEC 104 server that reliably logs measurement values to MySQL, handling multiple field devices without dropping data. The tricky part here is ensuring no packets are lost during high traffic, especially since you're dealing with live measurements that can't afford delays or gaps. I'd use lib60870-C for the IEC stack, it's stable and handles the protocol efficiently. First, I'd set up the server to parse incoming ASDUs and immediately queue them for async database writes, avoiding blocking. Next, I'd add connection recovery so devices can reconnect without losing data if the link drops. For testing, I'd run a soak test with simulated traffic to verify stability under load. I delivered something similar last month, a Python-based service that processed real-time sensor data into PostgreSQL with zero drops. Do you have an estimate of the peak messages per second you expect from each device? That'll help tune the queue sizing.

User Avatar
Flag of PAKISTAN

Do you already have the IEC 104 device names and point number ranges documented, and should the database schema use one table per device or a single table with a device column? Here is what I will build for you: A compact IEC 60870-5-104 server running headless on Ubuntu 22.04 that listens for client connections from multiple field devices, accepts live measurement ASDU frames and writes every incoming value directly into MySQL 8.0. Each record carrying the originating device name and IEC 104 point number, with non blocking handling of simultaneous connections so no data is lost, delivered with commented source code, a systemd service file for auto start on reboot, a SQL script creating tables and indexes, and a README covering build steps, configuration parameters and a quick test using a sample IEC 104 client, targeting a clean 24 hour soak test with no memory leaks or dropped packets. With appreciation, Akif U.

User Avatar
Flag of MALAYSIA

Building this as a small Python service on the Fraunhofer c104 stack (lib60870-C underneath) fits the narrow scope: listen on port 2404, take M_ME_NA/NB/NC measurement ASDUs from several field devices and insert each value into MySQL 8.0 with device name and IOA. Each connection gets its own handler, and values go through a queue to a batched MySQL writer, so a slow insert never blocks the sockets. Device names come from a config file that maps source IP and common address to a name. Unknown sources are still logged, not dropped. One thing to confirm: do your devices connect as 104 clients and send monitor-direction frames themselves? That decides how the receive path is wired. Before final payment you get the SQL script, systemd unit, README with the test client steps, and the soak-test log with memory readings.

User Avatar
Flag of UNITED STATES

Your measurement logging service needs to capture every incoming IEC 104 value accurately, identify its originating device and point number, and store it in MySQL without blocking simultaneous connections or losing data. I will build a lightweight IEC 60870-5-104 server using a proven protocol library, with concurrent client handling, ASDU parsing, device identification, and reliable MySQL 8.0 storage. I will implement the database schema and indexes, connection management, and error handling, then configure a systemd service for automatic startup on Ubuntu 22.04. Deliverables will include commented source code, SQL scripts, deployment configuration, and a README with build instructions and sample-client testing. I will also perform multi-client testing and a 24-hour soak test to check stability and data integrity. How are field devices currently identified in your setup: by IP address, IEC 104 common address, or another device mapping? Best regards, Sehrish K

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

把喜欢的内容,留在你的新标签页。

打开我的订阅