Help and troubleshooting

eXperiBot won’t turn on

• Charge your eXperiBot. For more information, see the section Charging the eXperiBot.

• If your eXperiBot still won’t turn on after charging, there is probably a problem with the eXperiBot’s battery. Please contact us directly.

eXperiBot does not respond to button presses and cannot be turned off

• The eXperiBot has crashed.

• Press and hold the Plus or A button and the Minus or C button on the control panel simultaneously for eight seconds to force it to turn off.

eXperiBot lights up pink after turning on and cannot connect to the app

• The eXperiBot has faulty firmware and needs to be restored.

• To do this, go to Settings via the gear button on the home page of your app. In the “Troubleshooting” section, you will find the option “Restore eXperiBot.” Select this and follow the instructions in the app.

Module is not displayed in the app

Under certain circumstances, modules connected to your eXperiBot may not be recognized correctly and displayed in the app. There can be several reasons for this. The status LED of the respective module provides further information about the cause of the problem…

Module status LED is not lit

• If the module status LED is not lit, the electrical connection to one or more modules is probably faulty.

• Disconnect all affected modules from your eXperiBot and then reconnect them.

• If the problem persists, please clean all gold contacts on your eXperiBot modules with a dry cloth.

Module Status LED is pink or red

• If the module status LED is pink or red, the firmware is likely damaged and needs to be restored.

• If the app does not offer automatic restoration after connecting the eXperiBot, you will need to do this manually. To do this, go to the settings via the gear button on the home page of your app. In the “Troubleshooting” section, you will find the option “Restore eXperiBot module.” Select this option and follow the instructions in the app.

Problem persists

• If the problem persists, there is probably a hardware error in the affected module, and it must be replaced. Please contact us directly.

Status LED of a module suddenly turns off during use

→ Module is not displayed in the app

Status LED of a module lights up or flashes red during use

→ Module is not displayed in the app

Status LED of a module lights up pink during use

→ Module is not displayed in the app

Module does not move despite a program command

• Check whether the program is actually running. You can tell if a program is running by the white or light blue status LED on the Powerbrain.

• Check your program code for possible errors. If you are using concurrent blocks, the end of the program or a new program command may stop the module’s movement before it has properly started.

• If the problem persists, there is probably a hardware defect, and the affected module must be replaced. Please contact us directly.

eXperiBot beeps three times when running a program, and the status LED on the Powerbrain briefly lights up red

• The program on the Powerbrain cannot be run.

• In the message log, you’ll find information about the error that occurred. Then check your program code for possible errors.

• Ensure that all eXperiBot modules required by the program are connected, have been recognized by the app, and have the correct LED color for the program.

• If the problem persists, your program may be too large for the eXperiBot’s memory. Try to reduce the size of your program (number of lines of Python code).

eXperiBot no longer behaves as expected when running a program

• There is a problem preventing the program from running correctly.

• Check your program code for possible errors.

• Check whether the status LED of a connected module is not lit, pink, or red. If this is the case, you can find more information in the section Module is not displayed in the app.

• If a Multisensor module is connected to the eXperiBot, there is probably a problem with it. For more information, see the section Multisensor.

• Charge your eXperiBot. For more information, see the section Charging the eXperiBot.

eXperiBot continuously plays a melody after connecting the charging cable

• The eXperiBot’s battery is severely discharged, and the eXperiBot attempts to switch itself off again immediately during charging.

• Leave the eXperiBot connected to the charging cable. After about two minutes, the melody should stop automatically.

• To avoid this problem in the future, please follow our instructions for charging the eXperiBot.

The Powerbrain control panel has different buttons than those shown in pictures and illustrations

• Newer Powerbrains have an alternative control panel with action buttons labeled “A,” “B,” and “C.” The function of the buttons is the same for all Powerbrains, regardless of their labeling.

Colors are not recognized at all or are recognized incorrectly

• Adjust the sensitivity value in the programming block where color recognition takes place.

