...
| Expand |
|---|
| title | If the Firewire/Hyperwire card is not under AerotechNode0 |
|---|
|
- For Firewire cards, find the card under the "Windows Devices > IEEE 1394 host controllers" tree. Right-click and select Pass to INtime using polling.
| Expand |
|---|
|  Image Modified
|
- For Hyperwire cards, find the card under the "Windows Devices > Aerotech Devices" tree. Right-click and select Pass to INtime using MSI.
| Expand |
|---|
|  Image Modified
|
- Navigate to File > Save Configuration to save the INtime Device Manager configuration, then restart the PC.
|
...
| Expand |
|---|
| title | For Hyperwire Drives |
|---|
|
- Open A3200 Configuration Manager.
- Navigate to Controller > Drive Configuration (Note: all axes will be disabled and all AeroBasic programs will stop running when Drive Configuration is opened).
- On the Communication Channels tab, ensure that the communication channels for each drive line up with the axes in the parameter file.
- If they do not, either assign new communication channels manually or click "Auto-Assign Channels" to assign them automatically.
- Click Commit to save the new communication channels.
 Image Modified
|
Once the above has been verified, the bottom line is that there is a communication disconnect between the controller/drive hardware and the computer/software.
- The drive is not powered. Check the power LED, ensure that the drive is receiving power.
- If possible, swap the drive with an identical drive in the system or with a spare to rule out an issue with the drive itself. If the system has multiple discrete drives, connect each drive to the PC individually (one at a time) to rule out a problem with one of the drives (or Hyperwire/Firewire cables).
- The Firewire/Hyperwire cable is either bad or not connected.
- The Firewire/Hyperwire card is either bad, not connected to any drives, or not fully seated in the PCI/PCIe slot. Try using different Firewire/Hyperwire ports on the card, and a different PCI/PCIe slot in the PC if possible. For Firewire drives, also try using a different Firewire port on the drive, if available.
- The PC configuration is preventing proper communication.
- Go through the Optimizing PC Performance and Windows 10 Update guides.
- External software (laser, camera, etc.) and any antivirus software or firewalls could be contributing to the issue. As a troubleshooting step, temporarily disconnect the PC from internet/network access.
- If the PC is in a remote client/server configuration, the client PC may not be communicating correctly with the server PC. Ensure that the axis still appears as virtual from the server PC (which is directly connected to the hardware).
- For Nstep and NServo units only: check the state of the CONFIG switch located next to the communication channel (device number) dip switches. This switch will cause the drive to report its last axis as virtual when set to the ON position.
...