ViewSonic with Serial GPS

Archived from groups: microsoft.public.pocketpc.developer,microsoft.public.pocketpc (More info?)

So you've verified that a null-modem adapter isn't required by the
cable/device?

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net


"Kenneth Evans, Jr." <evans@aps.anl.gov> wrote in message
newsIitVI5NEHA.3572@tk2msftngp13.phx.gbl...
> I have been unable to get my ViewSonic V37 upgraded to PPC 2003 to work
with
> a Garmin eTrex connected through the serial port, and would like to know
if
> others have had the same experience.
>
> It does not work with several GPS programs, including Pocket Streets and
> GPSInfo, as well as my own program. I have tried the ViewSonic serial
cable
> connected to the eTrex serial cable via a null modem and gender changer as
> well as another serial cable from Pc-mobile designed for the
ViewSonic/eTrex
> combination.
>
> All of these programs with the equivalent serial cables work on several
> versions of iPAQs as they should.
>
> It is not the software nor the configuration. It is either my V37, all
V37s
> with PPC 2003, or all V37s. Information as to which would be appreciated.
>
> It does sync with ActiveSync using the ViewSonic serial cable. The eTrex
> only uses pins 2,3, and 5 (of a 9-pin RS-232). ActiveSync also uses these
3
> pins (plus some others), but the voltages are different. ViewSonic was of
> no help. They said only ActiveSync is supported with the serial cable.
>
> The V37 serial port is COM1. Using an RS-232 analyzer I have determined
> that the data is going out from the software, is received by the eTrex,
and
> the proper response is sent back from the eTrex. It just is never
received
> by the programs.
>
> Any information or experiences would be appreciated.
>
> Thanks,
>
> -Ken
>
>

Archived from groups: microsoft.public.pocketpc.developer,microsoft.public.pocketpc (More info?)

If you connect an eTrex serial cable to a PPC serial cable, you need a null
modem and probably a gender changer. This is pretty standard. Transmit for
one has to be changed to receive for the other, etc.

What I said is the eTrex/V37 combination doesn't work with *any* cable,
whereas the eTrex/iPAQ combination works as expected. Moreover, the cable
is not the problem. The data go to the eTrex and come back. They just
don't get back to the software.

-Ken


"Chris Tacke, eMVP" <ctacke@spamfree-opennetcf.org> wrote in message
news:utRUnO5NEHA.2708@TK2MSFTNGP10.phx.gbl...
> So you've verified that a null-modem adapter isn't required by the
> cable/device?
>
> --
> Chris Tacke, eMVP
> Co-Founder and Advisory Board Member
> www.OpenNETCF.org
> ---
> Windows CE Product Manager
> Applied Data Systems
> www.applieddata.net
>
>
> "Kenneth Evans, Jr." <evans@aps.anl.gov> wrote in message
> newsIitVI5NEHA.3572@tk2msftngp13.phx.gbl...
> > I have been unable to get my ViewSonic V37 upgraded to PPC 2003 to work
> with
> > a Garmin eTrex connected through the serial port, and would like to know
> if
> > others have had the same experience.
> >
> > It does not work with several GPS programs, including Pocket Streets and
> > GPSInfo, as well as my own program. I have tried the ViewSonic serial
> cable
> > connected to the eTrex serial cable via a null modem and gender changer
as
> > well as another serial cable from Pc-mobile designed for the
> ViewSonic/eTrex
> > combination.
> >
> > All of these programs with the equivalent serial cables work on several
> > versions of iPAQs as they should.
> >
> > It is not the software nor the configuration. It is either my V37, all
> V37s
> > with PPC 2003, or all V37s. Information as to which would be
appreciated.
> >
> > It does sync with ActiveSync using the ViewSonic serial cable. The
eTrex
> > only uses pins 2,3, and 5 (of a 9-pin RS-232). ActiveSync also uses
these
> 3
> > pins (plus some others), but the voltages are different. ViewSonic was
of
> > no help. They said only ActiveSync is supported with the serial cable.
> >
> > The V37 serial port is COM1. Using an RS-232 analyzer I have determined
> > that the data is going out from the software, is received by the eTrex,
> and
> > the proper response is sent back from the eTrex. It just is never
> received
> > by the programs.
> >
> > Any information or experiences would be appreciated.
> >
> > Thanks,
> >
> > -Ken
> >
> >
>
>

Archived from groups: microsoft.public.pocketpc.developer,microsoft.public.pocketpc (More info?)

I'm running PPC 2003 on mine. Have you checked the baud rate? My eTrex
only lets me set 4800 for NMEA, but Mapopolis tried everything but 4800, I
had to change the config from Autodetect to the exact baud.

--
Floyd Burger


