Version 2022.6.10.1

Changes

• Code refactoring.
• Updated ABP headers and lookup tables.
• Improved support for log files containing BOM and added support for UTF16.
  This means the following formats are acceptable: ASCII, UTF-8, UTF-8-BOM,
  UTF-16-BOM.
• Updated ABP_CIPID_IA_PRODUCT_NAME to support both numeric and character
  display.

Fixes

• Fixed NC object's instance name lookup logic.
• Fixed ABP_NW_EXCPT_INFO_NONE, the verbose string was incorrect.

Version 2021.6.8.1

Changes

• Code refactoring
• Added support for ABCC SDK "log file simulation". It is now possible to take
  a standard SDK log file and simulate SPI messaging in the plugin via
  the AdvancedSettings.xml file. See plugin documentation for more information.
  NOTE: Some of these new configurable options are also available when using
  "standard simulation" mode. Example log files have been added to the
  ./doc/abcc_log_file_examples/ folder.
• Added support for message segmentation.
• Added support for enumeration of exception information and codes.
• Added support for message header fragmentation. Previously it was not possible
  for the plugin to handle cases where the ABCC message header was split
  between multiple SPI packets.
• Improved support for error response reporting. Error response is now included
  in the exported data and decoded protocols output.

Fixes

• Resolved static analysis issues.
• Fixed an issue with byte acquisition logic. If the clock transitions from high
  to low after the last bit in the byte has already been sampled but before the
  chip select deasserts, the plugin incorrectly reported this event as an error
  which in turn caused the SPI packet to be incorrectly marked with an error.
• Fixed bug regarding object specific errors. This issue resulted in an
  "Unknown" string entry being reported when it should not have done so.
• Added workaround setting to AdvancedSettings.xml to fix an inherent bug in
  the Logic software version 1.2.x. Error frames committed by the logic analyzer
  plugin which span < 8 samples require "expansion" to 8 samples in order for
  the software to properly establish a link between the decoded protocols entry
  and the bubble text.
• Improved CSV character escaping logic when using certain delimiters.
• Minor spelling fixes.

Version 2021.1.5.1

Changes

• Code refactoring
• Updated lookup tables to support latest ABP additions.
• Changed channel names to more closely match ABCC documentation.

Fixes

• Resolved static analysis issues.

Version 2019.7.17.1

Changes

• Updated lookup tables to contain latest ABP header information
• Migrated from VS2017 to VS2019
• Other minor changes & refactoring

Fixes

• (Issue #23) Fixed the state logic when the enable-signal toggles and there is
  no clocked data.
• (Issue #24) Fixed the logic behind multi-event markers.
• Fixed build issue for macOS Mojave.

Version 2018.10.10.1

Changes

• Significant internal code refactoring
• Updated lookup tables to contain latest ABP header information
• Added support for network specific error codes for Profinet Diagnostic object
• Significant rework of the plugin's simulation was done to improve highlighting
  the functionality of the plugin. The simulation now performs a more complex
  request-response messaging sequence that targets reading file information from
  the plugin's metadata for the compiled DLL. This doubles to provide built-in
  version information into the plugin for operating systems that do not contain
  such metadata for library objects.
• Significant rework of the CSV file exporting options for ABCC message data and
  process data. These exported files now include state information of the network
  and application. The CSV for message data now provides enumerated results
  making it much more human readable. Error event indicators are also now included
  to help point out CRC error, fragmented SPI packets, and retransmitted packets.
• Changed how the "display base" is used in the plugin. Now, only fields that are
  known to be of a 'character' base-type will be permitted to be displayed as
  "ASCII" or "ASCII & HEX". Frames that are not a "CHAR" base-type will be
  displayed in HEX for both of these options. In general, this means the ASCII
  display options will only apply to the "Message Data" field. This should provide
  a more intuitive user-experience in interpreting the information contained in
  the packet as a whole. Both attribute and command message data have been
  updated to follow these rules. For instance, the File System Interface's
  File_Open message data contains a filename that is naturally understood as a
  string which is classified as a 'character' base-type; whereas the "File Size"
  attribute is naturally understood as a 'numeric' data field. For any field,
  where it may be desirable to permit display in ASCII the BaseType::Character
  should be used. Future adjustments may be made to a particular command or
  attribute BaseType.
• Removed network types from settings that are ABCC 30-series only.
• This changelog has been modified to remove the "known issues" section. These
  are likely to remain as limitations of the software for some time and a separate
  document has been added to track these.
• Added option to limit the number of "clocking alerts" to report to the UI.
  This can be accessed from the advanced settings XML file.

Fixes

• Fixed lookup logic for the "Object" instance name. Previously, instance 0 was
  being reported as "Unknown" instead of "Object".
• Fixed "compact" indexing MOSI tag. The MOSI channels indexed results were
  mistakenly using the MISO_TAG_STR instead of MOSI_TAG_STR.
• Fixed issue with last packet not being committed. The last packet in a capture
  was not be correctly committed meaning there would be missing information in
  the results. This would affect results observed from both the "chipselect
  marker" behavior along with the exported CSV files.
• Fixed an issue with how extra "clocked data" is detected at the end of an
  SPI transaction.
• Fixed various issues with how advanced settings were being handled.

Version 2018.1.9.1

Known Issues

• A capture that starts in the middle of message fragmentation may result in a
  series of packets being incorrectly interpreted and possibly marked as invalid.
  To workaround this, the user can place a marker past this fragmentation and
  instruct the plugin to start analysis after this point.
• Due to a bug in the Saleae Logic software, the decoded results that indicate
  the packet ID may occasionally display an invalid value of 0xFFFFFFFFFFFFFFFF
  instead of the packet's actual ID.
• Settings window's "Advanced Settings" option is suppose to have a browse
  filesystem button. Saleae has acknowledged that this interface was never
  fully developed and should be resolved in a future release.
• Error markers are not given display priority. This is a limitation of the
  Logic software itself.

Changes

• Switched plugin's versioning to year.month.day.build notation
• Updated lookup tables to include latest ABP headers including new support for
  OPCUA, PNAM, EME, etc.
• Added advanced settings XML-file option. This file contains additional options
  that may be useful in special cases. Currently, two options are available:
  "4-wire-on-3-channels" and "3-wire-on-4-channels". "4-wire-on-3-channels" can
  be useful when limited on logic analyzer channels and would like to omit the
  SPI enable (chip/slave select) signal and use that channel for some other purpose.
  This provides added flexibility over normal 3-wire analysis since it will ignore
  timing requirements and permit "clock-idle-low" configurations (which the
  ABCC does not support in 3-wire mode and consequently this analyzer).
  "3-wire-on-4-channels" is useful when there is an extra channel on the analyzer
  that could be used to gain the analyzer "markers" that are normally drawn on the
  SPI enable channel. Using this mode will continue to treat the SPI channels in
  3-wire mode and enforcing timing requirements and clock-idle-high configuration.
• Added network specific instance names (i.e. Network configuration object instances)
• Changed decoded result's command extension, source ID, and instance to always
  use a combined decimal and hex notation (when no name is found) for consistency.
• Other minor changes

Fixes

• Last packet in capture may be missing a frame that will result in an
  uncommitted packet. This means that when exporting messages to a CSV, the last
  packet may be lost.
• Resolved various cases where the plugin would crash the software.