Alexander

Hello, If you are unfamiliar with VisiLogic I would recommend watching our series of webinars online which can be found on our support page. http://www.unitronics.com/support/webinars Also, there are many sample project examples within VisiLogic. These examples can be found within VisiLogic by navigating to the Help menu and selecting Examples then Version 900\ Project Examples\ Data Table.

There does not appear to be anything wrong with the code in the image that you posted. Has this issue occurred again? If the issue is repeatable please send your program in for further review to support@unitronics.com If we are able to replicate this issue consistently we may be able to determine the issue that caused it. Often this type of error occurs when a very specific sequence of events occurs within the PLC. Please let us know the exact conditions of any I/O or settings within the controller that led up to this error being displayed.

Which unit are you using and how do you have the input wired? Also, how do you have the high speed input configured within the software? Could you post the code that you are using?

The Ldr code will direct you to the subroutine that is causing the issues. If possible please send the project along with as many details as possible to support@unitronics.com for further review.

Hello, Do you know if the V350 unit would be acting as a Modbus master/client or slave/server? If you are unfamiliar with programming our software I would recommend watching our series of webinars. These will help to demonstrate the logic and how to set up different functions and configurations within VisiLogic. We also have specific webinar topics for Modbus RTU which can be found below. The Modbus IP (over Ethernet) commands will be exactly the same as Modbus RTU though you will need the additional Ethernet logic for it to work. Modbus IP example code can be found in VisiLogic under Help/ Examples/ Version 900/ Project Examples/ Communications/ Ethernet/ Ethernet Modbus IP. http://www.unitronics.com/support/webinars/modbus

Please know that the V1210 is rated at IP66/IP65 when panel mounted. It is possible to connect sensors and other devices via a RS485 cable to our controllers. Many customers have used this option before. The RS485 is only the cable and you would also need to know the protocol that the sensor will be using. Over serial the V1210 can communicate Modbus or any open ASCII protocol. From the devices PDF it does seem that Modbus may be an option. If using a protocol other than Modbus using our FB protocol blocks you can accept any ASCII string information as long as the message format is known. Also, ensure that the COM port on the V1210 uses the same serial communication settings as the Black Box device.

You are correct, the Enfora GSM modem does use 2G service for operation. We are not familiar with the Sixnet IndustrialPro SN-6000 router. Does it utilize a serial GSM or cellular modem? Any brand of Ethernet or cellular modem should work with our controllers as long as they have the required Ethernet COM port added to the controller. The controller would them be set up in exactly the same way as when on an office network. The only difference would be how the PLC is receiving the internet connection.

Unfortunately we do not have information regarding the internal ladder code as this is proprietary. However, additional general information can be found in the .zip file that contains an example application for the enhanced webserver as well as PDF documents describing how it is utilized with our software. Using these directions you should be able to test and implement your own html code running on one of our enhanced Vision Series controllers. This Complex Web Server .zip file can be downloaded on the PLC Tools and Application section of our support page at the the following location: http://www.unitronics.com/support/plc-tools-and-application

This type of error is caused by a fault within the logic. An unlikely sequence of events or a faulty FB within the program could potentially cause this issue. To review the code within VisiLogic you can use the Ldr code to search for the subroutine that causes the issue. This feature can be found under the Edit menu, then selecting Find Subroutine by Ladder Error Code. This error may also be generated by a fault in the O/S. I would recommend either updating or reinstalling the operating system within the controller.

Moved to Vision PLC Series and VisiLogic section

Yes, it is possible to print the ladder within the U90 Ladder software. The print options can be found within the Project drop down menu where the ladder, HMI, operands, and other elements can be printed.

You should not need any special cable. A standard USB to USB-mini cable is all that is required. Does your PC detect the cable when plugged into the UniStream Panel? Please try using the following method to connect the UniStream via USB: Power OFF the PLC > Unplug the cable > Close UniLogic > Open "Task Manager" and force the "Unitronics Notifier" to quit > Open UniLogic > Power ON the PLC > When the PLC finished to boot, plug the cable back in. If this does not solve your issue please send an email into support@unitronics.com

Since it is not possible to test when disconnecting the units, you will have to test if the issue occurs again. When/if this happens monitor the input/current to the PLC and each I/O point. Also, record which inputs/outputs are on or off at this point since it may be a combination of points that causes this issue. This information may help to determine the root cause of the problem.

Yes, there are till designated bits/tags that are controlled by the system. They can be found within the System tag window (to the left of Global) within UniLogic. These system tags can then be referenced within the project the same as any other tag.

