-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
What CAN interface are you using? Do the frames show up when logging via |
Beta Was this translation helpful? Give feedback.
-
|
I can send a request with an extended ID to my node. But the response from the node does not trigger the callback. |
Beta Was this translation helpful? Give feedback.
-
|
Not much to go on here. It seems the code should handle it transparently, from the PCAN interface driver through the python-can library to the canopen processing layers. Maybe you should try with some debug logging first to find out how far up the stack the message gets delivered. |
Beta Was this translation helpful? Give feedback.
-
|
Some older revision ago, the extended messages did not go through as the were specifically not forwarded. in the file network.py, at the very end is the MessageListener class, it gets instantiated and passed down to the can.notifier when the Networks connect. Put in a print(data) just before the the first “if”. You can also condition at print if msg.is_extended I do remember having seen PCAN-view software not showing the extended messages if the filter was set to 0x00 to 0x7ff (in pcanview) so if you have other software running at the same time as you python script, you may have some config that got pushed into the pecan-usb that prevents msg from even reaching the CANopen library |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
It works as intended. The issue was caused most likely by my test program which terminated immediately after sending, thus, it was not waiting for any response...
tested with python-can v4.6.1, canopen v2.3.0
'self.network.subscribe(0x18EEFF5A, self.__on_received_j1939)'
'self.network.send_message(0x18EA5A01, [0x00, 0xEE, 0x00])'
'time.sleep(1)'