Alexander

Gabriel, The OPLC has to have an OS that supports the project features. When using an older OS in the OPLC with a more recent project this is likely the cause as to why it was not properly displaying. I'm glad to hear that it is working now.

Are you operating the HMI in person, or are you connecting to the unit remotely?

Hello, Within U90 ladder you can check and update the O/S by navigating to Controller, then Operating System. Once in this menu you can check the current O/S and then download any available O/S files drop the drop down menu. New O/S updates can be added by navigating to Help\ Check For Updates\ Operating System.

Hello Gabriel, The mask entry option will display all entered numeric values as asterisks. This is to hide any information the user may not want openly displayed on the HMI.

Hi Keith, Without having the PLC name it is not possible to limit the number of downloads using a UniDownloader file. With the UniDownloader file they will not be able to view any logic or program information, but they will be able to download the program to any available controller. If possible, the customer could provide the PLC name from info mode on the controller. The Jazz controller has a clone module that limits the amount of downloads of a program, but this is limited to this model only.

There is a function block, Next Step, that when triggered will progress to the next step. This can be used when a step has a 0 timer and will not automatically go to the next step. You can also use the function block, Go To Step (Index) which will reference an MI value for a selected drum configuration. The value within that MI is the step you will go to. So for example if you are referencing MI 0 in the Go To Step FB and the value stored in that operand is 5, then when triggered the drum will immediately jump to step 5. This information can also be found in the VisiLogic help files in the contents section under Ladder\ FBs Library\ Drum.

Russ, How are you monitoring the RTC? Are the respective SI's changing (SI 30-38)? If you are using the RTC to ASCII functions I would check to see that the subroutine they are in is being actively called.

As Linxchas mentioned you will be connecting to the IP of the router, and not the PLC's local IP address. I would double check the routers IP, that an available socket is set for port 20256 as a slave (Default socket 1), and that the card and socket are properly initialized. Using a PC on the same network as the PLC, I would also attempt to ping the routers IP to ensure you can connect to that before troubleshooting the port forwarding. Also, after cycling power check the following system bits to make sure they are powered: SB 141: Ethernet: Card Exists SB 142: Ethernet: Card Initialized SB 143-146: Sockets 0-3 Initialized respectively depending on which one you are using

One of the images could have become corrupted in the controller. When downloading the updated project the corrupted image could cause a conflict and cause the "Failed to Download Images" message to appear. Performing another type of download will likely cause the same type of issue if it's trying to overwrite an existing corrupted image. The best course of action is to download a blank program containing no images to clear out the previous program. This should erase the images and clear any flash memory. After this is complete you should be able to download normally, using any of the download options. The spare V570 likely did not have the corrupt image which is why it downloaded without issue.

Hello, Within the project you have the PID configuration being powered by the power up bit, SB 2 in the HE PID subroutine. However, in your main routine you have a bit, MB 0, acting as an initial condition that calls the subroutine. If you are calling the subroutine to run after it has already powered up the PID configuration will not be able to run. All subroutines that have power up conditions being set should also be run on the first scan. Once the configuration is run you will be able to use the status message within the PID configuration to troubleshoot any issues.

It should be counting down as soon as the MB30 contact powering the TD timer is active. Is MB 30 accidentally set up as a coil instead of a contact? All contacts are used as inputs, and coils are used as outputs. If it it set up another way this could be why it is not working as you expect. The TD coil needs to remain powered and count down to 0 before the corresponding contact linked to the TD timer will become active. The nets should look like the following with the first net to power the timer, and the second to utilize the timers bit once active. MB 30 TD -| |-------( )- TD -| |- We also have a helpful webinar on using and creating timers within the logic that I would recommend. http://www.unitronics.com/support/webinars/timers---hd

Each Modbus command function will have an attached status operand if an error occurs. These status message values can be found in the VisiLogic help files. Though the value is not what you are expecting, it appears as if the PLC and Yaskawa are communicating but just not being addressed correctly. I would double check the slave address table for the Yaskawa which should describe the function and addresses for each register/coil.

Is the coil for the timer being called in a subroutine that is not running? Is the input condition, MB30 staying active during this time? The timer will not automatically display its current value unless selected or viewed in the operands window in online mode.

It is not required to have these devices set up within the MODBUS configuration block. You only need to know the IP and port number for the Yaskawa when using the TCP/IP connect function block.

The network ID will be 255 for all MODBUS IP configuration blocks. Have you been able to connect to the Yaskawa? It will have it's own individual port number, and it will not be the same as the port you set in the socket configuration. The socket configuration port will only be referenced when you are connecting to the V350 only if it is set up as a slave. Only once you are connected can you use the regular MODBUS commands to read/write information. When receiving information from the Yaskawa you will not perform the connection, the Yaskawa will have to perform the connection to a slave socket on the V350. You will also need to run the MODBUS scan function for the slave socket so it can receive MODBUS commands. We have webinars on both Ethernet and MODBUS communication that should help explain how to configure the logic in greater detail. http://www.unitronics.com/support/webinars