• The sensor may not recognize the expected color of an object. Problems can arise, especially when recognizing yellow, as the object may be perceived as white or green depending on the deviation in color tone.

• Ambient light can affect color measurement. When using color measurement, avoid the influence of direct sunlight or strongly colored artificial light.

Objects are unexpectedly recognized or not recognized

• Adjust the sensitivity value in the programming block where object recognition takes place.

• Objects are detected using an infrared sensor and an infrared LED that illuminates the object to be detected. If the object to be detected reflects little infrared light, it is more difficult to detect. White objects reflect a lot of infrared light, while black objects reflect little.

• If an object is detected unexpectedly, ensure that no infrared LED from another Multisensor (possibly on another eXperiBot) or other infrared source is directed at the sensor.

Dark or light surfaces are detected unexpectedly or not detected

• Dark or light surfaces, e.g., for a line tracking algorithm, are detected using an infrared sensor and an infrared LED that illuminates the surface. Only deep black and non-shiny surfaces are detected as dark surfaces. Gray scales and colors, on the other hand, are perceived as light surfaces.

Distance value for an object in front of the Multisensor does not change

• When using the “Multisensor—Distance to object” programming block or the “Multisensor—Distance to object” eXperiBot live data source:

  • The programming block is designed to detect objects in a range of 10 to 20 cm in front of the sensor. Distances outside this range return the minimum or maximum value, respectively.

• When using the “Multisensor—Distance to object on the right/left” programming block or the “Multisensor—Distance to object (lateral)” eXperiBot live data source:

  • The programming block is designed to detect objects in a range of 0 to 6 cm in front of the sensor. Distances outside this range return the minimum or maximum value, respectively.

Multisensor status LED suddenly turns off

• The Multisensor’s status LED is turned off while a program is running and the Multisensor is taking measurements. This is because the light from the status LED can interfere with the measurement. Once the program has finished, the status LED should light up again in its regular color.

• If the status LED is still dark when no program is running, there is probably a connection problem. For more information, see the section Module is not displayed in the app.

eXperiBot does not drive straight ahead, even though the same speed has been selected for the red and blue axles

• The two motors of the motor module are not synchronized and may differ in their running speed. Even slight deviations lead to a noticeable drift to the left or right. You can correct this deviation by controlling the two axles with different speed values.

• When using the “Motor drive forward/backward” programming block, the direction of travel is automatically stabilized by the Powerbrain’s gyroscope. Therefore, there is no deviation here. Unfortunately, automatic stabilization of the direction of travel is not possible for the other programming blocks for technical reasons.

The angle achieved when turning and reversing does not match the expected angle

• The gyroscope in the Powerbrain is probably incorrectly calibrated. Calibration is performed when the program starts. Try not to touch the Powerbrain while the program is starting. If you want to start the program by pressing the Play button, try not to move the eXperiBot when pressing the button.

• If the problem persists, there is likely a hardware defect in the motor module, and it needs to be replaced. Please contact us directly.

Pivot or Twister module does not rotate to the expected angle

• Pivot and Twister modules have a protective mechanism that switches off the module if it cannot reach the target angle within a few seconds. Make sure that the Pivot or Twister module can move freely.

• If the problem persists, there is likely a hardware defect in the affected module and it must be replaced. Please contact us directly for assistance.

Gripper arms do not open or close

• The Grabber module has a protective mechanism that ensures that the gripper arms only open or close when the resistance is not too great. Make sure that they can move freely.

• If the problem persists, there is likely a hardware defect, and the affected module must be replaced. Please contact us directly.

Gripper arms regularly drop foam cubes

• Check the charge level of your eXperiBot. A low charge level can affect the gripping force of the Grabber.

• It is normal for the Grabber to be unable to grasp the foam cubes correctly in some cases. However, if the problem occurs frequently, there is likely a hardware defect, and the affected module must be replaced. Please contact us directly.

Passive components can no longer be separated from each other

• Separating passive components that have been plugged together can sometimes prove difficult. In the section Separating passive components, you will find helpful tips on how to separate components that are stuck together.