"Kenneth Evans, Jr." <evans@aps.anl.gov> wrote in message
news:u4Vjck5NEHA.2468@TK2MSFTNGP11.phx.gbl...
> Pocket Streets and GPSInfo both need NMEA Out. Other programs that only
> track location would most likely use NMEA also. Programs that up and
> download waypoints, tracks, etc. would probably use GARMIN. That isn't my
> problem, however. I know which one to use for which program.
>
> So it seems your V36 works. Is it PPC 2003 or 2002. I didn't test mine
> with PPC 2002 because I didn't have a serial cable then. It doesn't work
> with PPC 2003.
>
> Thanks,
>
> -Ken
>
>
> "Floyd Burger" <floyd@adelphia.not> wrote in message
> newsbMZYe5NEHA.1160@TK2MSFTNGP09.phx.gbl...
> > I'm able to connect with my eTrex using Mapopolis, but I had to change
the
> > eTrex data format to NMEA OUT instead of the text that I was using.
But,
> > I'm using a V36. The ViewSonic people said that the serial ports were
> > identical between the V36 and V37. My cabling is the V36 serial cable -
> > null-modem DB9 - DB9 gender changer - serial cable to eTrex.
> >
> > --
> > Floyd Burger
> >
> > "Kenneth Evans, Jr." <evans@aps.anl.gov> wrote in message
> > newsIitVI5NEHA.3572@tk2msftngp13.phx.gbl...
> > > I have been unable to get my ViewSonic V37 upgraded to PPC 2003 to
work
> > with
> > > a Garmin eTrex connected through the serial port, and would like to
know
> > if
> > > others have had the same experience.
> > >
> > > It does not work with several GPS programs, including Pocket Streets
and
> > > GPSInfo, as well as my own program. I have tried the ViewSonic serial
> > cable
> > > connected to the eTrex serial cable via a null modem and gender
changer
> as
> > > well as another serial cable from Pc-mobile designed for the
> > ViewSonic/eTrex
> > > combination.
> > >
> > > All of these programs with the equivalent serial cables work on
several
> > > versions of iPAQs as they should.
> > >
> > > It is not the software nor the configuration. It is either my V37,
all
> > V37s
> > > with PPC 2003, or all V37s. Information as to which would be
> appreciated.
> > >
> > > It does sync with ActiveSync using the ViewSonic serial cable. The
> eTrex
> > > only uses pins 2,3, and 5 (of a 9-pin RS-232). ActiveSync also uses
> these
> > 3
> > > pins (plus some others), but the voltages are different. ViewSonic
was
> of
> > > no help. They said only ActiveSync is supported with the serial
cable.
> > >
> > > The V37 serial port is COM1. Using an RS-232 analyzer I have
determined
> > > that the data is going out from the software, is received by the
eTrex,
> > and
> > > the proper response is sent back from the eTrex. It just is never
> > received
> > > by the programs.
> > >
> > > Any information or experiences would be appreciated.
> > >
> > > Thanks,
> > >
> > > -Ken
> > >
> > >
> >
> >
>
>

Archived from groups: microsoft.public.pocketpc.developer,microsoft.public.pocketpc (More info?)

Floyd,

