Printable View
I think both of them. When accuracy is poor, lock to the road feature fails to lock to current road. I had it once. When I turned on my Nuvi with active route on screen appeared jumping car. The car icon was on the road nearby actual road and car icon was jumping. After a while accuracy increased, and Nuvi locked to the actual road. Car jumping gone.Quote:
Originally Posted by Neil [Only registered and activated users can see links. Click Here To Register...]
It would be interesting to see real 3490 Vs 3790 Converted to 3490.
Neil's experiment does conclude that maybe the 3490 Firmware is not 100% compatible with the 3790 Hardware.
The same as enabling MP3 and Video! only Plays Right Channel of Stereo Movie or MP3. (You can't win them All)
@dasilvarsa
Yes, you are right, 3490 v. 37>3490 convert side-by-side would be interesting and especially so if also alongside 3790 original and another 3490 convert further modded with gps fw from 3790 as Loly suggested. End up looking a bit like the pic from [Only registered and activated users can see links. Click Here To Register...] though, lol.
PS: Tell ya wot, Joe. Pack up your 3490 and sent to over. I promise to return it ......
Neil was of an invaluable utility your comparative test: now we are sure that there is a loss of precision in the 3790 converted and which seems to have little to do with the ability of system "learning" and fine tuning itself, because they seem sufficiently used. Despite of your unquestionable conclusion I was even more curious about the causes of these discrepancies. Several could be the causes, but by reading the text indicated by Catymag (post 758) of Garmin engineering, seems that the key element in the calculation of accuracy of gps is the algorithm that calculates the deviation/error of the oscillator by introducing a correction factor (constant) based on the current internal temperature of the device. The logic indicates that the algorithm (I assume garmin's property) does not change between models tested but most likely only the correction factor. This constant (correction factor) must be specifies for each model, because it depends on the internal ambient temperature of each one, that has to do with processor heat dissipation, size of the case and other different items of hardware.
The disneysw's hint in post 755, what the variable table resulting of correction calculation is installed along with the firmware did not convince me because it does not explain several situations, as you even reported in earlier posts, that is, that there was no change in accuracy when you reinstalled the firmware original in your 3790, meaning that was not installed new table. By the way, this standard table is only installed when the unit leaves the factory, which may explain the great inaccuracy when installed the 3490 firmware on a new and unused 3790, as was in my case (but it was self adjusting with time of use). Remains the question of its location and how to reset this table, but that's another question. How does not seem to be the algorithm and nor the table that are installed with the firmware, another real candidate is the correction factor, specific for the model, which influences on calculation and can generate inaccuracy such as those observed in the comparison that you did, this is my hypothesis: the "cause" is this constant that which may be different for each model, that seems to be the case.
I believe that to have more security would be important someone to do a quick test, same as static, between a original 3790 (preferably never modified) and a 3790/3490, but with the original firmware (of 3790). The result we can deduce a few things. We already know by your own report that when the original firmware was reinstalled the on the 3790 modified, there was no change in accuracy compared to 3490 firmware, but the question is what will be the behavior of 3790 (mod but with original firmware) in comparison with the original 3790 never modified. If the result is not similar in accuracy we have problems that will not easy to solve. In this case would have the table variable that remained hidden in some file, database or fimware region changing the correction values and hence the accuracy? Correction factor would have been permanently recorded? Among other possibilities ... If the result is the same in both (original never changed and 3790 now with original firmware), it may mean that was installed new algorithm, new factor and/or new table by the firmware and everything needed for the result we should expect ..
If I failed at some, or all (lol), reasoning, correct me ..
Just to add another point of data; accuracy is much worse on after 37xx to 34xx. I had two 37xx units and I flashed one at a time to 34xx and compared them side by side. The 34xx was always showing worse accuracy, sometimes double the 37xx.
I then revered the units and found the same conclusion. (34xx->37xx, 37xx->34xx).
The accuracy of the 34xx is so bad it often causes recalculations because the GPS thinks I'm on another street. Many times when my vehicle is at a full stop, the GPS will show that I am still moving, sometime upto 50km/h for longer than 1 min.
As much as I like the 34xx I will have to revert as the inaccuracy is too great.
Quote:
Originally Posted by angelozip [Only registered and activated users can see links. Click Here To Register...]
i think that problem is in new firmware. i've a nuvi 765 european versione and a nuvi 765 taiwan version (convert) and precision is 6-7 meters on european and 3-4 meters on taiwan in the same place at the same hours. in 765 taiwan is possible enable WAAS and i've see that if i enable WAAS precision in more good (3-4) when i disable WAAS precision is european=taiwan so i can deduce that firmware do the difference
@giuseppe66
You may possibly be on to something there i reckon.
WAAS is used as an acronym internationally, and it's actually the name of the original GPS accuracy augmentation system developed by the US FAA for improved vertical and lateral precision in aircraft approaches. I think it's more correctly called SBAS (Space/Satellite Based Augmentation System) internationally and I also think it's normally enabled by default in most modern units (e.g. my old StreetPilot 2610 also lets you turn WAAS on or off).
Could this be at least partly the problem with 37>34? Maybe WAAS is not working properly or at all when using 34 fw on 37 hw? It would explain the extreme variation in elevation readings I experienced in that test run. Also, again i think WAAS more effectively enhances the moving accuracy in a vehicle/aircraft. Moving accuracy was much worse in my tests than when stationary.
This is just another 'hypothesis' of mine. Ready to be shot down in flames by the Software Experts in the interests of keeping this discussion going ..... fire away!
EDIT: Another thought on this, note the differences in satellite displays between 3790 and 3490 in my two pics. 37 is locked on to 24 in both pics, 34 is not. In pic 1, 34 is using 153 but 37 is not. In pic 2, 34 is using 19 but 37 is not. WAAS/SBAS i think has someway of knowing more quickly than a non-enhanced GPS if a sat. is 'off' in that it's giving incorrect info., and ignores it.
This interesting discussion has been moved in a new thread ;) with Neil I thought , it might get even more attention as well.
Some info from my observations.
GPS accuracy compensation table. Where this data is stored? I think this data can be stored only in NVRAM (region 41). I have Nuvi 3790 flashed to 3490, and I never have had accuracy problems. For some time my Nuvi was with original (3790) region 41 but after some time I flashed region 41 from 3490. Still no problems with accuracy, despite the compensation data changed (I think so).
Hi voyager,Quote:
Originally Posted by voyager56 [Only registered and activated users can see links. Click Here To Register...]
I thought the same about accuracy problems, like you said 'no problems'. That is until i did the side-by-side with the original 3790 and converted 37>3490. The accuracy, although less than the stock 37x0, is still acceptable in my convert, as is yours and also Caty's 37>34. The problem is that some are not as lucky as us, and why? Maybe some 37x0 (like ours) have gps hw that is somewhat more compatible with the 34 fw. Going by the S/No, mine is an early production model.
