Repository navigation
Releases
Releases · vend123/modbusmanager-downloads
Modbus Manager 1.4.14
Fix: Modbus RTU sends one request at a time
- On a serial link (RTU, ASCII, and RTU / ASCII over TCP or UDP) every request now waits for the one before it and goes with its own unit ID. A write made while windows were being polled could meet a poll on the line and time out. Over Modbus TCP nothing changes.
Modbus Manager 1.4.13
TX/RX log
- Resize it: drag the log's top edge (up to 60 % of the window); ▾ / ▴
folds it. The size is remembered. It was a fixed 140 px, too little on a
small or scaled screen.
Modbus Manager 1.4.12
Test Center
- FC08, FC11 and FC17 work on every connection. They were sent with a
second Modbus TCP header over TCP, UDP, ASCII and RTU over TCP, and on RTU
the FC08/FC11 reply was never passed on - every one timed out. They are now
framed for the connection they go out on. FC17 shows the run status the
device sends (it always said OFF). - FC22 and FC23 do what you ask. FC22 has AND and OR mask fields (it sent
a mask that changed nothing and said OK), FC23 a write address and works
(it failed with "not a function"). - FC43 shows the device identification (VendorName, ProductCode, ...),
asks the unit in Slave ID (it used the Address field as the unit) and has
a read code (basic, regular, extended, one object) and object ID. - FC08 has a data field. A value that is not a number is refused instead of
being written as 0. Every text is translated. Without a connection the
Send button's tooltip says why it is off.
Serial Monitor
- Shows the bytes on the wire: on Modbus TCP the whole MBAP frame, not an
RTU frame with a CRC that is never sent; on RTU one line per frame, also
when the adapter delivers it in pieces. - Keeps running across a reconnect. Stopping it after a reconnect no longer
breaks the connection (every request timed out until the next reconnect). - Security: bytes a device sends are shown as text in the ASCII column;
they were rendered as HTML.
Scanners
- Slave Scan counts a device that answers with a Modbus exception as found -
it is there. Address Scan reads around gaps in a block instead of missing
the whole block.
Write tab
- FC22 and FC23 are now only in the Test Center (in the Write tab FC22 wrote
nothing and FC23 failed).
Updated guide: User manual.
SHA-256 (Modbus.Manager.Setup.1.4.12.exe):
48c93fc93c75fa9c2e84b8a7fb13f951325a72fc50e708d368b33dfa7d3157e0
Modbus Manager 1.4.11
Fixes
- RTU over TCP sends RTU frames. The RTU/TCP connection sent Modbus TCP
frames (with an MBAP header), so a serial device server in transparent mode
never answered and every poll timed out. It now sends RTU frames with CRC,
like RTU/UDP and ASCII/TCP.
Security
- The app's own UI answers only this PC. Its local web server listened on
every network interface and took requests from any web page. It now listens
on the loopback address only, checks that the request names this machine,
and accepts a WebSocket or a write only from the app's own page.
Guide: Modbus RTU over TCP.
SHA-256 (Modbus.Manager.Setup.1.4.11.exe):
23fd4c616647659df07fa3aa92a6c45eba69a0e0755a37da0f1c03403789b811
Modbus Manager 1.4.10
Connection settings
- TCP-SEC is real Modbus/TCP Security. Modbus TCP inside TLS 1.2 or newer
(port 802), with the client certificate and private key the device trusts
and the CA certificate that signed the device's certificate (PEM files,
loaded once with Choose… and kept in the application's data folder).
Verify device certificate is on by default. A refused connection says why:
untrusted device, wrong name, expired, or the device rejected the client
certificate. Until now this tab opened plain Modbus TCP to port 802. - RTU/UDP, ASCII/TCP and ASCII/UDP send their named framing - RTU frames
with CRC in datagrams, and:+hex+LRC frames on TCP and UDP. They used to
send Modbus UDP or RTU frames. - RTS Toggle raises RTS only while a request is being sent (RS-485
direction control). It used to switch on RTS/CTS handshaking. - Remove Echo drops the echo an RS-485 adapter hears of its own request;
a reply without echo is kept. It used to do nothing. - Disconnect and connect in quick succession: the new connection no longer
reports "Not connected", and a COM port no longer says "Access denied"
because the old handle was still closing. - Every field of the dialog is saved, including the checkboxes and the UDP
and TCP-SEC tabs.
Slave simulator
- The Server row names the port the slave really listens on.
- The Simulate dialog title is translated ("Holding Registers 0").
Other
- The toolbar's start-address label reads "Address:".
SHA-256 (Modbus.Manager.Setup.1.4.10.exe):
5ca40c25d4c22286649008493ff8b3e86a1d43412cec21d086eea9859a42e375
Modbus Manager Standard 1.4.9
Modbus slave
- Link panel: connected masters, requests per second, and every refused
request with its reason (unit ID not registered, address outside the
blocks). On RTU, frames with a bad CRC and frames for another unit are
counted and no longer answered — on a shared RS-485 bus a slave must stay
silent. - The RTU port list was always empty — it now lists the ports, virtual ones
included — and the RTU slave has its own baud rate and parity. - PID loop simulator on a holding register, with a process of its own.
Fixes
- A workspace with no Modbus windows loads everything after it, and does not
keep the previous workspace's windows.
SHA-256 (Modbus.Manager.Setup.1.4.9.exe):
de0f2b1927ce2b909146160db6572f789fb8e10ff908463d6eef043485aa99c7
Modbus Manager Standard 1.4.8
Security
- Names from a workspace file or a device are shown as text, never as
markup. A crafted workspace could previously run script inside the
application.
SHA-256 (Modbus.Manager.Setup.1.4.8.exe):
7376e831192a3c5a05552e94397d9e3a9fadad7ce6205e47fb1c447b3d779a41
Modbus Manager Standard 1.4.7
Export
- CSV and register exports save straight to your Downloads folder instead
of opening a save dialog, and a message tells you where the file went. An
existing file is never overwritten -(2),(3)is appended.
SHA-256 (Modbus.Manager.Setup.1.4.7.exe):
7f18b4969d65ded668ca3d46781fd46e732fb3e9807985cb1326a1dd9a95a9e2
Modbus Manager Standard 1.4.6
Modbus
- Slave / unit ID 0 is kept. A typed 0 was silently changed to 1 in every dialog that takes a slave ID, so devices that answer only on unit 0 — Huawei SmartLogger over Modbus TCP, among others — were never reached. The field showed 0 the whole time. Empty fields still default to 1.
- Real connect timeouts on RTU-over-TCP, ASCII-over-TCP and UDP. Behind a firewall that drops packets the app used to sit on "Connecting" for the operating system's own ~21 s timeout.
- A failed connection no longer leaks the port handle. PLCs that allow only one or two Modbus TCP sockets could refuse every later attempt until the app was restarted.
- Fragmented RTU replies are assembled. Diagnostics FC08/FC11/FC17 resolved as soon as five bytes arrived, and framed every serial connection as TCP — so they could not work over RS-485 at all.
- RTS Toggle is now labelled RTS/CTS flow control, which is what it actually sets.
- Register descriptions are stored per slave, so several slaves polling the same address no longer overwrite each other's descriptions.
- Simulated sine waves follow the clock, so they stay in phase after the app is busy.
Licensing
- A broken trial seal is no longer burned in. Renaming the PC or joining a domain could brand a legitimate trial as tampered, permanently, with no way back. The trial now recovers by itself once the cause is corrected.
- The registry backup carries the licence key, so a customer who loses their AppData folder is restored as licensed rather than landing on "Trial expired".
- An unwritable AppData folder logs a warning instead of throwing, which used to leave a blank window with no message.
Modbus Manager Standard 1.4.5
- Register descriptions are stored per slave + function code + address. Several slaves polling the same address no longer overwrite each other's descriptions.
- License screen cleanup