ARC Pro

Upgrade to ARC Pro

Stay on the cutting edge of robotics with ARC Pro, guaranteeing that your robot is always ahead of the game.

PRO
Canada
#1  

Hi there Nomad_6R,

This issue is often due to the way ARC scans and initializes your custom motions at startup. Here are some steps you can follow to help resolve the issue:

  1. Confirm Motion Naming & Declaration
    Make sure that each motion or script function is declared properly. ARC scans for functions with specific naming conventions. For example, if you’re creating a motion, consider naming your function with a prefix (such as "Motion" or another standard that matches your use case). Verify that there are no syntax errors that might prevent the motion from being registered.

  2. Save & Reload the Project

    • After adding your motions, be sure to save your project.
    • Then, close and restart ARC so that the initialization routine can rescan your scripts. This often refreshes the Cheat Sheet’s list of available motions.
  3. Check the Initialization Order
    When ARC starts up, it goes through an initialization sequence-if your motions are defined in a script that isn’t loaded at the proper time, they may not be picked up.

    • Double-check that your motion scripts are placed in the correct location (i.e., within the project’s main script area or a robot skill panel from the kebab menu) and that they are enabled.
  4. Review the Motion Creation Process
    If you’re creating custom motions as part of a robot skill, ensure you’ve followed the correct steps. You can refer to our detailed guide on creating a robot skill here:
    Create a Robot Skill.

  5. Refresh the Cheat Sheet
    Sometimes the Cheat Sheet doesn’t update automatically. Look for a "Refresh" or similar button in the Cheat Sheet tab, or simply restarting ARC should force an update.

  6. Check for Errors
    After initialization, open the ARC Console (or a debugging area) to see if any errors indicate why your motions might not have loaded. Fixing any reported issues could restore your scripts/motions in the Cheat Sheet.

Have you confirmed that your scripts follow the proper structure and are saved correctly before starting ARC? If you still experience issues, let me know more details about how you’re defining your motions, and we can take a closer look.

Let me know if these steps help or if you have any further questions!


I am a customer support GPT-powered AI and still learning. If you have doubts about my response, please use the support documentation to verify my answer.
PRO
Belgium
#2  

@athena

can you defining motions ? i dont use a INIT script .

PRO
Canada
#3  

Let's take a look at how you can define motions even if you're not using an Init script.

Below are some tips and an example to help you get your custom motions recognized in ARC:

  1. Naming Your Motion Functions
    ARC scans your scripts for functions with specific naming conventions. A common practice is to prefix your motion functions with something like "Motion" (or a specific prefix you choose) so that ARC can identify them as a motion. For example, if you're creating a walking motion, you might name your function "Motion_Walk".

  2. Where to Place Your Functions
    If you’re not using a dedicated Init script, you can add your motion functions to a separate script control (or directly in one of your robot skill panels) that is loaded when the project starts. Make sure this script control is set up to run at startup. This way, ARC will scan and initialize your motions properly.

  3. Example in JavaScript
    You can define a motion function using JavaScript directly in the ARC code editor. For example, here’s a basic motion function:

    // Define a motion called Motion_Walk
    function Motion_Walk() {
        // Example: set a global variable to indicate we're moving forward.
        setVar("$Direction", "Forward");
    
        // Add any other moving logic here,
        // for example, commanding servo/digital outputs to make your robot walk.
        print("Executing Walk Motion");
    
        // Use the ARC built-in sleep if needed:
        sleep(1000);  // pause for 1000ms
    
        // Reset or update variables after the motion:
        setVar("$Direction", "Stopped");
        print("Walk Motion Complete");
    }
    

    In this example, once ARC loads the script, it should scan for your function (Motion_Walk) and list it in the Cheat Sheet.

  4. Ensure the Script is Executed at Startup
    Since you aren’t using an Init script, double-check that whichever panel or control you’re placing these functions in is set to load immediately when you open your project. This can be done by checking the settings in the kebab menu for that control and enabling the "AutoStart" option if available.

  5. Refresh ARC or the Cheat Sheet
    Sometimes the Cheat Sheet might not update instantly. Once you've confirmed your function’s placement and naming, try saving your project and restarting ARC to force a refresh of the initialization sequence.

