hexagon logo
Register Sign in
  • Replies 22 replies
  • Subscribers 224 subscribers
  • Views 487 views
  • Users 0 members are here
Options
Related

tcp/ip port setting

Andy F.
I am having trouble connecting to my DEA controller on my Global.
Using rs-232 connection I was able to use hyper terminal to show the connections.

READY
SHOW TCPIP
TCP/IP Information

Ctrl Internet Address : 80.128.0.2
Port Number : 0
Host Internet Address : 80.128.0.1
Connection State : listening
Bad IP Checksums : 0
Bad TCP Checksums : 0
Packets Retransmitted : 0

Is there a way to change the port setting remotely? It should be set to 2001, but as you see it is 0 now. The motherboard was changed recently in the controller.
  • This is what I have...no warranty implied.
    Go to Control Panel
    Network Connections
    LAN
    Properties
    Then…
    Highlight TCP/IP
    Then…
    Properties
    Choose radio button tha says “use following IP ADDRESS”
    Type in at IP… 80.128.0.1
    Type in at subnet…255.255.0.0
    Under LAN…
    Properties
    General Tab
    Configure
    Advanced Tab
    Speed & duplex = 10mb FULL


    Within PC-DMIS…

    Machine Interface Setup
    Use TCp/IP link to drive Machine
    TCP/IP Address= 80.128.0.2
    TCP/IP Port Number= 2001


    Jim is right on the ball, and I especially like his pitcures and aspriations. Let me add a little more to this for background information.

    The same thing happens to me on occasion. The Leitz system can work with either serial (RS-232) or ethernet (TCP/IP) communications. Both will work for most measureing, but when it comes to scanning and passing large amounts of data, you'll see that TCP/IP is much faster. If you're not scanning, then it probably won't make much difference, unless you are running short of serial ports and would just rather use TCP/IP.

    The controller has a fixed IP address, typically something like 80.128.0.1 and the computer might be 80.128.0.2 (or vice versa). They are typically 1 unit apart. To find out what the PC is, you can go to a DOS prompt and enter the command

    IPCONFIG /ALL

    which will display a fair amount of information, but it will include the ethernet adress of the PC. From the same DOS prompt, enter the command to try to test the connection to the controller, such as

    PING 80.128.0.1

    or

    PING 80.128.0.2

    It should return a list of about 5 quick test calls, and you'll know immediately by looking at them if they worked or not. If PING works, then it is not a cable issue. If PING fails, then PC-DMIS will not work.

    To find out what PC-DMIS thinks the controller is set to, start it up and to the Edit / Preferences / Machine Interface and look in the tab where you would enable TCP/IP communciations, and you'll see the address it wants to find the controller at.




  • The problem is the TCPIP Port number is 0 at the controller. Setting 2001 under machine option does not change that setting in the controller.
  • I'm not at the cmm, but i think you can change 2001 by 0 in PC-DMIS (config CMM Window, just where you type TC-PIP adress). You're right, when you do a "show tcpip", it returns the controller config. You just have to configure settings off pc_dmis to make it work...
  • When I try to ping the machine I get: "Destination host unreachable."
    then " Request timed out."
    Setting the port to 0 under the machine settings does not work also. It has to be 2001.
  • If the settings worked after they installed the new motherboard then I would contact service again as it appears the controller has lost its ipconfig settings.
    If thats the case you will not be able to connect to the controller at all and it will require a controller firmware reinstall.
    (this happened to us a while ago with a "new" controller upgrade the reset/reinstall fixed a few issues we had been having with scanning)
  • If the settings worked after they installed the new motherboard then I would contact service again as it appears the controller has lost its ipconfig settings.
    If thats the case you will not be able to connect to the controller at all and it will require a controller firmware reinstall.
    (this happened to us a while ago with a "new" controller upgrade the reset/reinstall fixed a few issues we had been having with scanning)

    Is it the firmware or only the constant.dat that contains port number ? (i'm not at the cmm to check it...)
  • Is it the firmware or only the constant.dat that contains port number ? (i'm not at the cmm to check it...)

    I dont know.
    The engineer told me he did a firmware reinstall and that fixed all our i/o issues with the controller.
    What he actually changed I did not see, I wasn't next to the cmm at the time.
  • I plugged back the old computer again and when I try to ping the controller I got the same problem. It seems all this time it was running with the rs-232 com port. The strange thing is on my old computer (windows XP) it shows that a network status as connected so it is looks like you running the controller with your network card, but actually it is not working, because if you unplug the rs-232 cable then the machine lose connection.

    I wonder how can a firmware lose its setting info? Maybe it was not set up correctly at the first place? They want to charge 1400$ to come out to look at it.
  • My port #, both for the PC and the controller, is also 2001. Have you tried setting the port to 2001 at the controller?

    Sorry, I was being lazy, I see that you already know this, and also that it is not an easy thing to do, I will look further. . .
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement