Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Prodave 6.0MPI/IE db_write_ex6 very slow via mpi and don'w work via ethernet

Created by: Markku at: 3/28/2006 1:39 PM (7 Replies)

Rating (5)

Thanks 0

8 Entries

3/28/2006 1:39 PM	Rate (0)
Markku Posts: 7 Rating: (2)	Hi, I've been trying to use Prodave 6MPI/Ie software but I've noticed that some fuctions are very very slow via mpi bus and some don't work at all via ethernet bus. I've used previos version 5.6 vith several project and I had no problems earlier. When I use db_write (ver 5.6) and db_write_ex6 (ver 6.0) it take at least 100 times more time to write values to PLC (S7-300) with version 6.0 than previous 5.6 version. I wonder what causes that. I have also tried via ethernet and db_write_ex6 allways fails with error 0x410e. Same result when using db_read_ex6. But when I use field_write_ex6 and field_read_ex6, they work fine via mpi and via ethernet. Does anyone else have this kind of problems ?[:o] Attachment _prodave1.pdf (1106 Downloads)
Markku Posts: 7 Rating: (2)
Suggestion To thank Quote Answer

3/29/2006 10:51 AM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Hi Markku, actually I just wonder myself what the ERROR.DAT says about the error message 0x410e says or if this is a MS Windows error message. Nevertheless I would like to know what the parameters for the function LoadConnection_ex6 are in your program. I guess with thoseinformation's more could be said. Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

3/29/2006 11:19 AM	Rate (0)
Markku Posts: 7 Rating: (2)	Hi J_Bell, Error message form ERROR.DAT is 0x410E:Online: Connection aborted. I think that easiest to show how I use LoadConnection with testprogram which comes with prodave installation. This program C-languge program can be found from prodave exaple folder. I've also made test programs with DELPHI, but they work exactly same way. See below Regads Markku LOADING CONNECTION < l 0 IP 10.20.54.3 5 LoadConnection(S7ONLINE) success: ConNr=0 ... run time: 15.322 sec, command time: 0.391 sec < info as_info(0) success. MLFB: 6ES7 314-6CF02-0AB0 HW: V 2 0 11 FW: 0 1 ... run time: 17.495 sec, command time: 0.100 sec FIELD_READ_EX6 AND fIELD_WRITE_EX6 ALLWAYS WORKS FINE < fread d 10 10 10 field_read(0) success. 0x0000 01 01 01 01 01 01 01 01 01 01 .......... ... run time: 32.867 sec, command time: 0.030 sec < fwrite d 10 10 10 field_write(0) success. 0x0000 01 01 01 01 01 01 01 01 01 01 .......... ... run time: 43.612 sec, command time: 0.030 sec < info as_info(0) success. MLFB: 6ES7 314-6CF02-0AB0 HW: V 2 0 11 FW: 0 1 ... run time: 52.946 sec, command time: 0.101 sec BUT WHENEVER I TRY DB_READ_EX6 OR DB_WRITE_EX6 IT ALLWAYS FAILS WITH SAME ERROR MESSAGE < read 10 4 10 10 db_read(0) failed: RetVal=0x410e ... run time: 67.136 sec, command time: 0.000 sec IF I USE MPI CONNECTION, ALSO DB_READ_EX6 AND DB_WRITE_EX6 WORKS BUT EXTREMELY SLOW, SEE BELOW < l 0 2 2 0 LoadConnection(S7ONLINE) success: ConNr=0 ... run time: 160.530 sec, command time: 0.831 sec < info as_info(0) success. MLFB: 6ES7 314-6CF02-0AB0 HW: V 2 0 11 FW: 0 1 ... run time: 165.978 sec, command time: 0.160 sec < dir db_buch(0) success. 0x0000 0a 00 0b 00 0c 00 0d 00 0e 00 0f 00 14 00 1e 00 ................ 0x0010 46 00 50 00 51 00 52 00 F.P.Q.R. ... run time: 171.226 sec, command time: 0.391 sec < fread d 10 10 10 field_read(0) success. 0x0000 01 01 01 01 01 01 01 01 01 01 .......... ... run time: 181.350 sec, command time: 0.060 sec < read 10 2 10 10 db_read(0) success. 0x0000 01 01 01 01 01 01 01 01 01 01 .......... ... run time: 194.609 sec, command time: 1.422 sec
Markku Posts: 7 Rating: (2)
Suggestion To thank Quote Answer

3/29/2006 1:31 PM	Rate (2)
J_Bell Posts: 5822 Rating: (412)	Hi Markku, so, sadly you did not provide us with the detailed Call information but I try, even so I do not know much about the PRODAVE Trace to see what we have. If we check the Initiate string we see two thing which I try to interpret: LOADING CONNECTION < l 0 IP 10.20.54.3 5 So, here we have Connection # 1, with default access point S7ONLINE, IP Addressee 10.20.54.3.5, SLOT 5 LOADING CONNECTION < l 0 2 2 0 Here we have Connection # 1, with default access point S7ONLINE, MPI Address 2 , SLOT 2 Right? So, we know that the CPU is, if you have a S7-300, in Slot 2. If you address the Slot 5, where maybe the CP is placed, you try to write or read from the CP instead of the CPU. The MPI Address compared with that is always unique and therefore the direct access. If I am right you should change the Slot from 5 to 2 and it should work. But this is only expectation. If you have a S7-400 this might be different und you may have the CPU in Slot 5, than I am wrong. Yours J_Bell.
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

