News:

  • May 05, 2026, 07:31:13 PM

Login with username, password and session length

« previous next »
Pages: [1] 2

Author Topic: Do More as a Direct Logic client  (Read 19043 times)

Henryp

  • Hero Member
  • *****
  • Posts: 161
Do More as a Direct Logic client
« on: October 02, 2015, 05:40:06 PM »
I'm using a Do More as a data concentrator PLC with the DL PLCs in my distribution system.  The Do More data concentrator is able to use DL RX and WX commands for communications. Now I have my first distribution system client Do More PLC  and the data concentrator can't communicate to it using DL RX and WX commands but works ok with Modbus RX and WX commands. Does this mean that I have something setup wrong or that a Do More can't work as a DL client?
« Last Edit: October 06, 2015, 01:29:57 PM by Henryp »
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6154
  • Yes Pinky, Do-more will control the world!
Re: Do More as a Direct Logix client
« Reply #1 on: October 02, 2015, 07:19:13 PM »
Do-more does fully support both sides of DL RX/WX requests.
Logged
"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

Henryp

  • Hero Member
  • *****
  • Posts: 161
Re: Do More as a Direct Logic client
« Reply #2 on: October 06, 2015, 01:29:22 PM »
I have a field site that I want to upgrade to a Do More.  At the site I have a 250 and a Do More side by side. They have the same gateway address x.x.x254 and IP address  x.x.x.38 for the 250 and x.x.x.138 for the Do More. I can do a DLWX to the 250 but get this error from the Do More.

The target device NAKed a DLRX or DLWX request in DLWX @00000150 (DLWX at $Main@202)
Logged

Henryp

  • Hero Member
  • *****
  • Posts: 161
Re: Do More as a Direct Logic client
« Reply #3 on: October 06, 2015, 02:08:18 PM »
We tried adjusting the DM Internal Ethernet Settings and we get the same error. We also tried an Ecom 100 in the Do More base with the same results.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6154
  • Yes Pinky, Do-more will control the world!
Re: Do More as a Direct Logic client
« Reply #4 on: October 06, 2015, 10:02:56 PM »
The NAK is the 250 rejecting the request. I'll need the specifics of your request to give you guidance.
Logged
"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

Henryp

  • Hero Member
  • *****
  • Posts: 161
Re: Do More as a Direct Logic client
« Reply #5 on: October 08, 2015, 07:27:24 PM »
We did some more testing today.  We verified good communications with the 250 and the ECOM 100 card at the remote site and then we  move that  ECOM 100 card  into the remote Do More base and it stops communicating with the NAK error.   I don't understand how the ECOM card can work in the 250 and not the Do More. We have changed out the Do More, base and power supply. The radios back to the plant can be setup as a bridge or layer 3 OSPF router.  At the plant I can see it with netedit and even connect with DMD.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6154
  • Yes Pinky, Do-more will control the world!
Re: Do More as a Direct Logic client
« Reply #6 on: October 08, 2015, 07:38:57 PM »
What are you trying to read or write in the Do-more? The default ranges are different than the DL250, and the NAK sounds like he is rejecting the request.
Logged
"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

ADC Product Engineer

  • Hero Member
  • *****
  • Posts: 270
Re: Do More as a Direct Logic client
« Reply #7 on: October 09, 2015, 08:43:13 AM »
Did you change the peer table in the ECOM100 when you moved it?
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6154
  • Yes Pinky, Do-more will control the world!
Re: Do More as a Direct Logic client
« Reply #8 on: October 09, 2015, 08:56:19 AM »
The title says client, but it's really not clear to me what the actual transactions are. If it is client and he just moved the ECOM100, I don't think the peer table needs to be changed. If it is actually server, it's probably just that the requests are out of range. As a server, requests go to DLxx memory which is much smaller than DL's native memory by default.

We really need more detail Henry. What comm requests are failing, and is the Do-more side originating or receiving the request?
Logged
"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

Henryp

  • Hero Member
  • *****
  • Posts: 161
Re: Do More as a Direct Logic client
« Reply #9 on: October 12, 2015, 12:23:39 PM »
I have a Master Do More acting as a data collector. This Do More PLC polls and sends commands to field sites by doing DL RX and WX commands. At my field site I have a 250 and a Do More PLC side by side. The Do More PLC also has an Ecom 100 in the base and I have expanded the DLV memory table, so I’m not requesting data from an invalid location. The master Do More can ping the Do More in the field but can’t communicate using a DLRX command. I have tried using the internal port, Ecom 100 and even moved the Ecom 100 out of the 250 (which I have no problem communicating with) to the Do More  and it also fails. I have also tried Modbus with no luck. I have a computer at the master location with Do More Designer on it and it can connect to my field site (where I have the Do More PLC) with no problems. I have network connectivity, I just can’t do peer to peer communications.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6154
  • Yes Pinky, Do-more will control the world!
Re: Do More as a Direct Logic client
« Reply #10 on: October 13, 2015, 11:30:12 AM »
Henry, email us at support@hosteng.com. We're going to need more specific information. The key point is that it can work, but it's going to take more than what we can do via the forum.
Logged
"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

Henryp

  • Hero Member
  • *****
  • Posts: 161
Re: Do More as a Direct Logic client
« Reply #11 on: October 20, 2015, 03:46:46 PM »
We got it working but I’m not sure we identified the exact problem. It may be possible we had two hardware issues. The 205 6 slot rack and power was older from the 1990’s. Does the Do More load the power more than a 250 CPU or does the 205 power supply have a secondary voltage that a Do More uses and a 250 CPU doesn’t?

Thanks, soon to have our first distribution system Do More online.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6154
  • Yes Pinky, Do-more will control the world!
Re: Do More as a Direct Logic client
« Reply #12 on: October 20, 2015, 03:59:11 PM »
Do-more may use more current than the DL250, but I don't actually know what the DL250 uses. For 205, I'm thinking the only supply is 5v.


Great news on the first Do-more system up! Would love to hear your thoughts on how it compares to DL.
Logged
"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

ADC Product Engineer

  • Hero Member
  • *****
  • Posts: 270
Re: Do More as a Direct Logic client
« Reply #13 on: October 20, 2015, 08:56:12 PM »
The racks from the 90's had a lower capacity power supply in them.  It is entirely possible that due to age and other factors that it was in fact overloaded.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6154
  • Yes Pinky, Do-more will control the world!
Re: Do More as a Direct Logic client
« Reply #14 on: October 20, 2015, 09:10:39 PM »
And wasn't it specifically the 6 slot that was an issue, leading Koyo to put the 9 slot power supply in 6 slot bases...or am I mis-remembering?
Logged
"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
Pages: [1] 2
« previous next »