Help with LS20031

GPS/GNSS Development Boards
1

Hi everyone, I just bought an GPS LS20031, it has 57600 baudrate. Can I make it 9600, how?

regards,

mbox

2

Connect to it at it’s current baud rate. Issue the command

$PMTK201,9600*11

Connect at the new baud rate and verify.

Check out http://docs.trenz-electronic.de/GlobalT … ket_01.pdf

3

thebecwar:
Connect to it at it’s current baud rate. Issue the command

$PMTK201,9600*11

Connect at the new baud rate and verify.

Using the hyperterminal and send this $PMTK201,9600*11 will make it 9600? Okay I will try it…feed back you later.

4

I tried to use this code $PMTK201,9600*11 but it did not make any changes to my desired baudrate. I followed this tutorial http://diydrones.com/profiles/blogs/usi … s-gps-with Now I have it running 38400. I really need it on the 9600, because my available crystal is only 4Mz. I have the Realterm output, pls see the attached file. How do I get the Latitude and longitude and test it on google map? I tried to read the reference pdf but unfortunately I don’t get it. I feel the result from the RealTerm is not complete…please help.

regards,

mbox

5

The V in your $GPRMC sentence means that the receiver doesn’t have a lock. The error is a parity error. If you’ve got realterm expecting a parity bit, but there’s none, it’ll whine.

What don’t you understand about the references? If we knew, we might be able to help you understand.

6

Hi,

If I want 9600 baud rate is this what I need to send $PMTK251,9600*27? Is *27 is the position fix interval?

Probably the reason I don’t have a lock position due I’m in the house…could this be the reason?

mbox

7

mbox:
Hi,

If I want 9600 baud rate is this what I need to send $PMTK251,9600*27? Is *27 is the position fix interval?

Probably the reason I don’t have a lock position due I’m in the house…could this be the reason?

  1. The part after the * is the checksum byte. It’s calculated by XORing each byte between the $ and *. You will have to calculate the checksum for any other messages you want to send. the actual checksum byte for “PMTK251,9600” is 17. Apparently my math sucked this morning.

  2. The lack of a position fix is because you’re inside. The frequency GPS operates on doesn’t penetrate anything.

8

Hi thebecwar, I finally got it to work on 9600 :smiley: . but I got another question, is the default update rate is 1Hz? Can I use this command “$PMTK220,200*2C” (5Hz) to increase the performance?

thanks,

mbox