Information and discussion regarding the ACE PackXpert software


Postby TravisA » Thu Aug 28, 2008 10:22 am

This is meant to include answers to some of the more common questions and issues that may come up with a new system. Please reply with anything that I've missed and I'll add it to the FAQ

Installation notes
ACE has several prerequisites that must be installed. The installer will automatically check to see if they are installed, and if not, will install them. These prerequisites are:
• Microsoft .NET Framework 2.0
• DirectX 9.0c
• HexSight 3.4
• Basler Pylon driver and viewer 1.0

Installing on a PC previously using AdeptSight 2.0
Because ACE and AdeptSight 2.0 use some different vision components, there are potential conflicts when installing ACE. It is best to completely remove all AdeptSight 2.0 items before installing ACE. The following should be manually uninstalled before installing ACE:
• AdeptSight 2.0
• HexSight
• Basler BCAM driver/viewer

Can’t connect to a controller
Check the Windows Firewall settings, by default it may be blocking the ports that ACE uses to connect. The following network ports are used by the Adept ACE software:
• PC: UDP port 69 (for TFTP file transfer), UDP ports 1993 (for controller scan), 1994 and 1996 (for startup communication). Remote connections to ACE use TCP port 43434 and UDP port 43435. The remote vision server uses UDP port 43436.
• Adept controller: UDP port 1992 (for controller scan), UDP ports 1994-1997 (if using ActiveV), TCP port 1999 (if using AdeptWindows), TCP port 43234 (ACE communication).
Because ACE uses an ActiveV connection for some data, it is important to understand that this works through the V+ monitor window, so if there is a simultaneous AdeptWindowsPC connection, any input at the monitor window could disrupt ACE communications. Avoid running programs such as Config_c or dc_setup, and ensure the monitor window is free.

Can’t recognize camera
If your system has had AdeptSight 2.0 installed on it, the Basler BCAM driver may still be installed. Open the Device Manager (from windows Control Panel, open System, then on the Hardware Tab, click Device Manager). When the camera is plugged in it should show up as a “Basler pylon device.” If it shows up as a BCAM device, right-click on the camera and click Uninstall. Then unplug and reconnect the camera. It should show up as a Basler pylon device. If the problem persists, make sure the BCAM driver is uninstalled, and reinstall “Basler pylon viewer 1.0.” It can be found in the ISSetupPrerequisites folder on your ACE installation CD.
Vision window corrupt
Update the drivers of your PC components to their latest versions. In particular we have witnessed issues with the Intel P965 Express Chipset with onboard graphics.

3D Visualization not available
If the “3D” button is disabled on the workspace toolbar and not available in the View menu, there may be a graphics hardware or software problem. Verify the latest version of DirectX9.0c was installed correctly. Check the graphics properties on your PC, and see if Hardware Acceleration has been turned off; this would disable the Direct3D components from being displayed.

Setting up a conveyor for latching
If using a conveyor belt for tracking parts (vision or sensor located) the CX controller must be configured to read the latch signal. The sensor output or strobe output from the camera must be wired to one of the Fast Digital Inputs on the XDIO connector (signals 1001 – 1004). Open the controller editor in the ACE workspace, and click “Configure V+.” Go to the Configuration tab and scroll down to the .ROBOT section. Manually enter the configuration, for example:
BELT 1 = "/POS_LATCH 1001"
If more than one signal is to be used on the same belt encoder on the controller:
BELT 1 = "/POS_LATCH 1001 1002"
After you save this, the controller will have to be rebooted. If any V+ programs are executing they will have to be stopped before ACE can reboot the controller.

Return to ACE PackXpert

Who is online

Users browsing this forum: No registered users and 1 guest