| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This is without checksum support, and the daemon code does not do
anything with the RTCM data yet.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Specifically, the changes to sirf.c from ckuethe to stop
rAte-linmiting satellite messages (27 Dec 2007) and the changes to
packet.c and packet.states.h from ckuethe on 25 Dec 2007 to make the
packet sniffer 'a bit more picky'.
The packet-getter changes need to be re-implemented in a way
that doesn't break the RTCM regression test.
The SiRF changes will break the regression tests, and that's OK, but
they need to be committed along with a rebuild of the tests so
the tests pass after commit.
|
|
|
|
|
|
| |
about accepting TNT or Garmin Simple Text messages. Otherwise, they
often falsely accept "line noise" while sniffing for high data rate
devices
|
| |
|
|
|
|
|
|
| |
This is useful for devices like the Milltech Marine
SR162G integrated GPS/ Automatic Identification System.
With help from Maitland Bottoms, who reported this device originally.
|
|
|
|
|
|
|
|
| |
Diego Berge sent me an example of some line noise which just happened to have
$P<garbage> in it. This tricked the packet sniffer into thinking it found an
NMEA device. This change means that now 2 letters are required after the '$'
to trigger a detect. If this still false-positives too much, I might crank it
up to 4, to match on $PFec, $PFST, $PUBX, $PSRF and the like.
|
|
|
|
|
|
|
| |
now, all itrax features (including italk and $PFST) shall be
controlled with enable-itrax.
obviously i'm hacking on italk again, so make the italk driver compile again.
|
|
|
|
| |
functional but committed to allow for in-tree development.
|
|
|
|
| |
...(notably the TSIP ones). There's a conflict...
|
|
|
|
| |
Teach the daemon to ignore comment packets led with # and ended with \n.
|
| |
|
|
|
|
|
| |
This modifies the TSIP binary detection to also detect Garmin serial
binary. Nothing is done yet with the packet after it is identified.
|
|
|
|
| |
First line where possible, second line for scripts called with #!
|
|
|
|
|
|
|
|
|
|
| |
1) the product line is called SiRFstar
2) I don't have any original SiRFstar receivers but my documentation
says the protocol remained mostly the same between SS1, SS2 and SS3;
it just got richer as time went by. At least with my SS2 and SS3
receivers, this holds true.
3) elsewhere in the code there are SIRF_THIS and SIRF_THAT, which
implies (correctly) independence of chipset version.
|
|
|
|
|
|
| |
It's not compiled in by default, but it does require one architecture
change -- device channels is now a driver- specific capability, since
the Thales GPS our TrueNorth user is working with has 14 channels.
|
|
...there's an easier way to keep enum and name arrays in sync.
|