4/15/2010 4:44 PM | |
Posts: 95 Rating: (0) |
I am reviving this thread as I am trying to find more information about a paticular topic. I am interested in understanding the acyclic Profibus DP communications between a S7300 and MM440 drive. I have demo equipment and I want to enable acyclic reads from the drive. I have deduced that using SFB 52/53 will work and the sample offered from Siemens is ok, but what if you want to do a different amount of data? Like the OP, I want to know more about the data record (47). I have done acyclic data exchange with the simocode and the manual describes all the data record types. In my experiment, when I change the number of paramaters to read, I have no luck with SFB52/53. I have looked into the MM440 manual, parameter list, and profibus adapter manual and cannot find much detail regarding acyclic data exchage. thanks John Splitted from Comms with drives. |
Last edited by: O_Moderator at: 4/16/2010 8:16 AMnew subject after splitting |
|
4/16/2010 8:39 AM | |
Posts: 739 Rating: (55)
|
Helo, here are a cluster of: FAQ: http://support.automation.siemens.com/WW/view/en/26436769 and a Apps-note: http://support.automation.siemens.com/WW/view/de/29157692 |
4/16/2010 4:45 PM | |
Posts: 739 Rating: (55)
|
As first: sorry I send the worg Links. Apps = http://support.automation.siemens.com/WW/view/en/22078757 FAQ = http://support.automation.siemens.com/WW/view/en/26424185 (but any way, the G120 Faq should work either) second: all this FAQ are examples only to help the user, programming the PLC. It is not possible to take it one by one for a application. third: did you install GSD-file? here you have to parametice the FB/FC by your self ore do you using DriveEs (liable to pay costs)? here you can use allready set up FB/FC |
4/19/2010 1:03 PM | |
Joined: 8/25/2005 Last visit: 10/5/2024 Posts: 1162 Rating: (111) |
Hello picengineer123, which error messages do you get? Best regards Sabine |
4/20/2010 9:53 PM | |
Posts: 95 Rating: (0) |
thanks for the input attached is a print screen showing the logic online and the error thanks John |
4/21/2010 2:46 AM | |
Joined: 10/7/2005 Last visit: 10/19/2024 Posts: 3024 Rating: (1054) |
Hello picengineer123 I had the same"80B5" error problem some years ago while testing DS47 relatedread/write request with a Sinamics drive. Good news first: The problem is not your program but instead a bug in SFB52/53 (which also affects SFC58/59). Bad news: You will have to live it with (unless the Siemens S7 firmware development team reads this and finally decides to revise SFB52/53 and SFC 58/59). I ended up ignoring the Status output all together (as I can't trust it) and insteadimplemented atime out mechanimsbased onchanging the reference numberof the request (Byte 0 in the DS47 request header) for every new request and comparing it with the echoed back reference number(Byte 0 in the DS47 response header). I also had lenghty andexhausting E-Mail exchanges with Siemens Service & Support concerning this matter and the gist of the problem is this: The problem on the PLC side is: 1.) SFB52/SFC58 aborts a read record attempt with error code 80B5 on its STATUS output as well as setting the its ERROR bit in cases where the (DPV1) message from the Slave merely means that it is still busy processing the parameter request. 2.) SFB52/SFC58 do also NOT write 81hex into Byte 1 (Response ID) of the response DB which it should do as per Sinamics manual. 3.) The online help for SFC59 list all “80Bx” as permanent errors, 80B5 is however NOT a permanent error. 80B5 is actually not a true error at all, but rather a temporary status. 4.) The available help for SFB52/53 & SFC58/59 is lacking in detail and partially incorrect (see item 3 above) as well as contradicting parts of the available Sinamics help (see item 2 above). The problem on the Sinamics side is: 1.) It usually handles the DPV1 parameter requests without any problems and issues the requested parameter response in due time. 2.) Every so often the drive does however “decides” to be a bit slow as a parameter server and it takes anywhere between 0.5 and 1.5 sec to eventually issue the parameter response. It does in this case correctly issue the DPV1 read_res(-) though, butSFB52/SFC59 dothen incorrectlycreate the 80B5 error. Attached is a pdfwith Profitrace captures with additionalinformation for your perusal. I hoped back then it would be proof enough to get the S7 firmware development team to change SFB52/53 and SFC 58/59 as well as update the help files, but thus far I am still waiting for itto happen (I guess even Siemens is not perfect). Last but not least, updating the firmware of the Sinamics to the latest version that was available back then did help in avoiding that the Drive sometimes needed longerto response. This doesof course not solve the underlying problem with the SFB52/53 and SFC 58/59. I hope this at least helps in taking your worry away that you or your logic isdoing something wrong. AttachmentSinamics SFB52-53 DS47 request recording analysis.pdf (633 Downloads) |
Cheers |
|
This contribution was helpful to2 thankful Users |
Follow us on