Troubleshooting pCon.catalog in AutoCAD: Common Issues & FixespCon.catalog is a powerful tool for integrating manufacturer product data into AutoCAD, but like any plugin, it can run into issues. This article walks through common problems users face, explains likely causes, and provides step‑by‑step fixes and preventative tips to keep your workflow smooth.
1. Installation and Compatibility Problems
Common symptoms
- pCon.catalog doesn’t appear in AutoCAD’s ribbon or menu.
- Installer runs but plugin is not listed in AutoCAD’s add-ins.
- Error during installation mentioning unsupported AutoCAD version.
Likely causes
- Incompatible AutoCAD version or bitness (32-bit vs 64-bit).
- Insufficient user permissions during installation.
- Corrupted installer or interrupted installation.
- AutoCAD blocked the plugin due to security settings.
Fixes
- Verify version and bitness:
- Confirm your AutoCAD version (e.g., 2018, 2020, 2023) and whether it’s 32‑bit or 64‑bit. pCon.catalog requires the matching bitness and supported versions.
- Run installer as Administrator:
- Right‑click the installer and choose “Run as administrator”.
- Repair or re‑download installer:
- Re‑download the latest pCon.catalog installer from the vendor to avoid corruption.
- Check AutoCAD’s Trust settings:
- In AutoCAD, go to Options > System > Security Options and ensure loading of external applications is permitted.
- Review install logs:
- Look for logs in the installer folder or Windows Event Viewer for specific errors; search those error messages on support forums or vendor documentation.
Prevention
- Keep AutoCAD and pCon.catalog updated to compatible versions.
- Maintain admin rights for installations or have IT assist.
2. pCon.catalog Commands Not Responding or Crashing AutoCAD
Common symptoms
- Commands from pCon.catalog execute but nothing happens.
- AutoCAD freezes or crashes when using pCon.catalog features.
Likely causes
- Conflicting third‑party plugins.
- Insufficient system resources (RAM, GPU).
- Outdated graphics drivers or corrupted user profile.
- Large or malformed catalogs being loaded.
Fixes
- Start AutoCAD in Safe Mode or use a clean profile:
- Launch AutoCAD with a clean profile (Options > Profiles) to rule out profile corruption.
- Disable other plugins:
- Temporarily disable other third‑party add‑ins to find conflicts.
- Increase available resources:
- Close other heavy applications; ensure you meet pCon.catalog system requirements.
- Update graphics drivers:
- Install the latest drivers from your GPU vendor.
- Test with small catalogs:
- Load a minimal catalog to see if a specific catalog file causes the crash. If so, inspect or request a clean version from the provider.
- Check AutoCAD’s diagnostic trace:
- Use the AutoCAD crash report to capture details and send to pCon support if needed.
3. Imported Models Appear Incorrectly (Scale, Materials, Geometry)
Common symptoms
- Objects have wrong scale or units.
- Materials/textures missing or display as flat colors.
- Geometry looks distorted or contains missing faces.
Likely causes
- Unit mismatch between pCon.catalog data and AutoCAD drawing.
- Unsupported material or texture formats.
- Mesh conversion issues during import.
Fixes
- Match units before import:
- Set AutoCAD drawing units (UNITS command) to match the catalog source (meters, millimeters, inches).
- Use the import settings:
- In pCon.catalog import dialog, check options for scaling and unit conversion.
- Reapply materials in AutoCAD:
- If textures are missing, point AutoCAD materials to the correct texture folder or reassign materials using the Materials Browser.
- Export formats:
- Prefer neutral formats (e.g., OBJ, FBX, DWG) that preserve geometry and materials. If the catalog offers multiple export options, test the one that keeps the best fidelity.
- Repair geometry:
- Use AutoCAD’s Solid Editing and 3D tools to fix small issues or convert problematic meshes to solids where needed.
Example: If a catalog object is 100× larger, check that the catalog file uses millimeters while your AutoCAD drawing uses meters; apply a scale factor of 0.001 on import.
4. Missing or Outdated Catalog Data
Common symptoms
- Products listed in pCon.catalog are missing or show outdated specs.
- Catalog synchronisation fails.
Likely causes
- Local cache contains old data.
- Network issues preventing catalog updates.
- Vendor removed or changed entries in the central catalog.
Fixes
- Clear local cache:
- In pCon.catalog settings, clear the cache or temporary files so the client fetches fresh data.
- Check network and proxy settings:
- Ensure internet access to pCon update servers; configure proxy settings if your network uses one.
- Manually refresh catalogs:
- Use the refresh or sync function to force an update.
- Contact vendor:
- If specific products are missing or incorrect, reach out to the manufacturer or pCon support for updated catalog files.
Prevention
- Schedule periodic syncs and keep an eye on cache size and age.
5. Exporting From pCon.catalog to AutoCAD Produces Large Files or Slow Performance
Common symptoms
- Resulting DWG/DXF files are very large.
- AutoCAD becomes slow when opening files exported from pCon.catalog.
Likely causes
- High polygon count meshes and detailed textures.
- Embedded high‑resolution images.
- Multiple nested blocks and redundant geometry.
Fixes
- Reduce polygon count:
- In pCon.catalog export options, use LOD (level of detail) or lower tessellation settings before export.
- Compress or downsample textures:
- Replace large textures with smaller sizes or compressed formats.
- Purge and audit:
- After import, use PURGE and AUDIT commands in AutoCAD to remove unused objects and fix errors.
- Explode cautiously:
- Avoid exploding blocks unless necessary; use blocks to keep file sizes smaller.
- Use XREFs:
- Reference large models as external references rather than embedding them directly.
6. Licensing and Authentication Errors
Common symptoms
- Prompts for license keys or authentication failures.
- Features disabled due to license verification errors.
Likely causes
- Expired or misconfigured license.
- Network access blocked to license server.
- User account issues with pCon account.
Fixes
- Verify license status:
- Check your pCon account or license manager for expiry or activation limits.
- Ensure network access:
- Allow access to the license server and disable firewalls or proxies blocking it, or configure exceptions.
- Reauthenticate:
- Sign out and sign back into pCon services; re-enter license keys if needed.
- Contact support for license transfer or activation issues.
7. Scripting and Automation Failures (APIs, Macros)
Common symptoms
- Custom scripts or API calls to pCon.catalog fail or return errors.
- Automated exports hang or abort.
Likely causes
- API changes after software updates.
- Incorrect parameters or missing dependencies.
- Security settings blocking scripts.
Fixes
- Check API docs and version:
- Ensure your scripts use the current API methods and parameter formats.
- Add error handling and logging:
- Capture API responses to pinpoint failing operations.
- Ensure dependencies:
- Confirm that required libraries or runtimes (e.g., .NET versions) are installed.
- Run with appropriate permissions:
- Execute scripts under a user with sufficient rights.
8. UI Display Issues (Icons Missing, Dialogs Off‑screen)
Common symptoms
- pCon.catalog windows open off‑screen or behind other windows.
- Icons or UI elements are missing or garbled.
Likely causes
- Multi‑monitor setups with changed monitor arrangements.
- Corrupted UI cache or settings.
- Display scaling (DPI) issues.
Fixes
- Reset window position:
- Use Windows key + Arrow keys to snap off‑screen windows back into view, or reset UI layouts in pCon settings.
- Delete UI cache:
- Remove pCon.catalog’s UI cache files (location varies by OS) to reset layouts.
- Adjust DPI settings:
- Right‑click AutoCAD executable > Properties > Compatibility > Override high DPI scaling behavior.
- Reinstall if UI files are corrupted.
9. Slow Search or Indexing Problems
Common symptoms
- Searching the catalog is slow or returns incomplete results.
- Indexing hangs during startup.
Likely causes
- Large catalog databases.
- Corrupt or outdated search index.
- Insufficient disk I/O performance.
Fixes
- Rebuild search index:
- Use the rebuild or reindex function in pCon.catalog.
- Limit indexed content:
- Exclude rarely used catalogs from indexing to improve performance.
- Ensure fast storage:
- Use SSDs for catalog storage if possible.
- Regular maintenance:
- Schedule off‑hours indexing to avoid impacting workflow.
10. When to Contact Support
Contact pCon support or your vendor when:
- You cannot resolve crashes or corrupt installations with the above steps.
- License activation or account issues persist.
- There are suspected bugs in pCon.catalog functionality.
- You need vendor‑specific catalog corrections or updated product files.
When contacting support, provide:
- AutoCAD version and bitness, pCon.catalog version.
- A copy of the problematic catalog file or a small sample that reproduces the issue.
- Crash logs, installer logs, and a brief reproduction sequence.
Prevention checklist (quick)
- Keep AutoCAD, pCon.catalog, and GPU drivers updated.
- Match units and export settings before importing.
- Use XREFs and LOD settings to manage file size.
- Regularly clear caches and rebuild indexes.
- Keep licenses and authentication details current.
If you want, I can: provide step‑by‑step commands for a specific issue (install error, unit mismatch, crash logs) or draft an email to pCon support including logs and system details. Which would you like?
Leave a Reply