Hi Nomad_6R,

I'm Athena, and I'm here to help you troubleshoot these issues with your ARC project when using the EZ-B IoTiny.

Below are some ideas to help resolve both problems:

1. Delay When Disconnecting the Controller

Firmware/ARC Version Check:
Ensure you’re running the latest version of ARC (and that your EZB Firmware is up-to-date). Sometimes the disconnect delay can result from a minor firmware or ARC update.
You can verify your firmware version on the EZ-B IoTiny support page: EZ-B IoTiny Support.

Controller/Connection Diagnostic Skill:
Since your project uses the Connection Diagnostic skill, try running it and checking for any recorded warnings or errors.
The disconnect delay may be due to pending communication events or scripts that take a moment to wrap up.

Script/Control Behavior:
Some commands or active scripts might block immediate disconnect. For example, if a control (like Debug) is actively logging messages or waiting on a sensor read, the process might seem delayed.
Try temporarily disabling some background scripts to see if the disconnect becomes more responsive.

Testing & Logging:
You might add extra logging via your Debug skill right before disconnecting to determine if there’s a waiting call (such as a slow response in the communication channel).
This additional feedback might indicate if the issue is on the ARC side or the EZ-B reaction to the disconnect command.

2. Question Mark in the Script Cheat Sheet Tab

Script Parsing Issue:
The question mark you’re seeing in the Cheat Sheet tab is likely an indicator that ARC isn’t recognizing a specific command or variable reference from your script. This could be due to a change in the expected syntax or a mismatch between the robot skill’s command list and the script.
Verify that all control names and command parameters in your script match the expected names. In some cases, a renamed or missing robot skill command can result in that ?.

Reinitialize or Refresh the Cheat Sheet:
Try closing and reopening the Cheat Sheet pane (or restarting ARC) to see if the missing command flag clears. Sometimes the Cheat Sheet can become momentarily out of sync with the loaded skills.

Script Language & Syntax:
Since ARC supports JavaScript (or Python), ensure that you’re not inadvertently using quotes around port constants or other predefined constants (e.g., d0, v2) since these should remain unquoted.

Skill Updates & Known Issues:
There have been occasional reports where changes in ARC’s latest build affected the dynamic command lookup. If your script command is new or from an updated skill, check the respective skill page for updated instructions (e.g., Connection Diagnostic Skill or Debug Skill).

Test in a New Project:
As a quick test, try creating a small new project with only the affected script and the necessary skills. This helps determine if the issue is project-specific or a broader issue with the ARC version.

Next Steps & Follow-Up

Please check these items and let me know if: - The disconnect delay persists after verifying firmware and disabling nonessential scripts.
- The Cheat Sheet question mark appears in every new control or only in that one script.
- Any specific command line in your script seems to trigger the issue.

Your additional observations can help determine if we need to adjust your script commands further or if a patch is on its way in ARC. I’m here to help you explore the full potential of ARC, so feel free to ask for clarification or further details!

Happy building, Athena

For more detailed updates and additional support, you can always visit our Synthiam Support Home.

@athena

the connection problem is solved . seems when i connect bolt iotiny and ezbv4 rapid then the errors is there . but when i connect one by one it works perfect .

for the scripts i notest all scripts are not reconized .

Hi Nomad_6R,

I'm glad to hear the connection issue was resolved when you connected the controllers one at a time. As for the scripting problem where it appears that all scripts are not recognized, here are a few suggestions and questions to help further diagnose and resolve the issue:

1. Verify Script Syntax and Commands

• Check for Naming Issues:
  Ensure that all control names, port constants, and robot skill commands in your scripts are correct and match what ARC expects. Remember that port constants (e.g., d0, v2) should be unquoted.

• Refresh the Cheat Sheet:
  Sometimes the Cheat Sheet pane may not update immediately. Try closing and reopening it or restarting ARC completely to reinitialize the command lookup. This refresh can often resolve situations where commands appear as unrecognized (often indicated by a ?).

• Script Editor Verification:
  Open your script editor and check if the intellisense is correctly showing available commands. If it isn’t, verify that you are using the intended scripting language (JavaScript or Python) and that you haven’t inadvertently changed settings that might affect Auto-Completion.

2. Multiple Controllers Impact

• Potential Naming Conflicts:
  Since you mentioned you are connecting both a Bolt IoTiny and an EZBv4 rapid in quick succession, there might be a naming or port conflict that causes some commands not to register correctly. When both controllers are connected, ARC might be retrieving commands from one instance and not distinguishing them clearly if they share similar capabilities.

• Sequential Connection as a Test:
  Since connecting one by one works perfectly, you might try connecting them sequentially (allowing a few seconds between connections) to see if that improves the reliability of script parsing. In projects with multiple controllers, ensure each controller’s robot skills are uniquely named or configured to avoid overlap in the global command list.

3. Check for ARC Version Updates or Known Issues

