Learn about gpsid (GPS intermediate driver)

Only systems above mobile5.0 and wince6.0 are supported. You can add components when customizing the system.

Gpsid is a middleware, which is equivalent to a virtual serial port dedicated to GPS data. It supports simultaneous opening and operation of multiple applications.

But what I'm worried about is that this gpsid is fixed by Microsoft and all the data is rigid. What if I want to get some raw data?

Can raw data be obtained?

Some special GPS modules do not support gpsid, and some are not GPS modules, such as BeiDou and Galileo.

However, I can see on Microsoft's website that raw data can be obtained. How can this problem be obtained?

Of most interest may be the Accessing Parsed GPS Data and Accessing Raw GPS Data topics, which explain how to write code that uses GPS Intermediate Driver location data.

Also, how do we send commands to the GPS module? Can gpsid be passed through?

Hope to find some answers here http://msdn.microsoft.com/en-us/library/ms850332.aspx

The raw interface is one of two interfaces provided by the GPS intermediate driver for accessing GPS information. the raw interface, which makes GPS information available through a virtual COM port, mimics the design of precise existing GPS scenarios. in both
The existing scenarios and with the raw interface, applications callcreatefile To open a connection, call readfile some
Number of times to retrieve raw data, and call closehandle to close the connection.

For information about how to use the raw interface, see overall raw data code structure, which explains how to useCreatefile,Readfile,
AndClosehandleWith the GPS intermediate driver raw interface.

While it is not recommended in most scenarios, privileged applications can also call writefile and deviceiocontrol using
The handle returnedCreatefile. In this case, the GPS intermediate driver forwards these callto the hardware-specific device driver that interacts with the underlying GPS hardware. on platforms where trust is enabled, normal applications
Cannot successfully callWritefileOrDeviceiocontrol. In this case, the last error, accessible through getlasterror,
Will be set to error_access_denied.

In most cases, applications shoshould avoid callingWritefileOrDeviceiocontrol. Without the GPS intermediate driver, applications often interact directly with GPS hardware. In addition, in most cases only a single application
Uses the GPS hardware at a time. In this situation, it often doesn' t matter if an application usesDeviceiocontrolTo put the GPS hardware into a non-standard mode (for example, one where the hardware returns GPS data in a proprietary format ).
Because the application makes the change, it knows how to interpret data in the new format. in contrast, with the GPS intermediate driver, changing this type of setting affects all clients, some of which may not know how to interpret data in the proprietary
Format, or to even know that a change has been made.

Note callingDeviceiocontrolWith the same handle used to access data is different from callingDeviceiocontrolWith a handle to the GPS intermediate driver. In the former
Case-the case that uses the handle discussed in this topic-the ioctl is handled by the device driver that controls the underlying hardware. In the latter case-when you callCreatefileWith "gpd0:"-The IOCTL is handled by the GPS intermediate
Driver itself. For more information about controlling the GPS intermediate driver usingDeviceiocontrol, See controlling GPS
Intermediate driver execution.

From the above description, this gpsid is useful for some commonly used GPS devices, such as navigators, which are only single-star devices but GPS devices. But in case of support for GLONASS or Beidou, then this gpsid is not competent to complete this task.

I don't know whether this gpsid is open-source. If it is open-source, it can be changed to middleware that supports coexistence of GLONASS, Beidou, and GPS.