Skip to content

Releases: pylessard/python-udsoncan

v1.19.0

19 Sep 02:31
Compare
Choose a tag to compare

New features

  • Supports waiting on negative responses when SuppressPositiveResponse bit is set (#174).

Bug fixes:

  • Fixed the list of supported negatives response code for TransferExit (#173). Credits: @mikisama

v1.18.1

24 Jun 15:48
Compare
Choose a tag to compare

Changes:

  • #162 - Client attach a reference to the request in the response object.

Bug fix :

  • #161 : Bad static type in client.send_request() signature

v1.17.2

25 May 15:13
Compare
Choose a tag to compare

Bugfix

  • Fixed #157, Request and response decoding may fail depending on module loading order

v1.17.1

15 Mar 13:21
Compare
Choose a tag to compare

Bugfix

  • Fixed compatibility issue with Python 3.7 introduced by TypedDict usage in udsoncan V1.17

v1.17

15 Mar 00:55
Compare
Choose a tag to compare

New Feature

  • Added type hints to the library
  • Accepts non-standard services that extends the BAseService class (@HugGa)

Bug fixes

  • Fixed few instances where None values were not handled correctly
  • Corrected bad types in documentation
  • Bugfix for J2534Connection (@venden)

Changes

  • internal cleanup to remove mid-module import and circular dependencies problems
  • Reformatted everything with autopep8

v1.16

09 Jan 02:57
Compare
Choose a tag to compare

Features:

  • Added a connection for support of aisotp module as transport layer (Credits : @mikisama )
  • Added support for ResumeFile subfunction in RequestFileTransfer service (Credits : @kenjo )
  • MemoryLocation used for Read/WriteMemoryByAddress now accepts 64bits addresses (Credits : @driftregion )
  • Added supports for new Negative REturns Codes introduced in 2020 version of ISO-14229 (Credits @lumagi )

Changes:

  • Connections using a thread now sets the daemon flag to true (Credits : @lumagi)

Bugfix:

  • #143 - Fixed AccessTimingParameters service that wasn't handling the timing record parameter correctly.
  • #132 - Fixed a typo that would trigger an internal error if a bad DID config was given to the client.

v1.15

29 May 01:48
Compare
Choose a tag to compare

New functionality

  • #110 : Support new subfunctions for ReadDiagnosticInformation (0x19) (tests : kayoub5, yassin92)
    • reportDTCExtDataRecordByRecordNumber (0x16)
    • reportUserDefMemoryDTCByStatusMask (0x17)
    • reportUserDefMemoryDTCSnapshotRecordByDTCNumber (0x18)
    • reportUserDefMemoryDTCExtDataRecordByDTCNumber (0x19)

v1.14

13 Aug 00:01
Compare
Choose a tag to compare

Features:

  • Added support for J2534 passthru (#75, #76) [credit: @joeFischetti ]
  • Added possibility to send data bytes when requesting a seed with SecurityAccess service (#79) [credit : @guigor]
  • Added a parameter to disable the global timeout when sending a request, meaning it is now possible to wait indefinitely for a response if the server ask to wait continuously. (#73, #86) [credit: @martinjthompson ]
  • Added support for DynamicallyDefineDataIdentifier service (#78)

Bugfix :

  • Start receive timer after call to the connection send to avoid timing out while transmitting long payload (#43, #68) [credit: @wanam ]
  • RequestFileTransfer response now properly parse the filesize (#89, #90) [credit: @trivialpursuer ]

v1.13.1

19 Jul 16:18
Compare
Choose a tag to compare

New feature:

  • InputOutputControlByIdentifier service now support variable length DID with (Codec.ReadAllRemainingData). Fixes #57
  • Added a parameter to change the standard version support (2006, 2013, 2020).
  • When using version 2013 or 2020, DiagnosticSessionControl now requires the server to provides timing requirement (fixes #53)
  • Added a parameter to ignore server timing parameters when doing a DiagnosticSessionControl (for 2013 and 2020 version).

Bugfixes:

  • Fixed a typo in error code. IncorrectMessageLegthOrInvalidFormat becomes IncorrectMessageLengthOrInvalidFormat

Minor:

  • Changes few logging details.

v1.12.2

17 Apr 23:58
Compare
Choose a tag to compare

Bugfix

  • Fixed #51. Unlocking a security level that is already unlocked (seed=0) is now handled properly. No key is sent to the server and a positive response is returned to the user.