SFC13 Record ANY Pointer as VAR OUT

Hi Gang!

(A rough quote from F1 help for SFC13)
“The data that has been read from SFC13 (“DPNRM_DG”) is entered in the destination area indicated by RECORD following error-free data transfer.”

This data type is ‘ANY’

Is it possible to create that data type in the declaration table as an OUT within the LAD world?

Inside my project (attached)I am calling SFC13 from within FB1000 “DP Slave Diagnostics”. Currently I am using a pointer to a ‘yet to be created’ DB2.

I would like to be able to use this FB1000 and have no ‘hard coding’ within it but only have Variables from the declaration table assigned to/from it.

Any ideas? Do I have to have some STL code to magically convert the ANYto some strange carnation to accessindirect addressing on the OUTto achieve this vision? If so is anyone up for the challenge – since I have only ever programmed in LAD. (LADis a weakness of American programmers I guess – at least this one… )

If any of ya'llare so inclined to retrieve the project feel free to poke around and offer any tips/tricks or suggestions in my approach to working with some of the SFC's– I am very teachable with all this stuff. The project is the early stage so it isn’t too big and I have not created the instance DB’s yet since I am still working on the FB’s.

Thanks for all the continued support!!!

Cheers,
Darren in (Sunny Hot)Dallas

Thanks for the feedback GJohn!

I followed your link and have a follow-up question… We do have SCADA and HMI in the project but there is a whole separate group that is working on that part. It looked like all of the sample programs included OP’s therefore I did not download any of them. Is there a FB125 type function that does not include the OP’s and I can just output bits or DB locations etc or can I download the above projects and just strip out the OP part and still have the diagnostic functionality without OP’s?

Also can you compare the scan-time of running an FB125 type function vs. just the specific SFC’s to provide the data I am looking or? It just seems that there may be a lot of un-necessary overhead to run a ‘super FB’ but I may be wrong in that assessment.

Cheers,

Darren in Dallas

FB125 writes to a DB, so you can just strip out the OP part and still have the diagnostic funcionality. The structure of the DB is mentioned in the Siemens documentation. However it would be advantageous to give the other group working on the SCADA/HMI theOP part as it contains a lot of text lists etc. which saves a lot of work and makes displaying and diagnosing of faults easier.

FB125 is set up so it is only called by interupts OB82 and OB86 and when manually requesting information on slave faults on the OP it is called via OB1. SoI don't think there is any great overhead in scan-time.

Thanks Partner!

You have put my mind at ease with the questions I had. I will take this pony out of the barn and take him for a ride and see how the saddle fits. By the end of the day I hope to have him at a full gallop.

Once I have it working I will share it with the SCADA/HMI folks. Thanks so much for the great info.

Cheers,

Darren in (starting to cool off a bit)Dallas