Thread: GPSTracker on home server

Originally Posted by Cerberus

Ah ha! Mine constantly says connected!

I had wrongly thought it referred to the
Gps.

Do i need to turn the ping option on?
Will that make it realise it isnt really
Connected?

Cheers!
C

Good, we've found the issue. The problem is how to fix it. Ping doesn't do what you suggest. Its just there to see if the server is on. So you might have a network connection but have switched off your server. This problem is that your windows thinks you have a network connection but its not one that connects to the internet.

Can you try the following. Look at what connections you have and disable them and only leave the one you need enabled. If you say "but I only have 1" then we need to find out why its allways connected. Can you post what it is and what it does.

[Edit] had a play and i've added a check now for internet. It looks for www.microsoft.com and if finds it assumes there is a network otherwise fails network check.

Originally Posted by lambosprit

Good, we've found the issue. The problem is how to fix it. Ping doesn't do what you suggest. Its just there to see if the server is on. So you might have a network connection but have switched off your server. This problem is that your windows thinks you have a network connection but its not one that connects to the internet.

Can you try the following. Look at what connections you have and disable them and only leave the one you need enabled. If you say "but I only have 1" then we need to find out why its allways connected. Can you post what it is and what it does.

[Edit] had a play and i've added a check now for internet. It looks for www.microsoft.com and if finds it assumes there is a network otherwise fails network check.

I only have the wireless and the wired. Neither of which have an IP when i'm off the driveway...

I might be confused... but...

If the client believes it has network then it sends the xml data and marks
it as 'true' ?

Does the server reply back to acknowledge receipt?

Shouldn't your check for internet check the tracking server rather than
microsoft? Because if the client has internet but the server is offline
then the xml data is just going into a black hole. Unless there is an ack
from the tracking server?

Cerbie is confused...

C

Originally Posted by Cerberus

I only have the wireless and the wired. Neither of which have an IP when i'm off the driveway...

I might be confused... but...

If the client believes it has network then it sends the xml data and marks
it as 'true' ?

Does the server reply back to acknowledge receipt?

Shouldn't your check for internet check the tracking server rather than
microsoft? Because if the client has internet but the server is offline
then the xml data is just going into a black hole. Unless there is an ack
from the tracking server?

Cerbie is confused...

C

I dont know how microsoft decides whether it has a network connection or not so I dont know if its ipaddress dependant. Anyway i think with the changes I've made it shouldn't matter.

The client tries to sync with the server and if it doesn't connect then it gets marked as false. This has a hole in that it assumes the server not only recieves the data but has stored it successfully.

The problem here is that the false ones are only resent when a network becomes available again and because it never goes away, it never comes back, so it never resends...if that makes sense. The new exe allways tries to resend in the period set so regardless of whether a network appears or not it will resend any false. So in short it should work alot better. Try it and report back please.

Originally Posted by lambosprit

I dont know how microsoft decides whether it has a network connection or not so I dont know if its ipaddress dependant. Anyway i think with the changes I've made it shouldn't matter.

The client tries to sync with the server and if it doesn't connect then it gets marked as false. This has a hole in that it assumes the server not only recieves the data but has stored it successfully.

The problem here is that the false ones are only resent when a network becomes available again and because it never goes away, it never comes back, so it never resends...if that makes sense. The new exe allways tries to resend in the period set so regardless of whether a network appears or not it will resend any false. So in short it should work alot better. Try it and report back please.

Ahhhhh. Yes, makes sense now

I will put it on the PC before I drive home from work and see what happens.

Do you think I will suddenly get 3 days of data sent across? I haven't
seen any data set to false in the xml on the client. Maybe you aren't
holding data in the xml until it is sent tho?

I'm thinking too much. I'll try it tonight on way home and let you know

C

This new version errors. Didn't see exactly what the error was as I
was driving and I forgot to restart the app when I got home.

I do recall I had an option to continue and an option to quit. If
I chose continue it just errored again. Quit, closed the app. The
error said soemthing about 'root' *shrug*

I'll get a better look at it later

C

Any news cerberus. I've tried it myself now and it works flawlessly for me. If you can post the message you get I can help fix it.

Ooops! sorry I forgot all about it!

Error is "Root element is missing"

Hope that makes more sense to you than me!



C

Originally Posted by Cerberus

Ooops! sorry I forgot all about it!

Error is "Root element is missing"

Hope that makes more sense to you than me!



C

it does. I dont know why it does it because I haven't been able to replicate it in debug but when it tidies up the xml (ie deletes older than 30 day data) sometimes it corrupts it.

To fix (and I know its bad) either delete or rename your tracking.xml. Can you send me the xml file so I can see what's corrupted. As I say I cant reproduce so any info is good.

Originally Posted by lambosprit

it does. I dont know why it does it because I haven't been able to replicate it in debug but when it tidies up the xml (ie deletes older than 30 day data) sometimes it corrupts it.

To fix (and I know its bad) either delete or rename your tracking.xml. Can you send me the xml file so I can see what's corrupted. As I say I cant reproduce so any info is good.

Yep, Dumped the XML file and it created a new one and ran fine.

It doesn't say 'connected' when I'm away from home anymore. But it
doesn't seem to when I'm home and connected to the wireless either.

Didn't get any pins from the journey I just took. But I was only out
for 5 minutes (corner shop, should have walked really but I had a
good excuse to drive!). Except the now customary driveway pin
of course!

Dodgy xml attached

C