App cannot be opened in a web browser

• Please ensure that your web browser meets the app’s requirements.

App cannot be found in my device’s app store

• Please ensure that your device meets the app’s requirements.

eXperiBot cannot be connected to the app

• Please first refer to the section Connecting eXperiBot to the app.

• Please ensure that your web browser or device meets the app’s requirements.

• On some devices, technical issues may cause the connection to be interrupted when connecting an eXperiBot for the first time. Please try connecting your eXperiBot to the app again.

• There may be a problem with the eXperiBot’s firmware. To fix this, go to Settings via the gear button on the home page of your app. In the “Troubleshooting” section, you will find the option “Restore eXperiBot.” Select this and follow the instructions in the app.

• If the problem persists, there is probably a specific software issue. Please contact us directly.

eXperiBot modules are not recognized by the app

→ Module is not displayed in the app

Multimedia content cannot be loaded

• If multimedia content, such as an image, video, or assembly instructions, cannot be loaded, the animated loading indicator will not disappear, or a red warning triangle will be displayed.

• If you are working offline, please connect your device to the Internet once and restart the app.

• If the problem persists, there is probably a specific software issue. Please contact us directly.

Workspaces and projects have suddenly disappeared

• The app may no longer be able to access the working directory because it has been modified or moved outside the app.

• Please select the working directory again. To do this, go to the settings via the gear button on the start page of your app. In the “Data and files” section, you will find the option “Change working directory.” Select this option and follow the instructions in the app.

• If it is not possible to change the working directory on your device, or if the problem persists, there is probably a specific software issue. Please contact us directly.

Error messages when starting or using the app

• The app or a specific component of the app is likely in an error state.

• Please ensure that your web browser or device meets the requirements of the app.

• If you receive frequent error messages, try restoring the app. For more information, see the section Restore app.

Warning triangles on blocks in the block editor

• A warning triangle appears when there is a problem with the respective block. This can have various causes. Click on the warning triangle for more information.

• If you try to start a program that accesses modules that are not connected to your eXperiBot, the affected blocks in the block editor will be marked with a corresponding warning. This warning will disappear as soon as you change the module configuration of your eXperiBot or select a different LED color in the block.

• Blocks with the warning “This block is no longer supported!” no longer have any function and can no longer be used. Since we regularly improve the user-friendliness and functionality of blocks in the block editor, it is sometimes necessary to remove existing blocks and replace them with others. In this case, please search for an alternative in the toolbox. Please note that your program may not function correctly until the blocks that are no longer available are replaced.

Restore app

If you are experiencing issues with the app that cannot be resolved, you can try restoring it. To do this, go to Settings via the gear button on the home screen of your app. In the “Danger Zone” section, you will find the option “Restore App.” Select this option and follow the instructions in the app.

Restore app manually

If problems persist, you can also restore the app manually.

If you are using the eXperiBot Blockly app in Google Chrome or another Chromium-based web browser besides Microsoft Edge, proceed as follows:

1. Close all open windows or tabs in which eXperiBot Blockly is still open.

2. Enter the following address in the search bar of your web browser and confirm with Enter:chrome://settings/content/all?searchSubpage=experibot.com

3. Expand the “experibot.com” section.

4. Click on the trash can icon next to the “blockly.app.experibot.com” entry.

5. Restart your web browser.

If you are using eXperiBot Blockly in Microsoft Edge, proceed as follows:

1. Close all open windows or tabs in which eXperiBot Blockly is still open.

2. Enter the following address in the Edge search bar and confirm with Enter:edge://settings/privacy/cookies/AllCookies?searchSubpage=experibot

3. Open the “experibot.com” section.

4. Click on the trash can icon next to the entry “blockly.app.experibot.com”.

5. Restart Edge.

If you installed eXperiBot Blockly on a PC, tablet, or smartphone via the App Store, proceed as follows:

1. Remove eXperiBot Blockly from your device.

2. Reinstall eXperiBot Blockly.

If you installed eXperiBot Blockly on macOS via the App Store, proceed as follows:

