Releases: c4deszes/ldfparser
Releases · c4deszes/ldfparser
Release 0.26.0
Changed
- Empty signal encoders are now allowed
- Signals can now be associated with multiple frames, accessible under
signal.frames
- Physical values are now rounded to the nearest integer, rather than down
Migration guide for 0.26.0
- Newly written should be using
signal.frames
to determine the owners of a signal, for
compatibility reasonssignal.frame
is still set, but only when a signal is associated with one
frame - Physical values might be rounded the wrong way depending on the user's intention. This type of
rounding should generally work better in values ranging from0-X
, for example49.9
is no longer
rounded down to49
. If this is undesired the user can in most cases offset the input by0.5
and
it should work as previously as-0.5
rounds to0
, check
Python's round function for more.
Release 0.25.0
Changed
- Signals overlapping error message now includes relevant information
Release 0.24.0
Changed
- scientific/engineeering notation values can now have upper case E
Release 0.23.0
Changed
- Padding in a frame can now be changed from zeros to padding with ones
Release 0.22.0
Added
- Support for J2602 slave node attributes:
wakeup_time
,poweron_time
Release 0.21.0
Fixes
- Add support for encode/decode frame with byte array signals
Release 0.20.0
Added
- Support for SAE J2602 legacy version
- Grammar support for the following J2602 fields:
max_header_length
,response_tolerance
for the master noderesponse_tolerance
for slave node attributes
Release 0.19.0
Added
- ISO17987 version support
- Grammar support for the following ISO17987 fields:
LDF_file_revision
- Endianness
Changed
LDF::get_frame
can now return diagnostic frames
Fixes
LinSlave
protocol version property is now the correct typeLinUnconditionalFrame::decode
no longer calls the deprecatedparse_raw
function
Release 0.18.0
Changed
- Remove
tests
folder from python package - Close all files which are opened by the ldfparser
Release 0.17.0
Added
- Diagnostic addresses section in LIN 1.3 description files are now parsed correctly,
theinitial_nad
andconfigured_nad
attributes will be set according to the address