Flex727

I suspect the program is using some smoothing or filtering of the final value so that it doesn't jump around too much on the HMI display, or they're using a time period other than 20 seconds. That formula is perfectly precise and is using the K-Factor (the K-Factor of .25 means divide by 4, which you are doing).

Sounds like you have a math problem. Since each pulse is .25 liter, divide the number of pulses received in 20 seconds by 4, then multiply by 180 (3600/20) to get liters per hour. In order to reduce rounding error when working with integers, I would do the multiplication first then the division (or just simplify to multiply by 45 (180/4)). Depending on your flow rate, you may need to use MLs instead of MIs to avoid register overflow.

You cannot get an instantaneous flow rate from a pulse flow meter but you can approximate it. The basic procedure is to measure the time between pulses then divide the volume of each pulse by the time measured. If the pulses come too rapidly to measure the time interval accurately, then sum the pulses over a small time period and divide. Depending on what you plan to do with the calculated flow rate, you may need some smoothing or filtering of the data.

Just organize all your possible recipes into Data Table(s) and select them that way.

It's actually only about a minute or two, but Fernando is right - it would be much better to figure out how to do what you're wanting to do using Data Tables to keep everything confined to a single program.

Yes, this can be done easily. Look under the SD menu and select Clone to place in ladder. With that function you can save and load any type of SD program file. Look in the Help file to see the proper way to implement this function.

Moved to the We're Listening forum. Maybe someone from Unitronics will come along and address this - lead times are very long everywhere. Hopefully the supply chain issues and other covid issues are beginning to alleviate and lead times will return to normal.

As a general rule (is this ALWAYS the case? I'm not totally sure) the pieces on the left side of a Function Block are inputs to the function and the pieces on the right are the outputs of the function, so yes they auto-populate.

No this was a software update for PLCs in the field. Updating the software revision would require a firmware update that I don't want the customer to have to contend with. I have managed to complete the update without further problems. It required me to check the graphics after every small edit before saving. Doing it in this way prevented the problem from materializing for some unknown reason. Indeed it is. I will not ever voluntarily use that version.

Nope it hasn't. One of my pet peeves also.

And nowadays most tech experts just know how to use Google. Seems like every day I get a question from a friend or family and all I do is type their exact question into Google and give them the answer I find there.

If the answer to my question is yes, then the simplest way would be the following:

I'm not clear on what you're trying to do. The buzzer shuts off when EITHER the key#1 is pressed OR 8 hours have passed? What is SB 53 supposed to do? Also, DO NOT place multiple logic threads in a single ladder rung. Rung #4 should be two separate rungs and rung #5 should be 3 separate rungs.

Nearly new desktop PC that is never powered down. It only gets rebooted when MS decides to update. Never had a date or time issue. How certain are you that VisiLogic actually opened the file you renamed?

Just to clarify - the graphics are gone from VisiLogic, not the PLC.

Well, I'm kicking myself. I repaired all the damage yesterday and thought everything was fine. I opened the project up this morning and the same thing happened again. So this time I checked the HMI after each change and saved under a different name. Every step of the way I checked and saved, then finally got all the changes done and no missing graphics. What the heck is going on? Is this some sort of quantum mechanical thing - it only happens if I'm not looking at it? Here is the projected memory map of the completed project: Not even close to running out of memory.

Check the spec sheet for the model PLC you are using. They are all available at the Unitronics website.

Yes, you've learned that from me and a few other senior members of this forum. The issue is that when the rung is overly complex, the compiler may not execute the steps in the order you might think. In this case, it doesn't matter which order the two increment functions are executed therefore it doesn't matter whether the rung is set up as serial or parallel.

Yes, .152 corresponds to 9.8.65. Any 9.8.65 project opened in a later VisiLogic version will have the .152 project created which is just a backup of the original project in case you subsequently save it in the later version without a name change. I just tried that and a new .152 file was created. Not sure why that doesn't happen in yours. I was using VisiLogic 9.8.80 to open the 9.8.65 file.

Yes, I do this too. However, this particular update was completed in a single day so there was no incremental backup available. This is created when opening the project in a higher version of VisiLogic. Unfortunately, I never tried to open the file with another version, so there is no backup available. I only lost a few hours work, not the whole project, but this is still very disturbing to me. I had emailed the faulty file to my customer and fortunately he requested an additional update today before trying to load the file onto a working system. When I started working on the additional update was when I discovered the problem. I checked the file that I sent him via email and the problem existed there and not just on my local hard drive. I also checked the file on a different computer with the same result.

I just had a very disturbing event happen. When saving a large and very graphics intensive project in VisiLogic 9.8.80, all of the graphics have disappeared. Every HMI screen still exists, but they are all blank. The ladder logic appears intact. Anyone had this happen? This is a first for me in almost 15 years of VisiLogic experience. Any suggestions for recovery?

Why do you say this? It is functionally equivalent to place these increments in either series or parallel.

I'm going to say I had a similar issue many years ago. My memory is a bit fuzzy as to the specifics, but I also had a single bit that refused to cooperate. I never found the cause and finally decided to move the MB to another address and the problem was solved.

I wanted to toggle ALL the bits. Toggle Bit in Vector only does one.

@Fernando Castro, thank you for this. I suddenly had a pressing need for this strategy on my current project and it worked perfectly.