Remonter

Références pour l'enregistreur de données de GPS Photo Trackr CD-111BT

Références provenant du forum de Gisteq à http://www.gisteq.com/forum

Lecture du Forum de Gisteq : Je suis rendu à la page 8 de 17.   6 janvier 2009.

Étiquetage - Tagging
http://www.gisteq.com/forum/viewtopic.php?f=2&t=470

by Mleo on Sat Nov 08, 2008 8:28 pm

Tagging is not quite what one might expect.

Tagging on the GiSTEQ GPS is not a data point generating operation. Rather, whenever it is locked to the satellites the GiSTEQ GPS device is recording points at the user selected interval, no matter the tagging mode, and tagging simply adds some additional information (the tag) to the current point(s).

If the device is in waypoint tagging mode: when button 1 is pressed and held the next point recorded will be tagged with the value 254.

If the device is in trip tagging mode: when button 1 is pressed and held to activate trip tagging operation, all points from then on will be tagged with the value X, until button 1 is again pressed and held to de-activate trip tagging operation. X is a value in the range 101 and up. It increases in value by one each time trip tagging operation is activated.

Additionally, the first point recorded after either power-on or wake-up from sleep is tagged with the value 99.

The tag values are part of the raw data that is downloaded from the device.

It is up to the software that processes this downloaded raw data to interpret the tag attached to recorded points. A point with a tag of 254 can be used to create a waypoint. A point with a tag of 99 can be used to break up the data into separate tracks. Points with a common tag value in the range 101 and up can be used to highlight a (portion of) a track in some fashion.

The perl script iTU4l.pl and its companion sr2x.pl is the only GPS software that I am aware of that fully exposes this tagging data. Apparently tagging was a feature of the original Wonde Proud GPS device on which the GiSTEQ is based but GiSTEQ chose to limit the PhotoTrackr software to recognizing only waypoint records.

Disclaimer: the above is based on my observations and I am sure it is incomplete and may be misinformed. Perhaps others can fill in some more information.

To answer the original questions:

1) Yes, logging is the same as regular default mode. No, it does not record start and stop time but rather tags all the points in the "trip". And no, recording continues even after the trip end button is hit - it is just the tagging of points that stops.

2) No, waypoint tagging does not exactly record the spot you are in. Rather it tags the next point the device records to note that point as a special point - i.e., a waypoint.

Curiously, this scheme of tagging points can result is some error in the resultant waypoint if you are moving and the recording interval is infrequent. In an extream example, if say points are recorded every minute and you press the button for a waypoint while traveling in a car at 60 miles per hour (a mile a minute), then that waypoint may be recorded up to a minute after you press the button resulting of an error of up to one mile for the waypoint.

Additionally, one cannot record more than one waypoint per recording interval.

Also, the above discussion does not address behavior when the device is in the Recording Mode of "By Distance" rather than "By time". I have no experience with that mode.

PhotoTrackr CD-110BT [aka: CD-110M, BT-CD160MTK], PhotoTrackr Mac V 3.0.1 G, Mac Book Late 2007, Mac OS X 10.5.5 - as of Sep 15, 2008. Mleo Posts: 34
Joined: Thu Jul 31, 2008 5:38 pm

 

 

Boutons et lumières 1
http://www.gisteq.com/forum/viewtopic.php?f=2&t=58
Button and light overview
by MikeB on Fri Aug 03, 2007 10:48 pm

Summary of button and lights on the bluetooth logger. The current documentation does not actually describe very well what button does what, and on my first trip, it was hit or miss to figure out what was happening. (Gisteq, an overview like this would be really useful in the documentation).

Here are the references I am aware of, and the button presses I have worked out or read about. Post any other discoveries as replies to this thread

Power / sound / Lights:
Power on / off: press and hold middle button for approx 1 sec
Volume up: press left button (and expect to hear tone)
Volume down: press right button (and hear tone until sound is off - when you will then hear nothing)
Stealth mode: Press left and right button (approx 3 secs?) to disable all lights.
Same again to enable again. When disabled, it is hard to figure out whether it is
On or Off

Other:
Speak the time: Press and hold left and middle button for approx two seconds. Note the time is UTC
from GPS with whatever local time offset your PC had at the last sync with it.
Disable /enable bluetooth: Press and hold middle button for approx 1-2 seconds
Trip / Waypoint Tagging: Press and hold (how long?) left button to tag a waypoint / trip
(depends on how your unit is setup. See VI, Hardware in Gisteq docs)

