|
Garmin GPS error & USCG 'Consumer Safety Defect' Report
I have a Garmin GPSmap 172c GPS installed and connected to a Raymarine
ST4000 autopilot. When the GPS is operating properly, it outputs a sequence of NMEA navigational data every 2 seconds. This NMEA data is used by the autopilot to steer a course to a waypoint. However, there is a problem with the Garmin software in that every day at 23:59:59 GMT, it will no longer transmit the NMEA information reliably. Sometimes the NMEA data stops entirely and other times it becomes quite erratic and is transmitted at 8 second, 20 second or some other random interval. When this happens, the autopilot displays a 'No Data' warning message and then steers the boat on the last valid course that it received. This behaviour continues until 00:08:34 GMT at which time the GPS reverts to the normal 2 second transmission interval. I also have 2 Icom radios (M502 and M802), both of which are DSC capable and have a Lat/Lon display. When they no longer receive valid NMEA position information, the Lat/Lon display flashes, alternating between the last valid position received and a series of question marks. This is another indication that the GPS error is occurring. I've been in contact with Garmin about this problem and sent them NMEA log files that showed the error occurring. (Software is available that will display the NMEA data in real time as it is being transmitted.) After reviewing these log files, Garmin's Technical Support department acknowledged that it is a problem in their software. The issue was forwarded to their Software Engineering department in November of 2006 and I was told that a fix would be provided in 2 weeks. When the 2 weeks passed, I was informed that it would be another month and when that passed, Garmin said that they didn't know when a fix would be available. I'm still waiting for them to fix the problem. When the GPS stops transmitting the NMEA navigational information, the autopilot maintains the last heading that it received. If that heading happens to be for example, a 30 degree course correction, then the vessel will be steered off course by 30 degrees until it starts receiving valid NMEA data again. I think that this represents a significant hazard and so I cannot rely on the GPS to maintain an accurate course. I have notified the U.S. Coast Guard and submitted a 'Consumer Safety Defect Report' to them. I don't know if they will pursue a recall or just some kind of advisory but this issue needs to be resolved one way or another. The Garmin GPSmap 172c is running the latest firmware version which is 2.60, dated May 9, 2006. On the Garmin download site, the firmware for the GPSmap 172, GPSmap 178 and GPSmap 178c also have that same date for their latest updates. I'm trying to find out if this error also affects these units. Is anyone else using any of these Garmin GPS units and if you are, do you get intermittent navigational errors with them? |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
Very good report, it is a very danger problem because here almost all
sailors is using the autopilots interfaced with garmin Gps. I have some friends that have reported very similar problems with the GpsMap 276C, maybe could be the same problem. I will ask them to make tests at that time... If I found something I will report here. I will make myself this test maybe next week, since it demands the test in the boat at that time. Thanks Pascal On 11 fev, 13:34, wrote: I have a Garmin GPSmap 172c GPS installed and connected to a Raymarine ST4000 autopilot. When the GPS is operating properly, it outputs a sequence of NMEA navigational data every 2 seconds. This NMEA data is used by the autopilot to steer a course to a waypoint. However, there is a problem with the Garmin software in that every day at 23:59:59 GMT, it will no longer transmit the NMEA information reliably. Sometimes the NMEA data stops entirely and other times it becomes quite erratic and is transmitted at 8 second, 20 second or some other random interval. When this happens, the autopilot displays a 'No Data' warning message and then steers the boat on the last valid course that it received. This behaviour continues until 00:08:34 GMT at which time the GPS reverts to the normal 2 second transmission interval. I also have 2 Icom radios (M502 and M802), both of which are DSC capable and have a Lat/Lon display. When they no longer receive valid NMEA position information, the Lat/Lon display flashes, alternating between the last valid position received and a series of question marks. This is another indication that the GPS error is occurring. I've been in contact with Garmin about this problem and sent them NMEA log files that showed the error occurring. (Software is available that will display the NMEA data in real time as it is being transmitted.) After reviewing these log files, Garmin's Technical Support department acknowledged that it is a problem in their software. The issue was forwarded to their Software Engineering department in November of 2006 and I was told that a fix would be provided in 2 weeks. When the 2 weeks passed, I was informed that it would be another month and when that passed, Garmin said that they didn't know when a fix would be available. I'm still waiting for them to fix the problem. When the GPS stops transmitting the NMEA navigational information, the autopilot maintains the last heading that it received. If that heading happens to be for example, a 30 degree course correction, then the vessel will be steered off course by 30 degrees until it starts receiving valid NMEA data again. I think that this represents a significant hazard and so I cannot rely on the GPS to maintain an accurate course. I have notified the U.S. Coast Guard and submitted a 'Consumer Safety Defect Report' to them. I don't know if they will pursue a recall or just some kind of advisory but this issue needs to be resolved one way or another. The Garmin GPSmap 172c is running the latest firmware version which is 2.60, dated May 9, 2006. On the Garmin download site, the firmware for the GPSmap 172, GPSmap 178 and GPSmap 178c also have that same date for their latest updates. I'm trying to find out if this error also affects these units. Is anyone else using any of these Garmin GPS units and if you are, do you get intermittent navigational errors with them? |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
Sorry, I forget to ask: you have noted if the problem is only with not
sending the NMEA messages or the gps is not geting position fix or satellites as well? That is, this could be a software problem only, if it is restricted to the NMEA. But in case it is not geting gps signals or position fix at that time only, could be that the DoD is making "deny of signal tests" in this location at that time? Thanks Pascal I have a Garmin GPSmap 172c GPS installed and connected to a Raymarine ST4000 autopilot. When the GPS is operating properly, it outputs a sequence of NMEA navigational data every 2 seconds. This NMEA data is used by the autopilot to steer a course to a waypoint. However, there is a problem with the Garmin software in that every day at 23:59:59 GMT, it will no longer transmit the NMEA information reliably. Sometimes the NMEA data stops entirely and other times it becomes quite erratic and is transmitted at 8 second, 20 second or some other random interval. When this happens, the autopilot displays a 'No Data' warning message and then steers the boat on the last valid course that it received. This behaviour continues until 00:08:34 GMT at which time the GPS reverts to the normal 2 second transmission interval. I also have 2 Icom radios (M502 and M802), both of which are DSC capable and have a Lat/Lon display. When they no longer receive valid NMEA position information, the Lat/Lon display flashes, alternating between the last valid position received and a series of question marks. This is another indication that the GPS error is occurring. I've been in contact with Garmin about this problem and sent them NMEA log files that showed the error occurring. (Software is available that will display the NMEA data in real time as it is being transmitted.) After reviewing these log files, Garmin's Technical Support department acknowledged that it is a problem in their software. The issue was forwarded to their Software Engineering department in November of 2006 and I was told that a fix would be provided in 2 weeks. When the 2 weeks passed, I was informed that it would be another month and when that passed, Garmin said that they didn't know when a fix would be available. I'm still waiting for them to fix the problem. When the GPS stops transmitting the NMEA navigational information, the autopilot maintains the last heading that it received. If that heading happens to be for example, a 30 degree course correction, then the vessel will be steered off course by 30 degrees until it starts receiving valid NMEA data again. I think that this represents a significant hazard and so I cannot rely on the GPS to maintain an accurate course. I have notified the U.S. Coast Guard and submitted a 'Consumer Safety Defect Report' to them. I don't know if they will pursue a recall or just some kind of advisory but this issue needs to be resolved one way or another. The Garmin GPSmap 172c is running the latest firmware version which is 2.60, dated May 9, 2006. On the Garmin download site, the firmware for the GPSmap 172, GPSmap 178 and GPSmap 178c also have that same date for their latest updates. I'm trying to find out if this error also affects these units. Is anyone else using any of these Garmin GPS units and if you are, do you get intermittent navigational errors with them?- Ocultar texto entre aspas - - Mostrar texto entre aspas - |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
I also have a Garmin GPS76 handheld unit on board. The last time that
the errror occurred with the Garmin 172c driving the autopilot, I turned on the handheld unit and it did not have a problem acquiring the GPS signal. The GPS76 would accurately show my position and course at the same time as the Garmin 172c was having a problem. This would indicate that there is no problem with the satellite signal. In the Garmin 172c, when the error starts to occur, the following two NMEA sentences are transmitted: $GPRMC,235959,V,,,,,,,,,,N $GPRMB,V,,,,,,,,,,,,,N The first field of the $GPRMC sentence contains the time and the second field is a 'V'. The 'V' indicates a navigational receiver warning and none of the following fields exist except for the 'N' at the end. This 'N' means that the data is not valid. In the $GPRMB sentence, the same indication occurs. If you are using a Mac computer, download A HREF="http:// www.gpsnavx.com/downloads/GPSUtility.dmg"GPSUtility/A to display the NMEA information. |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
It's not due to WAAS because the error occurs both when WAAS is on and
when WAAS is off. During normal operation, NMEA transmissions occur every 2 seconds. For those who are familiar with software programming, the interesting thing is that the error begins at 23:59:59 GMT and normal transmissions resume at 00:08:34. The time interval of 8 minutes and 32 seconds just happens to be 512 seconds. Garmin has already acknowledged that it is a software problem in their product. What we don't know is how many other Garmin GPS models have this problem. Considering the amount of time that Garmin has taken thus far and no fix has been posted, the error may be quite widespread in their product line. They have a new series of Marine GPS units that are coming out soon and maybe they are quite concerned if this defect affects those as well. |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
I agree with this. I am worrying if the problem is shown in the Map276C. Some of the new "land" units have SIRF gps engines, in place of our traditional "legacy gps Garmin receivers", and could not have the problem. If the problem is with the legacy gps software, it could affect many (if not all) marine models like mine 276C. |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
Sounds to me like the problem is in the "back end" of the software, and
would be independent of the "front end" (ie, which receiver). "Pascal" wrote in message oups.com... I agree with this. I am worrying if the problem is shown in the Map276C. Some of the new "land" units have SIRF gps engines, in place of our traditional "legacy gps Garmin receivers", and could not have the problem. If the problem is with the legacy gps software, it could affect many (if not all) marine models like mine 276C. |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
I Chuck
I understand that you are saying that the problem is with the "application software" and not with the firmware of the gps engine" ? In this case, the problem could be restricted to the 172C and not spread to others models using the same "legacy engine"? Thanks Pascal On 15 fev, 17:57, "Chuck Tribolet" wrote: Sounds to me like the problem is in the "back end" of the software, and would be independent of the "front end" (ie, which receiver). |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
Ok, I have just made a test with my 276C for about 10 minutes in the
time interval of 23:56 - 00:04 GMT (-3 here) and it do not showed any problem with the position or satellites. I could not make the NMEA test because my serial cable is hardwired in the boat, pheraps I can do it this weekend. n 15 fev, 20:38, "Pascal" wrote: I Chuck I understand that you are saying that the problem is with the "application software" and not with the firmware of the gps engine" ? In this case, the problem could be restricted to the 172C and not spread to others models using the same "legacy engine"? Thanks Pascal On 15 fev, 17:57, "Chuck Tribolet" wrote: Sounds to me like the problem is in the "back end" of the software, and would be independent of the "front end" (ie, which receiver).- Ocultar texto entre aspas - - Mostrar texto entre aspas - |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
The error does not occur on the GPS's display. In other words, your
position and course will be correct on the GPS but what it will not do is transmit this information out of the NMEA port. The only sure way to see if your 276C unit is affected is to log the NMEA output to a computer and then examine the log file. |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
I will do this test asap
|
Garmin GPS error & USCG 'Consumer Safety Defect' Report
No, the other way round, so it could be easily occur on other models.
"Pascal" wrote in message ups.com... I Chuck I understand that you are saying that the problem is with the "application software" and not with the firmware of the gps engine" ? In this case, the problem could be restricted to the 172C and not spread to others models using the same "legacy engine"? Thanks Pascal On 15 fev, 17:57, "Chuck Tribolet" wrote: Sounds to me like the problem is in the "back end" of the software, and would be independent of the "front end" (ie, which receiver). |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
BINGO .....
Yesterday I have made a test with my GpsMap 276C in my boat, using my laptop and Hyperterminal. My Map 276C was taking 12 satellites and running normal until I have made the test, and I have get exactly the same results you have with your 172C. My position here (Salvador- Bahia-Brazil) is S 12 48 W038 27 and thus GMT – 3. The test showed: a)The 276C was sending NMEA messages normally until 08:59 LCL (23:59 GMT) after that, it begin to send invalid NMEA messages like you said, and little time after, stopped sending anything, see below a small sample: $GPRMC,235959,A,1248.705,S,03827.579,W,0.0,192.2,1 80207,23.0,W,A*3A $GPRMB,A,0.04,L,AIC,BA01,1248.413,S,03827.698,W,0. 315,338.3,,V,A*3B $GPGGA,235959,1248.705,S,03827.579,W,1,12,0.8,4.2, M,-10.5,M,,*60 $GPGLL,1248.705,S,03827.579,W,235959,A,A*41 $GPBOD,345.6,T,8.6,M,BA01,AIC*04 $GPBWC,235959,1248.413,S,03827.698,W,338.3,T,1.4,M ,0.315,N,BA01,A*6B $GPVTG,192.2,T,215.2,M,0.0,N,0.0,K,A*2F $GPXTE,A,A,0.04,L,N,A*07 $GPAPB,A,A,0.04,L,N,V,V,8.6,M,BA01,1.4,M,1.4,M,A*5 E ==================== = 23:59 GMT $GPRMC,000002,V,,,,,,,,,,N*51 $GPRMB,V,,,,,,,,,,,,,N*52 $GPRMC,000006,V,,,,,,,,,,N*55 $GPRMB,V,,,,,,,,,,,,,N*52 $GPRMC,000010,V,,,,,,,,,,N*52 $GPRMB,V,,,,,,,,,,,,,N*52 $GPRMC,000014,V,,,,,,,,,,N*56 $GPRMB,V,,,,,,,,,,,,,N*52 $GPRMC,000018,V,,,,,,,,,,N*5A $GPRMB,V,,,,,,,,,,,,,N*52 b)Around 09:08 LCL (00:08 GMT) the 276C started to send NMEA messages normally, see the sample below. $GPRMC,000134,V,,,,,,,,,,N*55 $GPRMB,V,,,,,,,,,,,,,N*52 $GPRMC,000138,V,,,,,,,,,,N*59 $GPRMB,V,,,,,,,,,,,,,N*52 $GPRMC,000142,V,,,,,,,,,,N*54 $GPRMB,V,,,,,,,,,,,,,N*52 $GPRMC,000146,V,,,,,,,,,,N*50 $GPRMB,V,,,,,,,,,,,,,N*52 $GPRMC,000150,V,,,,,,,,,,N*57 $GPRMB,V,,,,,,,,,,,,,N*52 $GPRMC,000154,V,,,,,,,,,,N*53 $GPRMB,V,,,,,,,,,,,,,N*52 $GPRMC,000158,V,,,,,,,,,,N*5F $GPRMB,V,,,,,,,,,,,,,N*52 ============== 00:08 GMT $GPRMC,000833,A,1248.705,S,03827.579,W,0.0,192.2,1 90207,23.0,W,A*32 $GPRMB,A,0.04,L,AIC,BA01,1248.413,S,03827.698,W,0. 315,338.3,,V,A*3B $GPGGA,000833,1248.705,S,03827.579,W,1,12,0.8,4.8, M,-10.5,M,,*63 $GPGLL,1248.705,S,03827.579,W,000833,A,A*48 $GPBOD,345.6,T,8.6,M,BA01,AIC*04 $GPBWC,000833,1248.413,S,03827.698,W,338.3,T,1.4,M ,0.315,N,BA01,A*62 $GPVTG,192.2,T,215.2,M,0.0,N,0.0,K,A*2F $GPXTE,A,A,0.04,L,N,A*07 $GPAPB,A,A,0.04,L,N,V,V,8.6,M,BA01,1.4,M,1.4,M,A*5 E Conclusions: 1)The problem is widespread like you and I have suspected, and comproved in garmins 172C and 276C. What other models have this problem? 2)As the 172C last update was in May/2006 and the last update (software version 4.8) of 276C was much more recent in Jan/2007, the suspicion of a widespread problem is very probable. 3)The time of day of the problem 23:59-00:08 is documented; could be that there is another times when the error appears? 4)I will send warning messages by e-mail to all people I know that sail using gps and autopilot. 5)I will open a new problem report with Garmin, regarding my 276C I suggest that other people using these Garmin gps models and other models too, do the test and open problem with garmin, since I repute this problem a very high risk issue. Here in Bahia, almost all sailors have Garmin Gps units interfaced with Raymarine Autopilots and we uses extensively this interface, about 95% of time, specially when sailing tricky routes, in narrow channels in bad weather or at night. Congratulations John, thanks for your advise and best regards Pascal Goncalves S 13 00 W 038 27 Salvador – Bahia - Brazil |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
Pascal,
Thank you for your effort in doing this testing and the comprehensive post with the results. It does indeed look as if this problem is widespread throughout the Garmin product line. I agree with your conclusions and think that your course of action is good and correct. The more reports that Garmin receives regarding this problem, the more likely it is that they will escalate its significance. I just hope that Garmin is not the kind of company that will wait until a loss of a vessel or life occurs with a resulting impact on their sales before they take action. I develop software professionally and would not be surprised if this problem affects most of their line in view of what the results are from your test of the 276C unit. When software routines have been developed, they are often cut and pasted from one program to another... the developers do not rewrite all of the code from the beginning if certain routines are adaptable to the current project. My boat is in Half Moon Bay in Northern California. The harbour approach is treacherous with shoals, breaking waves and rocks next to the channel. As it is Northern California, thick fog is often present and the entrance is a small gap in a rock seawall that surrounds the harbor. Radar and accurate navigation are essential. I'll keep this thread informed when I hear from the Coast Guard re what they plan to do. Regards, John Purins |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
Hi John,
In my experience with Garmin, they probabilly will fix the problem within 3 months. I had many problems with several Garmin Gps (GpsMap130, Map76 and Map276C) regarding the NMEA interface with my autopilot AH/ST4000, and after reporting the problems Garmin had fixed it within 3 months. The fix consisted of including the BWC message and implementing the Advanced NMEA Setup (Wpt Numbers x Names). Off course, there are another's problems that they do not recognize and have not fixed, like the problem with the promotion of the last go-to within a route even after a power-off/power-on, which I think is wrong and others revendications, like the support for AIS receiver etc. Best Regards Pascal |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
I don't know enough about this to help anyone, but I found it fascinating.
Nice job guys. I would appreciate your explaing something you said, John "During normal operation, NMEA transmissions occur every 2 seconds. For those who are familiar with software programming, the interesting thing is that the error begins at 23:59:59 GMT and normal transmissions resume at 00:08:34. The time interval of 8 minutes and 32 seconds just happens to be 512 seconds" I know little about programming but understand that the number 512 is a significant binary # and may be involved in some chance programming snafu. However, I don't see how you got an elapsed time from 23:59:59 to 00:08:34 of 8 min and 32 seconds, i.e. 512 seconds. I get 1 sec elapsed until 00:00:00 then 8 min 34 secs for a total of 8 minutes and 35 seconds which totals 480 plus 35 or 515 seconds, not 512. Did one of us count wrong? Thanks. Chet |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
Chet,
I think my post is not clear enough as to what the 512 seconds refers to and I did not include enough of my log file to show this. The following sequence occurred on 2006.11.23 and in this particular case, the GPS completely stopped transmitting NMEA sentences during the 'error period'. The last valid transmission before the error was at 235958 and normal transmissions resumed at 000834. $GPRMC,235956,A,3730.121,N,12228.827,W,0.0,199.6,2 31106,15.0,E,D $GPRMB,A,,,,,,,,,,,,A,D $GPGGA,235956,3730.121,N,12228.827,W,2,11,0.9,-7.2,M,-28.5,M,, $GPGLL,3730.121,N,12228.827,W,235956,A,D $GPBOD,,T,,M,, $GPBWC,235956,,,,,,T,,M,,N,,D $GPVTG,199.6,T,184.6,M,0.0,N,0.0,K,D $GPXTE,A,A,,,N,D $GPRMC,235958,A,3730.121,N,12228.827,W,0.0,199.6,2 31106,15.0,E,D $GPRMB,A,,,,,,,,,,,,A,D $GPGGA,235958,3730.121,N,12228.827,W,2,11,0.9,-7.3,M,-28.5,M,, $GPGLL,3730.121,N,12228.827,W,235958,A,D $GPBOD,,T,,M,, $GPBWC,235958,,,,,,T,,M,,N,,D $GPVTG,199.6,T,184.6,M,0.0,N,0.0,K,D $GPXTE,A,A,,,N,D $GPRMC,235959,V,,,,,,,,,,N $GPRMB,V,,,,,,,,,,,,,N $GPRMC,000834,A,3730.121,N,12228.827,W,0.0,199.6,2 41106,15.0,E,D $GPRMB,A,,,,,,,,,,,,A,D $GPGGA,000834,3730.121,N,12228.827,W,2,10,0.9,-5.8,M,-28.5,M,, $GPGLL,3730.121,N,12228.827,W,000834,A,D $GPBOD,,T,,M,, $GPBWC,000834,,,,,,T,,M,,N,,D $GPVTG,199.6,T,184.6,M,0.0,N,0.0,K,D $GPXTE,A,A,,,N,D $GPRMC,000836,A,3730.121,N,12228.827,W,0.0,199.6,2 41106,15.0,E,D $GPRMB,A,,,,,,,,,,,,A,D $GPGGA,000836,3730.121,N,12228.827,W,2,10,0.9,-5.7,M,-28.5,M,, $GPGLL,3730.121,N,12228.827,W,000836,A,D $GPBOD,,T,,M,, $GPBWC,000836,,,,,,T,,M,,N,,D $GPVTG,199.6,T,184.6,M,0.0,N,0.0,K,D $GPXTE,A,A,,,N,D From this log, each normal transmission occurs every 2 seconds and the time stamp seconds are even numbered. The error indication occurs at 235959 which is an odd numbered second so this means that the code is posting the error during the processing time before the next transmission. If things were operating normally, this next transmission would have occurred at 000000. When the code resumes normal operation, it must have done some processing prior to the NMEA transmission at 000834 so the 512 second interval that I refer to is the period of time that the code is not transmitting properly. This would be from 000000 to 000832. Of course, I don't have the Garmin source code nor do I know what their code does but my guess is that a counter is not being reset properly at the date rollover. It probably just keeps incrementing until it effectively resets to zero due to overflow. For example, 512 decimal would require 10 bits to represent so if 2 bytes are allocated to the counter, when it went to 513, the low order 10 bits would be all zeroes. If the software is using a mask or doing logical operations only on the 10 bits, then effectively the counter would be reset to zero. Obviously this is just conjecture on my part and I may be wrong. I hope that this explains what I meant more clearly... neither of us counted incorrectly; we were just referring to different things. |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
Chet,
The explanation in my previous post is wrong. The counter would not be reset to zero at 513... it would have to go to 1024 to reset to zero so perhaps they are using a 9 bit counter which overflows at 512 and resets to zero. As I said, I don't have the source code so the only thing I can do is guess. |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
John,
I think I do see how you counted it. I would think Garmin would be most appreciative of your input. Chet wrote in message ups.com... Chet, The explanation in my previous post is wrong. The counter would not be reset to zero at 513... it would have to go to 1024 to reset to zero so perhaps they are using a 9 bit counter which overflows at 512 and resets to zero. As I said, I don't have the source code so the only thing I can do is guess. |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
On 21 fev, 02:02, "CGB" wrote:
John, I think I do see how you counted it. I would think Garmin would be most appreciative of your input. Chet John, I have opened a problem with Garmin in 19 Feb and until today they have not replayed my question. I ask that if you receive any other communication from Garmin, could you pass to us here? I have put the information in several others forums from Google and Yahoo. One user at Yahoo 276C forum has replayed and says he have made the test with his Garmin 296 (aviation) and have not observed the problem. Here I have some 10 friends sailors with Garmin 276C and they are worried about the problem Regards |
Garmin GPS error & USCG 'Consumer Safety Defect' Report
I had received today a replya from Garmin saying:
Thank You for contacting Garmin Product Support! I will be glad to help you with this. Our engineers are currently looking into this issue. We are currently looking into adding this fix in a further update. However, at this time we do not have an exact date of when this update will be out for download. Thanks for the further information regarding this information. Best Regards, |
| All times are GMT +1. The time now is 08:46 PM. |
Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004 - 2014 BoatBanter.com