Activity for skyefire
-
skyefire posted a comment on discussion Engineering 🇬🇧
Final followup on this thread, for posterity: I engaged in a long discussion with Turck tech support, and they provided me a newer version of the same module -- same EIP stack, but with updated firmware. And it worked perfectly, all inputs and outputs. So it would appear there is some small, but crucial, issue in the EIP implementations between the older module and CodeSys that "broke" the outputs. As I mentioned above, the old module worked perfectly when attached to a Fanuc robot controller.
-
So, I've been poking at this in my spare time. It turns out that my Eth0 issues on the Pi were caused by the GPIO settings(!). Long story short, I had no idea there were multiple Device Descriptions for the GPIO in CodeSys. I was using a Pi4, with the "default" GPIO description (A/B), and was playing with GPIOs (just to blink LEDs) alongside my attempts at using Ethernet/IP. It turns out that, using the older GPIO description worked, mostly, but if I ever set GPIO28 or 29 to "Output", eth0 would...
-
Hm... I have Winpcap installed (as part of WireShark) already. 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. 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. So I went back to CodeSys, and tried creating a Generic EIP Adapter under the Scanner,...
-
It occurs to me that, so far, all my successes 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. 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 will run EIP, but I haven't found a definitive answer. 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...
-
The plot thickens... 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. 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 completely unable to get...
-
The plot thickens... 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. 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 completely unable to get...
-
So, a few updates, for posterity. :P My production Ethernet/IP connection worked instantly, just by importing the EDS file. It was for a complex Numatics G3 valve&I/O setup. So my test-bench problems with the much simpler Turck adapters remains a mystery. My ModBus connection, OTOH... I've had no luck connecting to my two ModBus I/O modules: (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/)...
-
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 must b something I'm doing wrong in CodeSys, and doing wrong consistently.
-
Thanks! 3) The maddening thing is, the official (if outdated) EIP tutorial on the CodeSys Youtube channel shows the Get_Attribute function for EIP, which looks like it would give me what I need... but I can't find any details about how to use it. Argh! 4) That would be the item in the SysTray, correct? So, right-click on it, hit Start, then turn off Simulation mode and use Device>Scan... download... that seems to work! I didn't understand the difference between that and Sim mode, I thought they were...
-
I need to have my CodeSys runtime act as both an EIP Scanner and a ModBus scanner. Can these run on the same Ethernet adapter, or do I need to have two different Ethernet adapters in my project? Do I need to have separate hardware Ethernet adapters? All the tutorials I've found for setting up the EIP Scanner appear to be outdated (I'm using 3.5.16). In the tutorials, the IP address of the EIP scanner has to be set up in the EIP configuration, but in my CodeSys, there's no place to do this -- the...
-
Well, after experimenting a little, it looks like the "line breaks" option interacts oddly with the "zoom" setting -- on a rung with only a few contacts, but looong variable names making the rung longer (turning off the "fixed size for operand fields" option for this test), the "line break" didn't make the rungs "wrap" until I added enough contacts that the contacts themselves made the rung too wide. Ah, well, I can work around this. Thanks, everyone, you really saved my eyballs! 😄
-
Strange... The "fixed size for operands", setting the character length and number of lines, works. But checking the "Networks with line breaks" option has no effect. Even restarting CodeSys doesn't make it take effect (and I checked, the "line breaks" option is still checked after the restart). This user interface is odd...
-
Finally got my new Pi, and now I have a completely new problem. 😩 I followed the directions in this tutorial (https://youtu.be/QrV7laAJkDk) (using the EDS file for the Turck TBEN module, instead of "generic EIP Adapter"), but unlike before, I can't get the adapter to connect. The CodeSys Ethernet Adapter is set to the same IP address as the Pi's eth0, and I'm able to SSH into the Pi on that IP. I've also confirmed that I can ping the IP of the TBEN module from the Pi. But when I go online, the EIP...
-
Finally got my new Pi, and now I have a completely new problem. 😩 I followed the directions in this tutorial (https://youtu.be/QrV7laAJkDk) (using the EDS file for the Turck TBEN module, instead of "generic EIP Adapter"), but unlike before, I can't get the adapter to connect. The CodeSys Ethernet Adapter is set to the same IP address as the Pi's eth0, and I'm able to SSH into the Pi on that IP. I've also confirmed that I can ping the IP of the TBEN module from the Pi. But when I go online, the EIP...
-
Pure CodeSys, downloaded direct from their website. I'm still having issues with branches, but I've stumbled my way into some methods that are probably quite poor, but are working for me for the time being. I'll have to do more experimenting when I have some more free time. Thanks for the help, everyone.
-
Ah! Not all I'd hoped for, sadly, but it still helps. Thank you!
-
When creating a branch, I don't get light blue squares. And shift-clicking on multiple contacts doesn't give me any diamonds. Is there some UI setting I have wrong here?
-
I'm stuck banging my head against the wall for inserting branches into LD rungs. I eventually figured out a way to add a branch working from right to left, though that seems awfully clunky. But I've been totally unable to find a better way to do it. Trying to branch from left to right, using the Branch Below button, leaves me with no way to "close" the branch back into the rung. But now, even that won't work for me. I try to add a branch the same way that's been working for me all day, but now CodeSys...
-
Stupid question: is there a way to "wrap" long rungs of LD, the way you can in RS-Logix? Or get long contact/variable labels to wrap? I've been assigned to "transcribe" an RS-Logix program into CodeSys (3.5.16), and the 40-character+ variable names I'm stuck with mean that my rungs spread wider than my 30in monitor when I go over 4-5 contacts/coils. Or I'm stuck shrinking everything to the point my old eyes can't read the text. And constantly side-scrolling is really hampering my throughput.
-
I'll try that, thanks. But I think I'll have to set up my test case on a different computer. For the moment, I think I've managed to fix the problem, but in a rather roundabout fashion -- for lack of any better ideas, I uninstalled my original 64-bit CodeSys package, and installed the 32-bit branch (still version 3.5.16.10). And now, when I create a new project from scratch as per the tutorial, everything works as expected. This should work for me (crossed fingers!) because my eventual production...
-
I'm trying to use the 30-day trial for a Control Win V3 3S, following the CodeSys tutorial, and I'm getting stopped at the first step. According to the tutorials, once I create the project, I should get a POU window and a Device-tree window. I only get the POU window, unless/until I go "online" with the simulated PLC (using Online>Simulation). At that point, I see the expected Device, with the Task beneath it, but I can't edit anything in this view, or add POUs, or, well, anything. And the moment...
-
Well, no joy so far. I tried re-creating the Pi from the original source image again, but this time blocked it from doing any system updates. Eth0 still dies within 60sec as soon as I start the CodeSys runtime for the first time. I've been unable to find anything online that even remotely matches the issue I'm having here.
-
I'll try out the "always update" setting, thanks. But I am using them in code. I have some "blinking LED" code running where I mapped my MainTask local variables to the %Q bits of the Turck module. In the CodeSys EIP Mapping screen, I can see the %Qs changing state. But the actual "physical" outputs on the Turck module (ie, the output indicator LEDs on the module) never light. The %Is are the same, but in reverse -- I can trigger the hardware inputs and see the LEDs light, but the %Is in the Mapping...
-
I've been trying out CodeSys on a Raspberry Pi 4 as "training wheels" as a run-up to an actual project replacing an old Allen-Bradley PLC with a CodeSys PC, and run into something odd. I've been able to connect a basic Ethernet/IP I/O module (a Turck TBEN 8-input, 8-output) to the CodeSys project, and when the project is running, the online monitor shows the module as gree, and the module's Bus LED is solid green, indicating that the bus is active and the Scanner&Adpater are communicating. But when...