Easy C, loader problem
 

After we download code from EasyC to the robot controller we have to press reset for the feedback LEDs to go back to green. The Program State LED remains orange and the RC Mode LED remains red. They are all blinking regularly. Is our code getting properly downloaded onto the robot controller?

Re: Easy C, loader problem
 

What happens if you start a new competition template, and download that into the controller? Don't add anything to the template code and just download it.

What happens then?

Re: Easy C, loader problem
 

Does the program LED flicker when the software says the program is downloading?

Re: Easy C, loader problem
 

We tried downloading a blank template and the same thing happened. The program LED flickers when the program is downloading. However, when the program should be done downloading it doesn't change color and continues to flicker.

Re: Easy C, loader problem
 

Can you try the IFI loader and see if you get the same results? You can look at the location of the .hex file that the EasyC loader is trying to download and download that file with the IFI Loader. That will tell help isolate the problem. Make sure that you close the EasyC loader when using the IFI loader to make sure there are no serial port conflicts.

Re: Easy C, loader problem
 

What year is your controller from? This may happen with the 2004 Controller, but shouldn't with the newer 2005, or 2006 controllers.

Re: Easy C, loader problem
 

It is the 2006 controller. Would reinstalling the firmware help? If so, where could I get it?

Re: Easy C, loader problem
 

You can get the Master Code here:
http://www.ifirobotics.com/rc.shtml

Scroll down to the bottom of the page.

If that doesn't fix it, call Ifirobotics SOON. Sounds like a problem to me.
If this is the NEW 2006 controller...

Re: Easy C, loader problem
 

If, after replacing the master code, you still have problems there are a few other remedies to keep in mind. BTW, you can replace the master code directly from the intelitek loader, by selecting options, and download master code from the loader menu.

I am going to assume that the code you are downloading to the controller works properly after you reset it; I see no reason why it shouldn't. Please let us know if the code does not execute after a reset.

It could be that the serial port you are using is not working 100% correctly. It is entirely possible that your code is downloading at a slightly different speed than it should be, and as a result the controller misses the last bit of information that signs off, and tells the controller that the download is complete. This would probably happen more frequently with laptop computers, which have notoriously finicky com ports. If this really becomes a problem for you, I would suggest switching computers to a desktop system, and trying a different serial cable.

Re: Easy C, loader problem
 

just wanted to let folks know that we turned on Easy C for the first time tonight and experienced the same problem with loader as described here.

(it has been working with the regular IFI loader, although there are sometimes that it needs to be asked to download several times).

After download,
Program light blinks on RC
Code error light on OI

Reset on the RC sometimes gets things working, but plenty of things haven't been working (like Arcade block using pwm 13), so blinking lights create suspicion.

Re: Easy C, loader problem
 

You folks that are having download problems...

Are you using a USB to RS232 convertor?

I hope not....

Re: Easy C, loader problem
 

I've used a usb convertor to download code to the bot a good dozen times with easyc, and have yet to experience problems. Good luck to you all, though.

Re: Easy C, loader problem
 

Not all USB convertors are created equal. Becareful using them. Use a "real" serial port when in doubt.

Re: Easy C, loader problem
 

PWM ports 13-16 should not be used with EasyC. Those ports are controlled exclusively by the user processer (i.e. the PWM pulse widths are timed by the user processor) and are not compatible with programs using interrupts heavily.

The problem is that when the IFI function Generate_PWMs is called to generate the values for 13-16 it disables interrupts for about a millisecond. When this happens, any sensors like encoders, the camera, and timers, start loosing data and missing counts. In a non-interrupt environment, there is little problem with doing this, but when our robots have fast devices like the camera which receives 11500 bytes/sec (and without hardware buffers) data will be lost.

BTW, you can use one of those for camera power to free up another port is you aren't already doing that.

You also implied that other things aren't working... please post what you're seeing so that we might be able to help or fix them.