My set up is:
USB cable using virtual serial port.
Until yesterday, this was working. using memory map UK national parks section, i could download routes tracks etc to GPS in seconds. Then I purchased additional memory maps, loaded them onto the PC ...it has failed to connect to GPS since that moment on. Re-loaded the software, drivers, checked all connections, licence numbers, port settings, rebooted everything several times over. Complete failure to connect to the GPS. At wits end...can anyone help ? I'd be eternally grateful as I'm stuck here with a whole load of disfunctional expensive kit. many thanks
An expert who has achieved level 3 by getting 1000 points
An expert that got 10 achievements.
An expert that got 5 achievements.
An expert who has answered 1,000 questions.
Re: Timeout 254 'Unkown Garmin' error
Was the add. memory in you alotted space or did you go over. What I would first do is delete and start over. Only if you have the orginal software. How long do you wait to get error mess? Is batt. charged all the way? Check before reloading.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Not surprised at that, don't know much about these units but from what i was able to find out they don't use a usb cable to load software they use a serial cable, and computer do not have a detection process for the serial cable, You need the cable as well as the software to load information up to or down from the unit. Quick check brought this to my attention and maybe something in here will help you.
I am using Windows 7 Ultimate 64 and the iQue did not work. There is no USB driver and as far as I know there isn't going to be one. However, I did get it working by installing Windows XP mode and the Windows Virtual Machine on my XP system. You need to check if your computer can run XP mode and there are Microsoft tools to do that. After you get XP mode installed and running, there will be a virtual XP window on your desktop. Plug the iQue in its cradle and plug it in to the USB port. Use your iQue setup CD to install the Palm desktop in XP as you normally would. At some point, you have to tell XP to attach your iQue to the USB port. Near the XP title bar, there is a USB pull-down menu. Use this to attach the device. It will ask for a driver. Just say to use the Garmin-supplied driver. Wait until this finishes successfully. Before trying a sync, open the Palm desktop and go to Hotsync/custom and change everything you can to "handheld overwrites desktop" and save this. Push the hotsync button on the cradle. If it doesn't connect, go to the USB pull-down and click attach. It should work!
Have you tried using the cable with another device just to check it's working ok.. And try a different usb port also, they can be funny that way. A Garmin rep I spoke to about this told me (off the record) to just go to my local electronics store to pick one up for app €15 as the same thing from Garmin would be about €75. So it's basically the same cable and should work. I tried it with a generic cable here in the shop and it worked in one usb port but not in the other two so a bit of trial and error is needed. All that failing I'd bring it back to the shop and ask them if there is a different type you could try, possibly you need one with a higher data transfer capability.. But try the cheaper and easier options first..
I had the same issue. I would plug it in and it would recognize the device then it would disappear.
What I did to solve the problem was to first turn on my Gamin 200w. After it was finished loading maps then I plugged in in to the usb port. My machine recognized the device without any problems. I am running Windows Vista Home Premium. Hope that helps.
If it were doing this just on the Vista machine I would say it was Vista related but since you are getting it from an xp machine as well the problem is either cable or the gps unit. You don;t say if this just started happening or ? If you can try out the cable on something else to make sure so you can eliminate it. About the only thing you can do is to make sure the port settings in the pilot are set correctly. Generally the slower the better if you are having communication problems as this makes the signal timing not as critical. Try 9600 baud to start. Make sure that the data bits are also set roght. This is the 8n1 or 7n1 thing you see. I can;t think of what the default is on the garmin but as long as both pc and garmin have speed, bits, parity, and stop but set the same they should talk.
Try to download from the unit as well as upload.Unfortunetly you can only change the speed and protocal or reset the unit. You won't be able to fix it if is a hardware thing. If you are using a USB to Serial adapter then I would say that is your problem or could be. Cheaper ones just don't work often on higher port speeds. You might want to try the gps on a pc with a actual serial port if you are using one. If it works then you should try a different brand of adapter or really slow down the speeds.
This won;t solve it unless you luck out but it should let you know where the problem is.
Try posting the problem listing your virtual port software or the laptop itself as the product, you may get many more experts taking a look.
Other than that, one thing to try would be to set it up on a machine with a serial port, and if you can get it working see what all the settings are - it may give you some clues.
I used to use C-map years ago, so probably now much different, but we often had unrecognised port problems that usually meant two or three restarts before it would pick up the port (this was without changing any settings). Maybe they cured this in the last few years, but the best answer I got back then for why it happened was bad software code in c-map, never bothered to try the later versions.
Hope this helps a bit :)