Shop OBEX P1 Docs P2 Docs Learn Events
VPN1513 GPS Receiver Module documentation problems — Parallax Forums

VPN1513 GPS Receiver Module documentation problems

macegrmacegr Posts: 5
edited 2011-12-09 19:52 in Accessories
Couple of issues with the VPN1513 board (Parallax 28506).

1.) Serial interface is 3.3V, not 5V. Interface voltage isn't documented. This voltage change can cause problems when connected to some devices, which expect higher minimum HIGH logic levels. In my customer's case, an earlier (discontinued) Parallax 5V TTL GPS module worked perfectly but this new module did not. An external level conversion circuit will need to be constructed. Documentation needs to be clear this is a 3.3V interface. It may work correctly in the exact example configuration provided, but may be unreliable or cause damage if used by someone assuming it's a 5V interface.

2.) In RAW (NMEA 0183) mode, the serial baud rate is actually 4800. The documentation only ever mentions the new interface speed of 9600, which I imagine holds true for the SMART mode of operation. This significantly increased the time required to troubleshoot the previous voltage level issue, because there were actually two problems to solve before communication with the GPS module was possible. Documentation needs to explain that baud rate changes to 4800 in RAW mode, or else the firmware needs to be updated to 9600 baud if this was an error.

Hope this helps anyone else having problems with this module.

Comments

  • Jessica UelmenJessica Uelmen Posts: 490
    edited 2011-09-19 13:22
    macegr,

    Thanks for pointing this out, we'll get the documentation updated ASAP.

    Cheers,
    Jessica
  • sidecar-racersidecar-racer Posts: 82
    edited 2011-12-07 16:19
    I asked a while back but can't find the answer; Is there a listing available for the Propeller firmware in VPN1513 module. Is the second 4 pin port (JP1) compatible with the prop-plug to allow programming. Is there a way to retrieve the existing program for review?
    Rick Murray
  • Cluso99Cluso99 Posts: 18,069
    edited 2011-12-07 16:46
    The firmware is available on the data page in the parallax store. I believe the second port is propplug compatible.
  • hover1hover1 Posts: 1,929
    edited 2011-12-07 16:57
    I asked a while back but can't find the answer; Is there a listing available for the Propeller firmware in VPN1513 module. Is the second 4 pin port (JP1) compatible with the prop-plug to allow programming. Is there a way to retrieve the existing program for review?
    Rick Murray

    The firmware is available on the bottom right of this page (Under Open Source Downloads):

    http://www.parallax.com/StoreSearchResults/tabid/768/txtSearch/28506/List/0/SortField/4/ProductID/757/Default.aspx


    If you go to page one of this document, you will see four holes on the right side to accept a PropPlug. Yes , that is JP1. That is for re-programming the Propeller's EPROM. You can't retrieve the program from the EEPROM, but the program loaded is the program in the firmware listing.


    EDIT: Posted while Ray was replying. (Never been a fast typist) :)
  • sidecar-racersidecar-racer Posts: 82
    edited 2011-12-07 17:56
    Thanks, teach me not tro read to bottom of page :innocent:
  • TorTor Posts: 2,010
    edited 2011-12-08 01:33
    The "traditional" baud rate for NMEA-183 GPS devices is 4800 though.. this holds true even for bluetooth GPS receivers. So maybe that's why nobody thought to document it explicitly.

    -Tor
  • sidecar-racersidecar-racer Posts: 82
    edited 2011-12-09 19:52
    I'm making progress with the VPN1513. Using the simple.serial.spin I created an interface of sorts.
    I am using the Propeller education kit with plans to go to USB board.
    Command is hard-coded, output is to CRT
    A couple of thing came up:
    1. As is published, 9600 baud is the correct rate.
    2. Normal mode (not inverted) is correct polarity.
    3. The command set is prefaced with "!GPS", got that from Stamp demo. Spent several hours with scope trying to figure that one out.
    4. The 1513 doesn't pull the SIO line all the way to 0 (.4v or so) but does work. (tried pull-down of 10K) Perhaps a pin release issue??
    5. Do only the number of reads that you expect bytes of data; too many; locks and waits.
    6. Documention error (??) GetDate returns UTC Date in Day, Month,Year format

    Rick Murray
Sign In or Register to comment.