Budget: 5000 USD Deadline: 7 days
Hello. I work with Python. I am ready for collaboration. Feel free to contact me.
Planned functionality in the test working version:
1. Creating, opening, saving a project
2. Adding devices
3. Adding tags
4. Reading and writing data to controllers
5. HMI visualization (adding diagrams and indicators).
6. Accidents, alarms
7. Logs + Reporting, graphs, data storage
8. Compiling an exe file (the scada itself, so it runs as a separate file, not through the development environment)
9. User roles and access
It may be necessary to additionally add:
10. Calculation logic = Tags read from the device often need to be processed: converted to engineering units, averaged, or used to create logical conditions.
Perhaps you can suggest what else needs to be added to create Scada in this version
Budget: 5000 USD Deadline: 7 days
Hello. I work with Python. I am ready for collaboration. Feel free to contact me.
Budget: 2000 USD Deadline: 15 days
Hello,
I’m ready to assist in developing the test working version of your SCADA system with the planned functionality you’ve described. I have experience in industrial automation software, data acquisition systems, and HMI visualization, and can help structure a scalable and reliable SCADA prototype.
The system will include core features such as project creation and saving, device and tag management, controller communication, HMI visualization, alarms, logs, reports, and executable compilation. I’ll also implement user roles with controlled access and integrate data handling logic for calculations, conversions, and condition processing.
Additionally, it would be useful to include system diagnostics, data backup and restore, trend recording for real-time monitoring, and a communication monitor to track device connectivity. These additions will make the SCADA version more robust and closer to a production-level tool.
Once you provide access to the current environment and tech stack, I can outline the architecture and roadmap for implementation.
Best regards,
Jeo Vincent Carretas
Budget: 1000 USD Deadline: 17 days
Hello! I guarantee quick and high-quality task execution. I work with attention to detail and am always focused on results.
Budget: 2275 USD Deadline: 17 days
Hello Anya
I am an experienced Python dev, and I'd suggest that you dm me, for me to get a glimpse of your project files, and I get to make the necessary corrections where needed. Have a good day.
Budget: 3200 USD Deadline: 30 days
Hello!
I can make your SCADA system a unified comprehensive tool, rather than just a set of disparate scripts. In my opinion, the project should have one central file that describes everything: devices, tags, alarm signals, calculations, screens, and reports. Based on this, the system will be able to build itself automatically. This means that when a new device is added or a tag is changed, the data will be transmitted throughout the project without the need to rewrite the code.
I will simplify the communication layer by using drivers for Modbus or OPC UA, and I will add a small scheduler that will handle polling, recording, and updating. Each tag can go through a calculation stage, so values can be transformed, averaged, or used in conditions without affecting the main code. Alarms will have the correct levels, delays, and confirmations, and they will always be logged in the audit trail.
For visualization, I will allow HMI screens to be dynamically loaded from the project file. This way, new diagrams or indicators will appear automatically. History will be stored in a time series format with the ability to quickly export graphs and reports. I will also add a simulation mode so that accidents and alarm signals can be safely tested before going live on real equipment.
All of this will be packaged into one executable file with clear user roles and access rights. If necessary, I can add intelligent flags to track sensor drift and a recipe mode for batch operations. This way, you will have a structured, easily extensible, and seamlessly functioning SCADA system.
Thank you!
Budget: 2500 USD Deadline: 50 days
Hello! 👋
We can implement a test working version of your SCADA system with the described functionality and offer an optimal architecture for future scaling.
💻 What we will do:
• Project structure (creation / saving / opening).
• Device and tag module (with the possibility of dynamic addition).
• Reading and writing data to controllers (Modbus TCP/RTU, OPC UA, MQTT).
• HMI visualization with dynamic diagrams, indicators, and alarms.
• Logs, reporting, trends, data storage in DB (InfluxDB / PostgreSQL).
• Compiling the project into a separate .exe.
• Role and access rights system.
• Calculation logic (normalization, filtering, engineering units, averaging, logical conditions).
⚙️ Additionally, we can offer:
• Runtime manager with automatic reconnection to controllers.
• Event engine for triggers and scripts.
• Built-in expression and formula editor for flexible logic.
• REST API for integrations.
⏱ Implementation time: 4–6 weeks
💰 Cost: from $2500 for a working MVP with complete documentation and installation.
We have experience in developing SCADA platforms and industrial equipment monitoring systems. We are ready to discuss the details and offer an optimal architecture for your tasks.
Здравствуйте. Судя по некоторым данным у Windows. Какая? И почему вас нужен именно .exe а не просто Python. Кроме того не совсем ясно. Scada имеет собственные средства визуализации, чем они не устраивают?
Brief I need a program in Python that runs on my PC (Windows) and creates faceless videos in the format of "voiceover + changing visuals from photos and clips" — like historical documentaries on YouTube (I will attach an example separately). I input a topic → the program writes a script, voices it, selects video/photos from free archives for each piece of text, edits them together → outputs a ready MP4. For me only. No website, no users, no sales. One user — me. How it works (step by step) 1. Input. A simple window opens. I enter the topic of the video and choose a voice from the list (**the list of voices is automatically pulled from ElevenLabs via API** — available on my account). I click "Create." (Second mode: insert a ready script instead of generating.) 2. Script. The program writes a script on the topic of the specified length via LLM API (OpenAI/Anthropic, key in settings). 3. Scene breakdown. LLM divides the script into scenes and returns for each: scene text; visual type: video or photo; search query (a detailed phrase of what should be in the frame); highlight mark + importance rating 1-10 (for intro, see below). 4. Voiceover. The text is sent to ElevenLabs API with the chosen voice → audio. The video sequence is cut to match the length of the audio for each scene. 5. Video/photo selection — from free sources via API (see the list below). A specific request is formed for each source (for accuracy). If one doesn't yield results — it tries the next. 6. Verification (maximum 3 steps per scene). Step 1: the program takes the first found option (video/photo) based on the request. Step 2: sends the frame to LLM — "does it fit the scene?". If it fits → stop. Step 3 (if it doesn't fit): the program switches to searching for photos (it's easier to find photos with an exact request than videos — this guarantees relevance) and takes it with enhanced motion (zoom + pan). No more than 3 steps per scene — this saves the LLM budget and ensures that the frame is relevant. 7. Assembly via ffmpeg/moviepy: clips and photos timed to the voiceover, photos are animated with zoom (Ken Burns effect), voice on top, simple transitions. Output: MP4 1920×1080. Video sequence rules (important — the program is responsible for this) First 60 seconds — intro teaser: a montage of the most impactful clips from the entire video (scenes with the highest importance rating that contain video) under a separate introductory text from LLM ("in this video you will learn..."), frames without explanations, creating intrigue. Then a transition to the main part. Alternation: video insert at least every ~6 seconds, no many photos in a row. Video share: at least ~40% of the time — live clips, the rest — photos with zoom. Frame length: 4-6 seconds (both photos and videos). No rapid cuts, no prolonged static shots. For purely historical topics where there is no video — photos with enhanced motion (zoom + pan). Sources (all free, with API) Modern video + photos: Pexels, Pixabay. Historical/archive (public domain): Wikimedia Commons, Archive.org, Library of Congress, Europeana, NASA, Smithsonian Open Access, Flickr Commons, openverse. Each source is a separate module, easy to add new ones. Use only public domain / free licenses with the right for commercial use. No parsing of other YouTube/sites, movie clips, images "from Google".Uniqueness of selection To ensure videos do not match others: take a random clip from the top results (not the first), maintain a database of already used clips (do not repeat), optionally — light processing of the clip (crop/mirror/speed). Options (enable/disable in settings) Photos only — if enabled, the video is assembled PURELY from photos, without video clips. Each photo MUST have motion (zoom and/or pan, Ken Burns effect) — even in this mode, there should be no static "dead" frames, minimal dynamics always. If disabled — standard mode (photos + video clips alternating, as per video sequence rules). No voiceover — if enabled, the video is assembled based on the text WITHOUT generating voice: the code DOES NOT call ElevenLabs and does not overlay voice (the video sequence is selected based on the text of the scenes, timing of frames — according to rules/parameters, without reference to audio). If disabled — it automatically generates voiceover based on the text through ElevenLabs, as usual. Atmospheric overlay — if enabled, a semi-transparent layer with floating particles/dust/glowing bokeh/light fog (particle/dust/bokeh/fog overlay, screen/add mode) is applied over the entire video sequence to make the frames look alive and cinematic. When installing the program, a set of 5-8 popular overlays (particles, dust,copybokeh, fog, light cinematic "grain") is placed in a local folder — I choose the needed one from the list. Adjustable transparency/brightness of the overlay (slider 0-100%), so the effect is neithercopytoo dull nor too pronounced — I adjust the strength myself. Ideally, the overlay should also be applicable to ALREADY finished videos separatelycopy(post-processing: take a ready MP4 → choose overlay → set transparency → save), not just during assembly. Where to get overlays for packaging (free license): Pexels, Pixabay (queriescopy"particle overlay", "bokeh overlay", "dust overlay", "light leaks", "film grain"), Mixkit, Videezy. The performer selects 5-8 pieces and places them in the program folder. Subtitles (embed or separate .srt). Clip processing for uniqueness. Resolution/format, video length, video share, search depth.Technical requirements Python. Modular structure (sources and LLM — through interchangeable modules, to easily replace or add). All API keys — in the settings file, not in the code. Simple window (GUI at the discretion of the performer — Tkinter/PyQt), launched by double-clicking. README with instructions, clear logs, comments in the code.What I provide API keys (ElevenLabs, LLM, where registration is needed — I will arrange). I will pay for any fees myself. Examples of video references (I will attach) and examples of topics for tests.Acceptance (ready if) I launch → window → I enter the topic, choose the voice → "Create" → I receive a ready MP4. The video sequence matches the meaning of the text, alternating video/photos, intro teaser 60 sec, voiceover on top. Works with at least 6 free sources, with fallback between them. Frame verification through LLM: max. 3 steps per scene (found → LLM checked → if not, photo with motion as a sure bet). Uniqueness: randomization + database of used. Only legal sources. There is a README, runs from scratch.Delivery of results All source code — in open view (all files), without obfuscation + compiled working version. I can run it myself from the sources according to the instructions (README: installation, keys, launch). The code must be clean, commented, and understandable, so **any other programmer can continue working** on it if needed (not tied to the author). **All everyday work — through the interface (buttons, fields, sliders, dropdown lists), WITHOUT the need to touch the code.** All settings (topic, voice, options, overlay, folders, length, formats) are changed in the program window, not by editing files. The code in hand — only as my property and insurance, not as a way to control the program. All rights to the code after payment — mine.Disk space management (important) The program should not fill up the disk. Implement: After assembling the video, all intermediate files (downloaded clips, temporary pieces, audio cuts) are automatically deleted — only the ready MP4 remains on the disk. Cache limit (parameter in settings, e.g., 5 GB): when exceeded, old downloaded files are automatically deleted (starting with the oldest). I set the folder for ready videos and for temporary files in the settings. Show how much space is occupied, and a button "clear cache" manually.Please specify in your response Examples of similar works (ffmpeg/moviepy, working with stock/archive APIs, ElevenLabs/LLM). Proposal for GUI. Does the solution use a database (which and why) — or are local files sufficient. Timeline and cost.
We are developing a real-time integration with the external service Trainer. We send structured snapshots of the state, receive recommendations, and display them in a pop-up bubble. The task is stable and complete data transmission for the correct operation of the Trainer. We are looking for a developer for the chain: data processing → HTTP communication → overlay. We need people with the following skills Python is good, Java basics, API HTTP/JSON-APIs The project is 90% ready but there are some inconsistencies
A local Python script needs to be developed to automatically fill a Google Sheet with data from the company's internal service. Main logic: 1. Connect to the Google Sheet. 2. Find rows where the ID is filled but two target values are missing. 3. Form a link based on the template: https://internal-service.example/item/{ID} 4. Retrieve the two values (via API, if it exists, otherwise via Playwright). 5. Write the values back to the Google Sheet. 6. Mark the row as processed. 7. Continue processing the next rows. Requirements: • Python • Google Sheets API • Priority to use the official API • If no API — Playwright • No OCR, screen recognition, or mouse coordinates • Confidential data must not be logged • Configuration via .env • Test mode (without writing to the sheet) • Do not process already filled rows • Batch write changes to Google Sheets • Proper error handling and retries It is necessary to provide: - source code; - requirements.txt; - example .env.example; - installation instructions; - running instructions; - brief architecture description. Before starting implementation, please: 1. Suggest an architecture. 2. List the necessary accesses. 3. Ask clarifying questions. 4. Indicate the cost, deadlines, and estimated number of hours.
As part of enhancing the cybersecurity level of our infrastructure, we need to abandon the practice of storing "eternal" and static API keys, passwords, and integration tokens in the configuration files (.env, appsettings.json, config.yaml) of our microservices. Business Goal: Create a single secure storage point for confidential data (secrets) with a mechanism for their automatic updating (rotation) in external systems on a schedule. Our other services will request current tokens "on the fly" via API, which will minimize damage in case of compromise of any system component.Security Model and Encryption (Crypto Core) No secret should be stored in plaintext in the database. Upon application startup, a Master Key is passed to the environment variables. If the key is missing or has an invalid length, the service should fail at the initialization stage with a clear error in the logs. Each secret is encrypted before being written to the database using this Master Key. Upon request, it is decrypted in memory and returned in the response body.Audit Logging (Audit Trail) Any action with secrets (creation, reading by the service, successful or unsuccessful rotation) must be recorded in a separate log file audit.log (or a separate table in the database). Strict Taboo: It is strictly prohibited to record the actual values of secrets in the audit log (neither in plaintext nor in encrypted form).
Need a specialist for writing parsers who can bypass CLOUDFRAME. Parsing of products occurs from sites with authorization. There are 10+ donors of varying complexity, with different levels of protection. Parsing of products occurs from sites with authorization. Parses data into a ready-made Mysql database + photographs on the server. It is necessary to write a parser according to the tasks described in the technical assignment and adapt the data to the existing database for full functionality on the site. Technical assignment and example donor upon request. Desktop parsers and C# are not considered.