Jake Troubleshooting Guide¶

This guide helps you diagnose and resolve common issues you might encounter while using Jake. Each section addresses a specific category of problems and provides step-by-step solutions.

Installation Issues¶

Jake Desktop Won't Install¶

If you're having trouble installing Jake Desktop, first verify that your system meets the minimum requirements outlined in our Getting Started Guide. Common installation issues often stem from insufficient system permissions or conflicts with existing software.

To resolve installation problems:

First, ensure you're using an administrator account on Windows. Then close all LabVIEW applications and related processes. Download a fresh copy of the installer from jki.ai and run it with administrator privileges by right-clicking and selecting "Run as Administrator."

If the installation still fails, check the Windows Event Viewer for specific error messages related to the installation. These messages can help identify the root cause of the installation problem.

LabVIEW Integration Problems¶

When Jake isn't properly integrated with LabVIEW, you might encounter issues with the QuickDrop functionality or context sharing. The most common symptom is that the Ctrl+G QuickDrop shortcut doesn't launch Jake's LabVIEW Helper.

To resolve integration issues:

First, verify that the QuickDrop plugin is correctly installed. Locate the jki-gaia.llb file in your LabVIEW Quick Drop Plugins directory (typically C:\Users\<username>\Documents\LabVIEW Data\Quick Drop Plugins). If the file isn't present, you may need to reinstall Jake Desktop.

For cases where the file exists but QuickDrop isn't working, manually copy the file to your LabVIEW's QuickDrop plugins directory: C:\Program Files\National Instruments\<labview_version>\resource\dialog\QuickDrop\plugins. Remember to use Program Files (x86) for 32-bit LabVIEW installations.

Connection Issues¶

Jake Can't Connect to LabVIEW¶

When Jake fails to establish a connection with LabVIEW, start by verifying that both Jake Desktop and LabVIEW are running with the same user account permissions. Check that your firewall settings allow Jake Desktop to communicate on your local network.

To test the connection:

Close both Jake Desktop and LabVIEW
Start LabVIEW first
Launch Jake Desktop
Open the Jake Helper through QuickDrop (Ctrl+Space, then Ctrl+G)

If the connection still fails, check the Jake Desktop logs for specific error messages. You can access these logs through the Help menu in Jake Desktop.

Intermittent Connection Losses¶

If Jake frequently loses connection to LabVIEW, this might indicate network configuration issues or resource constraints. Begin by checking your system's available memory and CPU usage. Close unnecessary applications to free up system resources.

To improve connection stability:

Configure your antivirus software to exclude Jake Desktop and its installation directory
Ensure your network firewall isn't blocking Jake's local communication
Check that your system's power settings aren't putting network adapters into power-saving mode

Block Diagram Context Not Working¶

If Jake isn't receiving block diagram context when you use the @bd marker, first verify that you have an active VI open and its block diagram is visible. The block diagram must be the active window when you request context.

To troubleshoot context sharing:

Save all modified VIs
Close and reopen the block diagram
Ensure the block diagram is the active window
Try sharing context again using the @bd marker

If problems persist, restart the Jake Helper through QuickDrop.

Front Panel Context Issues¶

When front panel context sharing (@fp) isn't working properly, ensure that your front panel is the active window and that all controls are properly loaded. Subpanel content and dynamically loaded controls might not be captured correctly in the context.

Performance Issues¶

Slow Response Times¶

If Jake is responding slowly, first check your internet connection speed and stability. Jake requires a reliable internet connection for optimal performance. Also verify that your system meets the recommended (not just minimum) requirements specified in our documentation.

To improve response times:

Clear Jake's conversation history regularly
Close unused VIs and projects
Ensure adequate system resources are available
Use specific context markers rather than sharing all context types

High Resource Usage¶

If Jake Desktop is consuming excessive system resources, start by closing unnecessary conversations and clearing your conversation history. Check that you're running the latest version of Jake Desktop, as performance improvements are regularly released.

Account and Authentication¶

When experiencing login issues, first verify that you can log into your vipm.io account through a web browser. If you've forgotten your password, use the password reset function on vipm.io before attempting to log in to Jake.

For persistent login issues:

Clear Jake Desktop's cached credentials
Restart Jake Desktop
Attempt to log in again with your vipm.io credentials
If problems persist, contact support through vipm.io

Subscription Recognition Issues¶

If Jake isn't recognizing your Pro subscription status, first verify your subscription status on vipm.io. Then sign out of Jake Desktop completely and sign back in to refresh your subscription status.

Getting Additional Help¶

If you're still experiencing issues after following these troubleshooting steps, several support options are available:

Technical Support Contact our support team through Jake Desktop or visit our support portal for assistance. Include specific error messages and steps to reproduce the issue.

Community Support Join our Discord community to connect with other users and share solutions. Many common issues have already been discussed and resolved in our community forums.

Documentation Review our User Guide and Feature Reference for detailed information about Jake's features and capabilities.

We continuously update this troubleshooting guide based on user feedback and common support requests. If you encounter an issue not covered here, please contact our support team so we can assist you and improve our documentation.