Lights overview:
Normal operation: Expect red, green, and blue lights to be flashing like a mini christmas tree
Red light flashing:- GPS signal being received (when no fix, this is off)
Green light flashing - power is on
Blue light flashing - bluetooth active
Stealth Mode: Green power light flashes briefly on power on and power off and no other lights show
You can only work whether it is on or off by the voice announcements about positioning
and lock. If volume is off, it is easy not to be sure about whether it is on or off.
c) Error mode In some cases of internal firmware error, the following light sequence may show. 2 x 4 red
light flashes, then 1 x green, 1 x blue (then repeat). Unit did not log or connect to PC. To
fix, reset (remove then reinsert battery).

What is my unit going to say to me?
Power on: "Satellites Positioning" (If volume not at 0)
Satellite lock "Satellite Fix" [ you hear this only on first lock, and not
thereafter if you go in and out of satellite coverage]
Low battery: "Battery Low" [I haven't heard this, the Xaiox manual says this happens]
Time (left & mid buttons): "X X X X" e.g. " 2 2 3 5" [for 22:35 as I write this]


References: (thanks to someone from another post for #2)
1) Gisteq Photo Tracker User Manual, V1.4 (comes with Bluetooth phototracker).
2) This seems to be the original hardware - I think Gisteq's firmware mods have changed some things slightly, but it is similiar: http://www.xaiox.com/download/xiox_itracku_nemerix_english.pdf See Page #5

Updates:
8-9 corrected bluetooth button to be middle button press
8-20 added error light sequence
Last edited by MikeB on Mon Aug 20, 2007 7:46 pm, edited 2 times in total. MikeB

Posts: 27
Joined: Tue Jun 26, 2007 9:52 pm

_____________________________________________________
A few corrections based on a CD-110BT (you should propably say that somewhere).

-Switching Bluetooth on and off just requires a brief press of the middle button, not 1-2 seconds which will turn the unit on or off.
-The unit will also announce "Bluetooth on" and "Bluetooth off" if sound is enabled when you switch Bluetooth on/off.
______________________________________________________

I've had the Low Battery warning. Really useful as it said 'Low Battery' and then switched itself off. An earlier warning would have been useful.
__________________________________________________

 

Boutons et lumières 2
http://www.gisteq.com/forum/viewtopic.php?f=2&t=445
I have a CD-110BT (with the MTK GPS chip and firmware v4.2).
Button 3 makes no sound when you press and hold the button, unless you set the Tagging Mode to User Adjustable in Settings.
If User Adjustable is set, you will hear one of two sounds when you press and hold button 3:
A simple long tone: Waypoint tagging mode is now enabled.
A musical tinkly sound: Trip tagging mode is now enabled.
Depending on the mode chosen via button 3, pressing and holding button 1 will:
Tag a waypoint (the current location is recorded in memory with a tag).
Enable Tag a trip (all new locations will be recorded in memory with a unique tag).
Disable Tag a trip (if Tag a trip is currently enabled).
You will get an "Uh Oh" sound for the Disable Tag a trip, and a "Ta Da" sound for the other two.
Hope this helps. The results may be different for other firmware and other models. And you may not agree with my description of the sounds. YMMV.

 

Boutons et lumières 3
http://www.gisteq.com/forum/viewtopic.php?f=2&t=302
Button 1 press: volume up
Button 3 press: volume down
Button 2 hold 2 seconds: turn power on/off
Button 2 hold 1 second: toggle bluetooth on/off
Buttons 1 & 3 hold 3 seconds: toggles LED "stealth mode" on/off
Buttons 1 & 2 hold 1 second: announce time with voice
Button 1 hold 2 seconds: set waypoint for current location

Flashing:
Button 1: Red: flashes when it has a GPS fix, off when it is not yet fixed
Button 2: Green: flashes 1x/sec when on
Button 2: Green: flashes 2x/sec when charging
Button 2: Green: off when unit fully charged
Button 3: Blue: flashes quickly when in pairing mode
Button 3: Blue: flashes 1x/sec when bluetooth connected

 

Synchroniser horloge
http://www.gisteq.com/forum/viewtopic.php?f=2&t=305

