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 have also been experiencing the very frustrating "Error Code 2" issue half way thru the calibration process. Sometimes the error occurs during measurement No. 1; other times on the 2nd or 3rd measurement. I am running a MacBookPro running OSX 10.7 (Lion Server) w/ Vmware Fusion v4.1.1 and Windows XP (SP2). After experiencing over a dozen of failed attempts to calibrate, I started to tweak the Windows setup. I found out after some experimentation that the issue is not so much the Alpine Imprint S/W, but much so with the USB/Serial interface hardware. The S/W has issues with error recovery, which forces the user to close and restart the application if an exception is encountered...but if the exception can be avoided in the first hand, it runs fine! Would suggest to try the following tweaks to address the Error Code 2 issue: (1) If using Vmware Fusion, ensure that the USB/Serial is connected. On the VMWare Fusion menu, select Virtual Machine->USB & Bluetooth->Connect Future Devices USB<->Serial. Ensure this is connected first before launching the Alpine Imprint Sound Manger (v2.10) application; (2) The USB cable that comes with the calibration kit is quite long and I am not sure the shielding is that good. So try to straighten the cable out and not allow it to coil when connecting to laptop; this should reduce any potential interference and signal degenerating issues; (3) Within XP, open up Control Panel->Administrative Tools->Computer Management->Device Manager, locate under "Ports" the corresponding port that the USB<->Serial interface emulates. Usually this is USB Serial Port (COM3). Open up the Port Settings under its properties menu.Apply the following override settings: Bits per second = 921,600 (or 115,200 is fine as well)Parity=EvenFlow Control=Hardware Click "Advanced" button and override the following settings:Minimum Read Timeout (msec) = 10,000Minimum Write Timeou (msec) = 10,000 These simple override setting works like magic for me.I was able to complete all the 6 measures without a glitch.Hope this works for your setup as well. PS. For subwoofer calibration I also found useful tuning down the gain beforehand on the amplifier. On the Alpine head unit, set the Subwoofer output level to very low (close to zero). On the amp-side (I am using 3 x Pioneer PRS-D4200F) set the gain switch anti-clockwise to a voltage slightly above 2V (do not over do this). Then after the calibration has completed, set it to just below 2V (clockwise rotation) to slightly elevate the output. The remaining subwoofer gain adjustment can now be done comfortably from the head unit's subwoofer output control. Cheers,Damo
This sounds like more of a communications problem than it does a "time out" problem. I am assuming that the printer is connected to the computer via a parallel cable. If that is the case, try unplugging the cable at both ends, the reattaching it. If that does not change anything, try replacing the cable.
If that does not solve the problem, try replacing the parallel cable with a USB cable and then follow the directions below.
If by some outside chance you have the printer connected to the computer via USB cable you can do one of two things. Replace the USB cable with a parallel cable or change the printer's port settings to use the USB cable. - If you do have the printer connected via USB cable you might be able to rerun the installation software that came with the printer and it may automatically pick up on the USB set up. If not, go to Contro Panel\Printers and Faxes\ - Right click on your printer and open properties. Under properties, click on the Ports tab. Since the error message stated "error writing to LPT1, check to insure that the LPT1 block is checked. If it is, and you are using a USB cable, scroll down until you see two blocks - "USB001 Virtual printer port for USB" and "DOT4_001". Check the box beside "DOT4_001" then click on Apply and close the window. The try printing again.
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.