• State Resolved
  • Locked Locked
  • Replies 16 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 419 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.

TMDS243EVM: Profinet pre-certification test

Vaclav Vadinsky
Prodigy 40 points
Part Number: TMDS243EVM


Tool/software:

Hello,

I have trouble with the pre-certification test:

Test Execution Log

1 09:58:51: DCP_1: Start of test DCP - DCP 1 without VLAN-Tag
2 09:58:51: DCP_1: Test step 1: Requesting ResetToFactory (reset communication
parameters) of the dut
3 09:58:51: DCP_1: Test step 2: Waiting for the DUT to apply the reset to factory
request. [ms]: 60000
4 09:59:51: DCP_1: Test step 3: Check the IdentifyAll response behavior.
5 09:59:51: DCP_1: Test step 4: The requested IdentifyAll failed.
6 09:59:51: Received an unexpected response block in a DCPIdentify.Res from type:
OemDeviceId.
7 09:59:51: DCP_1: Test step 4: DCP - DCP 1: Aborted due to errors.

Could the problem be in the OemDeviceId item?

I analyzed the communications in Wireshark, and the VendorID and OemVendorID are different. I am using my own VendorID, but the OemVendorID is 0x1c4.

Where can I change the OemDeviceId?

Thank you in advance for your response.

Best regards, Vaclav V.

  • 0
    TI__Intellectual 1470 points

    Hello Vaclav,

    based on your description I'm assuming you have defined your own VendorID in the GSDML file but not in the application. Would you please try to set

    PN_API_IOD_VENDOR_ID macro to the same value defined in your GSDML file?

    Thanks.
    Kind regards,
    Kamil
  • 0 in reply to Kamil Alkhouri
    Prodigy 40 points

    Hello, thank you for your reply.

    PN_API_IOD_VENDOR_ID and PN_API_IOD_DEVICE_ID are set correctly. I verified this in Proneta and Wireshark. The FW works correctly with the Siemens S1500 PLC. However, we are failing the DCP test.

    Best regards,
    Vaclav

  • 0 in reply to Vaclav Vadinsky
    TI__Intellectual 1470 points

    Hello Vaclav,

    would you please share your GSDML file? I wanna try to reproduce the failure on my side.
    Besides, what version of ind_comms_sdk are you using?

    Thanks.
    Kind regards,
    Kamil

  • 0 in reply to Kamil Alkhouri
    Prodigy 40 points

    Hello Kamil,

    We are using ind_comms_sdk v9.2.0.15. I need to check with the customer to see if I can share the GSDML. The error is probably not in the FW, but in the GSDML. When I tried to slightly modify the example GSDML (VendorID, DevideID, VendorName...), the DCP test passed.

    Best regards,
    Vaclav.

  • 0 in reply to Kamil Alkhouri
    Prodigy 40 points

    Hello Kamil,

    Would it be possible to provide the GSDML file outside of the forum? For example, by email.

    Thanks.

    Best regards,

    Vaclav.

  • 0 in reply to Vaclav Vadinsky
    TI__Intellectual 1470 points

    Hello Vaclav,

    yes you can send the GSDML file to my email address: k-alkhouri@ti.com

    I also kindly advice you to use the latest ind_comms_sdk release available on TI website (https://www.ti.com/tool/IND-COMMS-SDK)

    Thanks.
    Kind regards,
    Kamil

  • 0 in reply to Kamil Alkhouri
    Prodigy 40 points

    Hello Kamil,

    I apologize for the late reply, I was on vacation.

    I solved the DCP tests by adding IM5_Supported="true" to the GSDML file. Even though I had #define PN_API_IOD_INCLUDE_IM5  0 in pn_app_iod_cfg.h.

    I still have a few bugs to fix in other parts of the test. I may contact you again for advice.

    Best regards,
    Vaclav.

  • 0 in reply to Vaclav Vadinsky
    TI__Intellectual 1470 points

    Hello Vaclav,

    Thanks for your response. 

    For the time being, some of the config options in pn_app_iod_cfg.h are statically configured within the library. This means, your modification did not take effect in this case. We're working on resolving this limitation for most of the available parameters.

    You're welcome to open a new ticket when needed.

    Kind regards,
    Kamil

  • 0 in reply to Kamil Alkhouri
    Prodigy 40 points

    Hello Kamil,


    Thank you for your reply.


    I have updated the project to the latest version of IND_SDK 11.
    I only have one error left that I cannot resolve.

    Test Execution Log

    1 13:49:03: Precondition Precondition: Preparing the DUT for test run
    2 13:49:04: Preparing the DUT for test run Precondition: Preparing the DUT for
    test run
    3 13:49:04: Preparing the DUT for test run Test step 1: Switching on device A and
    waiting fot it to boot.
    4 13:50:04: Preparing the DUT for test run Test step 2: End of scenario
    Precondition: Preparing the DUT for test run.
    5 13:50:06: Preparing the DUT for test run Step 1: Reading of interface specific
    records.
    6 13:50:06: Reading of interface specific records. Step 1: Reading of interface
    specific records.
    7 13:50:06: Reading of interface specific records. Test step 1: Reading records
    fom Slot/Subslot: 0x0000 / 0x8000.
    8 13:50:06: Reading of interface specific records. Test step 2: RecordDataRead:
    PdInterfaceMrpDataReal block
    9 13:50:06: Reading of 'PdInterfaceMrpDataReal' block failed. MrpDomainName
    10 13:50:06: Requirement: mrpdomain-0
    11 13:50:06: Data: default-mrpdomain
    12 13:50:06: Reading of interface specific records. Test step 3: RecordDataRead:
    PdInterfaceMrpDataCheck block
    13 13:50:06: Reading of interface specific records. Test step 4: RecordDataRead:
    PdInterfaceMrpDataAdjust block
    14 13:50:07: Reading of interface specific records. Test step 5: End of test MRP
    Interop - Client (CLRPC). An error occurred during test execution.

    Can you please advise me?

    Best regards,

    Vaclav.

  • 0 in reply to Vaclav Vadinsky
    Prodigy 40 points

    Please, any advice?

  • 0 in reply to Vaclav Vadinsky
    TI__Prodigy 210 points

    Hi Vaclav, 

    sorry for the delay. 

    The issue looks like a issue in the test setup. We saw similar one if the setup was not correct. 

    Please make sure you are using the correct topology (MRP, not ETS Topology). For details reference PN Test specificiation. 

    Also make sure that you have configured the correct mrpdomain settings in your PLC program. The name which is leading to the error is configured from PLC. 

    Make here also sure that you have loaded the correct PLC program. 

    Regards

    Christof

  • 0 in reply to Christof Vogt
    Prodigy 40 points

    Hello Christof,
    thank you for your reply.


    I am performing the tests in Automated RT Tester v2.45. There is only one test option that is suitable for us (ETS Device Test Project). There are not many settings options here. Basically, you select the network card and load the GSDML file.


    When I tried the tests on TMDS243EVM and Profinet demo, all tests passed. But on my HW, I have a problem with the only test mentioned above.
    Can you please guide me as to which parameters in the GSDML file or in the FW (just in the demo project) affect this test?

    Best regards
    Vaclav

  • 0 in reply to Vaclav Vadinsky
    TI__Prodigy 210 points

    Hello Vaclav, 

    can you also share some wireshark records from the test system?

    Normally there are no GSDML or config parameter which should result in such a test result. The MRP domain which is wrong here is a setting which comes from the PLC and is only defined by PLC. I assume on your side also Siemens TIA Portal. How is the mrp domain there configured?

    Regards

    Christof

  • 0 in reply to Christof Vogt
    Prodigy 100 points

    Hello Christof,

    We are using https://www.ti.com/tool/TMDX654IDKEVM for testing with Automated RT tester https://www.profibus.com/download/profinet-test-bundle. Which sould be same test used for stack certification testing. We didn’t find any way to configure those parameters. As for logs, we will prepare them and send them soon.

    Best regards,

    Jan

  • +1 in reply to Jan Štepka
    TI__Prodigy 210 points

    Hi Jan, 

    it is fine to use the board, but this is not the full setup. See here the topology of the setup. You also need PLC with correct config:

    For more details see the Testspec which is part of the test bundle which you have referred. 

    Regards

    Christof

  • 0 in reply to Christof Vogt
    Prodigy 40 points

    Hello Christof.

    You are right, I have reviewed the documentation and our current test setup is not complete.

    Thank you for your reply. Best regards,

    Vaclav