On 2011-03-31, Uwe Klein uwe_klein_habertw...@t-online.de wrote:
Chris Albertson wrote:
Another possibility to check is that both are not using the same
system. What spheroid dose Google use? Is it WGS84? The GPS would
need to be set to match whatever Google uses. Errors on the order of
unruh un...@wormhole.physics.ubc.ca wrote in message
news:slrnipci4i.3la.un...@wormhole.physics.ubc.ca...
[]
Which route did you take-- PPS pin to RS232 (CMOS level) or via the
buffers/inverters?
All I am pointing out to people who might regard the sure board as a
really cheap path, but do
I've done some more careful inspection of the Sure GPS comms trace:
It really looks like the GPS does _not_ listen to commands by default,
instead the controlling program sends a solitary '0' char to ask for
permission to talk.
About 200 ms later the GPS boards drop the CD (Carrier Detect)
David J Taylor wrote:
I've done some more careful inspection of the Sure GPS comms trace:
It really looks like the GPS does _not_ listen to commands by default,
instead the controlling program sends a solitary '0' char to ask for
permission to talk.
About 200 ms later the GPS boards drop the
On 2011-03-31, E-Mail Sent to this address will be added to the BlackLists
Null@BlackList.Anitech-Systems.invalid wrote:
unruh wrote:
My only concern is that the unit places its location 12m
away from its actual location on Googleearth-- ie, either
googleearth is 12 m out in its alignment
On 2011-03-31, Terje Mathisen terje.mathisen at tmsw.no wrote:
Uwe Klein wrote:
http://www.google.com/search?client=operarls=deq=MG1613
going to have a look into the datasheets.
That or ask Sure-Elec or inspect the USB(serial) traffic
this could be a start: ( reading currently )
Chris Albertson wrote:
On Thu, Mar 31, 2011 at 9:44 AM, Uwe Klein
uwe_klein_habertw...@t-online.de wrote:
unruh wrote:
My only concern is that the unit places its location 12m away from its
actual location on Googleearth-- ie, either googleearth is 12 m out in
its alignment to lat/long grid
On 2011-03-31, Chris Albertson albertson.ch...@gmail.com wrote:
On Thu, Mar 31, 2011 at 8:19 AM, unruh un...@wormhole.physics.ubc.ca wrote:
For general useage, the garmin 18 is still probably the easiest bet.
While it does require soldering on power (eg usb) and a serial port,
that soldering
unruh un...@wormhole.physics.ubc.ca wrote in message
news:slrnipapga.co8.un...@wormhole.physics.ubc.ca...
[]
Using a soldering iron on surface mount devices is a bit trickier-- too
easy to bridge the pins is you do not have very steady hands. Not saying
you cannot do it. But Joe Bloggs might
On Thu, Mar 31, 2011 at 11:03 PM, Terje Mathisen terje.mathisen at
tmsw.no@ntp.org wrote:
I don't think any GPS comes even close to 2 ns, given that the entire GPS
constellation is only required to be within 14 ns or so of UTC.
First off this is a timing gps. That means the receiver knows the
Chris Albertson wrote:
On Thu, Mar 31, 2011 at 11:03 PM, Terje Mathisenterje.mathisen at
tmsw.no@ntp.org wrote:
I don't think any GPS comes even close to 2 ns, given that the entire GPS
constellation is only required to be within 14 ns or so of UTC.
First off this is a timing gps. That
unruh wrote:
On 2011-03-31, Terje Mathisenterje.mathisen at tmsw.no wrote:
Based on this I tried to use HyperTrm to send the pdf sample command to
turn on WAAS capability:
I think WAAS is turned on by default. My sure lists that it is using
DGPS but no DGPS station ID or time since source.
Terje Mathisen wrote:
unruh wrote:
On 2011-03-31, Terje Mathisenterje.mathisen at tmsw.no wrote:
Based on this I tried to use HyperTrm to send the pdf sample command to
turn on WAAS capability:
I think WAAS is turned on by default. My sure lists that it is using
DGPS but no DGPS station ID
David J Taylor wrote:
I would be most interested in a copy of the programming manual should
you get one.
Just got my two samples. nice. works out of the box.
The pcb design is rather well done imho.
Rather interesting to follow the GSV sentences
( sat number, direction and quality )
All Docs
On 2011-03-31, Uwe Klein uwe_klein_habertw...@t-online.de wrote:
David J Taylor wrote:
I would be most interested in a copy of the programming manual should
you get one.
Just got my two samples. nice. works out of the box.
The pcb design is rather well done imho.
Well, no they do not work
On Thu, Mar 31, 2011 at 8:19 AM, unruh un...@wormhole.physics.ubc.ca wrote:
For general useage, the garmin 18 is still probably the easiest bet.
While it does require soldering on power (eg usb) and a serial port,
that soldering is relatively easy to do, and the documentation on the
gps18 is
unruh wrote:
On 2011-03-31, Uwe Klein uwe_klein_habertw...@t-online.de wrote:
David J Taylor wrote:
I would be most interested in a copy of the programming manual should
you get one.
Just got my two samples. nice. works out of the box.
The pcb design is rather well done imho.
Well, no
Uwe Klein wrote:
http://www.google.com/search?client=operarls=deq=MG1613
going to have a look into the datasheets.
That or ask Sure-Elec or inspect the USB(serial) traffic
this could be a start: ( reading currently )
Terje Mathisen wrote:
Uwe Klein wrote:
http://www.google.com/search?client=operarls=deq=MG1613
going to have a look into the datasheets.
That or ask Sure-Elec or inspect the USB(serial) traffic
this could be a start: ( reading currently )
Chris Albertson wrote:
Another possibility to check is that both are not using the same
system. What spheroid dose Google use? Is it WGS84? The GPS would
need to be set to match whatever Google uses. Errors on the order of
up to 100M are posable. Not everyone uses the same system.
I
unruh wrote:
My only concern is that the unit places its location 12m
away from its actual location on Googleearth-- ie, either
googleearth is 12 m out in its alignment to lat/long grid
at my house, or the unit is misreporting its position.
Note that the scatter has only a standard
Terje Mathisen wrote:
b) Since both the PPS and NMEA drivers have fudge flags to use a falling
instead of the default rising edge of the DCD signal, I can use the
first version of David's hack, i.e. from the official PPS header via the
free RS232 level driver (U6 - pin 11-14). This should avoid
Inspired by http://www.satsignal.eu/ntp/Sure-GPS.htm and
http://www.leapsecond.com/pages/MG1613S/ I ordered one of these
boards, at a total cost of about $40 including shipping from Hong Kong.
It arrived after a week or so, and so far both USB and RS232 simply
works. :-)
Receiver
23 matches
Mail list logo
