Ldfparser

Latest version: v0.25.0

Safety actively analyzes 685670 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 6

0.9.1

Added

- Missing node attributes: Response Error, Fault State Signals and Configurable frames are now
linked to the `LinSlave` object ( 66 )

0.9.0

Fixed

- Fixed ASCII and BCD encoding types missing from the syntax ( 56 )
- Fixed `subscribed_to` variable on `LinSlave` containing the wrong objects ( 59 )
- Fixed whitespace not being allowed in the `Nodes` section before the colons ( 61 )
- Fixed parsing initial values of array type signals ( 62 )

0.8.0

Added

- Standard JSON schema for parsed LDFs

Fixed

- Missing encoders causing `KeyError` instead of `ValueError`

0.7.1

Fixed

- Frame encoder incorrectly encoding zero valued signals into their initial values ( 40 )

0.7.0

Added

- CLI interface for basic LDF tasks (33), entrypoint is added, documentation available in
the docs folder
- Frames are now linked to the publishing node

Changed

- Variant value now defaults to 0 instead of None

Fixed

- Signals incorrectly being appended to the published frame list

0.6.0

Added

- Signal and LIN node objects are now linked when subscribers and publishers are specified
- The following node attributes are now parsed into the LDF objects
- P2_min
- ST_min
- N_As_timeout
- N_Cr_timeout
- UnassignFrameId command which is in LIN 2.0 spec
- Schedule table commands are now parsed

Changed

- Signals with no subscribers are now allowed, while this is not to spec. OEMs use it ( kayoub5 )
- Node attributes section can now be empty ( kayoub5 )
- AssignFrameIdRange now accepts either 0 or 4 PID values

Page 4 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.