RSLogger 485 is a compact, dual-channel RS485 data logger for passive monitoring and long-term recording. It stores both channels in 512 MB ECC Flash with precise 1 ms timestamps, supports automatic USB Mass Storage backup and USB Virtual COM, and offers optional Modbus RTU decoding into readable text logs. The RS485 section is galvanically isolated from the logger electronics to help reduce ground loops, noise and moderate ground-potential differences.
RSLogger 485 is a compact hardware RS485 data logger designed for passive monitoring, diagnostics and long-term recording of two RS485 communication channels. It can simultaneously receive data from two differential signal pairs and store both data streams in the internal 512 MB ECC Flash memory.
The logger operates in receive-only mode and does not actively transmit data onto the monitored RS485 buses. Recorded data can be stored in one common file with channel indicators or in two separate files, one for each channel.
RSLogger 485 can record the original binary communication stream or use its built-in Modbus RTU decoding mode to create readable text logs containing timestamps, TX/RX direction, device addresses, function codes, payload data and CRC values.
RSLogger 485 provides two differential receive channels:
Both channels can be monitored and recorded simultaneously. Received data can be saved in one common log file with channel or direction indicators or in two separate files, one for each channel.
This allows RSLogger 485 to monitor two separate RS485 data streams or record both directions of communication when the transmitted and received signals are available on separate signal pairs.
The RS485 transceivers operate in receive-only mode. The logger does not actively drive or modify the monitored communication lines.
RSLogger 485 can record RS485 communication either as an unmodified binary data stream or decode recognized Modbus RTU frames into a clear, human-readable text format.
When Modbus RTU decoding is enabled, every recorded frame can contain:
- precise timestamp,
- TX or RX direction,
- device address,
- Modbus function code,
- frame payload,
- CRC value.
Example decoded Modbus RTU communication:
P 6:29:04.378 TX [ADR 01][FC 01] 00 00 00 08[CRC 3D CC] P 6:29:04.386 RX [ADR 01][FC 01] 01 4D[CRC 91 BD]
This format makes diagnostics easier because the operator does not need to identify the address, function and CRC fields manually inside a continuous binary data stream.
The recording mode is selected in the CONFIG.INI file.
MODBUS_RTU=0 Records the original raw binary data without protocol decoding or translation.
MODBUS_RTU=1 Enables Modbus RTU frame detection and human-readable text decoding.
Raw binary recording remains available for proprietary protocols, non-Modbus RS485 communication and applications requiring an exact copy of the original data stream to be analyzed/archived with an external software.
Modbus decoding affects only the saved log format. RSLogger 485 remains a passive receiver and does not transmit or modify data on the monitored RS485 buses.
The complete RS485 input section is galvanically isolated from the internal logger electronics, USB interface, external system ground and any computer connected through USB.
The functional isolation helps reduce:
Both RS485 channels share one common isolated reference and are therefore not galvanically isolated from each other.
Important: the isolation is intended for functional separation of communication equipment. It must not be treated as safety isolation, direct mains isolation or protection against continuous voltage differences in the kilovolt range.
Received data is stored first in the internal 512 MB ECC-protected Flash memory. The memory operates as a circular buffer, automatically replacing the oldest data when its available capacity is full.
A FAT32 USB Mass Storage device can be connected at any time to:
When a USB drive remains connected, newly recorded data can be copied automatically in the background. This provides practically unlimited recording capacity for low- and medium-traffic communication systems.
The logger can save data in a common file for both channels or in separate channel files. Depending on configuration, data can be stored in binary, HEX or decoded Modbus RTU text format.
The built-in real-time clock provides precise timestamps with resolution down to 1 ms. The RTC is supported by an internal rechargeable backup battery, allowing the device to retain its date and time when external power is disconnected.
Available timestamp modes include:
The Micro USB interface includes an FTDI-based USB Virtual COM port. It can be accessed with standard serial terminal applications and does not require dedicated RSLogger software.
Virtual COM can be used for:
The isolated RS485 ground and logger system ground are available on neighbouring terminals. They may be connected externally with a short jumper when galvanic isolation is not required and a common reference is preferred.
The grounds should remain separated when the RS485 installation and logger may operate at different ground potentials.
The programmable GPIO terminal allows RSLogger 485 to be integrated with external control systems, embedded controllers or additional interface modules.
In the standard firmware configuration, the GPIO output provides a UART-level copy of the data received through RS485 Channel 1. Other GPIO functions may be implemented as part of a customized firmware version.
RSLogger 485 combines passive dual-channel communication monitoring with local data storage, precise timestamps, USB data access and functional galvanic isolation. Unlike simple RS485-to-USB adapters, it can operate independently without a permanently connected computer.
The optional Modbus RTU decoding mode also provides immediately readable communication logs, making diagnostics and service work faster and easier.
It is a practical RS485 sniffer, Modbus RTU logger and serial communication recorder for technicians, engineers, developers and system integrators.
Typical RSLogger 485 current consumption
| Model | 5 V | 9 V | 12 V | 16 V | 24 V | 30 V |
|---|---|---|---|---|---|---|
| RSLogger 485 | 25 mA | 17 mA | 12 mA | 8 mA | 5 mA | 3 mA |
Values refer to typical current consumption during normal operation, without a connected USB storage device.
➡ Order RSLogger 485 today and add passive dual-channel RS485 recording, functional galvanic isolation and readable Modbus RTU logging to your monitoring system.
No. RSLogger 485 operates as a passive receive-only monitoring device. It records received data without actively driving or modifying the monitored RS485 signal lines.
Yes. When MODBUS_RTU=1 is enabled in CONFIG.INI, the logger detects Modbus RTU frames and records them in a readable text format containing the timestamp, TX/RX direction, device address, function code, payload and CRC.
Yes. With MODBUS_RTU=0, RSLogger 485 records the original binary RS485 data without protocol decoding or translation. This mode can be used with proprietary and non-Modbus communication protocols.
No. Decoding affects only the format of the saved log. RSLogger 485 remains a passive receiver and does not transmit or modify data on the monitored lines.
Yes. Both channels can be recorded at the same time. Data can be stored in one common file with channel indicators or in separate files for each channel.
No. Both RS485 channels share one common isolated reference. The complete RS485 section is galvanically isolated from the logger electronics, USB interface and system ground.
The functional galvanic isolation helps reduce ground-loop currents, electrical noise and moderate differences in ground potential between the RS485 installation and the logger electronics.
No. The isolation is intended for functional separation of communication systems. It must not be treated as safety isolation, direct mains isolation or protection against continuous kilovolt-level voltage differences.
Yes. Both grounds are available on neighbouring terminal pins and may be connected externally when galvanic isolation is not required. They should remain separated when ground-potential differences may be present.
In the standard firmware configuration, the GPIO output provides a UART-level copy of data received through RS485 Channel 1.
Recorded data can be exported automatically to a FAT32 USB Mass Storage device or accessed through the USB Virtual COM interface.
Yes. Firmware updates can be installed using a USB Mass Storage device. The logger also includes a protected factory firmware recovery function.