Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
app-notes:can-tcpsockets-parsing [2019/07/03 08:11] juraschek ↷ Links adapted because of a move operation |
app-notes:can-tcpsockets-parsing [2021/08/04 09:14] (current) |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| ===== Forward CAN Frames over TCP Sockets (can-tcp-broadcast.are) ===== | ===== Forward CAN Frames over TCP Sockets (can-tcp-broadcast.are) ===== | ||
| - | To show a possible use of forwarding CAN Frames over Ethernet can-tcp-broadcast.are provides a TCP client that broadcasts all incoming CAN Frames to one or several servers that can be passed as arguments. The SDK API already provides several functions to interact with CAN (see ftp://share.netmodule.com/router/public/system-software/latest/NB_SDK_API_Manual.pdf). | + | To show a possible use of forwarding CAN Frames over Ethernet can-tcp-broadcast.are provides a TCP client that broadcasts all incoming CAN Frames to one or several servers that can be passed as arguments. The SDK API already provides several functions to interact with CAN (see https://share.netmodule.com/public/system-software/latest/NB_SDK_API_Manual.pdf). |
| The function start_can() sets required attributes to the can interface and sets up a raw socket descriptor that is used in the main part of the script. Additionally filtering of CAN Identifiers is possible via nb_can_setfilter() to specify which CAN frames shall be filtered out and which shall be passed to upper layers. | The function start_can() sets required attributes to the can interface and sets up a raw socket descriptor that is used in the main part of the script. Additionally filtering of CAN Identifiers is possible via nb_can_setfilter() to specify which CAN frames shall be filtered out and which shall be passed to upper layers. | ||