Sorry about that, here it is. I cannot show images without them blowing up XXL-size, annoys the hell out of me.
So I just checked it myself and it appears as if the gps daemon kicks in the moment it is woken up by some other process connecting to port 2947. SignalK can do that when you make a connection as below; pypilot does the same. The moment gps daemon wakes up, it hogs the ublox, preventing you from catting the device. But the good news is, from that point on, the gps information is available on port 2947 on the localhost. You cannot access it on the lan interface though.
So I just checked it myself and it appears as if the gps daemon kicks in the moment it is woken up by some other process connecting to port 2947. SignalK can do that when you make a connection as below; pypilot does the same. The moment gps daemon wakes up, it hogs the ublox, preventing you from catting the device. But the good news is, from that point on, the gps information is available on port 2947 on the localhost. You cannot access it on the lan interface though.