bluehunt
Posts: 2
Joined: Fri Aug 03, 2007 2:16 pm

various problems

Fri Aug 03, 2007 2:40 pm

first of all i would like to congratulate you on this great piece of software.
i have a device that transmits the gps position using GPRS.
basically i have 3 problems.

problem 1.
i have found no way to separate the users.
for instance i would like "user1" to see: "car1", "car2", "car3"; "user2" to see "car4", "car5", etc.
what happens now is that every user can see all cars.
this is the most important problem that i face.

problem 2
with the default settings i have not managed to make the device communicate with the server. i have tried all combinations of user id and vehicle id trying to input the IMEI of the device with no results.
a have tried to use a different approach. i installed gpsgate client and this method works with no problem (device sends the data to a gpsgate client installed on a computer; gpsclient sends the data to the server.) everything ok. big disadvantage: each device needs a separate computer with a gpsclient installed.
i was not happy with this so i searched the forums and found a topic about PipeUdpSettings.xml. using the provided example it was very easy to set the device to send data directly to the server. disadvantage: each device needs a different port opened on the server machine.
i can live with that, though it would be nice to have all the devices send the data to the same port.

problem 3
is there any chance that i could use a different map provider ? is there any way that i can set the server to work with another API ? (mapquest, yahoo etc.)
it is a feature that will benefit all users which live in countries for which google does not provide detailed maps.
this is a kind of feature request more than a problem that i face.

thank you

P.S. please excuse any spelling and grammar mistakes; english is not my native language

User avatar
johan
GpsGate
Posts: 15145
Joined: Wed Aug 04, 2004 10:40 pm
Location: Sweden
Contact: Website

RE: various problems

Fri Aug 03, 2007 3:05 pm

problem 1

There are no "groups" in VehicleTracker 1.1, what you can do is to create multiple VehicleTracker applications. When you log in as SiteAdmin you can create more Vehicle Tracking applications, each with its own set of administrators/operators and vehicles.

problem 2

This is a protocol issue. It all depends on what kind of protocol your device uses.

1. Some GPS/GPRS devices only send a pure NMEA data stream. The problem is that it is not "authenticated", there is no way to see who sends the stream. Since the device will have a different IP address each time, you can not use that information, and you don't see the IMEI number unless it is included in the stream by the client.

2. Some other GPS/GPRS devices has their own proprietary protocols, which includes IMEI number and other data.

3. Some devices send a pure NMEA data stream with IMEI number embedded.

4. Some devices support our native GpsGate Protocol.

Case 1 & 3 will work with the dedicated port numbers in our "Pipe" solution, which you have used. More info on that solution here:
http://franson.com/forum/topic.asp?TOPIC_ID=5657

Case 2 needs a protocol adapter on the server. In GpsGate Server 1.1 we support GlobalSat and StarsNav, more will be supported soon.

Case 3 can be improved by "catching" the IMEI number, currently you need a separate protocol adapter for each type of device.

Case 4 this is the protocol used by all our client products, and some partner products (more to come.)

Note that the "Pipe" solution does not work on GpsGate.com only for GpsGate Server.

If you know that the IMEI number is sent in the stream to the server, we can help you to implement support for it. Do you have any link to the device you use? Do you have any link to the protocol specifications?

Please send it to use here:
http://franson.com/gpsgateserver/support.asp

problem 3
What we can offer right now as an alternative is to import a custom map, as described here:
http://franson.com/forum/topic.asp?TOPIC_ID=5654

Regards,
Johan

Franson Support

bluehunt
Posts: 2
Joined: Fri Aug 03, 2007 2:16 pm

RE: various problems

Mon Aug 06, 2007 4:44 am

thank you for your quick and comprehensive reply.

regarding problem 1 you've been very helpful. the solution you provided suits me perfectly.

regarding problem 2 i do not yet have a link to the specifications of the protocol used by the device.
i used a port sniffer on the port that receives data from the device and this is what came up:

81.12.xxx.xxx : 33388 Length = 280 bytes
MD5 = CA850423D633F85D20CFB0F9BA2205DE
---- 8/3/2007 02:03:11.265
No#200..xxxxxxxxxxxx915.. <-IMEI nr
$GPRMC,230134.000,A,4427.0313,N,02606.2502,E,0.00,,020807,,,A*79..
$GPGGA,230134.000,4427.0313,N,02606.2502,E,1,07,1.1,51.4,M,36.0,M,,0000*6A..
$GPGSA,A,3,03,16,18,21,07,22,19,,,,,,2.0,1.1,1.6*36..
$GPGSV,3,3,12,29,05,026,,06,03,128,,24,02,074,,14,00,158,*70

