Unknown Device ID(0)

[DavidGitz]

Hi, we're getting this error on the IFI Loader with a laptop connected with a usb-serial adapter. It works fine when connected directly to the camera, hyperterminal and the labview application work fine. When connected to the RC though it gets this error when trying to connect. Any ideas?

[Mark McLeod]

That generic error simply means the Loader isn't communicating with the device.

It can happen when the wrong COM port is chosen in IFI_Loader, but also when the serial connection is bad.
Check any cable or connection that's different from when you connect to the camera, and double check the IFI_Loader selected COM port and port settings. Just run a quick test through all the COM ports IFI_Loader offers up.

[DavidGitz]

I think if you pick the wrong COM port it says "Can't Connect" or something like that. But COM1 is selected. When I switch from the camera to the RC board, the only thing that I change is to install the TTL chip.

[Mark McLeod]

Sounds like the only change is your laptop application (IFI_Loader), and you just unplugged the serial cable from the camera and reattached the serial connector to the RC Program port. Concentrate on what changed.

A wrong COM port in IFI_Loader under certain circumstances will also return Unknown Device id (0).
USB-serial adaptors on laptops usually default to COM3 or COM4.
It doesn't hurt to quickly run through the ports in IFI_Loader.

The TTL converter isn't in the communication path, so it won't affect connecting the laptop to the RC.

[DavidGitz]

Ok I'll check that out Mark, thanks!

[EHaskins]

Click Options>Controller Verification, and post everything the status bar says.

EDIT: I've had a similar issue when I've programmed the EDU or Vex controllers from IFI Loader. Usually if I do a controller verification it solves the problem.

[DavidGitz]

Originally Posted by Mark McLeod

A wrong COM port in IFI_Loader under certain circumstances will also return Unknown Device id (0).

Thanks Mark you were exactly right, I had the wrong COM port. It works great now, thanks!

[paulcd2000]

hi, i'm having the same problem, however, i know the usb-serial adapter is in the right port, i've run controller verification. what else could it be?

[Mark McLeod]

Originally Posted by paulcd2000

hi, i'm having the same problem, however, i know the usb-serial adapter is in the right port, i've run controller verification. what else could it be?

Controller verification does not confirm you are using the correct serial port.
I know it should, but it doesn't.

What could it hurt you to step through each of the COM choices in IFI_Loader and click Download after each one?

We can go on to other possible causes, but we'll need to know you made the most obvious tests first.

[paulcd2000]

hey, me again. never did solve it. Now, i'll be ok, since i have other teammates with laptops. But this still bugs me, so i want to know how it's done.
i ran through every port, nothing runs controller verification or downloads but 3, and 3 only does controller verification. Same thing after i reinstall the driver. COntroller verification gives me:

Version|FRC|FRC|115200

i'd really appreciate it, not just for me, but for other people who have this problem
EDIT: so none of my teammates laptops work either
Any possibility besides trying to replace the cord?

[Mark McLeod]

Next I'd suspect the cable of course, then the USB Adaptor.
Do you have an alternate Adaptor you could test?

Are you able to download from any desktops?

Any nearby teams you could take a field trip to just to see if you can download to their controllers or get them to try your USB Adaptor and cable on their working machines?

[paulcd2000]

alright, so we bought a new adaptor, and that worked for a good while, until tonight, when all three laptops became unable to load code. We're wondering if there could be some kinda problem with the RC? or maybe just WIndows?

[lukevanoort]

We've ran into this issue on two out of the three laptops we've used for programming (the third has a real serial port); in all cases, the fix was reinstalling the driver. I would give that a shot.