1. Delete “eXperiBot Blockly” from the Applications folder (/Applications) in Finder.

2. In Finder, go to your user directory, then to “Library”, then to “Containers” (~/Library/Containers) and delete the “eXperiBot Blockly” folder.

3. Reinstall eXperiBot Blockly.

App cannot be opened in a web browser

• Please ensure that your web browser meets the app’s requirements.

App cannot be found in my device’s app store

• Please ensure that your device meets the app’s requirements.

eXperiBot cannot be connected to the app

• Please first refer to the section Connecting eXperiBot to the app.

• Please ensure that your web browser or device meets the app’s requirements.

• On some devices, technical issues may cause the connection to be interrupted when connecting an eXperiBot for the first time. Please try connecting your eXperiBot to the app again.

• There may be a problem with the eXperiBot’s firmware. To fix this, go to Settings via the gear button on the home page of your app. In the “Troubleshooting” section, you will find the option “Restore eXperiBot.” Select this and follow the instructions in the app.

• If the problem persists, there is probably a specific software issue. Please contact us directly.

eXperiBot modules are not recognized by the app

→ Module is not displayed in the app

Error messages when starting or using the app

• The app or a specific component of the app is likely in an error state.

• Please ensure that your web browser or device meets the requirements of the app.

• If you receive frequent error messages, try restoring the app. For more information, see the section Restore app.

Restore app

If you are experiencing issues with the app that cannot be resolved, you can try restoring it. To do this, go to Settings via the gear button on the home screen of your app. In the “Danger Zone” section, you will find the option “Restore App.” Select this option and follow the instructions in the app.

Restore app manually

If problems persist, you can also restore the app manually.

If you are using the eXperiBot Kids app in Google Chrome or another Chromium-based web browser besides Microsoft Edge, proceed as follows:

1. Close all open windows or tabs in which eXperiBot Kids is still open.

2. Enter the following address in the search bar of your web browser and confirm with Enter:chrome://settings/content/all?searchSubpage=experibot.com

3. Expand the “experibot.com” section.

4. Click on the trash can icon next to the “kids.app.experibot.com” entry.

5. Restart your web browser.

If you are using eXperiBot Kids in Microsoft Edge, proceed as follows:

1. Close all open windows or tabs in which eXperiBot Kids is still open.

2. Enter the following address in the Edge search bar and confirm with Enter:edge://settings/privacy/cookies/AllCookies?searchSubpage=experibot

3. Open the “experibot.com” section.

4. Click on the trash can icon next to the entry “kids.app.experibot.com”.

5. Restart Edge.

If you installed eXperiBot Kids on a PC, tablet, or smartphone via the App Store, proceed as follows:

1. Remove eXperiBot Kids from your device.

2. Reinstall eXperiBot Kids.

If you installed eXperiBot Kids on macOS via the App Store, proceed as follows:

1. Delete “eXperiBot Kids” from the Applications folder (/Applications) in Finder.

2. In Finder, go to your user directory, then to “Library”, then to “Containers” (~/Library/Containers) and delete the “eXperiBot Kids” folder.

3. Reinstall eXperiBot Kids.

The “eXperiBot Smart Team” and the elementary school product “Wayfinder” each have a play mat that is required to perform units.

eXperiBot veers off the path on the play mat or does not follow the programmed path

• Check your program code for possible errors.

• Check that your eXperiBot is assembled correctly and that the axles on the motor module are correctly connected to the wheels.

• Make sure that the play mat is lying flat on the floor and that there are no objects underneath it. Even small bumps in the play mat can cause the eXperiBot to no longer recognize its path correctly.

• Ensure that the play mat is not exposed to direct sunlight, as this may distort the measurements of the Multisensor. If necessary, move the play mat to a shaded area.

• If your eXperiBot still does not follow the correct path, there is probably a hardware defect. Please contact us directly.

If you are stuck or have a technical problem that is not listed here, simply send an e-mail to the eXperiBot team at experibot@cornelsen.de.

We will be happy to assist you!