Professional Documents
Culture Documents
Ucadefaultobjects - CFG Configuration File and For The "Iec 61850" Setting The Iec61850Defaultobjects - CFG File
Ucadefaultobjects - CFG Configuration File and For The "Iec 61850" Setting The Iec61850Defaultobjects - CFG File
8)
Summary of changes
- Fixed: Decode of large MMS PDU’s, like e.g. TASE.2 CreateDataSet request
- Improved: Display an error when TCP data has a sequence gap. Unfortunately UniCA
can reconstruct only simple sequence gap and retransmission situations
- When the analysis shows many retransmissions and sequence gaps we recommend
to investigate the router performance, network load and line quality.
- IEC 61850: If you select the “UCA 2.0”application setting, UniCA will use the
UcaDefaultObjects.cfg configuration file and for the “IEC 61850”setting the
IEC61850DefaultObjects.cfg file.
- Fixed: Increased the supported number of connections from 100 to 300 in one trace
- Changed the support e-mail address in the about box to: pc.helpdesk@kema.com
- We recommend 256 MB memory for smooth capture and analysis
- TASE.2: Decode a part of the TLS and X.509 certificates (need to be improved to
display attr values)
- IEC 61850; Improved the display of ACSI services mapped on MMS read/write
- Display a warning when available physical memory is low when starting a capture;
stop a running capture when available physical memory is very low
- Fixed: incremental time causes infinite loop when first frame isn’t visible
- Fixed: increased stack size to handle large/complex MMS getVarAccessAttr PDU’s
- Fixed: save/restore “increase capture performance”default document setting, when
checked the trace file is saved in the UniCA.exe folder as
UniCA_SaveBeforeAnalysis.uca
- Fixed: cyclic buffering + event recording correctly saves the captured data to disc
(previously some files could be corrupted)
- TASE.2; Capture TLS secured TASE.2 traffic and display uncrypted TLS messages
at transport layer just before the TASE.2 association (enable the TRA-layer and
search for TLS)
- TASE.2; Support for TASE.2 second edition, added TimeTagExtended data types
- 61850; fixed bug in ACSI decoding. Error message shown if object is missing from
object configuration file
- 61850: object configuration file updated
- Cyclic buffering and event recording; This powerful new feature enables you to
capture network traffic unattended for a long period of time. If any interesting events
happens you can configure UniCA to automatically store the buffer to file in the
UniCA installation directory. Configurable events are:
- Frame errors on session and higher layer,
- New association,
- Specific text in the visible layers,
- Always save the buffer
- Single line overview now with object name(s)
- TASE.2 timestamp and quality bits are recognized and decoded even when not
defined in the object configuration file
- TASE.2 Start/Stop Transferset and IM TransferReport services are recognized
- Changed website to www.kemaconsulting.nl
- Pre-analysis errors on all protocol layers are merged and displayed on the Message
layer
- New UniCA User manual and Tutorial
- Support *text* wildcards in the object configuration file, e.g. VAR, *_STATUS_*,
Data_StateQ
- The capture dialog can be minimized/restored, resized and moved to improve the
visibility of the analysis window
- With File – Scan documents you can extract errors from multiple trace files
- With CRTL-F12 you can toggle the ASN.1 decoding at session layer (expert use only)
- Monitor the actual values of one or more variables (when monitoring enabled). Just
add ,MONITOR after a non-wildcard variable definition in the object configuration file
- Improved network load display during capture
- Improved decoding for TCP, TP0 and ACSE protocol
Known bugs
- GOMSFE: Goose user bitstring is truncated (over 300 chars on a single line!)
- When one Ethernet packet contains multiple MMS PDU's, UniCA displays only the
first PDU at Tase2/Casm/Acsi layer (workaround: look at MMS layer)