hexagon logo

tcp/ip port setting

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.
Parents
  • 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.




Reply
  • 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.




Children
No Data