| Versions |
  |
|
| Author |
 Topic  |
|
jefcoop
USA
15 Posts |
 Posted - 28 févr. 2009 : 20:30:25
|
I looked again- the wires are definitely soldered in.
Thanks for the help- I'll wait it out, since a replacement wouldn't ship anyways until Monday.
Assuming I get a new one, I'll try it out, but I won't do anything "radical" until I have retrieved the trip's logs when I return later in March.
Thanks,
Jeff
|
 |
|
|
jefcoop
USA
15 Posts |
Posted - 01 mars 2009 : 01:44:23
|
With the LEDs all on, the device battery drained fairly quickly. Being hopeful, I plugged it into the computer and the charge light came on (that was the only thing working earlier today). After a few minutes, I powered it up, and it does seem to have recovered somewhat. It's dark now, but will take it out on a mini-trek tomorrow.
I reverted to using V4 for now. The first time I tried to read data, it said device was unknown (though it had successfully connected to it). The device itself seemed to act normally, i.e., I did a 30s log on my desk and the LED's behaved normally, but V4 couldn't read the data.
Then I downloaded the ephemeris data and wrote it to the device, which seemed to work. And then I tried to read the log again, and voila, it worked. So will let it recharge fully and take it out tomorrow and see how it does. I don't think I will even let V4 erase the logs until after my trip- I don't want to go through this again as I'm running out of time.
So whatever happened, the device got hung up. Whether simply erasing memory did it, or some combination of what I did in BT747 and the crash of that application for some reason- perhaps that crash left the device in a "Connected" state it couldn't recover from. Could have been any number of things. It did seem that after the erase, in BT747, I could still see the device. It was only after the app crashed that things went to hell.
Have you folks had BT747 hang? If so, did it have any effects? I don't know the nuances of what the device does or what state it's in when "Connected". Could be a combo of app crash and crappy firmware, who knows.
I thank you all for help- will post once more after my mini-trek once I confirm it's fully operational.
Thanks,
Jeff |
|
|
|
gpspassion
93389 Posts |
Posted - 01 mars 2009 : 01:48:36
|
Excellent news, hope the logging goes ok on your trek and I wouldn't erase the data with any software until you have retrieved the data you want.
Can't remember a freeze with BT747, and if it did, it never left one of my loggers in that state! |
Discounts and Assistance/Réductions et Assistance (Club GpsPasSion) / Où commencer? |
|
|
|
cdgmol
Netherlands
85 Posts |
Posted - 01 mars 2009 : 03:04:14
|
quote:
Originally posted by jefcoop at 03/01/2009 : 01:44:23
but V4 couldn't read the data.
A reply without looking into my "archive". I thought that the Qstarz software is no longer compatible if you configured the device with BT747, especially when changing the format items.
So, I did a quick check. V4 starts reading the log normally, but at the end "Failed to read data from GPS module!".
Jeff, have a nice trip or vacation, maybe with a working GPS logger.
[Edit/added]
If you use (configure with) PC Utility V3, you have the same problem. Qstarz have done this to protect their V4 (replaying) software. However, they did not listen/respond to my suggestion that the device should be used as a dongle for this purpose.
|
Chris |
Edited by - cdgmol on 01 mars 2009 14:18:17 |
|
|
|
jefcoop
USA
15 Posts |
Posted - 01 mars 2009 : 07:43:55
|
Hi Cdgmol,
I couldn't read it with BT747 either afterwards, but thanks for the warning as well. I only erased in this case- I didn't use format. I'm going to be *very* careful with it for a while at least, until I get a better hang of it and of BT747.
I will mini-trek tomorrow to double check that everything is fine, since worst case I could still overnight a new one on Monday if I absolutely had to. But I think this fella has recovered. :)
Jeff |
Edited by - jefcoop on 01 mars 2009 07:45:39 |
|
|
|
jefcoop
USA
15 Posts |
Posted - 02 mars 2009 : 21:24:46
|
I had a successful mini-trek yesterday, so things are looking good. The device appears to have recovered.
Thanks for the help and support.
Jeff |
|
|
|
cdgmol
Netherlands
85 Posts |
Posted - 03 mars 2009 : 15:28:42
|
I have not saved all my tracks in NMEA too, so I wanted to convert some GPX files to NMEA using GPSBabel. The processing is OK, but not the results. For the following examples I used a track of which I have both (BT747 created) GPS and NMEA (and csv too).
Using "GPX XML" as input, the "NMEA 0183 sentences" output file contains only this kind of lines:
---,$GPRMC,110025.000,A,4714.231,N,01153.941,E,1.77,0.00,250109,,*06
The related lines in the BT747 NMEA are:
$GPRMC,110025.000,A,4714.230996,N,01153.941026,E,1.766,,250109,,,A*41
$GPGGA,110025.000,4714.2310,N,01153.9410,E,1,7,1.23,525.806,M,46.4,M,,*5A
$GPZDA,110025.000,25,01,2009,,*5C
Note. The $GPRMC lines are (apart from rounding's and starting with ---,) not identical.
The trackpoint in the BT747 GPX with the same timestamp is:
<trkpt lat="47.23718327" lon="11.89901710" >
<ele>572.206</ele>
<time>2009-01-25T11:00:25.000Z</time>
<speed>0.9087</speed>
<name>trkpt-2009-01-25T11:00:25.000Z</name>
<cmt><![CDATA[IDX: 15020<br>TIME: 25-JAN-09 11:00:25<br>RCR: D <b>(DistanceStamp)</b><br>VALID: SPS<br>LATITUDE: 47.237183 N<br>LONGITUDE: 11.899017 E<br>HEIGHT: 572.206 m<br>SPEED: 3.271 km/h<br>HDOP: 1.23<br>DISTANCE: 5.48 m]]></cmt>
<sym>DistanceStamp</sym>
<type>D</type>
<fix>3d</fix>
<sat>7</sat>
<hdop>1.23</hdop>
</trkpt>
Any idea why I get unusable NMEA output files?
Is it related to GPSBabel or to BT747 (or to me)? |
Chris |
Edited by - cdgmol on 03 mars 2009 15:51:14 |
|
|
|
mdeweerd
798 Posts |
Posted - 03 mars 2009 : 16:04:08
|
I am not sure what your problem is.
The values from GPSBABEL seem more or less ok.
You can read more about NMEA here : http://home.mira.net/~gnb/gps/nmea.html#gprmc
BT747 uses 3.0 NMEA for this sentence and does not fill unknown values as set out by the NMEA specification (e.g., the heading is 0.00 in gpsbabel and empty in BT747). Apart from that last remark, the rounding and the NMEA sentence version, the GPRMC sentences are "the same".
If you want the other sentences in GpsBabel, you probably need to check out the gpsbabel options.
BT747 can read GPX too.
BT747 can be configured to output only GPRMC.
|
|
|
|
cdgmol
Netherlands
85 Posts |
Posted - 03 mars 2009 : 16:49:31
|
quote:
Originally posted by mdeweerd at 03/03/2009 : 16:04:08
I am not sure what your problem is.
The values from GPSBABEL seem more or less ok.
Thanks Mario for your response and the very informative link.
My "only" problem is/was that I needed the conversion and GpsAR could not read the GPSBabel output. But I don't need the conversion for GpsAR, it was only a check before transferring to my PocketPC where I will use it for GpsGate and GPS Tuner.
Note. I don't know if I need $GPGGA or $GPZDA there (I've to try or study the NMEA info).
I've tried a GPSBabel output now with GpsGate and that's OK. So, it seems to be a GpsAR problem and that's no (real) problem for me. It was only a little bad luck that I choose GpsAR for checking.
Thanks for your assistance. |
Chris |
|
|
|
cdgmol
Netherlands
85 Posts |
Posted - 06 mars 2009 : 16:46:59
|
quote:
Originally posted by cdgmol at 03/03/2009 : 16:49:31
I've tried a GPSBabel output now with GpsGate and that's OK. So, it seems to be a GpsAR problem and that's no (real) problem for me. It was only a little bad luck that I choose GpsAR for checking.I am not sure what your problem is.
But in the GPSBabel documentation I saw that GPRMC don't include the altitude, so I had to continue with GPSBabel (using mainly the GUI version). I tried a lot, but no GPGGA. During my "study" I also came at the download page and thus I checked my version. That was 1.3.5 dated 4-5-2008 and the newest was V1.3.6 dated 4-11-2008. Well, it was mainly a matter of routine to update the program. But the result is that the conversion from GPX to NMEA works now as I needed and expected!!!
The default output contains RMC, GGA and VTG and not that strange "prefix" anymore. Using the options (of the GUI version) works now too. So, the conversion problem was due to a bug in V1.3.5. |
Chris |
|
|
|
mdeweerd
798 Posts |
Posted - 06 mars 2009 : 20:10:13
|
| Why do you not use BT747 to convert to NMEA? |
|
|
|
cdgmol
Netherlands
85 Posts |
Posted - 06 mars 2009 : 20:22:38
|
quote:
Originally posted by mdeweerd 03/06/2009 : 20:10:13
Why do you not use BT747 to convert to NMEA?
Mario, I still don't have installed/used the desktop version, but maybe it's time for that now.
I'm using the BT747 NMEA outputs for replaying in GPS Tuner and I've seen that they don't contain satellite info. A 'GPS Tuner' output contains $GPGSA and a $GPGSV strings and my outputs has only RMC, GGA and ZDA. In the raw data is, at least, the number of satellites (total and active) available because "NSAT (USED/VIEW)" is in the CSV outputs. But whether or not the signal quality is available too, is it already possible to output that info by changing some settings? Or do you have to modify BT747?
Note. I have saved all the raw data of my vacation in 2 BT747log.bin files (copied that file before erasing the memory and starting new "Get log"). |
Chris |
|
|
|
mdeweerd
798 Posts |
Posted - 06 mars 2009 : 20:35:46
|
Hi Chris
BT747 outputs all the data in the CSV file if these fields are selected (Filter tab, then FMT tab).
Regarding NMEA in the PDA oriented version, you need to go to the 'Othr' tab, then 'NMEA file' and there you need to activate GSA and GSV.
|
|
|
|
cdgmol
Netherlands
85 Posts |
Posted - 06 mars 2009 : 22:23:47
|
Thanks Mario, I still have to learn something (maybe a lot). 
Fortunately, at Flt/FMT all items are checked. And at Othr/NMEA File I've now checked GSA and GSV too.
BTW, your documentation is clearly for this. But then I saw in the manual at page 16:
quote:
Be careful to have at least one regular sentence set to a value other than 0, otherwise the Bluetooth connection will no longer work.
Nothing is set at the moment! Could that be the reason that I had BT connection problems (until GpsGate resolved that problem)?
Greetings. |
Chris |
Edited by - cdgmol on 06 mars 2009 22:24:53 |
|
|
|
mdeweerd
798 Posts |
Posted - 06 mars 2009 : 22:40:38
|
| That quote concerns the "NMEA Output" settings (not "NMEA File") and yes, as the documentation indicates, if everything is '0', you have Bluetooth problems so it could be related (I do not understand how GpsGate solves that though). |
|
|
|
Topic |
|
|
|
| This page was generated in 2,33 seconds. |
 |
|
- 
- 
MTK Loggers - Configuration software - BT747
