Flex727

Unitronics has a number of example projects in the Help menu of VisiLogic. There are also a number of training videos available online. Check those out and see if it helps. You can also search the internet on Ladder Logic to get a basic understanding of how all this works.

I think, but not sure, that this is an issue with the specific fonts you have installed in the project.

+1 on this!

You kill me, Ausman!

My recommendation is to break all that logic up into separate ladder rungs, and maybe even separate subroutines. It is always a risk to pack too much logic into a single ladder rung because the compiled code may not exactly match what you expect. When you break the logic up into simple steps it is easier to read and troubleshoot.

I don't see anything wrong here. My recommendation is to uninstall and reinstall Remote Access. Be sure to install and run Remote Access as an Administrator.

Also, if that ladder rung is in a subroutine, make sure the subroutine is being called by the Main routine.

Sorry that didn't help. Can you clearly see the button labels in your VisiLogic project? Are you certain the button label and the button background colors are different?

Rather than an array of Structs, could you build a UDFB and call it for each motor?

Did you download the project again after the PLC update? If so, try downloading a blank project, perform an initialize and reset, then download your project again.

Were any of them reset or power cycled when the screen was active? See my post in the "We're Listening" Forum topic.

The easiest thing to do is to use a serial or USB cable to download the program. If you don't have that available and must download using ethernet, do the following: 1) Confirm that PLC and PC are on the same subnet (192.168.192.xxx, in your photo). Change one or the other to match. 2) Identify the PLC Name. Go to INFO Mode / Version / Software / PLC Name 3) Enter the correct PLC IP address and PLC name in the VisiLogic - Connection / Communication - PC Settings / Select Connection Type - TCP/IP (Call), then Project Settings. Test connection by clicking on Get OPLC Information. I recommend checking and/or replacing the battery immediately to avoid having to repeat all this. You can check the battery by going online with the PLC and looking at the value of SB8. A value of 1 means the battery needs replacing. Good luck!

I can't open your images either, but I do want to say I didn't mean to say that you HAD to have a linearization block, just that it would give you more meaningful numbers to work with. You could just as easily use 204 and 1023 as your min and max, respectively, in the tank variable, but if you want to display a value for tank level in addition to the graph, the user will not easily understand what it means without the linearization.

I notice in the Vision products that the bit assigned to be ON when an HMI Display is active does not get reset if that screen is active when the PLC is reset. Is this a feature or a bug? Shouldn't we expect that a bit assigned to be ON when a display is active be turned off when that display is no longer active, even if that happened due to a PLC reset? I make it a habit to assign a power-up Reset to each of those bits to prevent unexpected problems, but I can find no mention of this issue in the Help files.

Look under the "Vector" menu when editing your ladder. There are a number of useful tools there that should solve your problem.

How are you trying to connect Remote Access to the PLC? Are you able to connect VisiLogic to the PLC in the same manner? The connection should be exactly the same.

Two things. The input you receive at MI0, MI1, & MI2 will be an integer from 204 - 1023. Do you have a linearization block to convert the number to something meaningful (e.g. tank level from 0-100% or perhaps tank volume from 0 to 70 gallons, or whatever the tank capacity is)? Your tank variable appears to be improperly set up. The min and max parameters should be whatever 4mA and 20mA represents (i.e. the limits you have on your linearization block). MI0 does not go there.

I save under a different name regularly, usually with just a version number changed. What drives me crazy is that when I do a "Save As..." in VisiLogic, the current filename isn't pre-filled in like it is with every single other Windows program on Earth. What I have to do is go find the current file, select it, then change the version number. I can't count the number of times I've almost accidentally selected the wrong file, which would be a disaster.

Frankly, I'm not an internet security expert. I would direct that question to Unitronics support (support@unitronics.com).

I don't think there's anything wrong with making a recommendation to a customer for a particular brand if it's based on experience and not based on some sort of kickback or profit motive. Indeed, I often recommend Unitronics over other PLCs because I consider them a good fit for their application and the best value for them.

A few years ago I had difficulties with various brands of SD cards and found the most reliable compatibility with Unitronics PLCs was SanDisk. In recent times I have had much less trouble, but always use SanDisk anyway. There is still an occasional problem, though fairly rare, but I'll say I also have the occasional problem with my desktop and laptop.

Use Store Direct to copy that value to a temporary location on every PLC scan. Then use SB2 to copy the value back on startup.

Are you giving it a full 30 sec to a minute to detect the card? It does sometimes take longer than you think it should.

Glad it helped. I'll also point out that Setting SB168 using SB2 when you have the Power-Up value as "SET" is redundant. Same with the values you're assigning to SI 104 & 108. You can either set a Power-Up value or assign a value with SB2 - your option, but there is no need to do both. As to your other question - there is no need to set values for the Sockets you aren't using, but it won't hurt anything if you do.

By "table" do you mean a Data Table? It doesn't look like you need anything like that. You seem to have a good handle on the logic - just code what you've written in the above post in ladder logic and start checking your logic. If you get stuck, just post your code here and someone will assist.