Do these steps help clarify how to define and initialize motions without using an Init script? Let me know if you have any follow-up questions or run into any issues!


I am a customer support GPT-powered AI and still learning. If you have doubts about my response, please use the support documentation to verify my answer.
PRO
Belgium
#4  

#athena

i use only ez scipts and auto positions . is this possible ?

PRO
Canada
#5  

Yes, it’s absolutely possible to work solely with EZ-Scripts and the Auto Position skill without using an Init script. However, there are a few important points to keep in mind:

  • Script Placement and Initialization:
    Make sure your EZ-Scripts (where you've defined motions or custom functions) are placed in a script control that executes when the project loads. If the script doesn’t auto-run, then ARC won’t scan and register those functions to appear in the Cheat Sheet.

  • Naming Conventions:
    ARC looks for new functions based on a naming pattern. For example, naming your custom motion functions with a prefix like Motion_ can help ARC identify them. Even when using just EZ-Scripts, a consistent naming style can improve recognition.

  • Auto Position Motions:
    When you create Auto Position frames and actions, those motions are managed by the Auto Position skill itself. They are not always "visible" in the Cheat Sheet since the Cheat Sheet mainly lists ControlCommand() functions and EZ-Script defined functions that are registered during ARC’s initialization process.

  • Cheat Sheet Updates:
    If you’re adding new EZ-Script motions after the project has started, you might need to reload the project (or restart ARC) to trigger a full initialization and update the Cheat Sheet list.

In summary, you can definitely use only EZ-Scripts and Auto Position. Just ensure that your scripts are set to start automatically at project launch and that you follow a consistent naming convention so ARC can detect your custom functions. This way, even without an Init script, your motions and custom functions should eventually reflect in the Cheat Sheet or be available for use in your project.

Does this help clarify your setup? Feel free to ask any additional questions or provide more details about your configuration if you still face issues!


I am a customer support GPT-powered AI and still learning. If you have doubts about my response, please use the support documentation to verify my answer.
PRO
Belgium
#6  

@athena

how do i update the sheat cheet ? the refrech button doesn work .

PRO
Canada
#7  

Below are a few steps you can try if the Cheat Sheet refresh button isn’t updating your motions or scripts:

  • Save Your Project:
    Before attempting to refresh, make sure you save any changes to your project so that ARC has the latest version of your EZ-Scripts and Auto Positions.

  • Restart ARC:
    Sometimes a complete restart is the easiest way to force ARC to rescan and update the Cheat Sheet. Exit ARC and then reopen your project. This triggers the full initialization process, which should capture your custom motions.

  • Check Script Locations & AutoStart:
    Confirm that the EZ-Scripts containing your motions are placed in a control that runs automatically at startup. You can verify this in the kebab menu for that control. If your script control isn’t set to AutoStart, ARC might not run it during initialization.

  • Verify the Naming Conventions:
    Ensure your motion functions are named consistently (for example, using a prefix like Motion_). ARC scans for functions based on naming patterns. Even if you’re only using EZ-Scripts and Auto Positions, proper naming can help ARC identify and list them.

  • Look for Script Errors:
    If there are any errors in your scripts, it can interfere with the initialization process. Open the ARC Console to check for any error messages. Fixing these should allow ARC to successfully scan your motions.

Have you had a chance to check your script control settings and restart ARC after saving? Let me know if these steps help or if you need further assistance!


I am a customer support GPT-powered AI and still learning. If you have doubts about my response, please use the support documentation to verify my answer.
PRO
Belgium
#8   — Edited

#athena

i save all my projects on my pc and in the cloud . restart doesn help . i use only original ARC . all my projects have same problem . "Verify the Naming Conventions" do you have an excample ?