Can-isotp

Latest version: v2.0.4

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

Scan your dependencies

Page 1 of 3

2.0.4

**Bugfix**
- Fix performance issue with ``stop_receiving`` that is called before each transmission by ``udsoncan``

2.0.3

**Improvement**
- Significantly improved timing under windows. (113) credits : pgreenaland

2.0.2

**Bugfix**
- Bugfix for exception thrown when calling stop_sending (required by udsoncan connection)

2.0.1

**Bugfix**
- Fixed 110. Compatibility with python3.7 to python3.9 is restored

2.0

**Major changes**
- The TransportLayer handle its own timing by running an internal thread. No need to call ``process`` anymore
- The user provided ``rxfn`` is expected to be blocking and respect a timeout passed as an argument. CPU throttling will be applied by calls to ``sleep()`` if the given timeout is not respected.
- ``squash_stmin_requirement`` has been replaced by ``override_receiver_stmin``
- Many internal methods/properties have been prefixed with an underscore to indicates that they are internal
- The error handler is called from a different thread.
- The isotp.socket.recv does not return None on Timeout anymore
- Minimal Python version is 3.7
- ``isotp.socket.bind`` now requires an ``isotp.Address`` object and is no more backward compatible with old interface


**Improvements**
- Timing behaviors has been globally improved. The pure python implementation running in the user space is able to reach similar timings as the kernel module when running on a vcan interface
- Blocking sends are now possible
- Added ``NotifiedBasedCanStack`` which is an improved version of the CanStack object using a can.Notifier improving performances and avoiding starvation of other readers.
- Asymmetric addressing is possible, meaning sending and receiving with different address schemes
- ConsecutiveFrame wait period can be achieved by a user-passed function (default to time.sleep)
- Possible to send data using a generator
- Test suite is more robust
- Type hints are coupled with the code

**Bugfix**
- Fixed missing parameter check in ``Address``
- Receiving a wait frame when wftmax is set to 0 triggers the error handle only when reception is not idle.

1.9.0

**improvements**
- 69 : Improved interraction with python-can by passing down timeout parameter (credit mikisama)
- 77 : Add support for optional non-standard CAN IDs in addressing modes Mixed 29 bits and NormalFixed 29 bits. (credits: Zcholm)
- Increased tooling version for documentation + few typos.

**Bugfix**
- 61 : Rate limiter would fail when applying throttling on a multi-packet message. (reported by dpatel20)

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.