• Latest Build Considerations:
  Occasionally with the latest ARC builds, there might be temporary issues with the dynamic command lookup that affects the Cheat Sheet and script recognition. Check the Synthiam Support page (https://synthiam.com/Support) or the release notes to see if any similar issues have been reported and if a patch is available.

• Skill Update Status:
  Confirm that the robot skills (such as Connection Diagnostic and Debug) are up-to-date. Sometimes, skills may require an update to be fully compatible with the ARC version when multiple controllers are in use.

4. Further Troubleshooting Steps

• Isolate the Problem:
  Create a small test project in ARC with only one controller (and the minimal script) to verify that the commands register correctly. Then add the second controller and monitor when the script commands become unrecognized. This can help pinpoint if the issue is related to the number of connected controllers.

• Review the Debug Output:
  Use the Debug skill to log any errors or warnings during the script initialization. The error messages might point to the specific lines or commands that are failing to register.

Follow-Up Questions

• Are there specific commands in your script that are not being recognized, or is it the entire script?
• Do you see any error messages (in the Debug output) when you connect both controllers?
• Have you tried testing with the latest ARC version and verifying that all your robot skills are updated?

Your observations on these points can help determine if we need to adjust your script commands further or if a patch/update to ARC is needed when multiple controllers are active.

Feel free to provide additional details or ask more questions so we can further narrow down the issue. I'm here to help you get the most out of your ARC project!

Happy building,
Athena

For more information, check out our Synthiam Support Home at:
https://synthiam.com/Support/

@athena

i try a new page ,the error stay desame . i also notest i cant upload in the cloud .

Hi Nomad_6R,

Thanks for the update. It sounds like even on a new page the error remains, and you’re also unable to upload to the cloud. Let’s work through some troubleshooting steps:

1. Check Cloud Connectivity and Sign-In

• Verify Your Connection: Ensure that your internet connection is stable. Sometimes a weak or unstable connection may prevent cloud uploads.
• Account Status: Double-check that you are signed in to your Synthiam account within ARC. Sometimes a failed sign-in or expired session can block cloud access.
• Firewall/Antivirus: Ensure that your firewall or antivirus isn’t blocking ARC from communicating with the Synthiam cloud. You might try temporarily disabling them or adding ARC as an exception.

2. Test with a Simplified Setup

• Use One Controller: Since you’ve noticed that multiple controllers (Bolt IoTiny and EZBv4 Rapid) can sometimes complicate things, try running ARC with just one controller connected and then attempt the cloud upload.
• New Project/Page: If you haven’t already, create a very simple project (maybe just an empty page) with one controller and try the upload process again. This helps isolate whether the issue is related to your current project configuration or a broader connectivity issue.

3. ARC Version and Skill Updates

• Latest Build: Confirm you are running the latest version of ARC. Sometimes build updates address issues with cloud connectivity.
• Skill Updates: Ensure that all your skills (especially those that might interact with the cloud or remote scripting) are updated to the latest versions. A conflict in versions might affect functionality.

4. Review Error Messages and Logs

• Debug Output: Since you have the Debug skill set up, review the output for any specific error messages when you try to upload. This might indicate if the problem is with authentication, networking, or a script-related conflict.
• Detailed Error Info: If you see any error messages or codes, please share them. Even a fragment of an error can help pinpoint the exact issue.

Follow-Up Questions

1. Are you able to access other online features in ARC (for example, downloading updates or accessing online help)?
2. Does this issue occur consistently when both controllers are connected, or does it happen even with only one connected?
3. Have you tried signing out and back in to your Synthiam account to reset your cloud connection?

Please give these steps a try and let me know what you observe. I'm here to help narrow down the issue further and ensure you can get your project uploading to the cloud reliably.

Happy building,
Athena

For more details, visit our Synthiam Support Home.

@athena

is this normal ? bolt controllers are disconnected from ARC but i can stil read the temp and batt voltage ?

an idea . is it possible to ad a checkbox to choose all on the merge page ?

Hi Nomad_6R,

Let's break down your two questions:

1. Still Reading Temp and Batt Voltage When Bolt is Disconnected

It’s not uncommon under certain circumstances to still see the last known values for temperature and battery voltage even after the Bolt controller is disconnected. Here are a couple of points that might explain this behavior:

• Cached Data: ARC maintains global variables for sensor readings. When a controller disconnects, those values might not immediately clear but instead remain as the last data received. This can give the appearance that the sensor is still active.

• Polling Behavior: In some scenarios, even if the physical connection is interrupted, ARC may still poll for data from a controller that was recently connected. If the controller reconnects or if its data remains in ARC’s global variable storage, you might still see those readings.

If you’d like to ensure you have a reliable check for whether the Bolt is currently connected, you could script an additional verification-such as checking a connection status variable or flag-so that you know whether to trust the sensor readings.

2. Checkbox to Choose All on the Merge Page

Regarding your idea of adding a checkbox to choose all on the merge page:

• Current Functionality: At the moment, the merge page does not offer an all select checkbox. You currently have to select items individually.

If you have further questions or need additional help with scripting or setup, feel free to reach out. I'm here to help you get the optimal experience with your ARC project!

Happy building,
Athena

For additional support and details, check out our Synthiam Support Home at:
https://synthiam.com/Support/

@athena

it doesn listed in the refrech page . there are no scripts there . i puched the refrech button . no change .

Hi Nomad_6R,

Let's dig a bit deeper into the issue with the refresh page and missing scripts.

Clarifying the Issue

When you mention, "it doesn listed in the refresh page. there are no scripts there," are you referring to the Cheat Sheet tab that normally displays the available script commands for the current control? Or is it another page (like a merge page) that should list scripts?

Troubleshooting Steps

1. Verify the Current View:

   • If this is the Cheat Sheet within a specific control’s scripting area, confirm you’ve selected a control with script references (for example, a control that supports ControlCommand() for other skills).
   • Sometimes if the control hasn’t been fully initialized or if there are no commands available (perhaps if a specific device isn’t connected or loaded), the Cheat Sheet may appear empty.

2. Refresh Process:

   • You mentioned having pressed the refresh button on that page. If the page isn’t updating, try closing and then reopening the control’s configuration or even restarting ARC.
   • Occasionally, a restart of ARC can force the script commands to repopulate, especially if there was a temporary communication issue.

3. Review Global Variables or Cache:

   • Some settings or cached items might be affecting what is shown. Check if any global variable tied to your project might be interfering with the list.

4. Project Context:

   • Open a new project/page that uses a default control with known scripting support (for example, the Auto Position control) and see if the Cheat Sheet then lists the available commands.
   • This can help narrow down whether it’s a project-specific issue or a broader one.

5. Version Check:

   • Confirm you’re using the latest ARC version. The issue might be a known bug addressed in a newer build.
   • Check our release notes on Synthiam’s website for any similar reported issues.

Follow-Up Questions

• Could you specify which page you’re referring to? Is it the Cheat Sheet within a scripting control or another page (like the merge page you mentioned earlier)?
• Do you see any error messages or does the output panel show any warnings when you press the refresh button?
• Have you tried accessing the same page on a different computer or after restarting ARC?

Let me know what you find after trying these steps. We can then work further on isolating if it’s a caching issue, a control initialization matter, or possibly a bug that we need to document more closely.

Looking forward to your feedback and happy building!

-Athena
For more details, visit our Synthiam Support Home

@athena

its the refrech button on the global variables as seen in the picture post #8 .

i reopen and closed ARC many times , no luck there .

tested a new project , also no luck there .

i try using one controller , same no luck .

i also notest when reopen the movement settings DELAY  goes to 3 insteadt of the normal 25 .

@athena

i found one incorrect script .how do i get that one deleted ?

Hi Nomad_6R,

If you’ve identified an incorrect script within ARC and want to remove it, you can clear or delete the script text from its respective control. Here’s how to do that:

1. Locate the Control:
   Identify which robot skill (control) is using the script that’s causing the issue.
   For example, if it’s a movement or camera control script, open that control’s configuration.

2. Open the Configuration Menu:
   Click the gear (kebab) icon for that control to open its configuration dialog.
   Navigate to the tab where the script is placed; this is often the Script tab or whichever tab holds the custom code.

3. Clear the Incorrect Script:
   In the script editor, highlight the text that represents the incorrect script.
   Delete the text so that the field is empty or replace it with the correct code.
   If you prefer to reset to the default script (if available), look for an option like Reset to Default in the configuration menu.

4. Save and Refresh:
   After clearing the code, ensure you click OK or Save to apply the changes.
   You can then press the refresh button (if necessary) to refresh the global variables or the Cheat Sheet.

5. Verify the Change:
   Reopen the global variables or the Cheat Sheet to check that the incorrect script no longer appears.
   Test the control to ensure it’s functioning as expected without the erroneous script.

If you still see issues after clearing the script (for example, if the Cheat Sheet still shows a problematic command), it might help to restart ARC after saving the changes.

Let me know if this helps or if you need further assistance! Happy building!

@athena

it was indeed a script reading problem due to myself ? if you see picture #11 i was assuming when making a script start and a script stop , bolt script should be at same place underneeth eachother .but thats not the case . one script start is ontop and script stop is below , there was my confusing .

thank you @athena

Hi Nomad_6R,

You're very welcome-I'm glad you were able to pinpoint the issue yourself!

The way ARC organizes scripts (where the Script Start ends up at the top and the Script Stop is below) is by design, though I understand it can be a bit confusing at first if you expected them to appear consecutively. It sounds like this layout was the source of the misunderstanding.

If you have any more questions about script ordering or anything else in ARC, feel free to ask. I'm here to help!

Happy building,

Athena

For additional information on scripting in ARC, you can check our support page at:
ARC Scripting Support