kratmel

Two tips: 1. Try to check (read) what info you write to sensor before power-off. 2. Try to not disconnect green wire before power off... I think that after starting the sensor, it has communication settings in RAM memory. If the green wire is connected, the standard setting from ROM is recorded there. If green wire is not connected, the setting is loaded from another EEPROM memory. Actually you write something to EEPROM memory. So this information cannot be used by the sensor immediately - it must be turned off and it will download it after restarting. That is, it is important to follow the correct wire connect -disconnect sequence which is not specified in the manual...

Yes!

From manual wiring SET, V+ (power) when boot module into the "setting mode". Not connected or connected with the GND when boot into "mode of operation". Module configuration parameters such as Modbus address, baud rate, parity, communication protocol is composed of module inside the EEPROM (power down storage device stores). The specific configuration sometimes forget these parameters that cannot communicate with the module. In order to prevent this problem, the module has a special mode called "mode". When the module is based on the "mode" electric start, the module communicates with the following parameters: Fixed Modbus address 0 Communication configuration is 9600, N, 8,1 (9600bps, no parity bit, 8 data bits, a stop bit) That is if you connect green wire - sensor settings after power on is not from EEPROM but from standard (i select it via bold) internal settings.... You must use this setting for connect to sensor - then change EEPROM setting to needed value - than disconnect green wire - power off-on and connect to sensor via new EEPROM programmed settings. Communication protocol for Modbus-RTU Configuration parameters in EEPROM will not because the module into the "mode" and "will change, when the module is in communication with in the EEPROM configuration parameter is still running mode".

V350 J R34 has 3 Encoder input.... But if you need one more encoder input EXF-RC15 must be used. I try to generate all possible option for add encoder input without EXF-RC15

URB TCP + URD0200E(or URD0200D) + V100SET2 installed to V350. But i do not test this new hardware on Vision PLC. Maybe using secondary V130 Slave PLC with HSC +2хV100SET2 installed to V350 and V130 and modbus TCP can be faster in delivery and even cheaper.

There is a bit of a problem here, because the output may not be activated, and the user simply pressed and released the alarm button and everything accidentally started. Therefore, using the state machine known on the local forum, I simply turn off the required outputs with an alarm bit and when the danger has passed - everything returns to the state as before the alarm. That is, an unactivated bit is not accidentally activated

I received an interesting task related to the movement of a part using two axes. X and Z axes will work alternately. The only requirement is to use a large Vision V1210 screen (no snap -in present) and two powerful stepper motors with built-in step and direction drivers once purchased by the customer. Should I buy another TR34 or TRA22 PLC in addition to the existing one or order and wait for EXF-RC15? There is also a way to buy a motion control module and send tasks to it from the panel. What do you think is the most simple and effective solution of this task with present customer hardware? p.s. The stepper driver is not hybrid - therefore, it will not work to use the signal for a high-speed counter from its built-in encoder.

RTC is embedded to this PLC. You can find time and date in PLC Info mode. If you have project for V280 - you can add RTC to display. If you do not have a project and it is not burned to PLC (upload project is not possible) - you must program new project for add RTC on screen.

This is the same old school but paperless

Info from Jazz manual

You can try to set Jazz to STOP mode. Info mode must be used (via keyboard).

What you have encountered is a constant problem in PLCs with current input. When connecting the sensor, the user can accidentally short-circuit the 4-20mA line with the +24V power line. It can also be during the operation of the sensor - for example, someone cut the cable. The consequences are like yours. For a load of 37 Ω +24 V creates an overcurrent of 0.6 A. This is a complete annihilation of the analog input. Standard question - what to do? I have two solutions for such cases: 1. An expensive solution is to use an external galvanically decoupled analog signal to analog 4-20mA to 4-20mA or 4-20mA to 0-10V converter. 2. A cheap solution is to buy a high-precision 500Ω resistor and connect it between the 0V ground and the analog input turned on in the 0-10V mode. We read values in the range of 2-10V - which corresponds to the range of 4-20mA for the sensor you need. In the event of a short circuit, you will see smoke from the resistor if its power is less than 2W. Usually, the analog input in the 0-10V mode from +24V does not suffer. I also encountered 220VAC applied to the analog input - the consequences are even more terrible - the PLC usually breaks if the analog inputs are not isolated. And even if they are insulated - there is a lot of smoke!!! Another case is when the wires to the analog inputs pass close to the frequency converter... The problems are also significant - sometimes it ends fatally. P.S. Most recently, I had a case with a new module EX-D16A3-TO16 where user destroyed three current inputs in a row - because I said that in case of problems with one, there are two more spare and I made a software switch for redundancy - it did not help.

