Flex727

Stumbled on this and it's worth a watch. I think everyone here will find it interesting. Will our jobs be made obsolete by AI? Not seeing it in my lifetime (I'm old), but certainly eventually.

This forum does not contain a "Support Team". It is a user forum staffed by volunteer users, though a few Unitronics employees make an appearance from time-to-time. Unitronics support can be reached at support@unitronics.com. For a hardware issue under warranty you might also consider contacting your distributor for return or replacement. Regarding your question, I haven't encountered that particular issue before but perhaps someone here has. Good luck.

Nice solution, kratmel!

I probably should have put in rung comments: Rung 1 - reset all 6 MBs Rung 2 - Store 1 in the bit corresponding to the offset value of the random number MI Rung 3 - turn on the correct output

Here is how I would do the part you are uncertain of: You don't have to use vector functions - you can just use a series of compares - but this is easy and concise. You also don't have to group the elements in rung 3 the way I did with SB 1. I just like to group similar items in that way to save space and make for easier readability.

I just recently installed 9.8.96 and no registration was required. Thank you, Unitronics!

This has no meaning. An MB is a bit - it is binary, either 0 or 1. A random number would be an integer, typically an MI.

Even without a State Machine (which I use almost religiously thanks to learning about it from Joe), it's not that difficult to write a program that allows things to restart gracefully since all operands are retained automatically. The programmer must be cognizant of any timers and power-ups, but it's not that difficult.

In VisiLogic, use SB 16. UniLogic has the General.Touched Bit. Both do the same thing.

Right-clicking and selecting "Disable" is normally how a ladder rung is turned off, but there are some elements that VisiLogic won't allow to be in a disabled rung. Sometimes I want to disable a rung with those types of elements for some testing or troubleshooting and never thought of doing this <insert headslap emoji>. Thanks for the tip, MAL!

I'm more familiar with MODBUS than Protocol TCP/IP, but shouldn't there be slave addressing in your Protocol TCP/IP Configuration FB?

Hopefully you're aware of the vast differences between the way Ethernet works on a V700 vs a V1210. Why is Socket 3 the only available socket? Have you confirmed that you have not duplicated port numbers on any of the sockets? Are the PLC and server on the same subnet? What communications protocol are you using? Have you set up the connect logic properly? Can you post your program here for us to take a look?

Unitronics support always recommends initializing all 4 sockets at power-up even if only 1 or 2 are going to be used. This helps focus your attention on making sure there is no duplicate assignment. Do I do that? Rarely, but having all 4 default socket assignments memorized helps avoid the screwups.

Make sure the PC and PLC are on the same subnet. Note that your PC's wireless subnet will likely be different than the wired subnet.

I don't see anything wrong here. Are you able to connect to the PLC from a PC? Are you able to connect to your peripheral from a PC? Have you double-checked all IP addresses and port numbers? I see that you are using port 502 in the PLC and the peripheral. Nothing wrong with that, but just checking. Are you sure the peripheral is set up to be a MODBUS slave on port 502? I see in the comment that the slave ID MUST be 255. In my experience I haven't found that to make a difference, but you have ID 254. What happens when you try to connect? When you're online does SB 150 come on, even briefly? Does MB 0 come on briefly? Does MB 4 immediately reset? Just this morning I was fighting with a PLC that wouldn't connect with MODBUS. I was ready to pull my hair out until I replaced the Ethernet cable. The cable was relatively new and was just recently working. Make sure you troubleshoot the ENTIRE connection, including cables, hub, etc. If you're not using a hub, are you using a crossover cable or adapter?

Sockets are just defined pathways to specific ports. You can use any of the 4 sockets interchangeably as long as you have initialized them correctly and don't have 2 with identical settings. Each of the 4 sockets have a default initialization, but can be changed at any time (normally at start-up) with a socket initialization function block. The fact that the rung comment and the following ladder rung don't match is just a typo in the comment. Of course, the socket number must match in the initialization FB, MODBUS configuration FB, TCP connect FB, and the MODBUS read or write FB. I'm not sure what you're expecting here, 3 is the same in both hex and decimal. Enter a number greater than 9 if you want to see a conversion.

You lose me here. I don't see any link between Input O and the Set Coil in Picture 3 and there is no power flow to the Set Coil (TraceDataRecorded). I haven't downloaded your program file as I need to know the UniLogic version it was saved with.

You set up the coils in the same way you set up the registers (different tab). Be sure "Write" is an allowed action and you have the addressing correct. Feel free to post your program here for us to take a look.

No worries. I only pointed it out because I think we were confusing the OP. He put it in his program exactly as you showed with the Toggle coil on the left rail.

I've heard of Ignition that is a SCADA/database system. It looks like the OP needs help setting up MODBUS communications with a SCADA system. @Akash, please tell us what PLC you are using and what MODBUS protocol you are using.

That's calling an HMI screen, not a subroutine. You can't have a Toggle coil hanging on the left rail. I suppose you could, but it would uselessly toggle on every scan.

What is this, @Ausman? This cannot work. @Nico, this is awful coding and I don't even know where to start. Tell me in words exactly what you are trying to do (for example, "I'd like to turn O-84 on and off with a single button on screen", or "I need to have two separate buttons, one for OFF & one for ON", or...) and I would be happy to show you the proper way to do it. You claimed that you were calling the "02 Elevator Test" subroutine, but I sure don't see it. A general principle to keep in mind for the future - only one logic thread per ladder rung (rungs 2 & 4 each have two logic threads).

And this one?

Have you reviewed this thread?

Try this thread: