Live data from Hacker News

GPS

ciechanow.ski

191–200 of 296 posts

Re: GPS

#191

Earlier quoted context omitted.

Some are silly, some are effective ways to measure curiosity and ability to think through an abstract problem.

Yes, but how many of them are relevant to determining if a particular candidate is a good fit for a programming position?

No post body was provided.

Re: GPS

#192
post #41

This is very nice. Very clear, and the 3D interactives are excellent at guiding the explanation. One thing that I thought was a little confusing was right at the beginning, when we were estimating the position of the figurine and there was an area of uncertainty shown by the yellow circle. It isn't clear how you're estimating position, and why we have an area of uncertainty. At first I figured it was going to explain…

Was taught in college that if we get stuck, just move on forwards, things ahead can clear that up. And it works in this case for me. That part really doesn't matter much. At the end of the day, our brain is not a linear programming interpreter.

Re: GPS

#193
This is such a good write-up. Slowly builds on top of what I would consider the very basics of location terms while adding complexity in a digestible way. Excellent illustrations, great examples, and overall an informative teaching tone...

It is worth every minute you spend reading it (took me over 60 to get through it and I feel like I did skim a little towards the end)

Re: GPS

#194
post #166

Dumb question, but how does this deal with security? Can't anyone broadcast valid but malicious data on 1575.42 MHz? (e.g. to crash planes/missiles etc) EDIT: found wiki from some quick googling https://en.wikipedia.org/wiki/Spoofing_attack#Global_navigat...

It's illegal in most countries to jam or transmit on that frequency.

Re: GPS

#196
post #166

Dumb question, but how does this deal with security? Can't anyone broadcast valid but malicious data on 1575.42 MHz? (e.g. to crash planes/missiles etc) EDIT: found wiki from some quick googling https://en.wikipedia.org/wiki/Spoofing_attack#Global_navigat...

Yes, and there are moves in the next generation to add cryptographic signatures to the satellite streams. Someone could still jam it, but they couldn't spoof it.

Tons of info starting here: https://berthub.eu/articles/posts/galileos-authentication-al...

Continued here: https://berthub.eu/articles/posts/galileos-authentication-al...

And finally here: https://berthub.eu/articles/posts/galileos-authentication-al...

Re: GPS

#197

Earlier quoted context omitted.

I searched for an excellent, clear and precise explanation of GPS that is clean and ad-free, and landed on your comment.

I know not by what tools Web 3.0 content will be found, but Web 4.0 will be searched using hn comment breadcrumbs.

this is why i always add "thanks"||"it worked" in my queries

Re: GPS

#198

One of the things I love about GPS is: Since you know your exact position, you can pick a good GPS satellite (one of the satellite's you're using to calculate your position), look at the timestamp from that satellite, and use it as a highly-accurate time source! Purpose-built GPS time servers (like those from Meinberg) give you an option to enter the length of the coax cable connecting the receiver and the antenna, s…

My car does this. Unfortunately, it's a Honda/Acura, and there's a downstream bug in the way the receiver sends the info to the clock display that this year, almost all older Hondas/Acura's are reporting the wrong time: https://didhondafixtheclocks.com/ > Honda’s head unit receives a GPS signal for date and time including a number representing a week, coded in binary. These digits count from 0-1024 and rollover to 0…

It's been said that week number rollover occupies a "sweet spot of awfulness" where it happens infrequently enough that it doesn't get much testing, but often enough to impact equipment deployed in the real world.

The designers of GPS either should've made it use like 64 weeks so WNRO would happen constantly and we'd have to get good at handling it, or 32768 weeks so we could ignore it for the entire life of the system and any successors.

Re: GPS

#199
post #81

Earlier quoted context omitted.

This is going to come across as harsh, but if that is your favorite interviewing question, and you are not hiring GPS engineers, then it is a ridiculous question to ask and serves no purpose but to "haze" candidates.

I think it depends on the job. If this was for an embedded/firmware engineering position, I'd expect a level of EE knowledge that would at least make the concept of everyone's phone sending data to a satellite be a non-starter. I think it's more relevant than asking an embedded engineer which sorting algorithm is the fastest.

[deleted]

Re: GPS

#200

One of the things I love about GPS is: Since you know your exact position, you can pick a good GPS satellite (one of the satellite's you're using to calculate your position), look at the timestamp from that satellite, and use it as a highly-accurate time source! Purpose-built GPS time servers (like those from Meinberg) give you an option to enter the length of the coax cable connecting the receiver and the antenna, s…

It's a bit more complex than this, the entire GPS fix is 4D since position depends on time and vice versa. The time reported by a GPS receiver, once fix is attained, is not just the time from one of the satellites but the time resulting from the 4D fix in space and time. This eliminates (to within a certain precision) the latency. A lot of discrete GPS receivers have some nonvolatile storage where they "cache" fixes…

Or a test location emitted by QA's satellite simulator.

I have a small list of funny locations I like to pipe into gps-sdr-sim, including Null Island, the north pole, 500 feet above the Kremlin, the middle of Lake Erie, and a quiet beach in the Bahamas.

Not that I expect anyone to look at the first few sentences of output after I hand them hardware, but if they _do_...

Post reply on HN