Error Message

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error Message

    I'm getting an error message; "TCP/IP Communication Failed....Switch to RS-232?" (Yes or No.)
    What is this message and why am I getting it? If I click yes it opens up the programs. If I click no....it will not open up programs.
    Leinenkugel's....A Northwoods favorite...brewed in Chippewa Falls, Wisconsin by 73 people who care...

  • #2
    That is a network connection issue. Check all connections on the rear of your comp and the wire going to the wall. It sounds as if you back up all files on your network and your comp is searching for the network connection for the program. If all leads in your office are ok,,,contact your IT dept, it may be an issue with the server.

    VP A.Gore
    sigpicA.Gore

    Comment


    • #3
      Thanks
      Leinenkugel's....A Northwoods favorite...brewed in Chippewa Falls, Wisconsin by 73 people who care...

      Comment


      • #4
        Originally posted by Got-a-life View Post
        I'm getting an error message; "TCP/IP Communication Failed....Switch to RS-232?" (Yes or No.)
        What is this message and why am I getting it? If I click yes it opens up the programs. If I click no....it will not open up programs.
        Have you tried shutting the machine down? The controller and the computer running the CMM. The tcp/ip thing happens to me when the computer/controller get futzed up. Shut down restart, home and open a program.
        sigpic

        James Mannes

        Comment


        • #5
          try ping

          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.

          Comment


          • #6
            Don, Thanks for going the extra step,

            Here is Don's description plus my computer stuff (in my own note taking style).

            TCP/IP SETUP ON COMPUTER
            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.0.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/IPPort 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.
            sigpic

            James Mannes

            Comment

            Related Topics

            Collapse

            Working...
            X