81.12.xxx.xxx : 33388 Length = 280 bytes
MD5 = A63EA1967C9F2979E6E483AE433708D2
---- 8/3/2007 02:03:26.609
No#200..xxxxxxxxxxxx915..
$GPRMC,230149.000,A,4427.0304,N,02606.2493,E,0.00,,020807,,,A*7C..
$GPGGA,230149.000,4427.0304,N,02606.2493,E,1,07,1.1,60.7,M,36.0,M,,0000*6E..
$GPGSA,A,3,03,16,18,21,07,22,19,,,,,,1.9,1.1,1.6*3C..
$GPGSV,3,3,12,29,05,026,,06,03,128,,24,02,074,,14,00,158,*70

81.12.xxx.xxx : 33388 Length = 286 bytes
MD5 = 0F870DBCFBF91200278F8086BBAEC396
---- 8/3/2007 02:03:42.765
No#200..xxxxxxxxxxxx915..
$GPRMC,230204.000,A,4427.0306,N,02606.2494,E,0.00,,020807,,,A*73..
$GPGGA,230205.000,4427.0306,N,02606.2494,E,1,06,1.4,64.6,M,36.0,M,,0000*61..
$GPGSA,A,3,03,16,18,07,22,19,,,,,,,2.1,1.4,1.6*31..
$GPGSV,3,1,12,18,62,078,23,22,61,172,27,03,55,301,20,16,38,213,24*74

the device sends its IMEI number just before the nmea string. can you give me any advice as to how i can implement this protocol ?

regarding problem 3 i have read the topic regarding the use of custom maps. the last two days i have been playing with GPSTools. the software is very easy to use and i have managed to make the server work with a map i made.
unfortunately this solution creates two more problems.
a) the price of the custom maps. in order to have a decent map you need a lot of source data. buying the data from a gis company would be too expensive for the purpose of this project and there are not many free resources that i can use to make my own map from scratch.
b) let me quote from the topic with custom maps: "The current VehicleTracker application doesn't have an exposed gui-controller to control zoom-levels, thus you will not be able to switch zoom without additional coding". i don't know anything about coding, so it would be very difficult for me to implement this function by myself.

for these two reason i think it could me much easier for me to use a free resource already available and documented. this is why i would like some help in implementing the mapquest api to replace the google maps api.

thank you again.

User avatar
johan
GpsGate
Posts: 15145
Joined: Wed Aug 04, 2004 10:40 pm
Location: Sweden
Contact: Website

RE: various problems

Mon Aug 06, 2007 11:48 am

problem 2

We will implement an adapter during this week that can parse the input you describe. I will contact you with an update when this is done, and we'll also include it in the next update of GpsGate Server.

problem 3

I can see what you mean, the only available solutions for now are Google Maps and custom Maps. We will implement zoom support soon, it is on our near term list.

Regards,
Johan

Franson Support

User avatar
johan
GpsGate
Posts: 15145
Joined: Wed Aug 04, 2004 10:40 pm
Location: Sweden
Contact: Website

RE: various problems

Mon Aug 06, 2007 11:49 am

Could you please send a file with unchanged data from your "sniffer". Which includes unchanged IMEI data as well. I will use it to make sure your data stream passes our new protocol adapter. Send it to support at franson . com

Regards,
Johan

Franson Support

User avatar
johan
GpsGate
Posts: 15145
Joined: Wed Aug 04, 2004 10:40 pm
Location: Sweden
Contact: Website

RE: various problems

Wed Aug 08, 2007 9:40 pm

problem 2

We have now implemented a generic protocol adapter for all kinds of protocols that are influenced by NMEA, and contains an IMEI number.

GpsGate.com
-----------
The new adapter is installed on GpsGate.com

1. Create a user (or use an existing user).

2. Go to the preferences tab, click "Add Device". Enter the IMEI number for your device, and a suitable name.

3. Configure your device to send data to smartpipe.gpsgate.com on port 30176, both UDP and TCP/IP works.


GpsGate Server
--------------
This feature will be included in the next service release of GpsGate Server (that is the one after 1.1 build 62).

If you need a fix earlier, please contact us.

Regards,
Johan

Franson Support

Return to “GpsGate Server - How to setup and use”