The sockets do have default values set up, but they can be changed and initialized to suit your application. You will have to run the MODBUS IP configuration block on start up, and as long as you have one socket set up as a TCP master you will be able to send out MODBUS commands. You will also have to set up a TCP slave socket and have the MODBUS ScanEX function block constantly scanning for that MODBUS configuration. Once you have performed the connect function using the slaves IP and port number you can then send MODBUS commands. Yaskawa should provide the slave address table that shows which registers to read from, and what MODBUS commands should be used with each. In this case the slave address appears to be 10001 as provided by the documentation that you have. The device can then connect and send information back to the V350 using the Ethernet cards IP and the TCP/IP slave socket port number that was initialized.

mckruger, you can accomplish this by having the PTO bit set an MB when it is turned on using a positive transition. The MB that is set can power a TE timer. The TE timers bit will be active while running allowing you to have it run for a defined pulse length. While running you can use this timers bit to power your output.

This should all be possible through using the Function Block Protocol Scan function in conjunction with our Data Tables. Since the barcode can be up to 55 characters and variable in length you will need a way for the PLC to detect that the message has ended. Within the protocol scan function you can utilize a silence option in miliseconds to detect that the message has ended. The information that is read will be stored in the message buffer and can be copied to a data table. Using the data table will allow you to easily configure a FIFO system. Each time the data is written to row, you can perform a data tables copy row function to shift all of the rows except the last down by 1. The data table can have as many rows as necessary depending upon how much historical information you wish to save. When the photo eye is triggered and another barcode is read you can store this information to a vector for comparison purposes instead of the data table which is for "learned" information only. To compare the two you can perform a Data Table search and compare the newly stored vector against all of the rows in the data table. If the information is matched then it will output the row number that it was found on. If not than it will return a -1. Using these values you can use comparison functions to set or reset the good and bad bits. You can utilize both the Serial and Ethernet options within one program. Only one scanner can be used per port, but there are separate functions for Serial Protocol and IP Protocol so it is possible to have a program that utilizes both. We have a very helpful webinar on using our Function Block Protocol: http://www.youtube.com/watch?v=6jpuKTxXznw Also helpful might be our webinars that cover Data Tables.

The logic that you displayed appears correct. Have you also configured the M91 controller for use as as MODBUS master? The U90 help file under Communications/ MODBUS describes how to configure the controllers Network ID, timerout, retries, time delay, and baud rate. If this is not set up properly or the baud rate is not matched to the device you are communicating with this could cause an issue.

Hello Lawry, The maximum length for the EX-A2X expansion adapter cable is 20.0m. Other sizes are also avaialble in 0.5, 1, 2, 2.95, 4, 5, 6, and 10m lengths. They are proprietary cables so unfortunately we cannot provide the pinout diagram for them.

Moved to new thread. In the future please post any errors or issues to a new thread. Pertaining to the error it is likely an issue how VisiLogic was installed. If you are using Windows 7 or Windows Vista it has certain installation requirements. 1. UAC(user account controls) must be disabled when VisiLogic is installed and remained off when running. I have included a link containing a PDF for Windows 7/Vista and general reinstallation. These instructions also include the manual removal of a couple of files, which if not removed could be the cause of the errors you are experiencing. VisiLogic Installation instructions with UAC disabled: http://forum.unitronics.com/index.php?/topic/664-can-i-use-visilogic-with-vistawin7-uac/ 2. Running VisiLogic as an administrator is recommended for all operating systems. This 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.

The RS232 signal is only sent over 4 of the 6 pins on an RJ11 connector. The pinout for our controllers is detailed in the V130-33-R34 installation guide available on our Technical Library. http://www.unitronics.com/Downloads/Support/Technical%20Library/Vision%20Hardware/Vision130%20Installation%20Guides/V130-33-R34_INSTAL-GUIDE_10-08.pdf The pins will not match exactly. You will want to connect the outgoing pins from the RJ11 port, to the incoming pins on the modem/D-sub cable (Tx to Rx, Rx to Tx). When using RS232 you will also generally not need the DTR and DSR pins. Only 3 of the 6 pins on the RJ11 cable are required to make a connection: Pin 3; From the PLC (Tx) should connect to the Rx on the modem/cable Pin 4; From the PLC (Rx) should connect to the Tx on the modem/cable Pin 2 or 5; From the PLC (0V)should connect to a 0V reference on the modem/cable. Only one connection is required.

You can absolutely send an SMS message to another number after receiving the same message. It is not necessary to directly use SB's for this purpose as shown in your ladder image.This is described in more detail in the help file in U90 under Communications/ SMS/ SMS Message Properties. In the SMS Configuration you can link a specific message to both a send and receive MB. After the message is received the receive bit will go high. This can directly trigger the send bit which will send the message to all selected recipients within the SMS configuration. This will allow you to both receive a message, then immediately send it out again.

Thread moved to Software/ Vision PLC series and VisiLogic section. There is no default setting to power up to the last loaded string library, but it can be accomplished within the logic. Each time a string library is set store that specific libraries value (1, 2, 3, etc) into an operand reserved for last loaded library. Then upon power up always set string library indirectly using this direct operands value. In this way it should always load the last utilized library even after cycling power.

Hello, You are correct as it unfortunately is not available on the V570 or other enhanced models. That function is only available to Standard Vision Series Controllers and only pertained to moving images horizontally or vertically.