CANOpen Log file

[smita6789]

Hello,

We tried using many options like log, logger, MessageListener etc.
Is there any way to capture the log for the SDO and PDO in text file or any other format?

Details similar to PCAN-View trace file, like timestamp, CAN ID, request, response and so on

[acolomb]

Depends on your operating system. On Linux and similar, there is the simple candump command. Or you can use libpcap based tools such as Wireshark because well-behaved CAN interfaces implement the SocketCAN standard, which looks like a network adapter.

On Windows, PCAN-View is an option and I've heard of people getting Wireshark to work there as well. But it depends very much on your adapter, as there is no real standard interface on Windows.

On MacOS I don't know.

[smita6789]

Hello, Thanks for your reply. I am using PCAN-View to capture CANOpen trace manually. I am looking for the way to do the same through python. Is there any way to capture log through python script and store in a file? We are looking for automated way, may be with help of canopen or any other library. Thanks, Smita Classified as Business From: André Colomb ***@***.***> Sent: Wednesday, July 19, 2023 1:28 AM To: christiansandberg/canopen ***@***.***> Cc: Smita Deshmukh ***@***.***>; Author ***@***.***> Subject: Re: [christiansandberg/canopen] CANOpen Log file (Issue #387) You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Depends on your operating system. On Linux and similar, there is the simple candump command. Or you can use libpcap based tools such as Wireshark because well-behaved CAN interfaces implement the SocketCAN standard, which looks like a network adapter. On Windows, PCAN-View is an option and I've heard of people getting Wireshark to work there as well. But it depends very much on your adapter, as there is no real standard interface on Windows. On MacOS I don't know. - Reply to this email directly, view it on GitHub<#387 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBLHJAZHRA3BIPCZK3OJ5A3XQ3TEPANCNFSM6AAAAAA2OOFCOY>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[ericbaril72]

Simply use the python-can module to record in a file. Then post-processing to understand the SDO-PDO traffic. Otherwise, the CANOpen library only acts as the client or the server, not as an analyser… A block-transfer SDO from a client would receive “acknoledge” from the server on the bus and your python node.

…

On Wed, Jul 19, 2023 at 01:46 smita6789 ***@***.***> wrote: Hello, Thanks for your reply. I am using PCAN-View to capture CANOpen trace manually. I am looking for the way to do the same through python. Is there any way to capture log through python script and store in a file? We are looking for automated way, may be with help of canopen or any other library. Thanks, Smita Classified as Business From: André Colomb ***@***.***> Sent: Wednesday, July 19, 2023 1:28 AM To: christiansandberg/canopen ***@***.***> Cc: Smita Deshmukh ***@***.***>; Author ***@***.***> Subject: Re: [christiansandberg/canopen] CANOpen Log file (Issue #387) You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Depends on your operating system. On Linux and similar, there is the simple candump command. Or you can use libpcap based tools such as Wireshark because well-behaved CAN interfaces implement the SocketCAN standard, which looks like a network adapter. On Windows, PCAN-View is an option and I've heard of people getting Wireshark to work there as well. But it depends very much on your adapter, as there is no real standard interface on Windows. On MacOS I don't know. - Reply to this email directly, view it on GitHub< #387 (comment)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/BBLHJAZHRA3BIPCZK3OJ5A3XQ3TEPANCNFSM6AAAAAA2OOFCOY>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> — Reply to this email directly, view it on GitHub <#387 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADFFTRVUNPLAD6UDLXGS3JLXQ5YCJANCNFSM6AAAAAA2OOFCOY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>