Date: Mon, 17 Apr 2023 15:52:45 +0200 From: David Robertsson <david.robertsson@gmail.com> To: freebsd-hackers@freebsd.org Subject: Current status of the openPOWERLINK idea? Message-ID: <CAF1NeHd6ipgq7k-W7h%2BH7pAiY%2BSFf6sc12tR8iL7uRn7y8E31Q@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
--0000000000000a706505f988826a Content-Type: text/plain; charset="UTF-8" Noticed openPowerlink was added to the ideas page, is there someone out there already working on this? Otherwise this would be something that is aligned with my personal interests to work on. Not sure what the best path forward is. The OpenPowerlink "stack" today has two options as for Linux (afaik). 1. Userspace daemon with the help of LibPcap. 2. kernel driver that unloads the driver from a network card and then uses it for communication with powerlink gear. I have been using OpenPowerlink myself since 2014 in a Linux environment, and I'm not so sure the option 2 is desired. To build the code, it assumes that you know what gear it is you want to communicate with. So from a list of gear that the user has "setup" you then import that list into openConfigurator to generate a mnobd.cdc and a xap.h file. This is then used to broadcast the binary to all the powerlink devices on the network. The xap.h file contains a struct describing the devices - for example in which order the digital input & output modules are connected to every brain module (control node). One idea I have; is to try to make a port of the userspace daemon or perhaps try to make a standalone lib that can be used in any project that aims to run a powerlink control / master node on FreeBSD. What do you all think? Best regards David --0000000000000a706505f988826a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Noticed openPowerlink was added to the ideas page, is ther= e someone out there already working on this?<br><br>Otherwise this would be= something that is aligned with my personal interests to work on.<br><br>No= t sure what the best path forward is.<br><br>The OpenPowerlink "stack&= quot; today has two options as for Linux (afaik).<br><br>1. Userspace daemo= n with the help of LibPcap.<br>2. kernel driver that unloads the driver fro= m a network=C2=A0card and then uses it for communication with powerlink gea= r.<br><br>I have been using OpenPowerlink myself since 2014 in a Linux envi= ronment, and I'm not so sure the option 2 is desired.<br><br>To build t= he code, it assumes that you know what gear it is you want to communicate w= ith.<br>So from a list of gear that the user has "setup" you then= import that list into openConfigurator to generate a mnobd.cdc=C2=A0and a = xap.h file. This is then used to broadcast the binary to all the powerlink = devices on the network.=C2=A0The xap.h file contains a struct=C2=A0describi= ng the=C2=A0devices - for example in which order the digital input & ou= tput modules are connected to every brain module (control node).<br><br>One= idea I have; is to try to make a port of the userspace daemon or perhaps t= ry to make a standalone lib that can be used in any project that aims to ru= n a powerlink control / master node on FreeBSD.<br><br>What do you all thin= k?<br>Best regards<br>David<br><br><br></div> --0000000000000a706505f988826a--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF1NeHd6ipgq7k-W7h%2BH7pAiY%2BSFf6sc12tR8iL7uRn7y8E31Q>