Flex727
-
Posts
3,330 -
Joined
-
Last visited
-
Days Won
241
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Flex727
-
-
In VisiLogic, use SB 16.
UniLogic has the General.Touched Bit.
Both do the same thing.
-
51 minutes ago, MAL said:
That is dead code. That rung is only applicable to the v700. Its essentially a comment for this use.
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!
-
1
-
-
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?
-
1 hour ago, Joe Tauser said:
By also assigning port 502 to socket 3 without manually assigning something else to socket 2 we left the PLC in a position where it didn't know whether to shit or go blind.
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.
-
3 minutes ago, Jreese37 said:
I'm not able to connect over ethernet to the PLC from PC.
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?
-
27 minutes ago, Jreese37 said:
This line in the comments says "Below, both Ethernet card initialization and MODBUS Configuration are done as Power-up tasks.
Note that Socket 2 must be initialized, via the Socket Init FB, to function as a TCP Master. Network ID number MUST be 255!"I noticed that it is set to socket 3 in the demo file, and also set to client, along with the MODBUS IP CONFIG function block socket is set to 3. I had seen in some prior documentation that some were using different socket numbers there in the initialization rung. I was highly confused about how that could ever possibly work?
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.
33 minutes ago, Jreese37 said:I'm a bit confused as to how the hex conversion in Visilogic works, if I enter a 3 into the Start of vector box, and set to hex, it doesn't appear to be giving me the actual value for 3(0x0003.) Although I don't suspect this matters whether I enter it there as hex or decimal?
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.
-
44 minutes ago, Akash said:
That input is linked to in Picture3 Set bit but it is not red why?
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.
-
37 minutes ago, Ausman said:
Re the toggle coil, I had never thought it would be put on the rail, but agree it looks that way. This is akin to those manuals where the people who made the product explain how to use it, but because they know it innately the manual has lots of missing info because the writers know all about it in the first place.
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.
-
1
-
-
1 hour ago, Ausman said:
Elevator test is being called, but only on one scan after TD210 times out. Rung 4.
That's calling an HMI screen, not a subroutine.
1 hour ago, Ausman said:Flex, my suggestion was a different way to control the output other than what was initially being done, but I was expecting Nico to control the toggle somewhere else using logic they would think out. The whole point was don't have 2 MBs that will possibly conflict with each other controlling an output. How to do it and how to display it was a point of learning for Nico.
You can't have a Toggle coil hanging on the left rail. I suppose you could, but it would uselessly toggle on every scan.
-
On 1/15/2023 at 3:30 PM, Ausman said:
MB7 O84
-(X)------( )----
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).
-
-
Have you reviewed this thread?
-
-
1 hour ago, kratmel said:
Useful information about OS
Based on the spreadsheet in the post linked to by kratmel, you might try 9.7.60 if 9.8.31 doesn't work. Not sure if you can open a 9.8.09 project with VisiLogic 9.7.60 though.
Of course the other option is to upgrade the PLC firmware. It isn't all that difficult.
-
Try 9.8.31. I don't know all the firmware versions and associated VisiLogic versions, but I suspect this one might work.
-
By the way, when you opened the project in your VisiLogic 9.8.91, it should have warned you that you were opening an older version project in a newer version of VisiLogic and also told you the version of VisiLogic the project was last saved with. Don't ignore that warning!
-
I'm not sure exactly what you're asking, but you can set any number of timers you wish using the same ML that you loaded from the master timer. You could easily load from master and set all 13 timers in the same ladder rung.
-
8 hours ago, Senior said:
I am of the opinion ,one doesnt need to do a software update after making only an minor change.
And just to add to and clarify: the firmware update isn't required because you changed the program - it's required because you tried to load the PLC using a newer version of VisiLogic. We recommend not doing that.
-
I do this frequently. Have a 'master" timer that you set on your HMI, then perform in ladder "Load Timer/Counter Preset" (under the "Store" menu) to an ML. Then perform "Store Timer/Counter Preset" to all the timers you want to set from the master timer. Easy peasy.
-
Are the iPhone and PLC on the same subnet?
handle an emergency stop and resume the action
in UniStream: Hardware
Posted
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.