3/30/2006 7:27 AM	Rate (1)
Markku Posts: 7 Rating: (2)	Hello J_Bell, I'm sorry that I didn't provide detailed information, but even so You was able to solve the problem. I have S7-3314C in slot 2 and CP3431-IT in slot 5. I though that I must connect to that CP card (slot 5) but You were right. When I changed LoadConnetion to Slot 2, also db_read and db_write function works. I'm really grateful for Your help, but there is still the problem with the transmission speed. db_read and db_write function works very slowly via ethernet and also via mpi connection. When I read 10 bytes from PLC with field_read function, it takes about 0,03 sec, but when I read same 10 bytes with db_read fuction it takes 0.85 sec. Situation is even wurst then writing data to PLC. When I write with 10 bytes with field_write function, it take about 0,03 sec, but when I write same 10 bytes with db_write function, it takes 1,85 seconds. I think that too much to accepted in any application. Do You have any idea what can cause that, could it be a bug in Prodave with those fuctions. I think that it may be easier to change my applications to use field_read and field_write instead of db_read an db_write. Siemens support has also tested those functions and they are saying that there is no speed problem, so ? Here is also a testing report where the slowness of db_read and db_write can be seen. Thank's again Regards Markku ======= Prodave-IF Test Application ======= Runnig TestSequence 1 times as: "" ==> BEGINN Prodave6.dll: V06.00.00.00_01.08.00.01 release S7OTBXDX.DLL: V06.03.00.00_01.08.00.01 release S7ONLINX.DLL: V06.03.00.00_01.08.00.01 release > l 0 IP 10.20.54.3 2 LoadConnection(S7ONLINE) success: ConNr=0 ... run time: 8.593 sec, command time: 0.547 sec > fread d 10 10 10 field_read(0) success. 0x0000 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 .......... ... run time: 15.968 sec, command time: 0.031 sec > read 10 2 10 10 db_read(0) success. 0x0000 f1 f1 f1 f1 f1 f1 f1 f1 f1 f1 .......... ... run time: 24.078 sec, command time: 0.844 sec > fwrite d 10 10 10 field_write(0) success. 0x0000 01 01 01 01 01 01 01 01 01 01 .......... ... run time: 37.593 sec, command time: 0.031 sec > write 10 2 10 10 db_write(0) success. 0x0000 29 29 29 29 29 29 29 29 29 29 )))))))))) ... run time: 51.156 sec, command time: 1.844 sec > > l 0 2 2 0 LoadConnection(S7ONLINE) success: ConNr=0 ... run time: 49.437 sec, command time: 1.016 sec > fread d 10 10 10 field_read(0) success. 0x0000 29 29 29 29 29 29 29 29 29 29 )))))))))) ... run time: 63.312 sec, command time: 0.016 sec > read 10 2 10 10 db_read(0) success. 0x0000 29 29 29 29 29 29 29 29 29 29 )))))))))) ... run time: 82.593 sec, command time: 0.812 sec > fwrite d 10 10 10 field_write(0) success. 0x0000 01 01 01 01 01 01 01 01 01 01 .......... ... run time: 89.671 sec, command time: 0.031 sec > write 10 2 10 10 db_write(0) success. 0x0000 29 29 29 29 29 29 29 29 29 29 )))))))))) ... run time: 101.968 sec, command time: 1.750 sec >
Markku Posts: 7 Rating: (2)
Suggestion To thank Quote Answer

3/30/2006 11:18 AM	Rate (1)
Ramsing Posts: 19 Rating: (1)	Looks like my problem as well, for which I have found an explanation. db_write behaves differently in 6.0 than the older 5.2 and 5.6 without any mention thereof in the documentation in the manuals. Let me quote Siemens technical support: "With the function "db_write_ex6" for writing of data the following is done. The block is read complete in, then the new data are written to the block, then the block is complete written to the load memory of the AS. When the memory is very full , then no more enough associated memory is available, then the DB could not written. With "Compress" command of Step7 it is possible to compress the memory , but this compress could not used and is also not allowed to use with Prodave. A solution is : Instead of function "db_write_ex6" use the function "field_write_ex6" . Here not the complete DB is written, only the changed part of the data ( simular function like Step7 variable table)" I was quite surprised to find out about this change. I also have some problems still with latency, but am investigating the issue as we speak ( or write ) I have rewritten my io app ( C# dll. ) to use field write instead. My original problem was that the memory in the PLC was full after some write operations and a memory compacting was necessary. Regards Jes Ramsing
Ramsing Posts: 19 Rating: (1)
Suggestion To thank Quote Answer

3/30/2006 11:42 AM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Hello Markku, as said, I am not the specialist in PRODAVE, but I think seen form a certain point of view I would try to see where the problems may be in. There are 4 possibilities to check in: 1. PC Program 2. PC Driver 3. Communication 4. PLC Program Well, I would, because it is the easiest way, trying to verify the Traffic on the Ethernet. There we could check if the Cause of the Situation is the PC or the PLC. This could be done by tracing the Ethernet Traffic e.g. with Ethereal. If the Cause of the Problem is more on PLC side you could see the "Request" Telegram from PC side and the "Response" Telegram from PLC side with the Time difference you saw in the Trace file. This would show that the Problem is on the PLC. If you the Time gap is short than the Problem is more on PC side. But this is only an idea. I am not sure if this will help you, but this would be my point to start with. Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

3/30/2006 12:20 PM	Rate (1)
Markku Posts: 7 Rating: (2)	Hi Mr. Ramsing, Thank's for your advise. You were exactly right. db_write seems to read hole db and after changes it writes hole db back. I tested with smaller dbs and everthing work much much quicker. I'm supprised that Siemens supports hasn't told me this even if I have be asking constantly about responce time of these functions. I'll do the same as you and rewrite my application to use field_read and field_write fuctions. Thank's for your help Mr. Ramising and thank's also for J_Bell. Regards, Markku
Markku Posts: 7 Rating: (2)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on