Hello Alan This may be a stupid question, but have you checked control panel? In my cheapo PNA there was a control panel item that told in clear language what are the GPS settings (com port & speed) coupled with some other settings for the GPS. After that it was just needed to enter them in XCSoar and that's it. The name of the applet depends on the GPS unit installed, so it may be almost anything ;)
hannu On 21.2.2011 2:14, Alan Wilson wrote: > Gentlemen, > > I have a comparable issue getting XCSoar operating with my latest a YFLeader > cheap [$50] car GPS. I have installed Pez GPS unlock. I have all the XCSoar > screens working. And I have Windows CE operating. [Great, why don't all GPS > start with Windows CE] > > But the system does not recognize the GPS signal. It keeps saying 'unable to > open COM1' even though I have selected other comm ports from XCSoar config > "System Setup" page 9 "Devices". > > Is there some way I can activate similar programs. > > Or in short get XCSoar recognizing the presence of the internal GPS? > > Alan Wilson > Canberra Australia > > -----Original Message----- > From: Ronald Niederhagen [mailto:ronald_niederha...@freenet.de] > Sent: Monday, 21 February 2011 2:21 AM > To: xcsoar-user@lists.sourceforge.net > Subject: Re: [Xcsoar-user] Stupid connection question > > I don't know the HP310, so I can't help you with that. I'm using the > hx4700 and the Compaq 3870 with a FLARM. > > For XCSoar: > Got to "System Setup" page 9 "Devices". > Device A: > Name: Generic > Port: COM1 (that may be a different port number for your HP310) > Baudrate: 19200 > Device B: select the exact same settings as Device A. > > Configuring the FLARM device: > You must set the baud rate to 19200 to match the setting in XCSoar. > Instructions are on the FLARM page at: > http://www.flarm.com/support/manual/index.html > In the DataportManual is the description of the "Sentences" you need to > configure the FLARM device. > $PFLAC,S,BAUD,2 > The above sentence will set the FLARM to 19200 Baud. Write that sentence > to a file called flarmcfg.txt . Copy that file to an empty microSD card. > Switch the FLARM off, insert the card, switch the FLARM on and wait > until it shows the normal flashing Send light. > > You can also use the Flarmtool from that page > http://www.flarm.com/support/updates/index.html to configure the FLARM > device. This is useful when your FLARM has no microSD slot. But you need > a cable to connect your computer's COM port with the FLARM and a power > supply for the FLARM. > > Good luck. > Ronald > > > Am 19.02.2011 18:47, schrieb martin.kopp...@gmx.de: >> Moin, >> >> until now, I have only used XCSoar on my HP310 as a standalone device, not >> connected to any other instrument. >> >> I have now been trying to connect it to my Flarm device in order to use the >> same GPS data and also get the flarm warnings displayed on the HP, and also >> use the flarm as another logger. The Manual has nothing here. Now ... I'm >> kind of stuck. >> >> I do not have any information on how the settings should be for this >> connection. >> Com Port? Baud rate? What device device type for connecting with flarm? >> >> And then: How to check? As far as I understand, there will be no flarm >> display unless flarm traffic is close, so what will I see once it works with >> no traffic in my area? >> >> The only feedback I have so far is that when trying to declare I get a >> message "No Logger Found" or so. >> >> >> Viele Gr��e, >> Martin Kopplow >> >> --- >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Xcsoar-user mailing list >> Xcsoar-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/xcsoar-user > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Xcsoar-user mailing list > Xcsoar-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcsoar-user > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Xcsoar-user mailing list > Xcsoar-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcsoar-user ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