Unfortunately, I have not come across such a large number of PLCs that need to be updated. However, the main problem of updating is the control of changes in versions. I am a follower of the old school of programming where most of the work was done on paper. That's why I go straight to improving versions and always write down all the operands used. I introduced a system of their numbering and belonging to PLC functions. Accordingly, the project notebook with operands has sections where I can quickly see what and where I wrote. If the changes to the project are drastic, my update process involves loading a clean project, initializing and resetting. Then upload a new project. At the same time, I save operands after debugging in text format. Maybe it's longer, but I can easily make a comparison using my notes and a text file of operands. P.S. Having a training class with Vision PLCs, I have another problem - each subsequent student downloads his program and receives a gift in the form of operands from the previous user. Then he tries for a long time to understand why the program does not work.

Please read info from this link https://support.unitronics.com/index.php?/selfhelp/view-article/Vision-and-Modbus-communication

Moved... Please post robot model # if it is standard robot. What PLC you want to use?

No, ethernet port can't be used. You must add com module to PLC with RS485 function - UAC-CX-01RS4

This is not related to this topic, but in an empty project for some reason 0 is written in SI285 and I could not understand why this is done. Look at the STL view of the empty ladder program...

If you need advanced network functions for this type of PLC, you should probably pay attention to the new service from Unitronics - Unicloud. https://unitronics.cloud/unicloud_help/UCR_Routers__Creating_and_Connecting_Assets.htm And the new product from Unitronics UCR router https://unitronics.cloud/routers/

After quickly reading the documentation, I can only state the fact that controlling this controller from a PLC is possible. However, due to the proprietary communication protocol with the controller proposed by the manufacturer, writing the control program will take some time. Separately, you will also need to configure the controller itself using a program from the manufacturer. If you are an experienced user of Unistream, you will create a command library and program the controller settings via manufacturer software . If you are not familiar with writing a non-standard communication protocol, it is better for you to change the controller to a Unitronics servo drive and get ready motion functions without creating unnecessary additional protocols.

Please post motor controller model # or pdf. You must check - is it motor controller protocol supported by Unistream PLC.

Links to Unitronics site and forum topics https://www.unitronicsplc.com/videos-and-tutorials-visilogic/

Great job! Thanks for fine comment and links to publications about random number generation.

In Unistream you have two CPU = panel CPU (linux based PC with more the 4GB SD card inside) and PLC CPU with battery powered RTC and 1MB memory for Ladder code. Maybe I'm wrong (let the PLC Creators correct me), but in the project, only part of the code called Ladder is executed in the PLC CPU. The graphic part and all multimedia and network capabilities are placed on the panel CPU. Therefore, in a fairly high probability, it is the percentage of using its capabilities that is the limitation that is important for the end user. For more detailed explanations, contact support@unitronics.com.

Please check jumpers position inside module. If it is correct - please try to disconnect thermocouple from AN3 and connect to AN4 (with correct jumper settings). If no result - configure AN3 as analog Voltage via jumpers and connect to analog input small battery with known voltage - test via Visilogic is it Voltage readings correct (ADC readings must be adequate). If yes - replace K thermocouple to another one. If Voltage test is incorrect - module analog circuit is damaged.

In general, we must understand that any acceleration of the PLC programming process - copying or export import requires concentration and attention. Pre-allocating the variables for the project on paper and replacing the inappropriate variables before copying or exporting-importing simplifies the task, but again, attention, attention and more attention to this process. Everyone who has been programming in Visilogic for some time - creates his own style and acts as he likes. I developed a project template for all the PLCs I used. Accordingly, creating a new project means renaming the template and supplementing the standard functionality with the necessary modules from other projects. The only problem is the different number of variables available in different models and the number of inputs and outputs. However, this was also overcome by choosing the weakest PLC as the basic one in terms of resource allocation.