Flex727

You normally place SB 2 in front of configuration function blocks.

This is probably the best answer - a basic thermostat with hysteresis. Easy to implement and 100% reliable.

I haven't used it, but it's annoying as there is no way to turn it off and it fills up and keeps bugging me to delete restore points. It should be able to be disabled and/or, when it fills up the oldest should just automatically be deleted.

Restore Points is a new feature in the latest version of VisiLogic.

Did you try reverting back to the previous OS? Why did you upgrade the OS? I direct you to this thread:

Unitronics has many YouTube videos & recorded webinars. They are worth watching. Also, your VisiLogic installation came with many example projects. Review the ones that pertain to what you're doing. Unitronics also offers training classes periodically. They are terrific and inexpensive.

I'm sure it's even more difficult in VisiLogic, but please consider that as well.

Perhaps the Help file needs updating? To get the reading in F, simply use a Linearization FB, as follows:

While typing this I see a reply from kratmel, who always offers excellent advice. I'll leave mine up to provide some additional general information. ========================== No time at the moment to go through your project(s) in detail, so I'll just share my approach. When I have multiple situations that require activating a coil, I will identify all those situations and place them in a single ladder rung so that I can use a single coil without sets & resets. Sometimes each of those situations are too unwieldy for a single ladder rung, so then I create intermediate coils that will substitute for each unwieldy situation. Then each of those intermediate coils can be placed in parallel to activate the final coil needed. Set & resets I use for latches and sometimes to provide the opportunity for an HMI button to turn something on and off manually that will also be controlled by the PLC. You are correct that you can lose yourself with too many sets & resets, so for that reason I avoid them except for the items mentioned above.

This is well worth paying attention to and is a strong reason that conditional subroutine calls should be avoided.

I don't believe a V130 actually has a temp sensor.

👍 Wouldn't it be great if they offered a checkbox on the HMI element to allow the bit to be used for either hide or show.

Not with a V570 unless the program was "Burned" upon download. If not then the poster is out of luck. If it was burned on download, it would have loaded up immediately when powered on (with or without a battery). I suspect it did not which is why the poster is here.

Here is the way I would have done ladder rung 8:

Search your program for each coil that is not working properly. Almost certainly you have duplicate coils. Ladder logic does not allow duplicate Direct or Inverted coils (you can have duplicate Set & Reset coils). You can also perform a Project Optimizer under the Build menu to get a list of all duplicate coils. Also, there is no difference between coils set up in parallel or series in VisiLogic (other programming software can differ). I would also suggest avoiding using inverted coils routinely. It can be a bit confusing and it's usually just as easy to change the logic a bit and use direct coils. This is just a matter of programming style and won't affect the way your program works.

From the Help file (which everyone should note is actually very useful):

Depending on ventilation and environmental temp, I tend to see upper 30s to low 40s Celsius. A small fan does wonders.

I'd love to know what SI 14 is telling you, though you would need to calculate it using SB 14 in ladder first. I like to have a screen on most of my projects that includes PLC temperature, scan time, and other misc info that could be useful for troubleshooting.

Finally got a chance to look into this in detail. I am quite delighted with its simplicity and elegance. @Ausman, you are definitely one of the greats. By the way, I deleted SB 13. Maybe I'm all wet, but it seems like some kind of aliasing could be possible causing it to lose a second here and there. Probably negligible anyway, but saw no need to save the PLC this little bit of work. I also added a routine to "DoTheSDStuff" on first boot (first ever boot) because there would be no file created until the next Sunday even though data would be collected before then. Thanks again, Aus.

Good to hear. I hope you like working with VisiLogic. It can have a few minor irritants, but overall it's a joy to work with.

VisiLogic is definitely backward compatible. Older projects will open and automatically update to the version of VisiLogic you're using. While you can open older projects with a newer version of VisiLogic, you cannot open newer projects with an older version of VisiLogic. I have never seen the problem you're describing. How are you opening the project - from the VisiLogic menu (Project Open) or are you attempting to open by double-clicking in Windows File Manager? I recommend only opening a project directly from VisiLogic. Another possible problem is if the project file is on a shared directory that is not local. If that's the case, copy the project to your local computer to the Applications folder as set up by the VisiLogic install before trying to open it.

I went ahead and approved this post as someone here might volunteer to help. However, be mindful that this is a UNITRONICS forum, not Wonderware, Intouch, nor Schneider.

I love this! Nothing like experimental data. Try again with small, but useful program compared with larger program.

Hmm, I question whether simplifying code reduces energy consumption in the PLC. It can definitely reduce scan time, which might be important for programming reasons, but I don't think it would detectibly reduce energy requirements.

You know, I do that often myself, even though we have to realize that the PLC doesn't care in the least.