Compte tenu de l'importance j'ai copié toutes les interventions. Plus facile de suivre le lien ci-haut si on a conservé l'information.

 

 Sync camera time function is bad
by GeoPhoto on Thu May 29, 2008 1:00 pm
The Sync camera time function is not very accurate. The error is about six seconds per minute!!!!!
The computer clock is synchronized with a Garmin GPS receiver and a time server. That receiver can also show the time on its own display. Also, we have a DCF77 time receiver for double checking. All systems show exactly the same time. Only the PhotoTracker time is far from correct. The error gets worse every minute when the time is displayed using the Sync Camera function. The latest GiSTEQ PhotoTrackr Pro software was used (version 2.3.506.0). The camera time sync function certainly needs improvement. Till that time, don't use it!GeoPhoto
Posts: 15
Joined: Thu May 29, 2008 12:12 pm Top
--------------------------------------------------------------------------------
Re: Sync camera time function is bad
by Lawrence on Fri May 30, 2008 11:50 am
I have exactly the same problem. After first getting the GPS, I synched my camera and Phototrackr. The next day, I notice the two had drifted some 30 - 50 seconds from each other (I forget exactly). Thinking that the Camera may have had a bad clock, I synched my dive watch. I was curious to see the amount of drift, and after a minute I saw around 5 or 6 seconds of drift. As I watched I could see the two falling out of synch in real time.

I've not looked into this yet (only happened last night), but I was wondering if it was due to:
a) Poor signal from the satellite in the house (could be fixed by putting GPS at window)
b) Software lag while connecting to the PC (not the end of the world, as long as the GPS itself keeps good time)
c) The GPS has a crappy time chip (in which case I'm foobar'd and will have to accept that by the end of a 7 day trip, my photolocations are going to be approx 10 minutes off).

I've not upgraded the firmware OR phototrakr PC software (I think I saw another thread were people were having some problems with the firmware installation, and figured I'd not risk this 12 hours before I fly).

If there are any site admins, could you let me/us know if this is a known problem??Lawrence

Posts: 4
Joined: Fri May 30, 2008 11:42 am Top
--------------------------------------------------------------------------------
Re: Sync camera time function is bad
by GeoPhoto on Fri May 30, 2008 12:05 pm

Lawrence wrote:
I have exactly the same problem. After first getting the GPS, I synched my camera and Phototrackr. The next day, I notice the two had drifted some 30 - 50 seconds from each other (I forget exactly). Thinking that the Camera may have had a bad clock, I synched my dive watch. I was curious to see the amount of drift, and after a minute I saw around 5 or 6 seconds of drift. As I watched I could see the two falling out of synch in real time.

I've not looked into this yet (only happened last night), but I was wondering if it was due to:
a) Poor signal from the satellite in the house (could be fixed by putting GPS at window)
b) Software lag while connecting to the PC (not the end of the world, as long as the GPS itself keeps good time)
c) The GPS has a crappy time chip (in which case I'm foobar'd and will have to accept that by the end of a 7 day trip, my photolocations are going to be approx 10 minutes off).

I think it is a programming error in the PhotoTrackr software itself, not the firmware. What the programmer probably did is when you select the camera time sync function, it reads the current time from the GPS. Then the time and date is displayed, then a one second sleep delay is called, and then the seconds on the display are incremented. That is poor programming since you get an incremental error. And that is exactly what happens. After each minute, the time displayed is nearly six seconds behind. Even a 200 years old mechanical clock performs better. So we can only hope that they fix this bug soon. In the mean time, don't use this function, but find some reliable time source. You may go to http://www.timeticker.com for example. The time from that site is good enough for our purpose (error less then two seconds). A time receiver or a GPS with time display is more accurate.GeoPhoto

Posts: 15
Joined: Thu May 29, 2008 12:12 pm Top
--------------------------------------------------------------------------------
Re: Sync camera time function is bad
by Lawrence on Thu Jun 19, 2008 7:39 am

Yeah, you might be right. I was kinda hoping that the problem was not with the GPS clock, or the camera clock, but instead, just programmer error. It just did not make sense that a GPS clock (whether a local clock chip, or from the satellite itself) would drift like that.

I recently returned from a trip, and the tracks generated by the GPS seem to be okay (from a quick look). I'd like to see how good they were in terms of time, but my damn RAID choose this moment to kack.Lawrence

