Alexander

We always recommend using the Prolific USB to Serial drivers, which can be downloaded offline. When in your device manager which drivers are currently being used? Other than checking the drivers it may also require a Windows setting, such as running as an administrator. If this option is not set than it can cause the communications error that you experienced. To run VisiLogic as an administrator right click on the VisiLogic.exe file, navigate to the Compatibility tab, and select the check box to run the program as an administrator. Once this is set restart VisiLogic and ensure you are using the same COM port that you computer assigned through the Windows device manager. This should allow you to communicate. In general any USB-Serial converter should work, though we have heard of issues when using a Gigaware brand cable.

There is a clear history buffer function block that you can enable when needed. It can be found under the utilities/ alarm menu in VisiLogic.

Did you reinitialize and clear the operand values before downloading the program into the new PLC? If this was not performed than any values left over in the memory of the new PLC will still be there, and can affect the program. It is possible that this is the issue. I would recommend reinitializing the controller and seeing if this solves the issue. If the data you are seeing is wrong, is there any screen on the HMI where you can change it? The program itself does not know what values are needed and may need to be entered manually in order for correct operation.

How do you wish to detect the power failure? Do you have any external devices or inputs that are activated when power fails without notice? Our systems do not have any built in detection for if power fails, once there isn't any power the system shuts down and does not process any code.

Hello Salimin, I'm glad that Flex was able to answer your question. Please know that if you can not find answers to your questions within our help files or webinars we are happy to assist you directly. You can contact us within Unitronics technical support department by sending an email to Support@Unitronics.com.

Square wave signals can be created by using the high speed PWM functions and varying the duty cycle (0-100%) of the 24V output signal. For example a duty cycle of 50% would result in the output representing a 12V output, or if connected to an external solid state relay 50% of the output power it was providing. A sinusoidal wave may be more difficult to create depending on if you are using a PWM or analog output. An analog output may be the best to create a sinusoidal load. What type of output are you planning on using?

Is your PC the device that is listening? If so you will need to perform a TCP/IP connect function from the PLC's ladder code. Can ping the PLC from the PC?

Hello Nick, Is the battery backup installed in the V570? If the unit is powered down and the battery is low, or not installed than it is possible to lose the program and display no application. You will need to re-download the program. We recommend performing the Download All and Burn download option. This will download the program into the flash memory of the controller which will retain the program in case the battery backup fails when power is cycled.

You are correct. When linking a vector it will automatically use the sequential operands after the starting location. So in your example if you select MI0, it will automatically use MI 0, 1, 2, and 3 for the vector. Each one will represent an octet within the IP address.

Yes, as Joe mentioned you must first initialize the Ethernet card using a specific function block (TCP/IP Card Init). This function block can be found under the COM TCP/IP menu in VisiLogic. The IP Address, Subnet Mask, and Default Gateway will be defined in this block either using a defined value, or by linking a vector of 4 MI's for each address.

There was not any information in your reply. Were you successful in solving the issue?

We recommend running our software as an administrator. This is a Windows setting that if not applied can generate the run time errors as you have seen. It is not likely anything you have done or set up within your project. To run VisiLogic as an administrator, right click on the VisiLogic Icon, choose Properties, navigate to the Compatibility tag, and select the box labeled ‘Run this program as an administrator’. Hopefully this should eliminate the error you are experiencing. How did you set the IP address within the controller? Did you program it over serial first, or did you set the IP address through info mode in the controller?

Do you have any other Unitronics USB-mini cables to test with? Does the same cable work with previous V570's? By testing with a secondary cable and other V570's you should be able to determine if it is the cable that is the issue.

This can occur if the software is not running as an administrator. For Windows 7: Running VisiLogic as an administrator can be accomplished by right clicking on the VisiLogic icon, choosing Properties, going to the Compatibility tab, and selecting the box labeled Run this program as an administrator. For XP: To run the installation file as an administrator, you can accomplish this by right clicking on the VisiLogic icon and selecting RUN AS. You will then need to type in the username and password for the administrator account

