Either your poses are empty and don’t do anything, the ezb isn’t connected, or you have a syntax error. Look at the console debug and see if you have any errors in the script. You can run the script by pressing the start button manually to test it.

dj

the iotiny in this case is connected . the poses are working on the Auto Position page . they just dont work as init . i check the syntax .

Let's try a few things to narrow down the issue. Since your sounds (sayEZB) run during init and the IoTiny is connected-and you confirmed that your poses work correctly when triggered from the Auto Position page-it’s likely a timing/initialization order issue.

Here are some suggestions:

1. Add a Delay:
   It’s possible that when the init script runs, the Auto Position skill isn’t fully initialized. Try inserting a delay before calling your pose. For example, add a sleep() for 1-2 seconds before your control command:

   print("Running init script");
   sleep(2000); // Wait 2 seconds to allow skills to fully load
   controlCommand(Auto Position, AutoPositionAction, MyPose);
   

   Replace "MyPose" with the exact name of your action. This extra time can ensure that the Auto Position Movement Panel is ready to receive commands.

2. Double-Check Action Name and Syntax:
   Even though you’ve checked the syntax, verify that the action name in the command exactly matches the one defined in your Auto Position skill (pay close attention to spaces and capitalization). For example:

   controlCommand(Auto Position, AutoPositionAction, MyPose);
   

   If "MyPose" is the action name, it must match exactly.

3. Test the Command Manually:
   As DJ_Sures mentioned, try running the script manually using the Start button (in the debug window) after ARC loads. This helps confirm that the command works correctly when not run during the connection init.

4. Check the Debug Console:
   Look in the ARC console debug window for any errors or warnings when the init script runs. There might be feedback indicating that the Auto Position skill wasn’t ready or if there’s another issue.

5. Initialization Order in Connection Scripts:
   Since the init script is called from the connection configuration, it might run before all robot skills (like the Auto Position Movement Panel) have been fully loaded. This is often resolved by a short delay (as shown above) or by restructuring your init sequence so critical skills have completed their start-up routines.

Try these adjustments and let me know if the poses execute as expected. If you continue to have issues, feel free to share a snippet of your init script code (with the command and delay) so we can take a closer look.

@DJ@athena

okay its working . i took a new window ,saved all and it works now .

thank you bolt

Great news, Nomad_6R! I'm glad that creating a new window and saving everything resolved the issue. It sounds like it was just an initialization or workspace glitch. If you encounter anything else or have further questions about ARC, Auto Position, or any other skills, feel free to ask. Happy robotics!