iso15765_example.py sending corrupt ID and data. #226
Unanswered
jvanorsdal
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all. Hoping someone can give me some guidance here. I'm trying to get my feet wet with ICS python and I'm running into problems right out of the gate.
When I used a stripped down TX-only version of iso15765_example.py, the first frame does not send correctly. The arb ID is wrong and the message content is mostly empty. For example, I try to send 64 bytes on 0x7E0 per the example. The message that comes out on the other end is 0x1AA 10 40 00 00 00 00 00 00.
I've played with this a bit and found that it's using the tx.dl value for the upper 3 bits of the arb ID, and the padding value for the lower 8 bits. EG if I change tx_dl to 2 the arb ID is 0x2AA. If I change the padding to 0xAC, the arb ID is 0x1AC (or whatever the value of tx_dl is at that moment).
Sending single CAN messages with tx_can_example.py works perfectly. The problem seems isolated to 15765 messages.
My setup is a NeoVI Plasma with a Fire VNet, transmitting on HS-CAN1. I've got a Ford control module on the bus, and a Peak PCAN listening and providing network keepalive messages. I've verified all the data on the Ford and Peak side, so I'm confident the problem is with the Plasma or the underlying code.
OS is Windows 10.
icsneo40.dll is 3.9.19.17 installed from RP1210KitInstall.zip
Python is 3.13.5
python_ics is 922.16
I do not have a Vehicle Spy license.
Firmware on my Plasma is:
MPIC: 7.56
Core: 8.21
LPIC: 2.12
HID: 6.0
Here is my code:
This is the output from the Python console:
And this is the resulting CAN message: ID 0x1AA, DLC 8, Data 10 40 00 00 00 00 00 00
I sincerely appreciate any advice or hints. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions