Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Sorry if I was unclear. It happen often because of my bad English skills.

I mean that antenna inside of device wasn't attached properly. It was hanging with wires but wasn't attached with screws or glue.

Rookie

the only disadvantage over TrainigGymPro is that waypoints (and therfore also routes) created with ST have no Altitude. So feel free to change that.

If the waypoint has elevation set, it will be transferred to the device. I retested waypoints with 580P and tried to review the code for 625M and did not find any problem.
Have you set the elevation for the point?
If exporting an activity as a route, does the activity have elevation? (You can add that with ElevationCorrection)

I got a GH625-XT a couple of weeks ago to replace a GH615B which had served me well for the last 6 years. In general I'm pleased with the new watch (I mean to write a fuller 'report' in another thread soon). There is one serious problem I've run into, though, which is potentially a show-stopper, and I'm surprised no-one else on here has been affected by it. Once in a while, when I get back from a run and upload the data to SportTracks, I find that the track is wildly inaccurate, all over the place - and by inaccurate, I mean maybe even hundreds of metres from where I was! It's happened 4 times now, and with the latest one just now, it actually records my start point as a point over 200 metres from my house. The rest of the time, on all the other runs, it's incredibly inaccurate.

Three of the times the problem has occurred with a run starting at my house, and the other time was after leaving another building, so in each case this has in effect been starting the watch from 'cold' having just turned the watch on, and getting a satellite fix afresh. It's not occurred at all when I've reset my watch while out running, so this may give a clue as to where the problem lies. On each occasion the watch has indicated that it has a proper satellite fix and is ready to go, so it's the not the case that I'm starting to run before the watch is ready.

Just to be clear, the problem is with the watch, not the data upload, because I've noticed a clearly inaccurate distance reading on the watch before doing the upload.

I thought (and hoped) that it might be a firmware issue because the watch had version 1.0 firmware on it when I got it, so I upgraded it to the latest firmware last week. But the problem has occurred again today with the latest firmware.

Could it be a fault with this particular watch? It doesn't seem likely to me given that 9 times out of 10 the accuracy is spot on - I would have thought it would be wrong all the time or not at all.

my device rattles also but i can live with it unless it's fully opperational 

Dear gpssport

Thank you for your share information 

Have a nice day

Best Regards,
Angela

Dear Rookie

you mean your friend's device no antenna inside the device??

Thank you and have a nice day

Best Regards,
Angela

One of my friend reported similar rattling and he open device by himselves and located it loose antenna. He told that it wasn't clued at all inside of device and that's why it rattle.

Rookie

Buying GH-625XT in Nederland, gewoon te koop bij gpssport.eu daar is ook de GB580P te koop www.gpssport.eu

Sending the NMEA cold start command

Code: [Select]

$PSRF101,0,0,0,0,0,0,12,4*10doesn't report firmware version, instead I'm getting

Code: [Select]

$PSRF150,1*3Eand if I've enabled Development Data, I'm also getting

Code: [Select]

$PSRF156,23,1,0*09
and

Code: [Select]

$PSRFTXT,

nmeaNoOpHandler: id:156  pMsg:23,1,0*09



*0A
and a number of these:

Code: [Select]

$PSRF150,1*3E

$PSRFTXT,

nmeaNoOpHandler: id:150  pMsg:1*3E



*42
Trying to enable WAAS/EGNOS

Code: [Select]

$PSRF151,01*0Fgives me

Code: [Select]

$PSRFTXT,

nmeaNoOpHandler: id:151  pMsg:01*0F



*73

and

Code: [Select]

$PSRF156,23,1,0*09

$PSRFTXT,

nmeaNoOpHandler: id:156  pMsg:23,1,0*09



*0A

I have no problems with enabling or disabling GGA/GLL/GSA/RMC/VTG/ZDA output, or doing a warm start, cold start, factory reset, or enabling/disabling development data.

I have tried this both under Windows (running GPSinfo as a normal user and as an adminstrator), and under Linux (both as a normal user and as root).

While I can live without being able to see the firmware version, I would really like to be able to enable EGNOS.

Have the commands changed or if they haven't, is there a way to fix this?

No, it doesn't need to be configured in order for it to work.

Are you outdoors under an open sky?

Can you push the cold start button to "reset" it and see if it'll get a GPS fix afterwards?

-Jesse