<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Activity for danielbeers</title><link href="https://forge.codesys.com/u/danielbeers/activity/" rel="alternate"/><id>https://forge.codesys.com/u/danielbeers/activity/</id><updated>2024-09-22T02:23:11.113000Z</updated><subtitle>Recent activity for danielbeers</subtitle><entry><title>danielbeers posted a comment on discussion Automation Server 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/automation_server/thread/fd9d32741b/?limit=25#bf1e" rel="alternate"/><published>2024-09-22T02:23:11.113000Z</published><updated>2024-09-22T02:23:11.113000Z</updated><author><name>danielbeers</name><uri>https://forge.codesys.com/u/danielbeers/profile/</uri></author><id>https://forge.codesys.com/forge/talk/automation_server/thread/fd9d32741b/?limit=25#bf1e</id><summary type="html">Hello, I have a project using some EPEC PLC's. Some of them are programmable using Ethernet and some use CAN. We currently have a Raspberry Pi that is acting as a gateway to the Codesys Automation Server and is successfully working for the PLC's communicating over ethernet. I am trying to achieve a similar result for the PLC's that have only CAN access. I have PEAKCan drivers on the Pi, and can successfully send/receive messages. But the Gateway does not recognise the PLC when scanned from the Automation...</summary></entry></feed>