adccommunitymod (AutomationDirect) asked a question.

Peerlink Troubleshooting

Created Date: March 28,2013

Created By: bcarlton

**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****

Note - also posted at Host forum I have a network of 4 DL06s each with an H0-ECOM100 (firmware V4.0.334) All have Peerlink enabled. All are using address groups starting at V6000 Three have 'Publish ' selected at V6000, V6020 and V6040 respectively (In other words, one at V6000 the next at V6020, the third at V6040) The fourth has 'subscribe ' enable for V6000, V6020 and V6040 I have information (non-zero) in V6000 in the unit which is Publishing at V6000 Nothing (stays at zero) shows up in V6000 in the unit with V6000 enabled as 'subscribe ' I can see and program all of these from my PC. I have confirmed multiple times the Peerlink settings. All are running. Using Wireshark (picture appended) the three units appear to be publishing ok Note - this particular packet is from a unit with zeroes in the data area. I did capture one from the unit with data and it has expected values in the areas that this trace has zeroes. Documentation says that Peerlink uses TCP/IP broadcasts yet Wireshark labels these as UDP. Problem?


  • adccommunitymod (AutomationDirect)

    Created Date: March 28,2013

    Created by: bcarlton

    Sorry - false alarm

    I had two of the 'publishing ' units set to the same block. Changed and is now working.

  • adccommunitymod (AutomationDirect)

    Created Date: March 28,2013

    Created by: franji1

    If you turn status on in run mode, the PEERLINK instruction status should have shown you the issue. DMD0300 Help Topic in Designer shows the various status states. You should have seen the multiple Block ID with a Red Circle with a Slash (see Block 8 in the example below).

    http://hosteng.com/forumimages/peerlinkstatuskey.png

  • adccommunitymod (AutomationDirect)

    Created Date: April 01,2013

    Created by: bcarlton

    Just to tak on to my own question - which I answered - are the Peerlink communications synchronous with the program scan? That is - do they occur during the normal inter-scan communications interval?

  • adccommunitymod (AutomationDirect)

    Created Date: April 01,2013

    Created by: Do-more PE

    Yes. Since it relies on backplane traffic, it has to be serviced during the communications section at the top of scan.

  • adccommunitymod (AutomationDirect)

    Created Date: April 01,2013

    Created by: bcarlton

    Thank you.

    I'm liking the Peerlink function. Once ah PROPERLY set up it's incredibly convenient. Just place information in the area reserved for the Publishing unit and it 'magically ' (ok not really) shows up in the memory area of the Subscribing unit(s). As long as the rate (10 times per second) is taken into account it's very useful. Eliminates a lot of messaging commands.

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: March 28,2013

    Created by: bcarlton

    Note - also posted at Host forum

    I have a network of 4 DL06s each with an H0-ECOM100 (firmware V4.0.334)

    All have Peerlink enabled. All are using address groups starting at V6000

    Three have 'Publish ' selected at V6000, V6020 and V6040 respectively (In other words, one at V6000 the next at V6020, the third at V6040)

    The fourth has 'subscribe ' enable for V6000, V6020 and V6040

    I have information (non-zero) in V6000 in the unit which is Publishing at V6000

    Nothing (stays at zero) shows up in V6000 in the unit with V6000 enabled as 'subscribe '

    I can see and program all of these from my PC. I have confirmed multiple times the Peerlink settings. All are running.

    Using Wireshark (picture appended) the three units appear to be publishing ok

    Note - this particular packet is from a unit with zeroes in the data area. I did capture one from the unit with data and it has expected values in the areas that this trace has zeroes.

    Documentation says that Peerlink uses TCP/IP broadcasts yet Wireshark labels these as UDP. Problem?

    Expand Post