Flex727

Many of the Unitronics PLC models are very inexpensive - actually cheaper than what you would pay for simulation software for some other PLCs. Just buy a PLC and you will find that it's an even better learning experience than using a simulator.

Servers without encryption. I'm not sure there are any that still exist.

Have you reviewed this pinned topic?

Try setting a Power-Up value of about 10 in SI 105.

Every programmer has a slightly different way of data logging and it greatly depends on exactly what data needs to be logged and how much. I set up and write to Data Tables when I perform data logging. Can you provide specifics on exactly what you want to accomplish?

The code is essentially the same across the entire Vision line.

Moved to Vision forum. I strongly recommend uninstalling 9.8.95 and instead installing 9.8.96.

Moved to Vision forum.

I guess I'm the odd man out. Once I carefully studied these graphs in the Help file and recognized that the Preset get downloaded with the project, I found Unitronics' Timers to be quite intuitive and easy to use. Fernando does have a point about Timers losing their Presets for unexplained reasons, but I have found that in electrically noisy environments, any PLC memory register can get scrambled and Timers seems to be first on the list to get zapped. Gabriel's post came through while I was typing, but we seem to be in agreement. Also, while I rarely use the TA Timer, I do use the TE Timer very often. I'm sure it was intended just as it says, an Extended Pulse, but I also find it useful when I need to trigger a timer with a pulse instead of a direct contact. You just have to use a negative transition of the output bit instead of positive.

Use a TE (Extended Pulse) Timer. Activate the timer with a negative transition of the run bit or positive transition of the stop bit (depending on how you have your logic set up - looking above you would need the negative transition). Use the TE Timer output bit in parallel with whatever is activating the output. This will allow the output to continue to run for the preset time after stop signal occurs.

Thank you!

Since it appears you have a bit of unaccounted for resistance somewhere, just multiply your result by 1.01 (multiply by 101 then divide by 100). Be careful of register overflow - I recommend moving to MLs for this operation. There's also no law that says you must use 16383 in your linearization block. Use 16224 instead (or whatever gives you the answer you need).

Moved to VisiLogic Forum.

I was talking off the top of my head, but you actually experimentally determined the facts. I'm impressed.

Change the link in your Binary Text Variable to O 0, delete the Toggle checkbox, and add MB 7 as your Touch Property, Then add the following ladder rung to what I provided previously:

I think you absolutely can assume that. The PLC executes each ladder rung fully before moving to the next rung. This is one of the basic principles of ladder logic and fundamentally why you shouldn't have multiple parallel logic threads in a single rung. One thing I frequently do is combine multiple, very simple, related, but not dependent logic threads using SB 1. Something like this: Here I have 6 related items that have no mutual dependency that are very simple. Combining them this way makes for much easier to read code and simplifies comment documentation. Yes, the logic and code would work without the SB 1, but I think good programming practice should be carried out universally. This is true for physical outputs since they are not physically activated until the entire scan is completed. Addressing in a meaningful way is good programming practice. In this instance, I would use ML 11, 12, 13, 14 or ML 101, 102, 103, 104. But, as I always also say - the PLC doesn't care.

You have full control of the color and text of each state of the Binary Text Variable. Look carefully at Joe's example.

In that case, you are WAY overcomplicating things. Do this in combination with Joe's suggestion above with the Binary Text Variable: If you want the button to be momentary contact instead of toggle, just use an HMI button instead of the Binary Text Variable.

There is nothing wrong with this. It should work perfectly every time. In my nearly 15 years of full-time experience using VisiLogic I've never encountered a software bug such as you describe. Also, I concur with @Fernando Castro - use ladder for HMI screen calls, not the Links & Jumps tab on the HMI screen. The primary purpose for that tab is for non-touchscreen PLC models that might need different physical buttons, or a specific subset of physical buttons, to make HMI screen calls from various specific screens.

Yes, this is easy to do, but I can't help unless I understand your desired logic. What do you want to happen if there is a conflict between the HMI button and the input? I'll also add that you fail to understand how ladder logic works. If you're familiar with normal computer programming you will be led astray. A simple open contact with a direct coil is often thought of as an "If" statement - if I0, then O0 (looking at your top rung). But what most people new to ladder logic fail to understand is that the statement is incomplete. There is always the implicit statement: If Not I0, then Not O0. In your logic O0 and MB0 will always be in the same state as I0, irrespective of MB6 & MB7 (except for the single PLC cycle when they transition, which will be too quick for you to see).

Worry not. It's almost impossible to brick these PLCs. Software can be irretrievably lost, but the controller will still be serviceable.

You cannot download a .vlp file to the PLC from an SD card. You must install VisiLogic (available free from Unitronics) on your PC or laptop, connect to the PLC using a programming cable or mini-USB (if available on the PLC), then download the program. It is preferable to use the same version of VisiLogic as used to create the .vlp file. There are also a lot of ins & outs to this process and you should probably seek some guidance from an experienced programmer. My recommendation is to send the PLC back to the manufacturer and have them perform the install. Seems pretty lazy to just drop a .vlp file on you and expect this to turn out well. You're welcome to PM me if you decide you would prefer to engage paid professional help.

What I have done when I must use a Vision PLC but need certain communications protocols not available in the vision line is use a UniStream USC-B3-R20 and communicate the information to the Vision PLC via MODBUS TCP, as Dan is suggesting. It's a little more expensive than a Raspberry Pi, but if you already know how to program the UniStream then it's really convenient. It will just sit on the DIN Rail alongside other components and works like a champ.

This is exactly my philosophy.

You cannot upload the program from the PLC to your PC unless the program was downloaded with the "Burn Upload Project" option. Without that, the program cannot be retrieved from the PLC. You can try by "Upload" from the Connection menu while connected to the PLC and it will tell you.