https://forge.codesys.com/forge/talk/Engineering/thread/faa776fb2a/2021-02-22T14:53:31.447000ZRecent posts to A few quick Ethernet/IP and ModBus questions2021-02-22T14:53:31.447000Z2021-02-22T14:53:31.447000Zskyefirehttps://forge.codesys.com/u/skyefire/https://forge.codesys.com4c7c6da94d946e4e7a93b19880181fd944c4fbb0

<div class="markdown_content"><p>Hm... I have Winpcap installed (as part of WireShark) already.</p> <p>If I lacked some critical component, would CodeSys generate any warnings? B/c so far, I only get "device not found" in the EIP Scanner Log.</p> <p>As a test, I connected the module as an EIP Adapter to a Fanuc robot. This doesn't use an EDS file, just basic settings: Product Code, Manufacturer Code, Major/Minor Revs, and number of Bytes In/Out. It worked fine.</p> <p>So I went back to CodeSys, and tried creating a Generic EIP Adapter under the Scanner, using the same "generic" settings that worked on the robot. Still no luck.</p> <p>I've also tried connecting this module to my Raspberry Pi running CodeSys, and get the same failure.</p> <p>This is <em>really</em> frustrating. I can't figure out what I'm doing wrong here.</p></div>

2021-02-21T16:21:53.216000Z2021-02-21T16:21:53.216000Zhence.perssonhttps://forge.codesys.com/u/hence-persson/https://forge.codesys.com982c909546019d8d069c0ec93236ea02a38cbd7d

<div class="markdown_content"><p>Winpcap was it.. Needed for control win runtime not needed for rte. Needed at least for profinet unsure about ethernet/ip</p></div>

2021-02-20T09:14:24.312000Z2021-02-20T09:14:24.312000Zhence.perssonhttps://forge.codesys.com/u/hence-persson/https://forge.codesys.comaad2fdad4317aec0c5b3da71d8001e5a5b66217f

<div class="markdown_content"><p>Regarding win runtime.</p> <p>From what I remember modbus tcp works out of the box. Profinet needs to install a free software don't remember the name. Maybe the same is true for ethernet ip ?</p> <p>I have tested profinet in the demo runtime and that worked but ad I said needed to install some software first.</p></div>

2021-02-20T07:50:39.701000Z2021-02-20T07:50:39.701000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com96c5acb8942d3ead07866384ecaedc9ded1de5e7

<div class="markdown_content"><p>if you read the product description:<br/> <a href="https://store.codesys.com/codesys-control-win-sl.html" rel="nofollow">https://store.codesys.com/codesys-control-win-sl.html</a><br/> <strong>you see what is included (and licensed)</strong><br/> Fieldbus support</p> <p>With the delivery of the Runtime Package the following fieldbuses are supported:</p> <div class="codehilite"><pre><span></span><span class="n">CODESYS</span> <span class="n">CANopen</span> <span class="n">Manager</span> <span class="o">/</span> <span class="n">Device</span> <span class="n">CODESYS</span> <span class="n">EtherCAT</span> <span class="n">Master</span> <span class="n">CODESYS</span> <span class="n">EtherNet</span><span class="o">/</span><span class="n">IP</span> <span class="n">Scanner</span> <span class="o">/</span> <span class="n">Adapter</span> <span class="n">CODESYS</span> <span class="n">J1939</span> <span class="n">CODESYS</span> <span class="n">Modbus</span> <span class="n">TCP</span> <span class="n">Master</span> <span class="o">/</span> <span class="n">Slave</span> <span class="n">CODESYS</span> <span class="n">Modbus</span> <span class="nb">Serial</span> <span class="n">Master</span> <span class="o">/</span> <span class="n">Slave</span> <span class="n">CODESYS</span> <span class="n">PROFIBUS</span> <span class="n">Master</span> <span class="n">CODESYS</span> <span class="n">PROFINET</span> <span class="n">Controller</span> <span class="o">/</span> <span class="n">Device</span> </pre></div> <p><strong>extra license is needed for:</strong><br/> Product options</p> <p>The product can be extended by the following chargeable product options:</p> <div class="codehilite"><pre><span></span><span class="n">CODESYS</span> <span class="n">BACnet</span> <span class="n">SL</span> <span class="n">CODESYS</span> <span class="n">KNX</span> <span class="n">SL</span> <span class="n">CODESYS</span> <span class="n">SoftMotion</span> <span class="n">SL</span> <span class="n">CODESYS</span> <span class="n">SoftMotion</span> <span class="n">CNC</span><span class="o">+</span><span class="n">Robotics</span> <span class="n">SL</span> <span class="n">CODESYS</span> <span class="n">TargetVisu</span> <span class="n">CODESYS</span> <span class="n">WebVisu</span> </pre></div> </div>

2021-02-19T14:41:31.177000Z2021-02-19T14:41:31.177000Zskyefirehttps://forge.codesys.com/u/skyefire/https://forge.codesys.com6acba61f81d850fd9453bd0c31a2cac417f94080

