<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Activity for omiidla</title><link href="https://forge.codesys.com/u/omiidla/activity/" rel="alternate"/><id>https://forge.codesys.com/u/omiidla/activity/</id><updated>2022-02-21T18:46:06.285000Z</updated><subtitle>Recent activity for omiidla</subtitle><entry><title>omiidla posted a comment on discussion Runtime 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/7bd10254af/?limit=25#3a6e" rel="alternate"/><published>2022-02-21T18:46:06.285000Z</published><updated>2022-02-21T18:46:06.285000Z</updated><author><name>omiidla</name><uri>https://forge.codesys.com/u/omiidla/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Runtime/thread/7bd10254af/?limit=25#3a6e</id><summary type="html">I've been using various versions of these IFM AL modules, to varying levels of success. A few notes. Before SP17P2 the Profinet overhead was rather greedy and caused all sorts of problems in the soft controllers we used. I highly recommend using the 4.2.0.0 or 4.2.1.0 version if you're planning on using the Profinet master stack. Profinet_CommunicationTask can be slowed down - it's acyclic less important stuff. Profinet_IOTask running on recommended interval 1ms pre-4.2.0 ate all my resources. After...</summary></entry><entry><title>omiidla modified a comment on discussion Engineering 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/2ac5a50967/?limit=25#ce84" rel="alternate"/><published>2021-09-03T15:12:20.759000Z</published><updated>2021-09-03T15:12:20.759000Z</updated><author><name>omiidla</name><uri>https://forge.codesys.com/u/omiidla/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/2ac5a50967/?limit=25#ce84</id><summary type="html">Before you build your project again, in Device window open the PLC Settings tab. Select Enabled 1 or Enabled 2 under Always update variables. You now should be able to see your I/O when going online.</summary></entry><entry><title>omiidla posted a comment on discussion Engineering 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/2ac5a50967/?limit=25#ce84" rel="alternate"/><published>2021-09-03T15:11:28.635000Z</published><updated>2021-09-03T15:11:28.635000Z</updated><author><name>omiidla</name><uri>https://forge.codesys.com/u/omiidla/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/2ac5a50967/?limit=25#ce84</id><summary type="html">Before you build your project again, in Device window open the PLC Settings tab. Select Enabled 1 or Enabled 2 under Always update variables. You now should be able to see your I/O when going online.</summary></entry><entry><title>omiidla posted a comment on discussion Engineering 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/93bc9ccba9/?limit=25#9114" rel="alternate"/><published>2021-09-02T16:11:38.104000Z</published><updated>2021-09-02T16:11:38.104000Z</updated><author><name>omiidla</name><uri>https://forge.codesys.com/u/omiidla/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/93bc9ccba9/?limit=25#9114</id><summary type="html">That seems to have worked, thanks!</summary></entry><entry><title>omiidla modified a comment on discussion Engineering 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/93bc9ccba9/?limit=25#cd49" rel="alternate"/><published>2021-09-01T16:57:13.630000Z</published><updated>2021-09-01T16:57:13.630000Z</updated><author><name>omiidla</name><uri>https://forge.codesys.com/u/omiidla/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/93bc9ccba9/?limit=25#cd49</id><summary type="html">Hi, I'm running a (v 3.5.17.0) compiler on Phoenix-Contact PLCNext 2152/2404267 (Codesys control for PLCNext v4.1.0.0, using 2021.0 LTS firmware) as an ETHERCAT master. The system also uses an extension module for the additional network interface (AXC F XT ETH 1TX/2403115, Intel I210 based). If i use eth0 or the primary network interface as the Ethercat master, everything is running fine, my existing Ethercat devices are found and accessible. If i switch the master to use enp1s0 - the network interface...</summary></entry><entry><title>omiidla posted a comment on discussion Engineering 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/93bc9ccba9/?limit=25#cd49" rel="alternate"/><published>2021-09-01T16:14:12.801000Z</published><updated>2021-09-01T16:14:12.801000Z</updated><author><name>omiidla</name><uri>https://forge.codesys.com/u/omiidla/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/93bc9ccba9/?limit=25#cd49</id><summary type="html">Hi, I'm running a (v 3.5.17.0) compiler on Phoenix-Contact PLCNext 2152/2404267 (Codesys control for PLCNext v4.1.0.0, using 2021.0 LTS firmware) as an ETHERCAT master. The system also uses an extension module for the additional network interface (AXC F XT ETH 1TX/2403115, Intel I210 based). If i use eth0 or the primary network interface as the Ethercat master, everything is running fine, my existing Ethercat devices are found and accessible. If i switch the master to use enp1s0 - the network interface...</summary></entry></feed>