News:

  • July 01, 2026, 06:15:46 AM

Login with username, password and session length

Author Topic: Casting in a relational contact  (Read 28997 times)

ADC Product Engineer

  • Hero Member
  • *****
  • Posts: 270
Re: Casting in a relational contact
« Reply #15 on: April 15, 2015, 05:08:57 PM »
MODBUS TCP with a unique MODBUS TCP Client created for each slave.

Although using DLRX/DLWX is probably going to be nearly as fast.  And since this route is UDP based with this route you do not have to create new devices for each slave.

And BobO answered it better than I did.  :)  No shocker there.
« Last Edit: April 15, 2015, 05:16:30 PM by ADC Product Engineer »

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6164
  • Yes Pinky, Do-more will control the world!
Re: Casting in a relational contact
« Reply #16 on: April 15, 2015, 05:13:38 PM »
Multiple conversations get interlaced and confusion reigns.

There are (for now) two basic ways to move data between these devices: MRX/MWX (Modbus/TCP) and DLRX/DLWX(DL peer to peer).

Since Modbus/TCP is built on TCP...which is connection based...if you aim to talk to more than one thing, you should create a Modbus/TCP Client for every device you want to talk to. It isn't required, but it will greatly enhance the performance.

DL peer to peer, on the other hand, is built on UDP...which is unconnected...and if you want to talk to more than one thing, there is no significant performance penalty to do so using only one connection. Which is a very good thing...because it isn't possible to create additional clients for DLRX/DLWX.

The UDP Connection device that you referenced has nothing to do with DLRX/DLWX. Those devices are for creating custom protocols.

So the simple answer is to use DLRX/DLWX on the one and only built-in client. Unless you just really wanna use Modbus/TCP, then use MRX/MWX, and create a Modbus/TCP Client for each target device that you wish to talk to.
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6164
  • Yes Pinky, Do-more will control the world!
Re: Casting in a relational contact
« Reply #17 on: April 15, 2015, 05:20:38 PM »
MODBUS TCP with a unique MODBUS TCP Client created for each slave.

Although using DLRX/DLWX is probably going to be nearly as fast.  And I am pretty sure with this route you do not have to create new devices for each slave.

Modbus/TCP allows you to overlap comms to multiple devices...which could be faster...but with the additional overhead of processing multiple TCP sockets. DL peer to peer must process each request one at a time...which might be slower...but only requires processing one UDP socket. I could build a pretty good case for either one to win in certain circumstances. The only absolute is that DLRX/DLWX is easier.

I don't actually think there is a right or wrong answer, hence the confusion.
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6164
  • Yes Pinky, Do-more will control the world!
Re: Casting in a relational contact
« Reply #18 on: April 15, 2015, 05:22:12 PM »
And BobO answered it better than I did.  :)  No shocker there.

I cheat...I have the teacher's addition of the textbook. ;)
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

mhw

  • Hero Member
  • *****
  • Posts: 250
Re: Casting in a relational contact
« Reply #19 on: April 16, 2015, 12:27:57 PM »
Thanks for the clarification!