ESP-ForumSCADAscada.esp-forum.com ESP-ForumArtificial Lift & ESP Systems

Version history

Public release notes for ESP-Forum SCADA. Newest first.

0.12.7

  • Faster web interface: the home page and the well page open 3-4 times faster, one-week trends load about 4 times faster.
  • Background browser tabs no longer poll the server.
  • Clearer marks for VSD archive records in the log.
  • The logo in the interface and in PDF archive reports now matches the website.

0.12.6

  • After the link is restored, records from the VSD's own archive are shown in the log and trends with the VSD time, not snapped to the polling grid. Such rows are marked in the log.
  • Telegram sign-in: confirm with one tap in Telegram, operator access.
  • Profile window under the user name: password change and Telegram setup.
  • Improved authentication and account protection.

0.12.5

  • On the home page the administrator sees a server health plate with numbers: free disk space and the last data snapshot.
  • Two-factor login for the administrator and production engineer is set up only on the server. The web UI has no enrollment form and does not show the secret.
  • The features page now covers command confirmation, the action log, time zones, backup and server health.
  • Telegram notifications: well start and stop (all causes or protection trips only), and for the administrator link loss, link restore and server health. Each user links Telegram and picks the events and the notification language. Everything is off by default.
  • The well page header is reorganized: the last start and stop are shown under the well name, buttons are grouped.
  • The version number in the UI links to the version history.
  • Well and link status messages are shown in the interface language.
  • Fixed short gaps in trends while the link was stable.
  • Improved user authorization.

0.12.4

  • Security patch: stronger session checks and web UI hardening.

0.12.3

  • VSD control commands are confirmed by typing a word: start, stop, setpoint change and U/F curve.
  • Improved user authorization.
  • User action log for the administrator: logins, VSD commands, setpoint changes (old and new value), settings changes. Kept for 3 years.
  • Well page log: VSD time, server time or any time zone, the choice is saved per user. The scroll position stays when the period or step changes.
  • PDF archive export: time zone selection, the zone is shown in the document header. The file name contains the well number, field and dates.
  • VSD event history records appear in the log and the PDF as lines at the time of the event.
  • VSD clock corrections are recorded in the archive. Optional automatic VSD clock correction.
  • Well header status: no link is shown in yellow, a stopped VSD in red.
  • Improved modem check on the well. Reworked modem window.
  • Settings windows open without inner scroll bars.
  • Daily backup of server data. The administrator sees server health: free disk space and the result of the last backup.
  • More reliable database writes while polling and the web interface run at the same time.

0.12.2

  • Well page log: run data, starts and stops, link loss and setpoint changes, newest first. Click the heading to open the archive export.
  • Starts and stops show up in the log and the archive right away. The cause is a separate line: remote with the user name, operator at the VSD, automatic or a digital input.
  • Setpoint changes: old and new value, who changed it (remote with the user name or at the VSD), time from the VSD log.
  • The polling status in the well header is more compact and shows when there is no link to the well.
  • The English and Kazakh UI and the PDF archive now translate setpoint names, protection modes, stop reasons and units.
  • More reliable polling: fixed repeated server-side drops of modem connections.

0.12.1

  • Built-in well archive on the server: operating data, starts and stops, communication outages. Kept for 3 years.
  • Archive export to PDF: pick a date range and a 5, 10, 15, 30 or 60 minute step, in VSD or server time. Starts and stops show the exact time they happened, and the stop reason is spelled out. Current VSD setpoints are added to the file. The document is protected from editing and digitally signed.
  • The archive is retained when a well is deleted. The admin can bring a well back or export its archive. The archive can be erased only after explicit confirmation.

0.11.5

  • VSD clock: the well page shows VSD time, clock drift and server time. The time zone is detected automatically or set by hand. The production engineer or admin can sync the VSD clock.
  • After a communication outage, trend gaps are filled from the VSD's own archive. The VSD event log is stored on the server.
  • The well page adapts to screen width: the controller and the V/f curve keep their size, and on medium-width screens trends move below and stay within the panel. Fixed a browser freeze when zooming the page.
  • Improved access control. The admin can view the interface with a selected user's permissions, without leaving the current page.
  • Interface wording refined in all three languages.

0.11.4

  • Access control: fields are grouped into sections, and each user sees only their own fields and wells.
  • The server settings window runs from the system tray and starts at Windows sign-in. Fixed the window hanging when the server stops. Uptime now counts from the actual server start.
  • Home page: a field is created with a button right inside its section. Fixed closing of one of the dialogs. Removed redundant text from the dialog status strip.
  • Added connection diagnostics for field equipment when migrating from a previous SCADA system.

0.11.3

  • Modem header on the well page: clearer handling of modem replies.

0.11.2

  • Trends panel: compact height by default. A button expands it to the full left column and back. The choice is saved per user and well.
  • Trends expand/collapse control shows a single icon. Scale minima and time labels sit on separate rows so edge times do not overlap.

0.11.1

  • Display layout and trend series are stored per user and per well, with reset to the well baseline.
  • Trends: one shared chart, drag a curve to shift it, drag a scale to zoom, a scale per series (shared for downhole TMS), compact axis labels. Auto layout stacks the curves. The full data range stays in view.
  • Trends panel height matches the full left column.
  • Setpoint refresh/write and start/stop share one queue with the poller. Fixed a false pause on setpoint refresh.
  • Modem session handling and well-tile status cues improved. Authorization and link checks refined.
  • Well status opens a 24-hour error log. The status strip in dialogs no longer shifts the layout.
  • Refined operator messages on GPRS link status.

0.10.x

  • GPRS link: polling continues while the TCP session is active. A missing VSD response alone is not treated as a modem link failure.
  • Live register values reach the panel and trends as soon as a valid frame arrives.
  • Refined handling of modem replies and session close on transport-layer errors.

Before 0.10: development milestones

Key milestones in the development of the ESP remote monitoring and control system.

  • July 2026. Decision to develop an in-house poller instead of an off-the-shelf OPC server. Bench prototype: VSD simulator, Modbus polling, archive, and a web panel with the VSD display, LEDs and LCD.
  • Late July. Setpoints, the V/f curve, last start and last stop with the reason. Register maps for VSDs from several manufacturers. UI in three languages.
  • Same period. A home page with fields and well tiles, a well passport, a recycle bin. The server packaged as a single Windows executable with a settings window, users, roles and password sign-in.
  • August. Shared RS-485 operation with a third-party polling system: replies to the other master's requests are received, and only missing registers are polled.
  • September. Migration to the production server, HTTPS with a trusted certificate, website launch.
  • Late September. First GPRS modems connected on an oilfield 2G network. Analysis of network traffic and link loss causes, resulting in the 0.10.x branch.