I don't have Mapopolis. I rechecked the baud rate for GPSInfo
(available free from
http://www.mobilelinktech.com/corp [...] ort.html). It
seems to be well written and is apparently a utility for a larger package.
It uses NMEA. It autodetects (or just defaults) to COM1, 4800 baud. As
with all the programs I have tried, it works OK on my iPAQ and does not work
on the V37. On the iPAQ I only get data if the port is COM1 and the baud is
4800. Other combinations don't work on the IPAQ. This is reasonable and
consistent with what you said: The eTrex sets 4800 baud with NMEA Out and
that appears to be the only option. I use 9600 baud with GARMIN and that
works on all the other Pocket PCs to which I have access.

Pocket Streets uses NMEA and has a provision to set the COM port but
not the baud. It works anyway on my iPAQ but not the V37.

It is unlikely I have misconfigured all of these programs. They all
work on the iPAQ, and some I have had and used since I had a Jornada. My
V37 does not seem to receive through the serial port. With any of them I
can have them working on the iPAQ and switch only the cable from the iPAQ to
the V37. The V37 has never worked with the eTrex. However, it works with
serial ActiveSync.

I had hoped for more information from more users, but that doesn't seem
to have happened. I don't know what to do next.

Thank you for all the information. At least I know a ViewSonic with PPC
2003 works for someone.

-Ken


"Floyd Burger" <floyd@adelphia.not> wrote in message
newsmizdt5NEHA.620@TK2MSFTNGP10.phx.gbl...
> I'm running PPC 2003 on mine. Have you checked the baud rate? My eTrex
> only lets me set 4800 for NMEA, but Mapopolis tried everything but 4800, I
> had to change the config from Autodetect to the exact baud.
>
> --
> Floyd Burger

Archived from groups: microsoft.public.pocketpc.developer,microsoft.public.pocketpc (More info?)

"Kenneth Evans, Jr." <evans@aps.anl.gov> wrote in message
news:udLc2wPOEHA.3744@TK2MSFTNGP11.phx.gbl...
> Floyd,
>
> I don't have Mapopolis. I rechecked the baud rate for GPSInfo
> (available free from
> http://www.mobilelinktech.com/corp [...] ort.html). It
> seems to be well written and is apparently a utility for a larger package.
> It uses NMEA. It autodetects (or just defaults) to COM1, 4800 baud. As
> with all the programs I have tried, it works OK on my iPAQ and does not
work
> on the V37. On the iPAQ I only get data if the port is COM1 and the baud
is
> 4800. Other combinations don't work on the IPAQ. This is reasonable and
> consistent with what you said: The eTrex sets 4800 baud with NMEA Out and
> that appears to be the only option. I use 9600 baud with GARMIN and that
> works on all the other Pocket PCs to which I have access.
>

just out of interest, do you have tomtom navigator installed?

Archived from groups: microsoft.public.pocketpc.developer,microsoft.public.pocketpc (More info?)

>> Try shutting down
> ActiveSync, IR receive, anything else in the Running Programs list.

I've done that (and all the usual things).

> I just noticed that you've posted to the pocketpc.developer group (I
> always thought this was only in the pocketpc group), do you have VS 2003?
> If you do, you can write a quick terminal program using OpenNetCF just to
> see what is being received.

I wrote my own GPS program several years ago to up and download waypoints,
plot them on images, etc. It has worked from my old Jornada with the
original PPC to now *except* for the ViewSonic. I know what is being sent
and received, even without using the network analyzer. Nothing is being
received with the ViewSonic. The network analyzer indicates the data is
coming from the eTrex, though.

I do have VS 7.1. I didn't know about OpenNetCF. I did a search inside VS
and didn't get any hits, but it turns up on Google. So far I have avoided
using the .NET stuff on the PPC. What I did was done in EVC with straight
C++. Developing for the PPC has been very frustrating. Too many problems
just like this one.

Thanks, though,

-Ken

Archived from groups: microsoft.public.pocketpc.developer,microsoft.public.pocketpc (More info?)

Ken,

I bought the serial cable from viewsonic for my v37 and it works great with
my garmine 12 gps. It works with pocket streets from MS as well as Delorme's
pda maping stuff.

Skip

"Kenneth Evans, Jr." <evans@aps.anl.gov> wrote in message
news:%23CUvO6gOEHA.3312@tk2msftngp13.phx.gbl...
> On thinking about your question more, the answer is if you get the
Pc-mobile
> cables, you don't a need a null modem and gender changer. You only need
> them if you use the Garmin serial cable and the PPC serial cable. The
> Pc-mobile cables are much less cumbersome IMHO. (Of course, this assumes
> you have a PPC that works in the first place with a serial GPS, unlike my
> V37.)
>
> -Ken
>
>
> "Chris Tacke, eMVP" <ctacke@spamfree-opennetcf.org> wrote in message
> news:utRUnO5NEHA.2708@TK2MSFTNGP10.phx.gbl...
> > So you've verified that a null-modem adapter isn't required by the
> > cable/device?
> >
> > --
> > Chris Tacke, eMVP
> > Co-Founder and Advisory Board Member
> > www.OpenNETCF.org
> > ---
> > Windows CE Product Manager
> > Applied Data Systems
> > www.applieddata.net
> >
> >
> > "Kenneth Evans, Jr." <evans@aps.anl.gov> wrote in message
> > newsIitVI5NEHA.3572@tk2msftngp13.phx.gbl...
> > > I have been unable to get my ViewSonic V37 upgraded to PPC 2003 to
work
> > with
> > > a Garmin eTrex connected through the serial port, and would like to
know
> > if
> > > others have had the same experience.
> > >
> > > It does not work with several GPS programs, including Pocket Streets
and
> > > GPSInfo, as well as my own program. I have tried the ViewSonic serial
> > cable
> > > connected to the eTrex serial cable via a null modem and gender
changer
> as
> > > well as another serial cable from Pc-mobile designed for the
> > ViewSonic/eTrex
> > > combination.
> > >
> > > All of these programs with the equivalent serial cables work on
several
> > > versions of iPAQs as they should.
> > >
> > > It is not the software nor the configuration. It is either my V37,
all
> > V37s
> > > with PPC 2003, or all V37s. Information as to which would be
> appreciated.
> > >
> > > It does sync with ActiveSync using the ViewSonic serial cable. The
> eTrex
> > > only uses pins 2,3, and 5 (of a 9-pin RS-232). ActiveSync also uses
> these
> > 3
> > > pins (plus some others), but the voltages are different. ViewSonic
was
> of
> > > no help. They said only ActiveSync is supported with the serial
cable.
> > >
> > > The V37 serial port is COM1. Using an RS-232 analyzer I have
determined
> > > that the data is going out from the software, is received by the
eTrex,
> > and
> > > the proper response is sent back from the eTrex. It just is never
> > received
> > > by the programs.
> > >
> > > Any information or experiences would be appreciated.
> > >
> > > Thanks,
> > >
> > > -Ken
> > >
> > >
> >
> >
>
>