Flex727

It sounds like you stop calling the subroutine when you let go of the button. Since the subroutine is no longer called, it cannot turn off the coils. Unless there is some specific need, do not conditionally call your subroutine.

There is one included with VisiLogic. Go to Help/Examples/Version 900/Project examples/Communications/EX-RC1/EX-RC1 With Analog/EX-RC1 with AI4AO2/EX-RC1 with Digital and AI4AO2.VLP

Why are you resetting SI 104 and 108? I normally store a value of 10 in SI 103-106 and a value of 20 in SI 107-110. I find that a value of zero in those System Integers will cause the PLC to be unable to restore a lost connection.

I use the "RTC To ASCII" function block. I find it convenient to use RTC To ASCII #7 to store mm/dd/yy to 5 MIs and RTC To ASCII #9 to store hh:mm:ss to 6 MIs. Then I copy all that to a Data Table along with some text to describe the event I'm logging. This works very well.

See this Forum topic: http://forum.unitronics.com/topic/662-how-do-i-use-version-swapper/

Use "Legal Entry" in the HMI input to know when the timer has been updated. Then compare the Timer Preset with the min and max values you want. You can either reset the preset to the min or max value, or pop up a screen that informs the operator that they've made an error. The option you suggest does exist for numeric entries and I agree that it would be nice to have it for Timer inputs also.

Make sure you're not trying to export the subroutine to a folder that is nested too deep. I find that VisiLogic has file path limitations that are slightly more restrictive than Windows itself.

The V350 is capable of communicating at a baud rate of 115200. This speed will greatly reduce the program download times over using 38400. Typical values for Timeout and Retries are 2 second timeout and 3 retries. This will also reduce the time you must wait to find out your communications failed.

No reason why that shouldn't work, but why are you communicating at such a slow baud rate? And why the 12 retries?

If you're only missing the cable and have the RJ11 to DB9 connector, you can use any ordinary phone cable for a landline phone.

Moran, you need to distinguish between the "Tag: Link" and the "Tag: Touch...". The Tag: Link is what will be changed in your ladder to have your button change in appearance. The Tag: Touch is where you define the actions that will occur when the button is touched. Those actions can include Set or Reset of the Tag: Link.

Yes, it takes 3 steps, in this order: 1) Compare your MI to another MI used to temporarily store the value, and if equal, run a TD timer set for the "certain amount of time" you need. 2) Store Direct the first MI to the temporary MI. 3) A Positive Transition of the timer initiates the stuff you want to do.

Timer functions in Ladder are simply Contacts and Coils with Timer selected instead of Bits. Once you've selected the Timer address you want, you can then select which of the 3 Timer types you need. On the HMI, click the Timer icon on the sidebar.

Oh, got it. Use Strings: Transpose, and select the function "Byte to MI (Expand)".

Upper left.

I'm not sure what you're asking. Memory Integers (MIs) ARE Registers. Just make sure the memory is identified as strings on both ends.

The screen resolution is 800x600 on the V1040 while the screen resolution is 320x240 on the V570. When you change the PLC model in the HW Configuration from V1040 to V570, every HMI element beyond 320x240 will be permanently lost. You will first need to update every screen on the V1040 program (save under a different name) to fit all the elements within 320x240. HMI elements will need to be re-sized, moved, and fonts changed. After completing that, you will be able to change the PLC entry in the HW Configuration and the program should work properly. Be aware that if you have complex graphics with shading or 3D effects, you will lose much of that detail due to the reduced number of pixels available to work with. After the update be sure to thoroughly test your resulting program with the V570.

My previous answer did not encompass the V700. It has 8 Sockets instead of 4 and there are other minor differences from the other Enhanced Vision products, but the Help files are there. Regarding strings stored in MIs, be aware that an MI consists of 2 bytes. Two characters are stored in an MI, one character in the upper byte and one character in the lower byte. The numbers are not added together, but when you look at the stored value in decimal, it can be hard to decipher.

The only way to stop the program, that I know of, is through the Information Mode or by command from a PC that is online with the PLC. The one exception would be if the Watchdog timer were to expire. Another possibility would be if the PLC battery is bad and there was a power failure (I think you only lose RAM values in the M91, not the program [not sure off the top of my head], but that may be enough to cause your problem). From a hardware standpoint, other than the battery, the RS232 serial port may have had a failure - or a failure in the connection between the PC and PLC. If you're using a GSM modem to communicate, there are a number of other possibilities to investigate.

Should I set up the ethernet card in each process of communication or only once?Initialize the Ethernet card once using SB2 or when applying a new IP address to the PLC without restarting. The IP local port for each communication should change?Not sure what you're asking here. You always identify a Port # for each device you communicate with. Both sides of the communication need a Port #, but they do not need to be the same #, nor do separate remote devices need to have unique Port #s. You have 4 sockets, but you can address them with any allowed Port #. The communications occur from a local Port # to/from a remote Port # through a particular Socket. In the FB TCP/IP connect or close there is a parameter named "Remote port", what is that?It is the port number for the remote device you are connecting to or communicating with. The ping FB is linked with the PLC IP or PC IP?The IP in the Ping FB is the IP of the device you want to Ping from the PLC. You also identify the socket # you use to send the Ping.

I would be surprised if this is the most cost-effective solution for you, however, I think you'll find that many PLC manufacturers have the same issue - they (properly) wish to protect the intellectual property rights of the program owner.

It's not possible to give you a definitive answer without knowing your logic (for example, what is turning on MB13?), but It would seem that you need to use a TE (Extended Pulse) timer if you want the output to be on for exactly 10 seconds. You should also use a Positive Transition contact to activate the timer, especially if it's a pushbutton. If you're wanting to DELAY the keg rinse operation by 10 seconds, then you're using the correct timer. You're welcome to post your project file here if you want more detailed help. By the way, you will get better help if you post to the VisiLogic forum rather than the UniLogic forum, as it appears you are using VisiLogic.

If you decide you want to re-create the original program and need to hire a programmer, you may be able to get help by posting details in the forum "Projects seeking Programmers".

Yes and yes. Use the "Load Timer/Counter Preset" (under the Store Menu) to move the TD1 preset into an ML and then "Store Timer/Counter Preset" to move the ML value into TD2. You can detect an update of the TD1 Preset by using the "Legal Entry" bit in the operator entry function. It will go high when an update is made. You can then use a Positive Transition of this bit to do the Load & Store for TD2.

Most of the Snap-In modules do not have analog input filtering. Use the filter function block in VisiLogic.