<div class="markdown_content"><p>It occurs to me that, so far, all my <em>successes</em> with EIP and ProfiNet have been on a licensed runtime -- my failures have been on my desk machine, running the "demo" mode 2hrs at a time.</p> <p>The demo mode does ModBus fine, but is it limited on EIP or PN? I've heard elsewhere that the demo mode can't run PN, but <em>will</em> run EIP, but I haven't found a definitive answer.</p> <p>Does anyone know where there might be an official CodeSys document that details just what the "demo" mode can/can't do? (aside from the 2hr run time limit)</p></div>

2021-02-18T14:15:44.353000Z2021-02-18T14:15:44.353000Zskyefirehttps://forge.codesys.com/u/skyefire/https://forge.codesys.com320febede28e050950cef03c5916e39af86db5c1

<div class="markdown_content"><p>The plot thickens...</p> <p>The two "production" ModBus modules I've been trying to connect to are proving to be very stubborn (despite working fine on an RS-Logix PLC) -- my customer is looking into replacing them with EIP modules instead. EIP on this CodeSys PC (Win64, non-RTE) has been working effortlessly (so far) on a big Numatics G3 valve/input module stack.</p> <p>In the meantime, I've been using a Turck TBEN multi-protocol I/O module on my lab bench to experiment with. I've been <em>completely</em> unable to get CodeSys to connect to this module via EIP. But when I switched the module to ModBus, I was able to connect with no trouble at all. Is CodeSys's FieldBus implementation just really finicky?</p> <p>This TBEN module will also do ProfiNet -- I guess I'll try that next.</p></div>

2021-02-17T17:14:47.780000Z2021-02-17T17:14:47.780000ZMorberishttps://forge.codesys.com/u/morberis/https://forge.codesys.com40e979cc8d08398229d8cf8b6c55c56cddadaf3b

<div class="markdown_content"><p>Heh, it's probably too late to switch your modbus TCP/IP acromag modules to profinet module? Are you using the module with i20?</p> <p>Unfortunately the few times I've used modbus tcp/ip it's just worked so I don't have much advice for you. Have you tried the modbus communication with the EIP communication removed?</p> <p>If you're spending hours trying to get it to run if you have the authority or can get permission I would recommend buying a support ticket.</p></div>

2021-02-15T15:08:13.283000Z2021-02-15T15:08:13.283000Zskyefirehttps://forge.codesys.com/u/skyefire/https://forge.codesys.coma54ff17a55d691b2a2b59c68e23ad09c86bab1d1

<div class="markdown_content"><p>So, a few updates, for posterity. :P</p> <p>My production Ethernet/IP connection worked instantly, just by importing the EDS file. It was for a complex Numatics G3 valve&amp;I/O setup. So my test-bench problems with the much simpler Turck adapters remains a mystery.</p> <p>My <em>ModBus</em> connection, OTOH... I've had no luck connecting to my two ModBus I/O modules:<br/> (https://www.acromag.com/shop/signal-conditioning-network-i-o/ethernet-io-modules/ethernet-digital-i-o/xt1120-16-channel-discrete-ethernet-i-o-modules-with-sourcing-outputs/)<br/> The ModBus log just shows "socket error." Nothing more. I've confirmed I can ping the modules from my CodeSys runtime computer. And I spent hours playing with the Connection settings, without any luck -- I couldn't even get a different error!</p> <p>And I was informed that this CodeSys will <em>also</em> be running ProfiNet. So now I may have <em>three</em> bus protocols running on the same ethernet port. All fairly low-traffic, so hopefully it will work, but....</p> <p>I've been told that the "free" 2hr runtime will do <em>all</em> the FieldBusses <em>except</em> Profinet, for some odd reason (probably Siemens Licensing, I would guess). I have yet to try this for myself.</p></div>

2021-02-04T15:11:18.493000Z2021-02-04T15:11:18.493000Zsgronchihttps://forge.codesys.com/u/sgronchi/https://forge.codesys.com31d108902d8047c3b0190516f13241c0560ad221

<div class="markdown_content"><p>I cannot help you about EIP because I never used it (just know something about it).</p> <p>Simulation mode works inside the IDE, and it executes 61131 code and visualizations (with some differences to the real TargetVisu). No communication with the external world.</p> <p>The other is the real Windows SoftPLC, which needs a license to work, full featured.</p> <p>But if you are developing for a PLC that's not x86-based (ARM, POWER, Aurix, ...) like I usually do, if you want to test your logic locally the two ways are<br/> 1) testing in simulation;<br/> 2) maintaining a second project or a second device in the tree targeting Windows SoftPLC replicating your logic;<br/> The second one is time-consuming.</p></div>

2021-02-04T15:05:40.024000Z2021-02-04T15:05:40.024000Zskyefirehttps://forge.codesys.com/u/skyefire/https://forge.codesys.comf138fb677efb2d091352896725d7ac2b6220652c

<div class="markdown_content"><p>Addendum: I get exactly the same issue connecting these modules to my Raspberry Pi CodeSys engine, and I've checked that these modules function on a regular Allen-Bradley PLC. So there <em>must</em> b something I'm doing wrong in CodeSys, and doing wrong consistently.</p></div>