Posts: 4
Joined: Fri May 30, 2008 11:42 am Top
--------------------------------------------------------------------------------
Re: Sync camera time function is bad
by PsynceFiction on Mon Jul 14, 2008 6:08 am

I'm having the same problem here. Synchronised my camera with the DPL700 and 4 hours later my camera is 6" "off".

What can be done to this problem??PsynceFiction

Posts: 2
Joined: Mon Jul 14, 2008 2:40 am Top
--------------------------------------------------------------------------------
Re: Sync camera time function is bad
by Jesper on Thu Jul 17, 2008 11:16 am

Are you aware that GPS time is not the same as UTC / GMT time?
If you compare GPS time with your computer clock, which might be set to UTC or some other timezone setting, you'll notice that they are a few seconds apart.
That's deliberate. See: http://en.wikipedia.org/wiki/GPS_time#GPS_time_and_dateJesper

Posts: 4
Joined: Thu Jul 17, 2008 1:56 am Top
--------------------------------------------------------------------------------
Re: Sync camera time function is bad
by GeoPhoto on Thu Jul 17, 2008 11:35 am

Jesper wrote:
Are you aware that GPS time is not the same as UTC / GMT time?
If you compare GPS time with your computer clock, which might be set to UTC or some other timezone setting, you'll notice that they are a few seconds apart.
That's deliberate. See: http://en.wikipedia.org/wiki/GPS_time#GPS_time_and_date

If the time difference was never more than a few seconds....
The error Gisteq made is incremental, and that is a classic one. That is caused by poor programming. It takes Gisteq a long, long..., very long time to correct. So for the time being you better use the 200 years old antique clock that does a better job.GeoPhoto

Posts: 15
Joined: Thu May 29, 2008 12:12 pm Top
--------------------------------------------------------------------------------
Re: Sync camera time function is bad
by gewe on Tue Aug 05, 2008 4:17 pm

Hello, same problem here:

The difference between
the time displayed by the photrackr software and my radiocontrolled clock grows by 5 seconds every minute.

Regards
gewegewe

Posts: 4
Joined: Thu Jul 31, 2008 2:27 am Top
--------------------------------------------------------------------------------
Re: Sync camera time function is bad
by gisteq on Wed Aug 06, 2008 10:25 am

Hello,
As long as The PhotoTrackr device is with 30 seconds of the Camera time, it will tag the pictures correctly.
Thank you
Tech Support
GiSTEQgisteq
Site Admin

Posts: 283
Joined: Thu Jun 07, 2007 1:08 pm Top
--------------------------------------------------------------------------------
Re: Sync camera time function is bad
by GeoPhoto on Wed Aug 06, 2008 11:06 am

gisteq wrote:
Hello,
As long as The PhotoTrackr device is with 30 seconds of the Camera time, it will tag the pictures correctly.
Thank you
Tech Support
GiSTEQ

If you never move from same spot, you won't need a PhotoTrackr either. In other words, Gisteq is not going to solve this silly bug?
Why not make the software open source? There are some very talented programmers out there who can fix the bugs and add some fancy features all for free.
At the moment I am using GeoSetter which is free software, and has some nice features that GiSTEQ PhotoTrackr Pro software doesn't have.

Selon Gisteq
http://www.gisteq.com/forum/viewtopic.php?f=2&t=404
The clock data is always downloaded from the GPS satellite data, so you'll have no problems.
______________________________________________________

Selon Gisteq

Hello,
As long as The PhotoTrackr device is with 30 seconds of the Camera time, it will tag the pictures correctly.
Thank you
Tech Support
GiSTEQ

 

Antenne extérieure
http://www.gisteq.com/forum/viewtopic.php?f=2&t=389
Yup. Gisteq support replied with basically the same point: if there is no connector for an external antenna then it's the MTK version.
But they ought to update the darn manual so that it doesn't still describe the old hardware. Not to mention the inconsistent model numbers, etc.
But for the moment I'm happy. Still trying to figure out all the quirky lights, though.

 

Capacité de la mémoire
http://www.gisteq.com/forum/viewtopic.php?f=2&t=446
The PhotoTrackr is advertised to be able to store about 250000 points.
4MB flash memory for data logging, with 16 bytes binary data per record that stores up to 250K
You can store 250.000 points.
When you store every 15 sec. a point, than you can 250.000 * 15 = 3.750.000 sec. store your position.
That is more than 43 day's (24 hours a day)
I have read somwhere that, when the memorie is full, it begins to write over from the begin.

 

