The sign is a symbol and it’s a (i) symbol, not a # number sign.

Athena is incorrect on that because she can’t see pictures. The symbol you’re talking about is a letter i in a circle. That means "information". It’s a global icon representing information.

about a year ago there was an update with ARC that allows control commands to return values and provide written description information when hovering over the option.

The (i) symbol that you’re talking about merely shows that there is information about the ControlCommand if you hover your cursor over it.

ps, i removed Athena’s incorrect responses so the conversation in this thread better aligns with the question.

hi DJ

so how can i use my poses i made ?

Click on the ControlCommand and it adds to your code editor. The video I pasted above shows that in the example.

move the mouse cursor above the ControlCommand in the cheat sheet. When the mouse cursor is over the item that you wish to use, click the mouse button.

i did that but they dont work for some reason . in the init the sound does work .

Hi Nomad_6R,

Let's narrow this down step by step. When you say "they don't work," do you mean that when you invoke your pose actions via the control command, nothing happens (i.e., the servos don’t move to the poses you defined)? Meanwhile, you mentioned that your initialization sound or similar commands are working correctly. This suggests that ARC and your project are running, but there might be an issue with how the Auto Position actions are being called.

Here are a few things to check:

1. Verify the Action Names
   Ensure that the name of your action in the Auto Position skill exactly matches the name you use in your script (including spaces and capitalization).
   For example, if your action is called "MyPose", your ControlCommand should be:

   controlCommand(Auto Position, AutoPositionAction, MyPose);
   

   Sometimes a small mismatch can prevent the action from being recognized.

2. Check the ControlCommand Syntax
   Ensure you are using the correct syntax when calling the command in your code editor.
   If you’re using JavaScript, you might have something like:

   // Example: calling an  Auto Position Action
   controlCommand("Auto Position", "AutoPositionAction", "MyPose");
   print("Attempting to execute MyPose pose");
   

   If using Python, make sure to follow the same concept while keeping variables in sync.

3. Ensure the Auto Position Skill is Active
   Double-check that the Auto Position Movement Panel (Gait) skill is properly loaded and active in your project.
   Confirm that your poses (frames and actions) are defined correctly inside its configuration.

4. Test with a Simple Control Command
   You can temporarily create a very simple action with only one or two frames (or even a test "dummy" action) to see if it triggers.
   This helps isolate whether it’s an issue with the action’s configuration or the ControlCommand itself.

5. Check for Feedback in the Cheat Sheet
   When you hover over the ControlCommand in the Cheat Sheet, you should see the information tooltip. Although the "i" symbol indicates extra info, it will not affect functionality.
   Make sure that after clicking the command, the code editor inserts it and that there’s no syntax error.

6. Inspect any Error Messages
   When you run your project, keep an eye on the ARC log/output window to see if any errors or warnings appear when you call the pose action.
   These messages may help indicate if the action isn’t found or if there’s another issue.

7. Initialization Order
   Since you mentioned that in the init the sound works, it may hint that your Auto Position skill is loaded after some initial commands fire.
   Consider adding a slight delay before calling your pose from your script to ensure all skills are fully initialized.

Could you verify these points? Also, if possible, please share a snippet of the code you’re using to trigger the pose and a quick summary of your action’s exact name. Once we have that info, we can help pinpoint what might be stopping your pose from executing as expected.

Let me know how it goes or if you have additional details!

You have code in a script that you’re calling an "init script". You’re saying the code isn’t running? Like Athena said above, is it the code or is it the script not being called?

If it’s the code, you’ll see an error in the console debug window of the script.

if it’s not being called, then call it. Init scripts are called from the connection control confit menu. There’s a script for each ezb connection.

heres a tutorial for init scripts: https://synthiam.com/Support/Get-Started/Tutorials/init-script

#athena

i wil make a video . it shows better the problem .

dj

i take a script and called init put some sounds and poses in ? the sound will play or sayezb("hello") , the posses are not excuted . i put the init in the connection window .