Download the CPTT 2.24 installation file from cptt_2.24.msi (approx. 2780K). For installation, double click the MSI file and follow the installation instructions.
What is new?
General:
(2.24.1) Every Message in the Message Storage now has a Message Tag. A Message Tag is a value between 0 and 255. The Message Tag value is (currently) assigned to the Message by CPTT.
Messages can be filtered based on their Message Tag: For example, only all Messages with Message Tag 5 can be displayed, or only Messages with Message Tags 3 to 4.
At the moment, Message Tag values are assigned, among other things, after analysis while network monitoring. Each TCP/IP connection receives its own Message Tag value. Which TCP/IP connection is identified by which Message Tag is listed in the Message Storage after monitoring.
(2.24.1) We have expanded the communication protocol between RIO Client and RIO Server. The new GCP version now transmits Message Tags, signals line idle (no characters received from/on the RIO server) and lists the known medium/locations of the RIO server. Of course, the new communication
protocol is backward compatible, and communication reception from existing RIO servers is still guaranteed.
(2.24.1) Operating CPTT at very low baud rates is now smoother.
(2.24.2) Issue around IEC 60870-5-104 Message Tag filtering fixed.
(2.24.3) WibuKey Runtime Kits prior to version 6.70 contain serious security vulnerabilities. That is why the WibuKey Runtime Kit version is now tested more consistently:
If a WibuKey Runtime Kit prior to version 6.50 is installed, CPTT issues a warning message and starts only as a viewer.
If a WibuKey Runtime Kit prior to version 6.70 is installed, CPTT issues a warning message.
(2.24.4) Now on MS Windows and on Linux Ethernet frames from a "loopback monitoring adapter" are processed (with latest Pcap or Npcap installed).
(2.24.4) Adapted to MS Windows 11 version 24H2.
Many minor improvements ...
GUI:
Many minor improvements ...
Transmission Protocols:
(2.24.1) ABB SPA-Bus: Fixed problems when editing a Message. For Messages with a time stamp, you can now specify that the current date/time should be used for the time stamp(s) using "Apply current date&time".
(2.24.1) We have integrated initial versions (experimental implementations) for the M-Bus and SML protocols. At the moment only monitoring is supported.