News:

  • August 30, 2026, 07:13:24 PM

Login with username, password and session length

Author Topic: Remote access  (Read 24578 times)

mhw

  • Hero Member
  • *****
  • Posts: 250
Remote access
« on: November 05, 2013, 02:32:59 PM »
Is it possible to connect to a H2-DM1E with DMD over the internet using port forwarding?

rlp122

  • Sr. Member
  • ****
  • Posts: 92
Re: Remote access
« Reply #1 on: November 05, 2013, 02:36:23 PM »
Sure thing.  I have done it several times.  While disconnected from the PLC go into the Communications Link.  Pick Port, then Advanced Settings.  Ping the PLC and multiply the ping time by 10.  Put this value into your timeout setting.

If the ping time is really variable, you might have to multiply by more than 10 to get a reliable connection.

mhw

  • Hero Member
  • *****
  • Posts: 250
Re: Remote access
« Reply #2 on: November 05, 2013, 02:42:19 PM »
Every time I configure a link and click on auto my program locks. I have a test setup in my office with port 28784 forwarded to the DM. I can switch the CPU to a DL260 and put an ECOM in one of the slots and connect using DS5.

rlp122

  • Sr. Member
  • ****
  • Posts: 92
Re: Remote access
« Reply #3 on: November 05, 2013, 04:02:12 PM »
You can't use Auto for Port Forwarded links.  Select Continue instead.

mhw

  • Hero Member
  • *****
  • Posts: 250
Re: Remote access
« Reply #4 on: November 05, 2013, 04:25:51 PM »
Quote
You can't use Auto for Port Forwarded links.  Select Continue instead.
I do not see a "Continue" button in the Link Editor. If I click on "Accept" then I will receive the link failed message. Selecting "Continue" will exit the link editor but the link will not work.

rlp122

  • Sr. Member
  • ****
  • Posts: 92
Re: Remote access
« Reply #5 on: November 06, 2013, 08:43:24 AM »
In the link editor under Protocol add more time to the timeout there as well.  Same thing.  Ping x10.

mhw

  • Hero Member
  • *****
  • Posts: 250
Re: Remote access
« Reply #6 on: November 06, 2013, 08:49:12 AM »
Quote
In the link editor under Protocol add more time to the timeout there as well.  Same thing.  Ping x10
I think you are missing the point. DMD will lock and stop responding when I try. I can stick an ECOM card in the rack and connect to it but not to the H2-DM1E onboard port.

rlp122

  • Sr. Member
  • ****
  • Posts: 92
Re: Remote access
« Reply #7 on: November 06, 2013, 10:16:04 AM »
I understand that part.  I am just trying to take you through all of the troubleshooting steps that I would take if it were me.  By going through the steps, perhaps we can figure out what exactly is different that is causing the issue.

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6174
  • Yes Pinky, Do-more will control the world!
Re: Remote access
« Reply #8 on: November 06, 2013, 10:17:25 AM »
I think you are missing the point. DMD will lock and stop responding when I try. I can stick an ECOM card in the rack and connect to it but not to the H2-DM1E onboard port.


if it is locking up and if you don't mind, please PM me the connection details. I would like to try to duplicate what you are seeing and/or successfully connect. we'll keep everything private.
"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

rlp122

  • Sr. Member
  • ****
  • Posts: 92
Re: Remote access
« Reply #9 on: November 07, 2013, 04:37:59 PM »
Did you get this working?

mhw

  • Hero Member
  • *****
  • Posts: 250
Re: Remote access
« Reply #10 on: November 08, 2013, 08:27:55 AM »
Quote
Did you get this working?
The short answer is no. I contacted AD tech support and PM'd BobO a couple of days ago and am still awaiting a response.
I appreciate your wanting to help rlp122. What I have found is that DMD will not lock if I select edit or add link from the Launchpad. It will just give me the "link not responding" error message. If I do this from within an open project, either by selecting it from the file menu or the "offline" button on the status bar, then it will lock instead of giving me the error message. I encourage you to try this with a random IP address and see if you get the same result.
Putting all that aside, I still cannot get a connection to a H2-DM1E using the onboard port. To reiterate, I have a PLC setting in my office with a H2-DM1E and an ECOM100. I have set both Ethernet ports to the same IP address but only connect a cable to one at a time. When connected to the ECOM it works but when connected to the H2-DM1E it doesn't. All setting in DMD link editor are the same. This proves to me that my port forwarding and cabling is fine.

plcnut

  • Hero Member
  • *****
  • Posts: 815
    • premiersi.com
Re: Remote access
« Reply #11 on: November 08, 2013, 08:56:55 AM »
Try re-seating the CPU. I had one that would only connect via USB, a re-seat and all was good. It has to do with scan times, (my understanding is that) when there is a bad connection the CPU spends do much time at the backplane that it will timeout on the Ethernet port servicing.
Circumstances don't determine who we are, they only reveal it.

~Jason Wolthuis
Premier Systems Integration, LLC
https://premiersi.com

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6174
  • Yes Pinky, Do-more will control the world!
Re: Remote access
« Reply #12 on: November 08, 2013, 12:23:22 PM »
...PM'd BobO a couple of days ago and am still awaiting a response...

I did try it and was not able to connect. I was not able to duplicate any lockup behavior.
"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: 6174
  • Yes Pinky, Do-more will control the world!
Re: Remote access
« Reply #13 on: November 08, 2013, 12:42:15 PM »
I also tried the forward facing unit we have here and it worked fine. The same unit has been tested and works great from ADC.

As for differences between ECOM100 and DM1E, that's hard to say. They run different stacks and there are some subtle differences between implementations, but nothing that I have ever seen prevent proper function.

Switches can get pretty smart, and if you are switching out different devices with the same IP address, I've seen that confuse the switch and require a power cycle. Beyond that it's hard to say. I would be happy to PM you the connection details of the unit we have on our forward facing network if you would like to try connecting to it.
"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: Remote access
« Reply #14 on: November 09, 2013, 08:18:05 AM »
Rookie mistake, of course. I needed a gateway address.
I had assumed that I did not need it since I could connect to the Ecom.
The problem with the link editor locking has never been explained, but apparently I am the only one that can make this happen. As long as I have a good destination or open the link editor from the Launchpad then I don't have the problem either.
Thanks to all for your help, especially BobO!