IolinkAnalyzer 1.2.0 (28 Nov 2023) [INFO] New firmware Version 1.17.1: Fixed hangup (two leds blinking indefinitely) of IO-Link Analyzer Device in some rare circumstances. (MANTIS-0000141, MANTIS-0000139) [INFO] New firmware Version 1.17.1: Adds the ability to capture also IO-Link Safety devices that use a ready pulse at startup. (Mantis-0000124) [INFO] New firmware Version 1.17.1: Fixes an issue that led to loss of the first byte of the frame with COM3 device with very fast cycle times. (Mantis-0000128) [INFO] Application updated to .net framework 4.8 (framework 4.5 is out of support by Microsoft). (MANTIS-0000142) [FEATURE] Added license management feature to allow storage of licenses inside the IO-Link Analyzer device. [FEATURE] Added a new com speed detection mechanism based on shortest pulse measurement. (MANTIS-0000113, MANTIS-0000126, MANTIS-0000129) [FEATURE] Integrated application logging facility to enable problem diagnostics. (MANTIS-0000137) [FEATURE] Event numbering in details tab now starts with 1 (not 0) and uses lowercase 'e' to avoid confusion. (MANTIS-0000143) [FEATURE] Added textual interpretation of BLOB profile items and other profile defintions. (MANTIS-0000086) [FEATURE] Added interpretation of Smart Sensor Profile indices. (MANTIS-0000147) [FEATURE] Added interpretation of Function Tag (Index 25), Location Tag (Index 26) and Product Uri (Index 27). (MANTIS-0000148) [BUGFIX] Fixed a bug with parsing of TYPE_2 events when multiple events wereactive at the same time. TYPE_2 events were also errorneously displayed as TYPE_1 events. (Mantis-0000123) [BUGFIX] Fixed detection issue if wakeup occurs within 1sec after fallback. (MANTIS-0000131, MANTIS-0000132) [BUGFIX] Fixed: Frames view shows 'master checksum invalid' when device part is mssing (MANTIS-0000125) [BUGFIX] Fixed: Command "Back to Box" (131) is not decoded (MANTIS-0000136) [BUGFIX] Fixed: wrong decoding of Index 3 (Data Storage) when read without subindex (MANTIS-0000135) [BUGFIX] Transfers based on faulty ISDUs are not displayed on the overview tab anymore, to avoid confusion. (MANTIS-0000122) 1.1.2 (24 Mar 2020) [BUGFIX] Fixed exception when loading trace file with less than 50 frames. (Mantis-0000119) [BUGFIX] Fixed exception when capturing or loading some traces captured during TMG TestSystem run. (Mantis-0000120) [BUGFIX] Fixed: The isdu counter in the status bar and on the analyzer info tab was not counting. (Mantis-0000121) 1.1.0 (01 Mar 2020) [INFO] A new extensive automated testing environment has been created to speed up the integration testing of future releases. This will enable a more frequent update cycle in the future. [INFO] Significant improvment in performance for COM3 devices. Some COM3 devices have not worked, fixed! [INFO] To simplify working while a live capture is in progress, the scroll direction of all lists has been inverted (now the newest item is at the bottom). A selectable auto scroll function is implmeneted to always display the most recent items during live capture. The PAUSE function is obsolete by these changes and has been removed. (Mantis-0000059) [INFO] Updated firmware to Version 1.9.1. [FEATURE] Added CSV export capability. [FEATURE] The ISDU list now shows human readable error code descriptions for standard error codes. (Mantis-0000106) [FEATURE] Added new smart filter options: 'capture invalid frames', 'capture process data in changes', 'capture process data out changes'. (MANTIS-0000006, MANTIS-0000077) [FEATURE] Implemented a new aboslute timestamp that assings the host pc's absolute time to each frame. The system timestamp isshown in the 'Frames' section. [FEATURE] A new indicator in the status bar will show up if there was a buffer overflow between the analyzer and the PC. (Mantis-0000105) [FEATURE] The microseconds timestamp is now extended to 64 bits to prevent overflow after 1.2h. (Mantis-0000111) [FEATURE] In 'Frames' section, fields of the master and/or device are now grayed out if the master and/or device checksum is not correct. In this case, these fields can not be relied on (PDOut, OD, PDIn, PDValid, EventFlag). (MANTIS-0000078) [FEATURE] Added a new column 'Interpretation' to 'Overview' section, showing detailed application level descriptions of the transfers. (MANTIS-0000031, MANTIS-0000063) [FEATURE] Added decoded error code information to the 'ErrorCode' colunm and decoded event information in the 'Overview' Section. (MANTIS-0000031, MANTIS-0000063) [FEATURE] In the 'Frames' list, the raw data has now a colored background to distinguish between master data and device data. (MANTIS-0000062) [FEATURE] Added decoding and display of data storage index list in transfer view (index 3, subindex 5). [FEATURE] Added decoding and display of Profile Characteristics Index in transfer view (index 13). [FEATURE] Added progress information while opening a .ioltrace file. [FEATURE] In ISDU list: Success and error are now visualized with a corresponding icon. (Mantis-0000093) [FEATURE] Events on the overview tabs are now displayed with more details (appearance / disappearance and error code). (Mantis-0000109) [FEATURE] The ISDU view now has an option to hide 'BUSY'-ISDUs. (Mantis-0000098) [FEATURE] Added support for Legacy Frame Type 1. (MANTIS-0000072) [FEATURE] ISDU ABORTs are now also displayed in Isdu list. (MANTIS-0000095) [FEATURE] ISUDs with parsing error are now displayed in Isdu list, with data fields grayed out. (MANTIS-0000005) [FEATURE] Added support for wakeup sequences that do not include the COM3 request, but immediately start with a COM2 request. (MANTIS-0000014) [FEATURE] Added 'ISDU Supported' information to 'Device Info' Section. (MANTIS-0000024) [FEATURE] Added tooltip to display index and subindex in hexadecimal format for overview section. [FEATURE] The IO-Link Analyzer device can now be selected by serial number. [FEATURE] The version of the IO-Link Analyzer Application is now shown in Windows 'Apps and Features' dialog the simplify the handling of multiple versions installed in parallel. (MANTIS-0000017) [FEATURE] The status display in the lower left corner is now made clear. [FEATURE] Reworked operating state tracker to better handle IO- Link firmware update captures. [FEATURE] Analyzer device is now opened in exclusive mode to avoid conflicts when running multiple instances of the application. (MANTIS-0000058) [FEATURE] The process data view is now grayed out if the analyzer is in SIO mode. (MANTIS-0000085) [FEATURE] The application now asks to quit if there is unsaved data. The loded file name is now shown in the window title. (Mantis-0000097) [FEATURE] Replaced the firmware update status dialog, now showing the downloaded firmware version. (Mantis-0000018) [FEATURE] The M-Sequence Capability is now displayed more detailed on the overview panel. (Mantis-0000115) [FEATURE] Redesigned button icons. [FEATURE] The main window title now also shows the program version. (MANTIS-0000081) [FEATURE] Shortened time for tooltips to show up. (MANTIS-0000022) [FEATURE] The "Start Capture" button now shows "Resume Capture" when capturing is paused. [BUGFIX] Fixed frame parsing issues for some legacy device (eg. MURR MVP12). (MANTIS-0000076) [BUGFIX] Fixed issue that showed the Data Storage upload request (0xFF91) event before the ParamDownloadStore (0x05) command. (MANTIS-0000013) [BUGFIX] Fixed issue that did not allow to store ioltrace files, introduced with version 1.0.3. [BUGFIX] Fixed issue with decoding of process data for some devices. (MANTIS-0000074) [BUGFIX] In the 'Overview' section the subindex number was displayed incorrectly for direct parameter access. The number was referring to the 'Address' in the direct parameter page instead of the subindex number. Now the subindex number is displayed together with a hint (DP). (MANTIS-0000073) [BUGFIX] Frames with invalid checksum are not considered for event or isdu decoding anymore to avoid putting the decoder into invalid states by invalid frames. (MANTIS-0000050) [BUGFIX] Fixed a bug that a frame's device checksum was considered correct if the device part of a frame was missing. (MANTIS-0000091) [BUGFIX] Fixed: There was a rounding difference between the Frame timestamps and the other timestamps (events, isdus, transfers) that lead to slightly different timestamp values. This was confusing for example when trying to find a frame that corresponds to an event. (MANTIS-0000094) 1.0.0 (31 Mar 2015) [INFO] First stable release.