• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 198 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LP-AM261: Profinet - Delayed Application Ready

Jamel Zribi
Prodigy 20 points

Part Number: LP-AM261

Tool/software:

Dear TI Support Team,

I am working with the LP-AM261 and its PROFINET stack as provided in the SDK ind_comms_sdk_am261x_10_02_00_05. I have a question regarding the handling of the "Delayed Application Ready" mechanism in the PROFINET implementation.

Does the PROFINET stack support delaying the Application Ready signal from the device to the IO-Controller?

My use case involves receiving configuration data via Write Record, then processing the Parameter End indication. After that, the application performs internal setup, such as configuring the underlying network interfaces or devices.

  • If an error occurs during this setup phase, is there a way for the application to indicate an error back to the IO-Controller, before signaling Application Ready? (e.g set the erroneous submodules to "ApplicationReady pending" )

  • Additionally, is it possible for the application to explicitly send the Application Ready signal once the internal setup completes successfully?

I would appreciate any clarification on whether this flow is supported by the stack?

Best Regards
J.Zribi

  • +1
    TI__Intellectual 2540 points

    Hello J.Zribi,


    Thanks for your inquiry.

    Yes, our PROFINET solution allows this scenario as follows:

    In the implementation of PN_API_IOD_paramEndCbf (PN_APP_IOD_cbParamEnd in our demo app) you can return the value PN_API_IOD_SubmodStatusAppReadyFollows instead of PN_API_IOD_SubmodStatusRun. This informs PROFINET stack that the application is not yet ready and that it will send "application ready" later. Meanwhile, IOPS/IOCS of the exchanged data is set to BAD.

    Once the parametrization for your submodules is done on the application side, you can call PN_API_IOD_asyncApplReady with the new value of submodule status (e.g. PN_API_IOD_SubmodStatusRun) and the value of MoreFollows parameter set to false. This will trigger the stack to send the "application ready" and set the data status to GOOD.

    You can find the mentioned information in the documentation of PN_API_IOD_paramEndCbf() and PN_API_IOD_asyncApplReady() functions.

    Kind regards,
    Kamil