Which version of VisiLogic are you using? Even if the PLC is displaying the boot mode screen you should be able to access Info Mode and update the O/S using a micro-SD card. Using an SD card formatted with our SD card Suite you can place the V130 O/S within the system folder and download this to the controller. Do you have another V130 operating with this updated O/S? If so you can upload the file onto the SD card, then download it to the controller with the issue. You can access Info Mode by pressing and holding the 'i' key. The default password to enter Info Mode is 1111. Then navigate to SD then O/S and upload/download the file as needed.

Yes, It could be caused by the I/O or attached modules or from the environment that all of the equipment is installed in. Is it possible to disconnect the V1210 and all of the I/O and set it up in an office environment without any of the I/O points connected? If the issue continues to occur it could be the hardware, if the issue is resolved it may be the environment or a combination or the I/O with certain points being on/off.

If it also occurs with a replacement module it is likely the environment that it is installed in (electrical noise, or power surges, failures) that is causing the issue. As you mentioned this could be from certain I/O points being turned on/off.

The issues could very likely be caused by the frequency of the information being written to the SD card. I would try writing this data table information to the SD card less frequently. This can be accomplished by writing the entire table only after a certain number of rows or after a longer period of time. Hopefully this should resolve this issue.

I would recommend checking the power when it occurs and if possible have the technicians report if they notice any combination of devices being turned on/off that triggers the condition. If the program is not executing once the screen has gone dark then it is likely that the controller is powered off. It is strange that the unit boots up and works properly up after cycling power. Usually as long as the unit is receiving enough voltage and current then it will stay powered or even cycle power once the requirements (24VDC & up to 0.5 amps) is restored. Having to cycle power indicates either hardware or power flow being the issue if you can no longer communicate with the unit. If you continue to experience issues please send an email to support@unitronics.com.

If the VisiLogic version and O/S version were not a match then it will display the PLC needs to be updated message. You can also check for more recently released O/S files under the help drop down in VisiLogic. I'm glad to hear that it's working with VisiLogic 9.4.0, though the same steps should solve the issue in all VisiLogic releases. If you continue to experience any issues please send an email to support@unitronics.com.

Unfortunately there are not any system registers or bits that will indicate any issues with power. It appears as if the unit is powering off or experiencing a surge which can not be anticipated by the PLC. Do you notice that this occurs during any specific times (when an output or drive turns on or off)? When you checked the voltage and current was this when the unit was displaying the black screen? When displaying the black screen is the I/O units still receiving power? I would recommend checking the current draw directly from the power supply if possible. The voltage is slightly high since the V1210 runs on either 12 or 24VDC. The V1210 itself draws a maximum of 1 amp at 12V and 0.5 amp at 24V. Where did you measure 0.8 amps from? Even though the power supply is rated for 6A it may be supplying less or experiencing periodic surges. Also, does this occur with any other similar system or is this isolated to this individual unit?

What type of I/O is this controller using. Does it have snap in or local I/O attached? If the I/O draws more current than the power supply is able to provide it could trigger the controller to lose power. When this occurs I would recommend checking the I/O modules to see if they are running and check the power to the V1210 to see if the voltage has dropped below 24VDC. If possible also check to see if the current has dropped as well. It could be that when a combination of I/O or drives on a single circuit are turned on it draws too much power and causes a units to lose power.

Topic moved to Vision PLC and VisiLogic section. When this issue occurs can you still communicate with the unit? Is it possible that the system integer controlling the brightness, SI 9, has been set to 0 within the program? Also, when the screen is displaying black can you access Info Mode by pressing and holding on the screen for 5-7 seconds? This will automatically set the brightness higher so the HMI screen will be visible. Then you can navigate to operands and modify the SI value manually. If this works it is only a temporary solution if this works as the application will likely reset this value back to 0 at some point.

This can occur if the system images have become corrupted corrupted. The keyboard is still functional even thought the keyboard is not visible. The images becoming corrupted, distorted, or missing is not common but can sometimes occur after updating the firmware in a controller or after many downloads. If images become distorted or corrupted please follow these steps to resolve the issue: Download the latest system files (O/S, BinLib. BOOT) via COM port RS232 (or mini-USB). If OS is up-to-date, please click “advanced” and select files for OS, boot, bin lib. Please select the largest numbered file in the available folder. Download a blank application Open your project and restore the system images (see below how to) Perform build all from "build" menuDownload your application.