Currently the only method to modify the RTC is on the PLC itself, either through UniApps or by modifying the system tags using an HMI widget for the time or date.

It may be the operating system that is causing the HMI to look like it is blank. The PLC will beep when the HMI is not displaying properly due to the operating system. You will need to put the unit into Boot Strap Mode, which is similar to a computers safe mode. To do this you will need to do the following: 1. Power off the PLC 2. Hold your finger on the HMI and power the PLC on 3. After 2-3 seconds tap the HMI screen firmly at least 2 times 4. Attempt to communicate with the PLC Hopefully this will put the unit into bootstrap mode. If you are able to put it in this mode then perform the following: 1. In VisiLogic navigate to the Connection drop down menu and select Communications & OS 2. Select the 4th tab for Operating System 3. Select check and update the O/S if it is not up to date 4. If it is up to date select the Advanced button then select each of the Bin, Boot, and O/S files manually. It should automatically open the folder containing the correct file. After updating the HMI should hopefully be restored and you should be able to establish communications.

I'm glad that you have found the software enjoyable so far. Within VisiLogic there are two sets of PID function blocks as you have noticed. The first is the original PID blocks which is generally only used when working with legacy code. We would not recommend using this, and would suggest using only the functions from the PID Auto-tune menu. The new one is titled PID Auto-tune, which has the same capabilities as the regular PID, yet has an additional function block that allows for auto tuning your system. If you have set up the original legacy PID functions you will need to replace all of the existing PID functions (config, run, etc) with the same ones from the PID Auto-tune menu. There is no requirement that you use the Snap-In I/O. It is an option for the V570 as it does not come with on board I/O, though if you are using a local expansion adapter it will work jut the same.

Can you still communicate with the V570? What is displayed on the screen? It may be necessary to update the operating system or reinstall the firmware. Once this is complete we recommend downloading a blank program, then attempting to download this project again.

It may be necessary to perform a full uninstall, then reinstall of VisiLogic. In instances where the initial install is not successful, we recommend running the installer file as an admin. This should hopefully solve the error.

This compile error is from Visual Basic. Did you have an error in an of our software such as VisiLogic?

Yes, there are two possible ways to compare programs for the Standard Series controllers, such as the V120. The first method is to perform a Verify operation, under the communications menu. This will compare the Ladder, Ladder Parameters, HMI, HMI Fonts, Timers, counters, Hardware configuration, Functions blocks, Data Tables, and Upload data. It will show it it matches or if it does not, but will not indicate specific differences. The second method is to use VisiDiff which can be found under the Tools menu in VisiLogic. This compares two VisiLogic program files to one another but will show in greater details the differences between the two programs. VisiDiff can not be used to compare a program that is currently within a controller.

The nature of floating point operands it to be able to hold very small and very large numbers using a scientific format. Due to the nature of how the 32 bit floats operate they often will have small rounding errors as their format is not exact. For this reason we do not recommend using the float operands for precise math operations. If possible whole number integers such as a Memory Long or Double Word may be used instead. Although they do not have a true decimal point, a theoretical one can be applied and displayed on the HMI.

Currently running more than one instance of UniLogic is not supported. Please know that this feature request has been passed to our development team.

In the images I did not see output 7 being used. Is it in a different part of the code? One issue that I do see is that the same coils (Output #0-3) are being called in multiple nets. This creates the issue where the logic will process each net, but the state of the output will only reflect the last shown net. For example if there are conditions to reset Output #0 in nets 60 and 65, then only the logic in net 65 will matter. Even if the logic in net 60 tried to reset output #0, if the logic in net 65 does not trigger the output to reset than it will not be reset. This is because the PLC processes the scan as follows. 1. Read physical inputs 2. Process ladder code 3. Update outputs Since the outputs are only updated after the entire ladder is run, this will cause the last instance of an operand to be the determining condition,

You are correct, the Vision Series controllers do not support TLS/SSL encryption for emails. If this feature is required the UniStream models do support the use of encrypted email servers.