We have hit a programmers worst nightmare. A cyber brick wall. No communication between the RC board and the computer. It’s worked before, but for some reason, it took a giant dump on itself. We are so frustrated right now most of us just feel like dropping the tools and going home… :mad:
We are using a very noob friendly program called RobotC. This program is used for VEX but has an option to be used for FRC instead. Any other compatible programming is like a foreign language and we have no clue how to use it. If anyone has a miracle, we will display your name and achievement in big letters on our bumpers.
Any simple walkthrough on a program that will work is also appreciated. We just don’t have anyone to tutor us right now.
Step 1: Don’t Panic.
Step 2: Search this site for “RC Hard Reset”, it involves pressing a button and attaching power. If you don’t find it, search the IFI forum site.
EDIT: Here’s the info:
With main power applied, press and hold the Reset and Prog buttons at the same time. Release only the Reset, while continuing to hold the Prog until the Battery Power LED becomes solid green. Now release the Prog button. Now press and release the Reset button.
As for Step 1: Worst is that you program it at the regional with IFI’s help. no big deal.
heyy
you can use “easyC”
there is a copy provided in the KOP
its a very simple drag and drop type program
if you decide to use it
step 1. load it onto the programming computer
step 2. go to file and go to frc competition or something to that effect
step 3. on the side, it will say user functions, or at the bottom of the left side, double click operator
step 4. Drag and drop from the rc control side menu, the type of drive u want, arcade or tank
step 5. a window will pop up and the top of it will say operator interface or something and choose which ports and the axis of ur joysticks
step 6. choose the PWM slots for the motors
step 7. u can drag another Motor operator for arms, claws, or anyother motors
im not sure wat to do if you have an autonomous, or pnuematics
srry
step 8. search the menu bars for a “build and compile or load” or something like that
and click it
then it will say it completed the HEX file. click ok
then connect the comp to the RC and Do what u regularly do to load a program
hope this helps
you can go to the help tab and find out more info
We had trouble with EasyC’s activation code. Something or another had happened and the key we got was faulty. This was the predicament that caused us to used RobotC. As we speak…err…type we are going to reinstall it and see if it has a trial period. If not, we are dead in the water.
if you really need help, you could contact me and i could work you through some basic C code…
Did you check all the stupid things? is the serial cable dead (run an ohmmeter through each pin, if the resistance is not close to 0 in one of them, you have a dead serial)? is your COM port enabled? Does the robot give feedback to other computers?
there is so much you can troubleshoot to find the source of this error… there are a lot of variables. Something tells me that if you get a new program like EasyC running, you will have the same problem.
Personally, with ship date tomorrow, we don’t have time to check for those things or go through a walkthrough. We appreciate the help 100%. We were just looking for a quick fix. As more time goes on, we may have to just pack up our robot and get it working before competition.
To add to the situation, our only programmer left. It’s just the mechanical crew here now.
We especially appreciate the helpful advice from everyone. If you are attending the Chicago regional, stop by our pit. Just look for the RoboHawks #2364 banner.
At many regionals, they try and put each rookie’s pit between two veteran teams. When you get there, ask your neighbors for help. I guarantee they will do anything they can to get you running.
Actually, they put the newest teams next to those who are the oldest at the competition. For instance, last year, we, team 2264, were the newest team at our regional and were placed right next to team 81 and 93 (I hope I got that right), the oldest teams at our regional, who were amazing at helping us get a working robot past inspection.
RobotC uses a bootloader/firmware which is resident in the user code. If you download with the IFI loader or do the hard reset procedure, that bootloader is erased.
I think I know what’s wrong! While you are supposed to set the RC into Program mode when downloading the firmware, you do not do it when you’re downloading user code. I’m very much used to the IFI Loader way of doing things, so this threw me for a loop at first too. Just power up the RC, send the code, and tell us how it goes.
