The Aaronia GPS - Logger includes a total of 6 sensors, all of them on the cutting edge of technology, making it the world's first stand-alone data logger with such a variety of sensors. Not to forget is also the very small form factor and the extremely high data rate of approx. 35 logs/second (freely adjustable). The logger with battery weighs just 88 grams.
The RTSA Suite is multi-platform compatible and available for Windows, MacOS and Linux, thus encompassing all important operating systems. Our easy-to-use tactical display controls and visualizes all integrated components and sensors (RF detector, radar, cameras (PTZ), jammers, etc.). If you turn it on when the device is already powered on, you'll activate the recording mode. The GPS/ Sensor data will be written to the SD card until you turn the logger off. Mini USB Port Connect the device via USB cable with your PC to use the device in streaming mode with our software Micro SD-Card Slot Insert the micro SD card into the slot.
- Uninstall and reinstall the driver. The device driver may have become corrupted. Uninstall the driver from Device Manager and scan for new hardware to install the driver again. In the device's Properties dialog box, click the Driver tab, and then click Uninstall. Follow the instructions. Restart your computer.
- . Multi-device capability, remote control of several SPECTRAN. Analyzer via the integrated USB port. Aaronia AG, Gewerbegebiet Aaronia AG, DE-54597.
The main purpose of the GPS logger consists of recording the position and even the orientation of the Aaronia antennas (HyperLOG X, HyperLOG EMI or Magnotracker series). The GPS sensor allows for easy collection and documentation of your measurement position , including elevation information.
Even more interesting is the Tilt-sensor and the digital compass, hereby the inclination and orientation of the antenna can be recorded and evaluated during the measurement. This special feature allows you to easily create an 'RF heat map' including frequency , direction and strength of an RF source within 360 degrees.
The Aaronia GPS-Logger offers a very fast update rate of up to 35 complete logs with all sensor data per second (on microSDCard and/or USB-Streaming) offering a 'real time' display of the unit orientation. At maximum rate the Aaronia GPS-Logger will produce around 50MB/hour (uncompressed)! The maximum usable microSD volume is 2GB, offering a maximum recording time of about 2 days at full speed on the
microSD card. The data rate can be adjusted to much lower rates to keep data volume much lower offering long time recording on the microSD card over weeks or even months.
The Aaronia GPS - logger can be used with the internal LiPo battery (standalone) and / or USB (provides unlimited operating time).
The logger has three operating modes :
• Streaming / logging on the internal ( removable) microSD Card, completely independently as a stand- alone device
• Continuous recording via USB port (PC, Linux or MAC OS)
• Transfer of files stored in internal microSD Card (PC, Linux or MAC OS)
The Aaronia GPS - logger can be mounted directly on HyperLOG X, Magnotracker and HyperLOG EMI antennas (screws and adapter included). It can also be mounted on any other device , car, etc. with the included adapter. This only requires 2 holes to be drilled to attach the supplied adapter.
VersionsType and SensorsPriceGPS Logger
GPS, Compass, Acceleration, Tilt, Pressure249,95€Buy now!DatasheetTypeSensorsPriceGPS LoggerGPS, Compass, Acceleration, Tilt, Pressure249,95€Buy now!
The software for our GPS Loggers allow the read-out and display of all data from the different sensors.Documents
Scope of delivery
Logger with internal 650mAh Lipo-Battery (works up to 7h), transport case with foam inserts, USB Cable, 2GB microSD card, micro on SD Adapter, USB Reader, evaluation Software (PC, Linux, and Mac OS), mounting rail and screwsDownloadsGPS Logger Software (Windows) [v.2.4.4]GPS Logger Software (MacOS) [v.2.4.2]Programming Guide GPS LoggerDemo Data GPS Logger
SpecificationsGPS LoggerGPS SensorHigh End 66 Channel GPS Sensor incl. antenna offering position (accuracy: 1,8 meters), speed (maximum velocity: 515m/s with 0,1m/s
accuracy) and height (maximum altitude: 18.000 meters) information with a sensitivity of -165dBm.3D Kompass 1° to 2° Degree Compass Heading Accuracy (Wide Magnetic Field Range of +/- 8 Oe)Beschleunigungssensor3D/Triaxial Accelerometer with up to 4mg resolution (+/- 2g, +/- 4g or +/- 8g range / 10.000 g shock tolerant)Gyro / Tilt Sensor3D/Triaxial Gyro/Tilt Sensor with a sensitivity of 14 LSBs per °/sec. (10.000 g shock tolerant / ±2000°/sec)
Altimeter / Drucksensorvery high accuracy/resolution and a wide pressure range of 260-1260mbar and a height resolution of up to 20cm! (0,020 mbar RMS resolution)Dimensions102 x 42 x 21 mmColor
Aaronia Port Devices Driver UpdaterblackWeight88gWarranty2 Years
These cookies are not optional. They are needed for the website to function.
In order for us to improve the website's functionality and structure, based on how the website is used.
In order for our website to perform as well as possible during your visit. If you refuse these cookies, some functionality will disappear from the website.
By sharing your interests and behavior as you visit our site, you increase the chance of seeing personalized content and offers.
For certain Universal Serial Bus (USB) devices, such as devices that are accessed by only a single application, you can install WinUSB (Winusb.sys) in the device's kernel-mode stack as the USB device's function driver instead of implementing a driver.
This topic contains these sections:
Automatic installation of WinUSB without an INF file
As an OEM or independent hardware vendor (IHV), you can build your device so that the Winusb.sys gets installed automatically on Windows 8 and later versions of the operating system. Such a device is called a WinUSB device and does not require you to write a custom INF file that references in-box Winusb.inf.
When you connect a WinUSB device, the system reads device information and loads Winusb.sys automatically.
For more information, see WinUSB Device.
Installing WinUSB by specifying the system-provided device class
When you connect your device, you might notice that Windows loads Winusb.sys automatically (if the IHV has defined the device as a WinUSB Device). Otherwise follow these instructions to load the driver:
- Plug in your device to the host system.
- Open Device Manager and locate the device.
- Select and hold (or right-click) the device and select Update driver software... from the context menu.
- In the wizard, select Browse my computer for driver software.
- Select Let me pick from a list of device drivers on my computer.
- From the list of device classes, select Universal Serial Bus devices.
- The wizard displays WinUsb Device. Select it to load the driver.
If Universal Serial Bus devices does not appear in the list of device classes, then you need to install the driver by using a custom INF.The preceding procedure does not add a device interface GUID for an app (UWP app or Windows desktop app) to access the device. You must add the GUID manually by following this procedure.
Load the driver as described in the preceding procedure.
Generate a device interface GUID for your device, by using a tool such as guidgen.exe.
Find the registry key for the device under this key:
Under the Device Parameters key, add a String registry entry named DeviceInterfaceGUID or a Multi-String entry named DeviceInterfaceGUIDs. Set the value to the GUID you generated in step 2.
Disconnect the device from the system and reconnect it to the same physical port.Note If you change the physical port then you must repeat steps 1 through 4.
Writing a custom INF for WinUSB installation
As part of the driver package, you provide an .inf file that installs Winusb.sys as the function driver for the USB device.
The following example .inf file shows WinUSB installation for most USB devices with some modifications, such as changing USB_Install in section names to an appropriate DDInstall value. You should also change the version, manufacturer, and model sections as necessary. For example, provide an appropriate manufacture's name, the name of your signed catalog file, the correct device class, and the vendor identifier (VID) and product identifier (PID) for the device.
Also notice that the setup class is set to 'USBDevice'. Vendors can use the 'USBDevice' setup class for devices that do not belong to another class and are not USB host controllers or hubs.
If you are installing WinUSB as the function driver for one of the functions in a USB composite device, you must provide the hardware ID that is associated with the function, in the INF. You can obtain the hardware ID for the function from the properties of the devnode in Device Manager. The hardware ID string format is 'USBVID_vvvv&PID_pppp'.
The following INF installs WinUSB as the OSR USB FX2 board's function driver on a x64-based system.
Starting in Windows 10, version 1709, the Windows Driver Kit provides InfVerif.exe that you can use to test a driver INF file to make sure there are no syntax issues and the INF file is universal. We recommened that you provide a universal INF. For more information, see Using a Universal INF File.
Only include a ClassInstall32 section in a device INF file to install a new custom device setup class. INF files for devices in an installed class, whether a system-supplied device setup class or a custom class, must not include a ClassInstall32 section.
Except for device-specific values and several issues that are noted in the following list, you can use these sections and directives to install WinUSB for any USB device. These list items describe the Includes and Directives in the preceding .inf file.
USB_Install: The Include and Needs directives in the USB_Install section are required for installing WinUSB. You should not modify these directives.
USB_Install.Services: The Include directive in the USB_Install.Services section includes the system-supplied .inf for WinUSB (WinUSB.inf). This .inf file is installed by the WinUSB co-installer if it isn't already on the target system. The Needs directive specifies the section within WinUSB.inf that contains information required to install Winusb.sys as the device's function driver. You should not modify these directives.Note Because Windows XP doesn't provide WinUSB.inf, the file must either be copied to Windows XP systems by the co-installer, or you should provide a separate decorated section for Windows XP.
USB_Install.HW: This section is the key in the .inf file. It specifies the device interface globally unique identifier (GUID) for your device. The AddReg directive sets the specified interface GUID in a standard registry value. When Winusb.sys is loaded as the device's function driver, it reads the registry value DeviceInterfaceGUIDs key and uses the specified GUID to represent the device interface. You should replace the GUID in this example with one that you create specifically for your device. If the protocols for the device change, create a new device interface GUID.
Note User-mode software must call SetupDiGetClassDevs to enumerate the registered device interfaces that are associated with one of the device interface classes specified under the DeviceInterfaceGUIDs key. SetupDiGetClassDevs returns the device handle for the device that the user-mode software must then pass to the WinUsb_Initialize routine to obtain a WinUSB handle for the device interface. For more info about these routines, see How to Access a USB Device by Using WinUSB Functions.
The following INF installs WinUSB as the OSR USB FX2 board's function driver on a x64-based system. The example shows INF with WDF coinstallers.
USB_Install.CoInstallers: This section, which includes the referenced AddReg and CopyFiles sections, contains data and instructions to install the WinUSB and KMDF co-installers and associate them with the device. Most USB devices can use these sections and directives without modification.
The x86-based and x64-based versions of Windows have separate co-installers.
Note Each co-installer has free and checked versions. Use the free version to install WinUSB on free builds of Windows, including all retail versions. Use the checked version (with the '_chk' suffix) to install WinUSB on checked builds of Windows.
Each time Winusb.sys loads, it registers a device interface that has the device interface classes that are specified in the registry under the DeviceInterfaceGUIDs key.
Note If you use the redistributable WinUSB package for Windows XP or Windows Server 2003, make sure that you don't uninstall WinUSB in your uninstall packages. Other USB devices might be using WinUSB, so its binaries must remain in the shared folder.
How to create a driver package that installs Winusb.sys
To use WinUSB as the device's function driver, you create a driver package. The driver package must contain these files:
- WinUSB co-installer (Winusbcoinstaller.dll)
- KMDF co-installer (WdfcoinstallerXXX.dll)
- An .inf file that installs Winusb.sys as the device's function driver. For more information, see Writing an .Inf File for WinUSB Installation.
- A signed catalog file for the package. This file is required to install WinUSB on x64 versions of Windows starting with Vista.
Note Make sure that the driver package contents meet these requirements:
- The KMDF and WinUSB co-installer files must be obtained from the same version of the Windows Driver Kit (WDK).
- The co-installer files must be obtained from the latest version of the WDK, so that the driver supports all the latest Windows releases.
- The contents of the driver package must be digitally signed with a Winqual release signature. For more info about how to create and test signed catalog files, see Kernel-Mode Code Signing Walkthrough on the Windows Dev Center - Hardware site.
Download the Windows Driver Kit (WDK) and install it.
Create a driver package folder on the machine that the USB device is connected to. For example, c:UsbDevice.
Copy the WinUSB co-installer (WinusbcoinstallerX.dll) from the WinDDKBuildNumberredistwinusb folder to the driver package folder.
The WinUSB co-installer (Winusbcoinstaller.dll) installs WinUSB on the target system, if necessary. The WDK includes three versions of the co-installer depending on the system architecture: x86-based, x64-based, and Itanium-based systems. They are all named WinusbcoinstallerX.dll and are located in the appropriate subdirectory in the WinDDKBuildNumberredistwinusb folder.
Copy the KMDF co-installer (WdfcoinstallerXXX.dll) from the WinDDKBuildNumberredistwdf folder to the driver package folder.
The KMDF co-installer (WdfcoinstallerXXX.dll) installs the correct version of KMDF on the target system, if necessary. The version of WinUSB co-installer must match the KMDF co-installer because KMDF-based client drivers, such as Winusb.sys, require the corresponding version of the KMDF framework to be installed properly on the system. For example, Winusbcoinstaller2.dll requires KMDF version 1.9, which is installed by Wdfcoinstaller01009.dll. The x86 and x64 versions of WdfcoinstallerXXX.dll are included with the WDK under the WinDDKBuildNumberredistwdf folder. The following table shows the WinUSB co-installer and the associated KMDF co-installer to use on the target system.
Use this table to determine the WinUSB co-installer and the associated KMDF co-installer.
WinUSB co-installer KMDF library version KMDF co-installer Winusbcoinstaller.dll Requires KMDF version 1.5 or later
Winusbcoinstaller2.dll Requires KMDF version 1.9 or later Wdfcoinstaller01009.dll Winusbcoinstaller2.dll Requires KMDF version 1.11 or later WdfCoInstaller01011.dll
Write an .inf file that installs Winusb.sys as the function driver for the USB device.
Create a signed catalog file for the package. This file is required to install WinUSB on x64 versions of Windows.
Attach the USB device to your computer.
Open Device Manager to install the driver. Follow the instructions on the Update Driver Software wizard and choose manual installation. You will need to provide the location of the driver package folder to complete the installation.
Aaronia Port Devices Driver License Test
Aaronia Port Devices Drivers
WinUSB Architecture and Modules
Choosing a driver model for developing a USB client driver
How to Access a USB Device by Using WinUSB Functions
WinUSB Power Management
WinUSB Functions for Pipe Policy Modification