Difference between revisions of "Diagnostic Steps for Master Power On Problems"

From ATTWiki
Jump to: navigation, search
Line 7: Line 7:
 
= Check the IP Address of the Operator Station =
 
= Check the IP Address of the Operator Station =
  
#Press the '''SYSTEM''' button<br>http://www.advancedtubular.com/images/cncbender/ipaddress/step1_systemmenu.jpg
+
#Press the '''SYSTEM''' button<br><br>http://www.advancedtubular.com/images/cncbender/ipaddress/step1_systemmenu.jpg
#Press the '''NETWORK INFO''' tab  
+
<br>#Press the '''NETWORK INFO''' tab <br><br>
#Your Operator Station IP Address will be listed
+
#Your Operator Station IP Address will be listed<br><br>
  
 
If the Operator Station IP address DOES NOT begin with "192.168.0" then all CNC Bender will not be able to communicate with the Modules and the CNC Bender software will not functional. (CNC Bender uses a Class C network standard, which requires the first three octet values be identical for every device on the network. Most SMT/ATT CNC Benders use a Net Indentifier of "192.168.0")
 
If the Operator Station IP address DOES NOT begin with "192.168.0" then all CNC Bender will not be able to communicate with the Modules and the CNC Bender software will not functional. (CNC Bender uses a Class C network standard, which requires the first three octet values be identical for every device on the network. Most SMT/ATT CNC Benders use a Net Indentifier of "192.168.0")

Revision as of 17:56, 29 June 2006

Contents


Diagnosing Master Power On Issues

There are a number of diagnostics that you can perform if you experience problems starting the master power on your SMT/ATT CNC Bender. Step through these diagnostics to resolve master power issues.

Check the IP Address of the Operator Station

  1. Press the SYSTEM button

    http://www.advancedtubular.com/images/cncbender/ipaddress/step1_systemmenu.jpg


#Press the NETWORK INFO tab

  1. Your Operator Station IP Address will be listed

If the Operator Station IP address DOES NOT begin with "192.168.0" then all CNC Bender will not be able to communicate with the Modules and the CNC Bender software will not functional. (CNC Bender uses a Class C network standard, which requires the first three octet values be identical for every device on the network. Most SMT/ATT CNC Benders use a Net Indentifier of "192.168.0")

Ping the IP Addresses of your Modules

  1. Open a command prompt through Windows (Start Button ->Run), then type "CMD" and press "Enter"
  2. Type "Ping 192.168.0.233" (The address of the first module)
    • A typical successful ping should look like:
Pinging 192.168.0.233 with 32 bytes of data:

Reply from 192.168.0.233: bytes=32 time=1ms TTL=64
Reply from 192.168.0.233: bytes=32 time=1ms TTL=64
Reply from 192.168.0.233: bytes=32 time=1ms TTL=64
Reply from 192.168.0.233: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.233:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms
    1. A typical failure will look like:
Pinging 192.168.0.233 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.233:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

If pinging the IP Address fails, then CNC Bender will not be able to communicate with the modules around the bender. The master power will not switch on until this issue is resolved.

Failure could mean a number of things:

  1. Cables that connect to the modules could be loose.
  2. Cables could be broken.
  3. Modules could be malfunctioning.
  4. Ethernet switch could be malfunctioning
  5. IP Address Conflict.

Check the Indicator LED's on the Netgear Ethernet Switch and on the Modules.

If CNC Bender is running within Windows, there should be a LED flashing for every cable plugged into the Netgear Switch. If the LED is not lit, the cable is probably broken. If the LED is not flashing, CNC Bender is not communicating the modules.

Typically a good start in troubleshooting the Netgear Switch is rebooting the Switch by unplugging the power and plugging it back in.

Check to be sure that CNC Processor is not frozen

  1. Close CNC Bender
    1. CNC Bender will attempt to close other support programs (like CNC Processor)
  2. When it is closed, press Ctrl-Alt-Del to display the Windows Task Manager
  3. Activate the Processes tab in the Windows Task Manager
  4. Sort the Image Names alphabetically from A to Z by pressing the "Image Name" column title. If the items are sorting from Z to A, then press the column title again to reverse the sort.
  5. Carefully examine the list for cncprocessor.exe
  6. If you find it, then select it, then press the End Process button. (This was the problem.)
  7. Answer "Yes" to "Are you sure you want to terminate this process.?"
  8. Close the Windows Task Manager
  9. Start CNC Bender again
  10. View the Processor menu
  11. Check to see if there is activity in the CNC Processor log. (There should be text in this log, indicating that CNC Processor is running in the background.)

Check the Safety Devices

  1. Safety Mat
    • Is it activated?
    • Is there Conduit on the mat?
    • Is there a box on the corner of the mat?
    • Has there been a heavy object dropped on the mat recently?
    • Is there a cut in the mat? (Dropping a tube end onto the mat can cut through and cause the mat to constantly activate)
    • Is the mat cable broken?
    • Is the mat cable connected?
  2. Safety Plate
    • Check the safety plate on the back of the bend arm. Is the switch activated?
  3. E-Stop
    • Is the E-Stop pulled?
    • Is there more than one E-Stop? If yes, then are they both pulled?

Is CNC Processor set to LOAD in the LOW LEVEL menu?

  1. Go to the System tab
  2. Click on the LOW LEVEL Setup button in the MAIN SYSTEM tab
  3. Press the General Dynamic Options tab
  4. Scroll down to about option 29 or 30. Look for "Load CNC Processor"

It should be set to LOAD.

If it is set to [disabled], and this bender was recently running, then you may have a corrupt configuration file.

If this is the case, then see this link for restoring the configuration file: