Flex727

I don't know what you mean by this. There is no problem with using multiple Data Table Write Row FBs, or having multiple Data Tables if it's easier.

If you are asking me, the problem occurs in VisiLogic, but the image will also not have transparency if downloaded into a PLC.

Anyone else experience this? Whenever I have a very complex HMI screen with dozens of image elements, one or more will randomly lose their transparent property (the box unchecks itself). This has been happening to me often over the last 10-15 years through every version of VisiLogic up to and including the most recent version, multiple PLC models (all color touchscreen), and has happened on multiple computers and operating systems. Very frustrating.

Keeping a log would look something like this: To display the data use the copy row to vector FB and display the appropriate addresses for the vectors.

Unless you are keeping a log of all the recent start & stop times, you don't need to use Data Tables. Just store the start & stop times in MI vectors as a string using the RTC To ASCII FB. Then you can display the string or clear it out as desired. If you are keeping a log, then create a Data Table with 2 columns of String property and store the Date & Time at the appropriate moment with a Write Row FB. It's easy to keep the most recent value at the top of the Data Table with the Copy Rows function to copy all the rows down 1 either just before or just after your write.

How often is the PLC being polled? Try entering a Power-Up value of something around 20 in SI 103-106 for the appropriate socket.

UDP is a communication protocol somewhat similar to TCP, but unlike TCP, UDP is not connection-based. Since it doesn't require a connection, communication between multiple devices does not require separate sockets. The disadvantage is that not every message is guaranteed to be received. If your system allows the use of UDP and your communications can be tolerant of the occasional missed message, then UDP would work well for you.

Add 12 more V700s and you can communicate with all of them simultaneously. Seriously though, if your only choice is TCP protocol, then you will need to connect and disconnect each socket 12-13 times in order to communicate with all 100 sensors. The connect/disconnect process can take a few seconds, so you should be able to complete the communication with all 100 sensors in about a minute, assuming you have all the associated hardware (routers, etc) set up properly. Another option might be to move to UniStream where you do not have an 8 socket limitation as you do with the V700.

Moved to the VisiLogic forum.

And I can't believe nobody laughed at my incredibly funny joke in the last reply. 😄

Got it. No problem. At the risk of going off topic, I'd like to point out that you should not be putting two or more logic threads in a single ladder rung, as you are doing in rung 9 above. Usually it doesn't matter that much and it doesn't often result in a compile error (though that may, but not necessarily, be the cause of the compile error in rung 27 of your PUMPS subroutine), but it is extremely poor programming practice and can cause unexpected results . The whole point of ladder rungs in ladder logic is to separate logic threads into discrete pieces that can be properly compiled into machine language in an expected way.

With some of this stuff, PID loops in particular, it seems like we're all just blind pigs, but we do find an acorn once in a while. 😄 By the way, my advice about not multiplying by 10 is important. If you don't understand what I'm saying, please feel free to ask. Precision and significant digits can be very important with PID control.

I strongly recommend doing that in the linearization FB - don't just multiply by 10. Multiplying by 10 does not add any precision to your value, while doing it in the linearization block does add precision.

Status 10 = "PV exceeds proportional band, no calculation performed", in other words, the PID isn't running. What is the value in MI 203? Do you have the decimal correct in your linearization FB for psi? How about for the Set Point? I say that because you say 0-50 just above but your screenshot shows 0-500.

It would be very helpful if you would provide some data. What are the settings you are using and what is the value of the PID Status register?

Yep, I'm totally confused now as to what is being asked.

Absolutely. I've done this dozens of times. Simply modify the PLC program to be a MODBUS TCP slave on port 502 (or the port of choice), set up the other Ethernet parameters needed for comms, and have the SCADA administrator connect to the PLC over Ethernet. Provide the SCADA system with the addressing for anything desired to be displayed and you're done. Easy peasy. There are example projects that came with your VisiLogic installation that show how to do this.

Yes. However it will come into play if you have an Ethernet to serial conversion in the communication path. I don't think it's applicable here though.

If you want to turn them all off at once, use Vector Fill:

Thanks. Very interesting.

This function is a bit confusing and I've never had the need to delve into it to understand fully, but here is what I would do in the absence of any additional help: create a test program and download into an available PLC then trigger the function while watching online to see precisely what it does. Try various scenarios until you have a complete understanding. It would probably take less than 20 minutes to have it all figured out. Alternatively (which is what I would probably do since I'm usually time-pressed), would be to simply brute force it with several ladder rungs and coils as needed to make it work without the Vector Shift FB.

Resolution is almost always more important than speed, but it's important to evaluate the physical properties of the sensor as it relates to the system as a whole. The system's response to the input, whether it's a heating element, pump, or other action, is key to determining needed speed of the input. It seems to me that very few PLC programmers nowadays understand the controls engineering aspect of their software.

There isn't much flexibility in the way Real numbers can be presented on the HMI screen, therefore you are likely going to have to brute force it. It should be a fun and challenging experience.

Moved to the Vision forum. FYI, alexgarlo, we need to see inside your MODBUS Configuration FBs in order to provide any help.

Touch & hold, not tap.