<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Activity for hanlec</title><link href="https://forge.codesys.com/u/hanlec/activity/" rel="alternate"/><id>https://forge.codesys.com/u/hanlec/activity/</id><updated>2020-09-29T10:47:57.159000Z</updated><subtitle>Recent activity for hanlec</subtitle><entry><title>hanlec posted a comment on discussion Engineering</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#289c" rel="alternate"/><published>2020-09-29T10:47:57.159000Z</published><updated>2020-09-29T10:47:57.159000Z</updated><author><name>hanlec</name><uri>https://forge.codesys.com/u/hanlec/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#289c</id><summary type="html">ok, I googled a little bit on this topic: SocketCAN documetation on kernel.org reads: 4.1.3 RAW socket option CAN_RAW_LOOPBACK To meet multi user needs the local loopback is enabled by default (see chapter 3.2 for details). But in some embedded use-cases (e.g. when only one application uses the CAN bus) this loopback functionality can be disabled (separately for each socket): int loopback = 0; /* 0 = disabled, 1 = enabled (default) */ setsockopt(s, SOL_CAN_RAW, CAN_RAW_LOOPBACK, &amp;loopback, sizeof(loopback));...</summary></entry><entry><title>hanlec posted a comment on discussion Engineering</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#b936" rel="alternate"/><published>2020-09-29T10:36:53.844000Z</published><updated>2020-09-29T10:36:53.844000Z</updated><author><name>hanlec</name><uri>https://forge.codesys.com/u/hanlec/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#b936</id><summary type="html">thanks Edwin, adding [CmpSocketCanDrv] Loopback=1 in /etc/CODESYSControl_User.cfg does the trick... still - two questions remain: 1) why isn't that enabled by default? IMHO SocketCAN behaves just like a (hardware-)bus: everything that is on the line should be seen by every device attached to it. what reason is there that the CodeSys-CanDriver even has the option of disabling this behavior at all?! 2) why do you advise do "remove it later after finishing this dump investigations"? I actually do need...</summary></entry><entry><title>hanlec modified a comment on discussion Engineering</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#a4d4" rel="alternate"/><published>2020-09-29T07:02:44.211000Z</published><updated>2020-09-29T07:02:44.211000Z</updated><author><name>hanlec</name><uri>https://forge.codesys.com/u/hanlec/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#a4d4</id><summary type="html">Hi All, I'm using CodeSys on a Raspberry Pi. I successfully use the CANbus library/module to read an write messages using SocketCAN and an attached CAN-hardware (MCP2518FD) in CodeSys I use: can0: CAN.CANBus_11bit the driver is initialized with the following config: can0Config: CAN.DRIVER_CONFIG := (usiNetwork := 0, uiBaudrate := 500, ctMessages := 200); the driver is opened/started with: can0(DriverConfig:= GVL.can0Config, eError=&gt; ); ...and as mentioned initially: everything works - almost! the...</summary></entry><entry><title>hanlec modified a comment on discussion Engineering</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#a4d4" rel="alternate"/><published>2020-09-29T07:02:04.536000Z</published><updated>2020-09-29T07:02:04.536000Z</updated><author><name>hanlec</name><uri>https://forge.codesys.com/u/hanlec/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#a4d4</id><summary type="html">Hi All, I'm using CodeSys on a Raspberry Pi. I successfully use the CANbus library/module to read an write messages using SocketCAN and an attached CAN-hardware (MCP2518FD) in CodeSys I use: can0: CAN.CANBus_11bit the driver is initialized with the following config: can0Config: CAN.DRIVER_CONFIG := (usiNetwork := 0, uiBaudrate := 500, ctMessages := 200); the driver is opened/started with: can0(DriverConfig:= GVL.can0Config, eError=&gt; ); ...and as mentioned initially: everything works - almost! the...</summary></entry><entry><title>hanlec modified a comment on discussion Engineering</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#a4d4" rel="alternate"/><published>2020-09-29T06:59:19.911000Z</published><updated>2020-09-29T06:59:19.911000Z</updated><author><name>hanlec</name><uri>https://forge.codesys.com/u/hanlec/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#a4d4</id><summary type="html">Hi All, I'm using CodeSys on a Raspberry Pi. I successfully use the CANbus library/module to read an write messages using SocketCAN and an attached CAN-hardware (MCP2518FD) in CodeSys I use: can0: CAN.CANBus_11bit the driver is initialized with the following config: can0Config: CAN.DRIVER_CONFIG := (usiNetwork := 0, uiBaudrate := 500, ctMessages := 200); the driver is opened/started with: can0(DriverConfig:= GVL.can0Config, eError=&gt; ); ...and as mentioned initially: everything works - almost! the...</summary></entry><entry><title>hanlec modified a comment on discussion Engineering</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#a4d4" rel="alternate"/><published>2020-09-29T06:58:14.695000Z</published><updated>2020-09-29T06:58:14.695000Z</updated><author><name>hanlec</name><uri>https://forge.codesys.com/u/hanlec/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#a4d4</id><summary type="html">Hi All, I'm using CodeSys on a Raspberry Pi. I successfully use the CANbus library/module to read an write messages using SocketCAN and an attached CAN-hardware (MCP2518FD) in CodeSys I use: can0: CAN.CANBus_11bit the driver is initialized with the following config: can0Config: CAN.DRIVER_CONFIG := (usiNetwork := 0, uiBaudrate := 500, ctMessages := 200); the driver is opened/started with: can0(DriverConfig:= GVL.can0Config, eError=&gt; ); ...and as mentioned initially: everything works - almost! the...</summary></entry><entry><title>hanlec posted a comment on discussion Engineering</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#a4d4" rel="alternate"/><published>2020-09-29T06:57:51.999000Z</published><updated>2020-09-29T06:57:51.999000Z</updated><author><name>hanlec</name><uri>https://forge.codesys.com/u/hanlec/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/fb83184bd3/?limit=25#a4d4</id><summary type="html">Hi All, I'm using CodeSys on a Raspberry Pi. I successfully use the CANbus library/module to read an write messages using SocketCAN and an attached CAN-hardware (MCP2518FD) in CodeSys I use: can0: CAN.CANBus_11bit the driver is initialized with the following config: can0Config: CAN.DRIVER_CONFIG := (usiNetwork := 0, uiBaudrate := 500, ctMessages := 200); the driver is opened/started with: can0(DriverConfig:= GVL.can0Config, eError=&gt; ); ...and as mentioned initially: everything works - almost! the...</summary></entry></feed>