Do I use the tx wire or the rtx wire I have looked at the connection diagram and don't know? How can I hook it up to the bs2e with a serial connection or how would you do it? Thanks Toby
when i use the demo code that is provided for the (gpsdemov1.1.bs2) very first gps unit it debugs funny very funny numbers and it appears 700 to 1600 mph
I am looking for some demo code for the pmb688 gps unit where could i find it?
Could you attach the code you are downloading to the stamp to your next post? Try writing simple code that just outputs what the gps is sending you. Don't try any fancy conversions until after you are getting correct and stable data.
The 28146 is a 'smart' GPS unit, meaning it is set up to wait for commands and then transmit requested data. The 28501 just sends out GPS data all the time and you have to capture it.
I dont have no idea what i am doing wrong I am trying to change the baud rate setting to 19200 con 32 is that correct I am sure having problems the lcd appear all kind of numbers and symbols and nothing seems to work right what am I not doing
First, are you able to display words and numbers properly on the LCD? Can you display your name, and the value of a counter variable? If not, tackle that first.
If you're okay on the LCD side, then your issue is in capturing the parts of the GPS output strings that you want to use. The GPS simply sends out strings of characters:
You need to read those strings in using a SERIN command, WAITing for the $GPGGA (or whichever string you're going to use), then SKIPing to the position in the string that contains the data you need. You will probably need to convert the string of characters to whatever format you're going to use.·For example, the $GPRMC string gives you speed in knots, but it's not a single variable holding that speed as a number. It's a set of characters (that is, again, a string), such as "022.4". You'd need to read in the first character, convert it to a number, multiply that number by 100, then read in the second character, convert it to a number, multiply that number by 10 and add it to the first number, read in the third character, convert it to a number, add that to the first two, and then if you're willing to tackle fractions, do the same with the tenths position (that's going to be more difficult, of course, as Stamps use integer math).
So for "022.4", if you were just doing the integer part, you'd read the first three characters into a three-character byte array. "0" = ASCII 48, and "2" = ASCII 50. If you have a digit character from 0-9, you subtract 48 from the·Ascii code for that character to get the corresponding number. So you'd do
Where Speed is a word-sized variable holding the numeric version of your speed, and GPSSpeed[noparse][[/noparse]3] is a byte array into which you've read the first three characters of the "speed over the ground" part of the $GPRMC string. If you wanted the fractional part as well, the easiest way would be to just multiply everything by ten (so you'd have "1000*(GPSSpeed[noparse][[/noparse]0]"), etc.), and deal with it later in display or in whatever you're dumping the data into.
is that also going to work for the pmb666 or 28501 unit from parallax? I haven't tried that but will later is there anywhere that i could find some demo code for a bs2e on speed etc. Thanks, Toby
Tobias said...
is that also going to work for the pmb666 or 28501 unit from parallax? I haven't tried that but will later is there anywhere that i could find some demo code for a bs2e on speed etc. Thanks, Toby
Any unit that sends NMEA strings out as serial data can be parsed to grab out the data you want. You need to check to make sure that it sends out the data you're after, of course. If, for example, it were only to send out the $GPGGA string you wouldn't get the direct readout of speed over the ground that you get from the $GPRMC string (though you might be able to use the position data to calculate speed - I wouldn't want to myself). Take a look at the product description to see which strings your GPS sends out. It's good practice to get used to reading those product descriptions carefully - you'll learn all sorts of things that you need to know.
I doubt that you're going to just stumble across demo code that gives you the speed readout. You're going to have to learn to parse the strings and pull out the data yourself. If you're going to work with GPS and microprocessors, that's something you need to figure out. It will be very educational for you to work through that, and you will understand how to get out whatever data you need.
Tobias
Posts: 95
Comments
The basic communication process is the same for all gps serial units. Have a look at the docs for the 28146.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Tom Sisk
http://www.siskconsult.com
·
I am looking for some demo code for the pmb688 gps unit where could i find it?
Thanks, Toby
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
- Stephen
Here is some good reading : http://forums.parallax.com/attachment.php?attachmentid=67605
You will have to modify the baud rate setting for a BS2e to get 4800.
Jim
Thanks, Toby
If you're okay on the LCD side, then your issue is in capturing the parts of the GPS output strings that you want to use. The GPS simply sends out strings of characters:
http://www.gpsinformation.org/dale/nmea.htm#GGA
You need to read those strings in using a SERIN command, WAITing for the $GPGGA (or whichever string you're going to use), then SKIPing to the position in the string that contains the data you need. You will probably need to convert the string of characters to whatever format you're going to use.·For example, the $GPRMC string gives you speed in knots, but it's not a single variable holding that speed as a number. It's a set of characters (that is, again, a string), such as "022.4". You'd need to read in the first character, convert it to a number, multiply that number by 100, then read in the second character, convert it to a number, multiply that number by 10 and add it to the first number, read in the third character, convert it to a number, add that to the first two, and then if you're willing to tackle fractions, do the same with the tenths position (that's going to be more difficult, of course, as Stamps use integer math).
So for "022.4", if you were just doing the integer part, you'd read the first three characters into a three-character byte array. "0" = ASCII 48, and "2" = ASCII 50. If you have a digit character from 0-9, you subtract 48 from the·Ascii code for that character to get the corresponding number. So you'd do
Speed = (100*(GPSSpeed[noparse][[/noparse]0] - 48)) + (10*(GPSSpeed[noparse][[/noparse]1] - 48)) + (GPSSpeed[noparse][[/noparse]2] - 48)
Where Speed is a word-sized variable holding the numeric version of your speed, and GPSSpeed[noparse][[/noparse]3] is a byte array into which you've read the first three characters of the "speed over the ground" part of the $GPRMC string. If you wanted the fractional part as well, the easiest way would be to just multiply everything by ten (so you'd have "1000*(GPSSpeed[noparse][[/noparse]0]"), etc.), and deal with it later in display or in whatever you're dumping the data into.
The BS2pe can handle all of this just fine.
I doubt that you're going to just stumble across demo code that gives you the speed readout. You're going to have to learn to parse the strings and pull out the data yourself. If you're going to work with GPS and microprocessors, that's something you need to figure out. It will be very educational for you to work through that, and you will understand how to get out whatever data you need.