Review on 🚗 T600 Universal Car HUD Head Up Display - Digital GPS Speedometer with Speedup Test, Brake Test, Overspeed Alarm - TFT LCD Display for All Vehicles by Jerimiah Augustine

This device has a number of attractive features. For me, for example, it is (almost) the perfect solution because of its size and the possibility of mounting it on the dashboard next to the windshield. Unfortunately, its accuracy makes me scratch my head. As others have noted in their reviews, the readings were initially quite wide compared to the other two GPSs. No problem, sez me, I just fix the settings in the menu and that's it. Not really. I spent quite a bit of time setting it up and yes I was able to get it to match the other two GPS's exactly at highway speeds (60-70 mph), but at low speed it broke off. So I adjusted it accurately at low speed. Again, perfect speed match at 25 mph but at 70 mph. The weird thing is that it can be too HIGH at high speed and too LOW at low speed! Or too LOW at high speed and too HIGH at low speed depending on how you set it. Very strange. The best I can do, after playing with it too much and messing with the setting on one end or the other, is get good accuracy at 70mph and about 1mph at 25th (or vice versa). The "transition point" is somewhere between 40 and 50 miles per hour - above this value the error is in one direction, below it in the other. Normally I wouldn't give much importance to a 1mph error. However, this thing has to be steered by a GPS device, and at a constant speed, they usually don't always deviate in a certain direction (or change the direction of the error at some point). I recently put together a GPS display using a Wemo D1 Mini, a GPS module and a small display and have never seen errors like this. (Firstly, it was NEVER necessary to create a method to spoof the speed reading as the speed is set by the GPS module - if you are not tracking enough satellites, or there is multipath or a weak signal, speed is speed and you don't need an offset in units.) So, I really have no idea why the speed error exists, but I'm wondering if it has to do with rounding the error in the display routine - rather than to the next to round MPH maybe you truncate the number - who knows? In any case, as I said, this is a compelling point. I just wish I had a little more confidence in the displayed speed. and I have never seen such bugs as this device. (Firstly, it was NEVER necessary to create a method to spoof the speed reading as the speed is set by the GPS module - if you are not tracking enough satellites, or there is multipath or a weak signal, the speed is the speed and you don't need an offset in the unit.) So, I really have no idea why the speed error exists, but I'm wondering if it has to do with rounding the error in the mapping routine - instead rounding to the nearest MPH, maybe they'll truncate the number - who knows? In any case, as I said, this is a compelling point. I just wish I had a little more confidence in the displayed speed. and I have never seen such bugs as this device. (Firstly, it was NEVER necessary to create a method to spoof the speed reading as the speed is set by the GPS module - if you are not tracking enough satellites, or there is multipath or a weak signal, the speed is the speed and you don't need an offset in the unit.) So, I really have no idea why the speed error exists, but I'm wondering if it has to do with rounding the error in the mapping routine - instead rounding to the nearest MPH, maybe they'll truncate the number - who knows? In any case, as I said, this is a compelling point. I just wish I had a little more confidence in the displayed speed. because speed is given by the GPS module - if you're not tracking enough satellites, or there's no multipath or weak signal, speed equals speed and you don't have to compensate for anything in the block.) So, I really have no idea why the Error in speed exists but I'm wondering whether this is due to rounding errors in the display procedure - instead of rounding to the nearest mph the number may be truncated - who knows? In any case, as I said, it is an exciting topic. I just wish I had a little more confidence in the displayed speed. since the speed is set by the GPS module - if you aren't tracking enough satellites or there is multipath or weak signal, speed is equal to speed and you don't have to compensate for anything in the block.) So, I really have no idea why there is a speed error, but I'm wondering if it's due to rounding errors in the display procedure - instead of rounding to the nearest mph, the number may be truncated - who knows? In any case, as I said, it is an exciting topic. I just wish I had a little more confidence in the displayed speed. but I'm wondering if it's due to rounding errors in the mapping routine - instead of rounding to the nearest mph maybe they truncate the number - who knows? In any case, as I said, this is a compelling point. I just wish I had a little more confidence in the displayed speed. but I'm wondering if it's due to rounding errors in the mapping routine - instead of rounding to the nearest mph maybe they truncate the number - who knows? In any case, as I said, this is a compelling point. maybe shorten the number - who knows? In any case, as I said, this is a compelling point. I just wish I had a little more confidence in the displayed speed. but I'm wondering if it's due to rounding errors in the mapping routine - instead of rounding to the nearest mph maybe they truncate the number - who knows? In any case, as I said, this is a compelling point. maybe shorten the number - who knows? In any case, as I said, this is a compelling point. I just wish I had a little more confidence in the displayed speed. but I'm wondering if it's due to rounding errors in the mapping routine - instead of rounding to the nearest mph maybe they truncate the number - who knows? In any case, as I said, this is a compelling point.