Skip to content

Conversation

@chinnk2
Copy link

@chinnk2 chinnk2 commented May 13, 2017

No description provided.

alistair23 and others added 30 commits March 5, 2020 20:36
travis: Update the Python versions
 #### Issues Addressed
 When using OBD over legacy protocols like K-line the
 message is rejected because the ecu id is undefined
 even if the data is retrieved correctly.

 #### Summary of changes
 Add the ENGINE ID and TRANSMISSION ID to the list of ecu
 map at object creation time to have it available when
 receiving the message.

 #### Summary of testing
 Data is retrieved correctly on K-Line. Car used VW Lupo GTI
 Data is retrieved correctly on CAN cars. Car used Ford Focus.

Signed-off-by: Catalin Ghenea <[email protected]>
Increase "0100" query (PIDS_A) timeout to support inexpensive/slow OBDII adapters.

This patch fixes the case in which "SEARCHING" is not shown after "0100",
due to slow response of cheap devices.

```
[obd.elm327] write: '0100\r'
[obd.elm327] read: b'SEARCHING...\r...
```

It should also fix the case in which the debug mode needs to be active:
in fact the debug logs might slow down the query timeout enough to be able
to catch the query answer.

Reference #205

Reference #200

Reference #187
 #### Issues addressed
 Can't auto detect protocol on BT connection
 even if the elm devices detects the protocol
 successfully.

 Add delay after erasing stored protocols
 so the adapter can read the discover command

 #### Summary of testing
 Tested on an Mazda MX5.
 The protocol can be detected successfully
 on each run. Tested for about 10 times in a row.

Signed-off-by: Catalin Ghenea <[email protected]>
Right now __read() will stop reading at "OK" even if a ">" is still coming.
This can cause the ">" to be seen as the response to the next command, which
confuses the initialization sequence, since the initialization sequence
expects a very specific set of responses to its commands.

This changes __read() so that by default it only treats ">" as the response
terminator. When we issue the "ATLP" command to enter low-power mode, we will
use "OK" as the response terminator instead, since that's the only time we
don't expect to see a prompt.

This should fix #226 and should also fix #227.
Signed-off-by: Alistair Francis <[email protected]>
Moving to a feature branch

This reverts commit 3ecbf6f.
This reverts commit eb8679e.
Also fixed some of the doc headers for more modern versions of mkdocs
Without this fix, Python 3.13.1 yields this warning during "import odb":

    …/obd/utils.py:177: SyntaxWarning: invalid escape sequence '\C'

I'm not a Windows expert, but the correct naming convention seems to
be described here:

https://support.microsoft.com/en-us/topic/howto-specify-serial-ports-larger-than-com9-db9078a5-b7b6-bf00-240f-f749ebfd913e
Also corrected some of the package classifiers to indicate that this
python library no longer supports python 2. It didn't even with the
older 0.20.* Pint, though Pint itself now only supports python 3.9+
Uprev pint to 0.24.* for python 3.13+ support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.