11/13/2022 0 Comments Delta hmi macro programmingI must migrate the project to the newest version because macros do not work properly or at all in projects created under DOPSoft 2.00.01. Strange thing, they work OK if addressed directly (address without a tag). The problem doesn’t exist on DOPSoft V2.00.01. They’re refused by the multi state indicator in the newest version (“Fail to input address”). They are Allen Bradley SLC 500 word addresses. I have created hundreds of tags for the multi state indicator. Secondly, I have a serious issue with migrating my project from DOPSoft version 2.00.01 to 2.00.04. Unfortunately, I can’t switch the protocol to DF1 as some of the PLC’s are part of the DH485 network. I checked it on several 5/04 and one 5/03 CPU’s. When I switch the PLC controller and HMI to SLC5 (DF1) protocol everything is working perfect so it must be the DH485 driver problem. It reads everything correctly but this stupid error pops up and it slows everything down. This happens when multiple elements are on the screen. The products I performed the test on are B07S415, B07S411, W157B, soft used – DOPSoft 1.01.10 and 2.00.01 and 2.00.04.įirstly, when connected to SLC 500 cpu (5/04) via RS232 DH485 protocol I am getting this error – “Read Error Receive Unknown Code”. To start the Delta HMI Screen Editor setup, please refer to the following. I have couple of issues to report about your Delta DOP-B and DOP-W products. write communication protocol with communication macro command to connect. Be sure then change controller type that into communication parameter software automatic change back to RS232, you have to set to RS485 again otherwise you can fight long time before you find out problem. If you only use DELTA DVP PLC as controller then you only get one way communication. If you use communication port COM 2 from PLC to COM 1 into HMI and protocol RS485 you have to use DELTA DVP Q-Link as controller to have right communication. Go to Communication settings into your DOB software and check out you controller settings, many different controllers can be used Delta and other brand too. This case as I describe may have follow solution. Many thing can go wrong, do systematic troubleshooting and only change one thing at time. If any problem that only one way communication from Delta HMI to Delta PLC, Mean that you can write to address into PLC from HMI and you can monitor into PLC that actually right value are written into PLC, but nothing is revived back to HMI then you may have wrong setup into your communication. Nothing …………………………… not have form enter menu system, also have the botton ,as other models… ************ the hmi new have one program y only have space in the upper corner. Press the prompt window which shows the message of “Enter the system menu?” on the left-upper corner within one second. *********************jajajaja dont know the tcp/ip the hmi dop-w is new you cant dowload way ethernet….?Ģ: Long press the blank space for 3 seconds. And go to HMI system screen by clicking on system directory button. To enter the system screen and download the screen How to enter theġ: Open DOPSoft software and create the button of system directory. In the manual soft page 1922 say …Chapterīefore introducing W series HMI, following sections will briefly introduce how Maybe because the limiting factor is the execution time of the macros and not the communication itself. Ethernet would only solve one part of the problem (that of communication speed), but, surprisingly, I didn’t notice any considerable improvement. In the meantime I made some tests, using Ethernet. So I would need extra cabling and communication extension Lmabay: It can only exchange data between certain registers (up to 100) and, the way I understand it, the read and write area is defferent so I still need a lot of extra programming, if it’s possible at all.īesides that, PLC link uses it’s own network to connect the PLCs together. PLC link is very limited, compared with what I need. This way I will be able to reuse each HMI screen for any PLC that is currently selected. The user changes the selected PLC ID and then HMI starts showing data from the new PLC. What I need is HMI to be able to communicate with one PLC at a time. My data is spread all over the PLCs memory, as it is normal for a big program that uses a lot of data registers for read or write between HMI and PLCs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |