IvanBratanov

Perhaps there is some kind of a protection. For example in OP320 series HMI panel there’s no option for uploading the project at first. The manufacturer intentionally did not provide such an option as precautions method. You may reach out Eaton and ask them for details…

Its a hard challenge you've taken. Its a very old PLC series and so is the software (Sucosoft S30-S4). As long as I know it is even DOS-based and not to be found, even at the manufacturer. I've had such task years ago but never made it to the end.

My searching gave me an answer which I posted here days ago but it never appeared. So I'm posting it again. It seems that a positioning module could be regarded as an indexer. Here's what does this article say about that: Its about stepper motors but it applies here as well. In my case the indexer is a type of MPU that is capable of driving a single servo axis by receiving commands from the PLC and transforming them into pulse train signals (both step and direction pulse commands). So this explanation fits my question from the first topic perfectly. A positioning module could be rearded as an indexer.

Thank you for the answers! I’d rather ask if a servo positioning module could be ragarded as indexer? For example I have a Delta DVP01PU-S positioning module. It is designed to be attached to a Delta Slim series PLC and get commands by PLC’s internal communication bus. Then it converts received instructions into pulse train signals thru its outputs to the next standing servo driver. With other words it is designed to make every Delta Slim series PLC capable of driving a single servo axis (mostly if the PLC cannot do that by its own or its output channels are insufficient). If there are few servo axes to be driven, the coresponding number of modules could be attached to the PLC. So I only need to know could this module be regarded as an indexer?

Hello! I’m in constant search for several days for something that is called indexer in the area of servo control. From this site: https://www.valin.com/resources/articles/pulse-control-basics-for-motion-control You can see that indexer here means a device that accepts communications commands from another device (i.g. PLC) and converts them into pulse trains to the servo driver. According to other sites however indexer is a rotating table (or something like that). Googling “servo indexer” returns that only. It has nothing to do with electronics. So what should it be? Could a positioning module, receiving commands from a PLC and converting them in pulse trains to the servo driver be regarded as indexer? Thank you!

You should use for compiling the same software you used for creating the project. DOP-B series is supported by Screen Editor and DOPsoft V2.00. DOP-100 series is supported by DOPsoft V4.00 and DIAscreen. When a project file is created by using DIAscreen it should be compiled by using the same product. When there are compilation issues it could be because of program errors. Compiler shows the errors due to which compilation can't succeed.

Perhaps you've made an Ethernet Client-Host connection between both HMI's and RS-485 connection between the Host HMI and the PLC. You may take a look of the document attached to my post. It explains how to set both HMI's and the serial connection to the PLC. HMI+HMI+PLC.ppt

You have to choose a brand to work with. I’ve made my choice based on a qualty and price of the brand’s automation. Others decide to point at most top brands regardless of the price. The most difficult part is to become a specialist in this area enough qualified to build schematics and control programs. Most of us are engineers in different areas. In order to start exploring this area you must know that some basic knowledges are mandatory and without them further improvement is impossible. For example there’s no way to be a historian or a doctor and suddenly start learning industrial automation. You should have at least some degree in electronics, physics or some electric speciality.

Which type of positioning do you use? There are two types: PR mode and external pulse train. P.S If you’re using absolute positioning its not possible to perform positioning to the same location again. That’s the point of the absolute positioning. Each position of the axis in absolute values has its own “address”. For example if you positioned the servo to location 100 000 there’s no way to do the same again being at the same location - you are already there. You can only make another absolute positioning upwards and backwards. For example when the servo is at absolute postion 100 000 and you command absolute position 70 000, servo will go 30 000 units back. There’s an option to do sequently 100 000 positioning commands but in incremental mode command. In this case servo will perform positionings by 100 000 units each time.

As I mentioned above DVPDNET-SL module can not work remotely or separately, i.e. it must be coupled with a DVP-S series PLC. I deeply doubt that KUKAs are controlled by such PLCs so you have to couple the DVPDNET-SL to a DVP-SA2 PLC for example first. Then you have to configure both devices to work together. Then you have to connect the KUKA’s automation to the SA2 PLC in order to send and receive data to/from the DEVICENET network. The SA2 has built-in one RS-232 and two RS-485 ports supporting MODBUS ASCII and RTU protocols. If the robot’s automation doesn’t support such interfaces you have to add a coresponding left-side module to the SA-2 PLC. In this case the PLC should interact as s gateway between both interfaces. For example if the robot supports PROFIBUS, you should attach and configure a DVPPF02-SL left-side module to the SA2 PLC. I don’t believe that using third-party automation together with such devices as KUKAs is a good idea because of the complications and difficulties you have to go thru first.

This module is intended to be used as a DeviceNet slave gate to DVP-Slim series DI/DO or special (AI/AO, temperature, loadcell) right-side extension modules. It could be coupled with DVPDNET-SL DeviceNet module. DVPDNET-SL is a left-side module for DVP-Slim series PLCs. Unlike RTU_DNET it could be used as both master and slave. This way users could built a high speed network. Configuration software used is called DeviceNet Builder and could be downloaded freely from Delta's Download center. RS-485 configuration is set by the path Setup-> Communication setting-> System communication port and then <serial port setup> window from the configuration software menu. Both modules could be setup using the same software. The RTU-DNET application manual posted above should be used. DVPDNET-SL operation manual is located here: https://filecenter.deltaww.com/Products/download/06/060305/Manual/DELTA_IA-PLC_DVPDNET-SL_OM_EN_20230906.pdf

You need to establish a working serial connection between the HMI and the VFD regardless of the equipment’s brand. That means correct interface and protocol settings. HMI and VFD communication ports should have same settings (but different addresses) in order to communicate each other. Each VFD capable of RS-485 control has a set of control registers. By writing pre-determined values to those registers, VFD starts, accelerates, decelerates, stops and other functions. All control registers, their addresses and possible values are described in the manufacturers’ manuals. You should create screen objects that write and read those values to/from the control registers of the VFD. Some registers are writable and readable (for RUN and STOP commands for example) while others are read-only (for status and alarms for example). Steps are identical regardless of the brands. I don’t work with Weintek but it is all the same.

As long as I know any actions related to passwords breakdowns are not allowed here at the forum. If there is a password on the PLC that means there is a copyright on the program inside. That is the main purpose of the password. I suppose the site admin could take a stand on the matter, but I think it is forbidden. Anyway the problem that started your topic was solved.

You’re welcome! Working equipment (the correct software and adapter and the proper PLC) should establish the connection at once. PC to PLC RS-232 or RS-485 connection is the most easiest thing when the proper equipment is held.

I don’t work with LS but I could suggest you to work only with the brand’s original equipment. I have had the same problems with my brand and solved them by using an original adapter. As far as I can see, the converter from the link is universal and there is no guarantee that it can work with your controller. It could be possible that pin arrangement of the USB to RS-232 converter is different than the PLC’s port. If there is not an autodetect function of the software you may not coonect as well. There may be other reasons related to a wrong converter.