News:

  • October 14, 2025, 12:18:25 AM

Login with username, password and session length

Author Topic: connecting to new cpu  (Read 4270 times)

PLCGuy

  • Internal Dev
  • Hero Member
  • ****
  • Posts: 677
connecting to new cpu
« on: December 27, 2016, 08:08:09 AM »
What am I doing wrong that I can not config a new CPU over ethernet? I have to use my usb then Ethernet. I am on the same network, no switch, and when I scan, nothing shows.
Is there a procedure to configure a new CPU?

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6126
  • Yes Pinky, Do-more will control the world!
Re: connecting to new cpu
« Reply #1 on: December 27, 2016, 09:33:32 AM »
Sounds like a multi-NIC problem. From NetEdit, choose the adapter you are connected to from the Network menu.
"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

PLCGuy

  • Internal Dev
  • Hero Member
  • ****
  • Posts: 677
Re: connecting to new cpu
« Reply #2 on: December 27, 2016, 12:22:40 PM »
I got connected. I changed the address to 192.168.0.6 but when I said okay, the cursor just kept on spinning until an error message came up. I forgot to write it down. So I thought maybe I should change my notebook to the address of 255.255.255.6 thinking well that is the default of the cpu. But of course windows did not like that and said it was out of range. ummm. Okay so get out the usb cable and go that route. I set up the cpu config and such and all was good. I finally looked at the address and it was already set to 192.168.0.6. So the addy change did take effect. I think what happened, the address changed but now my notebook needed to change also to the same 192.168.0.x. I think there should have been some type of message telling me once i accept the change I will no longer be able to communicate and I would need to change my notebook addy to re-connect. I will try to duplicate the error message with another cpu and see what the message was.
Am I right in thinking that it changed, but now my notebook needed to change?

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6126
  • Yes Pinky, Do-more will control the world!
Re: connecting to new cpu
« Reply #3 on: December 27, 2016, 12:33:25 PM »
The short answer is likely that the address you set the CPU to was not on the PC's (logical) network, so once it was set it could no longer 'see' the CPU. Best thing I can recommend is to get your IT guy to help you and/or get a book or tutorial on IP networking basics. It's not hard, but it does have to be done right.
"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

Mike Nash

  • Hero Member
  • *****
  • Posts: 645
Re: connecting to new cpu
« Reply #4 on: December 27, 2016, 01:03:47 PM »
I think there should have been some type of message telling me once i accept the change I will no longer be able to communicate and I would need to change my notebook addy to re-connect.

I have seen this warning so many times with Allen-Bradley I didn't even realize Do-more doesn't warn of it. I guess after awhile it becomes second nature, at least until I forget.

There is also the whole "Windows watching butterflies in left field" thing and not updating network status on connected computers and devices, sometimes for hours (days even.)

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6126
  • Yes Pinky, Do-more will control the world!
Re: connecting to new cpu
« Reply #5 on: December 27, 2016, 01:07:47 PM »
Funny. We get no end of complaints about the number of warnings we generate, and people often cite AB as an example of one that doesn't warn where we do.

This is basic TCP/IP networking and exactly the way we have been doing it for nearly 20 years. Not saying we can't do better, but this isn't a new issue.
"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

PLCGuy

  • Internal Dev
  • Hero Member
  • ****
  • Posts: 677
Re: connecting to new cpu
« Reply #6 on: December 28, 2016, 11:59:30 AM »
I read the posts and went back over what had happened. It was that the address changed and da, being so caught up in trying to get the project done, I did not realize my notebook is not going to reconnect if the address has been changed from what i was set to. Do-More is not doing anything "wrong", just that there was no warning of the change and i will lose connection. Just something I should have known. I have been doing networking for a few years and should have known better. Just sometimes I get so caught up in the project and all that is going on, little things slip by.