IFI Loader Problems

[lasindi]

We are having troubles with loading HEX files. When I try to open one that I've compiled, I get an error message that comes up that says, "Run-time error '76': Path not found." I've heard that the directory address of the HEX file cannot exceed a certain number of characters. I moved it to a folder directly on the hard drive and I still get these errors. I'm not sure if the connection has anything to with "path" errors, but we are using a USB-to-serial adapter because the laptop that we're using doesn't have any serial ports. We tried to see if we could open a connection with the robot using a different program and it worked. The loader, however, says that it is "Not Connected". Does anyone know how to solve this?

[Mike Betts]

Originally Posted by lasindi

We tried to see if we could open a connection with the robot using a different program and it worked. The loader, however, says that it is "Not Connected". Does anyone know how to solve this?

We use the Bafo USB to serial converter suggested by Dr. Johnson (do a search on "Bafo") and have had no problems with any PC connecting to last year's or this year's controller.

One thing to check is which COM port your USB converter is connected to (it can be different each time it is unplugged/plugged into the USB, depending on other things being used in your system.

As far as the path not found statement, I don't have a clue. I'd try reinstalling the USB driver as I am not sure if the IFI loader is generating the message...

Good luck.

[gnormhurst]

That error sounds familiar. I got it just last night after installing all the tools on a new laptop. Windows 2K SP4. It was an "Argh" moment.


I'm not sure what I did to solve it. I think my solution was to uninstall (using control panel/AddRemove Programs) and reinstall IFI loader. I think I chose to install version 1.0.6 instead of 1.0.7, just to see if that made a difference. Things worked well after that -- I don't know what exactly fixed it.

Hope that helps.

-Norm

[Greg Ross]

I think I might have seen this message when my .hex file was located too deep in the directory tree. (i.e. the file path was more than 64 characters.) If this might be your problem, you could try moving your project directory closer to the root.

[Ryan M.]

Some suggestions:
1. Try recompiling the file and moving it to the root of the drive.
2. Reinstall the software, it's kind of tempermental.
3. Find a computer with a 9-pin serial port. I don't see why this would cause a path error, but you never know. Might be a badly written error message.

Hope you get it working!

[nevrgonastopme0]

yeah, we had this problem too, I also dont remember what we did to fix it, but I think I uninstalled it, moved the code to a folder right on the root drive *C:\* and set up the output in the build options to go to that folder. it worked, I might have done something else too that i dont remember, but after i did that, it wouldnt find the COM port.... I know for a FACT that the problem your having dosent have anything to do with the COM settings, it can occur later, but thats not the case right now, its something with the compilleing...also make sure your saying build-all not just make, dont know if that would change it, but it never hurts to try...


Kris

[Mike Betts]

Originally Posted by nevrgonastopme0

I know for a FACT that the problem your having dosent have anything to do with the COM settings,

Kris,

It sounded like a two problem problem. Lasindi indicted "no connection" AND the path error. The two may be independent...

Regards,