Audience
Protocol

Subscriber

End users and everybody interested in reliable solutions for device integration including device manufacturer and system vendor staff.

Publisher

Device manufacturer searching for cost efficient deivce integration or for support in the development of tailored solutions.

Interoperability Partner

System or tool vendors with the wish to offer a generic integration solution as part of their existing solutions.

Protocol

Protocol

Communication protocols mainly used in the process industry. Please choose from the list below. You may combine aspects from different tabs of the solution finder in order to find the best match!

FOUNDATION Fieldbus

HART

Modbus

PROFIBUS

PROFINET

WirelessHART

Home Forums Technical Support HART CommDTM (FDT1.2) communication be blocked issue when connected 2 HART CommDTM (1.0.58 )

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #5700
    aoming yang
    Participant

    Hi Expert,

    Could you please follow my test step to re-procedure below failure case and give me a feedback?
    To confirm:
    1.If HART COMMDTM issue?
    2.if 1 is Yes.Please give me a solution or workaround.

    Test Enveriment:
    a.Pactware
    b.Hart Modem COM4
    c.Hart Modem COM8
    d.HART CommDTM (FDT1.2) 1.0.58

    —————————————————————————————————-
    Failure case procedure:
    1.Add 2 HART CommDTM and config COM4 and COM8 and both connect succeeful.
    2.Add device dtm under COM4 and connect succeeful.
    3.Diconnect COM4(disconnect HART CommDTM).both com4 and device dtm diconnect succeeful.
    4.re-connect COM4.COM4 connect succeeful but device dtm communication is blocked.

    —————————————————————————————————-
    Success case 1:
    Same step 1,2,3.
    4.Diconnect COM8
    5.re-connect COM4.both com4 and device dtm connect succeeful.

    Success case 2:
    Same step 1,2
    3.Diconnect device dtm succeeful.
    4.re-connect device dtm succeeful。

    Thanks.

    #5731
    Quality Assurance
    Participant

    Dear Aoming Yang,

    thank you for your precised description of this HART CommDTM issue.
    Your described behaviour suggests that the fault can be found in the driver layer. We added your issue to our backlog.
    If you are interested in further deeper analysis and fix, please contact us via “sales@codewrights.de”.

    Best regards,
    Annelie Lamprecht

Viewing 2 posts - 1 through 2 (of 2 total)
  • The forum ‘HART CommDTM (FDT1.2)’ is closed to new topics and replies.