FAQ/Help Page

Below are many of the issues that come up when working with and programming the IntelliBrain bot. While this is not a comprehensive list, we are doing our best to cover any problems you may encounter and provide you with solutions. If you have an issue that is not on this list, please contact us, and we will figure it out and add it to the list.



The Issues


I see red lines (in my program)...


Red lines in your program are generally a result of one of three things:


  1. The JAR file is missing
  2. The correct import statements are missing
  3. Mispelled variables in your code

Solution 1: If netbeans did not import the JAR file correctly try to import it again. You can do this by right clicking on the project and choosing properties then click on Library. On the right there should be a button that says “Jar File” click it and find the Robo JDE folder in programs. Click on the folder and then click on the file “RoboJDE.jar” then click open. Once this has been completed click “OK” in the properties window and you have now imported the JAR file.


Solution 2: You must have the imports to be able to use any of the predefined methods. A good rule of thumb is to have the following imports in every program 1) import com.ridgesoft.intellibrain.*; 2) import com.ridgesoft.io.*; 3) import com.ridgesoft.robotics.*. With these imports you will cover all the methods needed to make your robot run correctly. Make sure you also put the imports in the correct place. They always go at the very top of your code before anything else. Otherwise Netbeans and Robo JDE will not understand that the imports are to apply to all the code and you will receive an error.


Solution 3: One of the most important things to be aware of when programing is the spelling of your variables if you are not careful you can run into big problems if you do not spell the variable the same way as you did when you declared it. One thing that I do when writing code is use variable names that are easy to spell and remember 2) if I get an error about a variable that was not declared and I know I declared it earlier then i check the spelling of when i used it against the spelling of when i declared it this will help reduce the number of spelling errors you will have. Another useful aspect of the IDE is that if you put the cursor on a variable it will highlight every place that the variable occurs in the program.



A sensor isn't working right...


Sensors not working correctly often have three possible causes:

  1. The cables have come loose
  2. The batteries are getting weak
  3. The way the program is written doesn't match expectations

Solution 1: Check that the cables for the sensor are attached securely. Don't be afraid to ask an adult for help with this!


Solution 2: Replace all batteries with ones that have been fully charged. Put the used batteries into the charger so they will be ready the next time they are needed.


Solution 3: Check your code. Examine your code line by line to see if the robot is simply doing what you've told it to do, but it differs from what you actually wanted it to do. Often times this is a result of variation between sensors, robots, and how we think versus how a computer thinks.



The robot isn't going straight, even though it should be...


Several issues may keep your robot from driving in a straight line when it should be.


  1. The batteries are getting weak
  2. The program has the motors set to different speeds
  3. The tuning of the motors is off

Solution 1: Replace all batteries with ones that have been fully charged. Put the used batteries into the charger so they will be ready the next time they are needed


Solution 2: Check your program code to make sure the motor speeds are set to be the same for the robot to move in a straight line.


Solution 3: This is a little more time consuming to fix and isn't very difficult, but care and caution needs to be taken (adult supervision recommended). First you need to write a simple program that has the motors set at the same speed (probably very similar to the program you were working on when this issue came up). Then there are small screws on the back of the motors that you can make small adjustments to with your toolkit. These adjustments help tune the motor speed, and it will simply be a process of trial and error till the robot is moving straight. You will set the robot down, see which motor needs adjusting, pick it up, make a small adjustment, set it down and see what it is doing, and repeat until the robot is going in a straight line.



Robo JDE is unable to connect to robot, or unable to link/build the program...


The following are common issues that keep the robot from talking with the computer.


  1. The batteries are getting weak
  2. The serial cable/bluetooth connector are not connected properly/securely
  3. The virtual machine on the robot has been deleted

Solution 1: Replace all batteries with ones that have been fully charged. Put the used batteries into the charger so they will be ready the next time they are needed.


Solution 2: Check the connection of the serial cable or the bluetooth (whichever you are using) to make sure it is completely and securely attached.


Solution 3: In Robo JDE under tools, select reload virtual machine and follow the on screen instructions.



My friend and I are using the same sensor numbers, but our robots aren't doing the same thing...


Each robot is unique. It is very likely that there will be some small variations in the values that the sensors obtain.

  1. Same sensor values, different performance

Solution 1: Write a simple test program for the sensor in question and check the values that you are using for that particular robot. Do they make sense and fall in line with your expectations, or do you need to use different values in your code? Don't be afraid to try different sensor values in the same code!



My robot isn't working properly...


We all have times where our robot just doesn't seem to work right.

  1. The batteries are getting weak
  2. The program isn't written correctly

Solution 1: Replace all batteries with ones that have been fully charged. Put the used batteries into the charger so they will be ready the next time they are needed.


Solution 2: Check your code. Examine your code line by line to see if the robot is simply doing what you've told it to do, but it differs from what you actually wanted it to do. Often times this is a result of variation between sensors, robots, and how we think versus how a computer thinks.