User's Manual

4MB flash memory for data logging, with 16 bytes binary data per record that stores up to 250K

 

Éditer et conversions des fichiers .GPS 1
I had the same questions when I first used my tracker.
Here is what I do and it works ok.
Use a text reader, like notepad.
make one long document by sequentially adding the log files.
Each log file has a "-pp" at the beginnng.
Use the find and replace funcion of the program and remove all "-99" and replace it with "---".
Leave the first "-99" at the beginning of the file.
After the software removes all the extra "-99", rename the file and use that with the trackr software.
This gives me a single track for the entire journey.
I hope this helps.
Conversion des fichiers d'enregistrement .GPS
http://www.gisteq.com/forum/viewtopic.php?f=2&t=196
Check this website: http://www.gpsvisualizer.com/convert
Here you can convert .gps files
Maybe try gpsbabel?
Check http://www.gpsbabel.org/capabilities.html for all supported filetypes.

 

Éditer et conversions des fichiers .GPS 2
http://www.gisteq.com/forum/viewtopic.php?f=2&t=264
Re: Import/Convert files
by justinribeiro on Mon Jun 30, 2008 12:28 am
You might try GPSBabel: http://www.gpsbabel.org/
It will convert GPX to NEMA, but you have to use the gistek option as noted on the following linked page:
http://www.gpsbabel.org/htmldoc-development/fmt_nmea.html
The reason according to the folks there is because "the logging format used by the Gisteq hardware is very close to NMEA format, but with a few small quirks." There was a thread on the GPSBabel mailing list a while back that this option will create the proper *.GPS file for use importing into PhotoTrackr.
Hope you find this helpful and does what you're looking for.
Cheers, Justin

 

Fichier Log
Nombre de satellite utilisé pas Gisteq
http://www.gisteq.com/forum/viewtopic.php?f=2&t=256
Dans ces lignes le 08 indique le nombre de satellite interogé.
$GPGGA,080338.000,4620.4302,N,02548.4000,E,1,08,00.0,661.0,M,00.0,M,,*6F
$GPGGA,080342.000,4620.4580,N,02548.3824,E,1,08,00.0,659.0,M,00.0,M,,*6C
$GPGGA,080346.000,4620.4853,N,02548.3632,E,1,08,00.0,658.0,M,00.0,M,,*63
$GPGGA,080350.000,4620.5123,N,02548.3440,E,1,08,00.0,656.0,M,00.0,M,,*62
À cela gisteq répond
Re: PhotoTracker Lite log always shows 8 available satellites
by gisteq on Tue Apr 29, 2008 1:25 am
Because of the limitation of the memory storage (to fit 250,000 data points), we can only store certain information in the tracker. Satellite number is one of the information we intentionally left out while recording the data in each binary record - we simply put "8" on all NMEA data when exporting from our binary record to NMEA.

 

Batteries 1
http://www.gisteq.com/forum/viewtopic.php?f=2&t=417
Re: Battery life - take spare batteries!
by freewilly on Wed Aug 27, 2008 4:12 am
With GP 2300 mAh rechargeable batteries, my DPL700 run for about 7 - 8 hours with full charged batteries.
My PT is always on, and I don't use the vibration sensor. (vibration sensor disabled).
The PT write every 6 sec. my position to the flash memmory.
I take always a few reserve batteries with me, and it don't take much place.

 

Batteries 2
http://www.gisteq.com/forum/viewtopic.php?f=2&t=370
by libeco on Wed Jul 30, 2008 1:37 am
With regular non-rechargable batteries I managed to get about 12 hours from a full battery. Won't you have any electricity around on your cycle trip? Maybe a solar cell charger is an option?
by freewilly on Tue Jul 29, 2008 9:40 am
I use GP 2300 mAh rechargeable batteries and my DPL700 run for about 7 hours with full charged batteries.

Les batteries durent 7 heures avec une rechargeable et 12 heures avec non rechargeable.

 

 

mwl

 

 

 

 

Au besoin Cliques ici pour m'envoyer un courriel.

Dernière modification : 11 janvier 2017.