- Drivers Velleman Instruments Usb Devices Adapter
- Drivers Velleman Instruments Usb Devices Download
- Drivers Velleman Instruments USB Devices
Drivers Velleman Instruments Usb Devices Adapter
Velleman 1MHz USB Function Generator PCGU01 The new PC USB miniature function generator is simple to use and has a frequency range of up to 1 MHz! This nifty measuring instrument can generate sine, square and triangle waveforms, and it has a DAC resolution of 10 bits. The K8055 interface board has 5 digital input channels and 8 digital output channels. In addition, there are two analogue inputs and two analogue outputs with 8 bit resolution. The number of inputs/outputs can be further expanded by connecting more (up to a maximum of four) cards to the PC's USB connectors. All communication routines are contained in a Dynamic Link Library (DLL). When I connect my USB DAQ or CompactDAQ (cDAQ) device to my computer, Windows recognizes that new hardware was found. When I look in the WindowsDevice Manager, the device has a yellow exclamation point and saysUSB Flash Firmware Loader. My chassis, device or module isn't showing up or recognized in Measurement & Automation Explorer (MAX).
-->Summary
- Guidelines for choosing the right programming model
- UWP app and desktop app developer experience
Important APIs
This topic provides guidelines for deciding whether you should write a UWP app or a Windows desktop app to communicate with a USB device.
Windows provides API sets that you can use to write apps that talk to a custom USB devices. The API performs common USB-related tasks such as, finding the device, data transfers.
'Custom device' in this context means, a device for which Microsoft does not provide an in-box class driver. Instead, you can install WinUSB (Winusb.sys) as the device driver.
Choosing a programming model
If you install Winusb.sys, here are the programming model options:
Windows 8.1 provides a new namespace: Windows.Devices.Usb. The namespace cannot be used in earlier version of Windows. Other Microsoft Store resources are here: UWP app.
Before Windows 8.1, apps that were communicating through Winusb.sys, were desktop apps written by using WinUSB Functions. In Windows 8.1, the API set has been extended. Other Windows desktop app resources are here: Windows desktop app.
The strategy for choosing the best programming model depends on various factors.
Will your app communicate with an internal USB device?
The APIs are primarily designed for accessing peripheral devices. The API can also access PC internal USB devices. However access to PC internal USB devices from a UWP app is limited to a privileged app that is explicitly declared in device metadata by the OEM for that PC.
Will your app communicate with USB isochronous endpoints?
If your app transmits data to or from isochronous endpoints of the device, you must write a Windows desktop app. In Windows 8.1, new WinUSB Functions have been added to the API set that allow a desktop app to send data to and receive data from isochronous endpoints.
Is your app a 'control panel' type of app?
UWP apps are per-user apps and do not have the ability to make changes outside the scope of each app. For these types of apps, you must write a Windows desktop app.
Is the USB device class supported classes by UWP apps?
Write a UWP app if your device belongs to one these device classes.
name:cdcControl, classId:02 * *
name:physical, classId:05 * *
name:personalHealthcare, classId:0f 00 00
name:activeSync, classId:ef 01 01
name:palmSync, classId:ef 01 02
name:deviceFirmwareUpdate, classId:fe 01 01
name:irda, classId:fe 02 00
name:measurement, classId:fe 03 *
name:vendorSpecific, classId:ff * *
Note If your device belongs to DeviceFirmwareUpdate class, your app must be a privileged app.
If your device does not belong to one the preceding device classes, write a Windows desktop app.
Driver requirement
Driver requirement | UWP app | Windows desktop app |
---|---|---|
Function driver | Microsoft-provided Winusb.sys (kernel-mode driver). | Microsoft-provided Winusb.sys (kernel-mode driver). |
Filter driver | If filter drivers are present, access is limited to privileged apps. The app is declared as privileged apps in device metadata by the OEM. | Filter driver can be present in the kernel mode device stack as long as it doesn't block access to Winusb.sys. |
Code samples
Sample | UWP app | Windows desktop app |
---|---|---|
Get started with these samples |
|
Development tools
Development tools | UWP app | Windows desktop app |
---|---|---|
Developer environment | Microsoft Visual Studio 2013 Microsoft Windows Software Development Kit (SDK) for Windows 8.1 | Use WinUSB Application template included with Visual Studio (Ultimate or Professional) and Windows Driver Kit (WDK) 8 Note For isochronous transfers, Visual Studio 2013 with Windows Driver Kit (WDK) 8.1 |
Programming languages | C#, VB.NET, C++, JavaScript | C/C++ |
Feature implementation
Key scenario | UWP app | Windows desktop app |
---|---|---|
Device discovery | Use Windows.Devices.Enumeration](/uwp/api/Windows.Devices.Enumeration)'>Windows.Devices.Enumeration namespace to get a UsbDevice](/uwp/api/Windows.Devices.Usb.UsbDevice)'>UsbDevice. | Use SetupAPI functions and WinUsb_Initialize](/windows/win32/api/winusb/nf-winusb-winusb_initialize)'>WinUsb_Initialize to get a WINUSB_INTERFACE_HANDLE. |
USB control transfer | ||
Getting USB descriptors | WinUsb_GetDescriptor](/windows/win32/api/winusb/nf-winusb-winusb_getdescriptor)'>WinUsb_GetDescriptor | |
Sending USB bulk transfer | ||
Sending USB interrupt transfer | ||
Sending USB isochronous transfer | Not supported. | |
Closing the device | UsbDevice.Close](/uwp/api/Windows.Devices.Usb.UsbDevice#Windows_Devices_Usb_UsbDevice_Close)'>UsbDevice.Close | WinUsb_Free](/windows/win32/api/winusb/nf-winusb-winusb_free)'>WinUsb_Free |
Documentation
Documentation | UWP app | Windows desktop app |
---|---|---|
Programming guide | Talking to USB devices, start to finish | How to Access a USB Device by Using WinUSB Functions |
API reference | Windows.Devices.Usb | WinUSB Functions |
Related topics
RST Instruments Ltd. provides Windows® Certified Drivers for our devices that use USB communication. This certification is your peace of mind that the USB drivers we provide for your product are stable, and fully authenticated by Microsoft® to be compatible with your particular Windows® Operating System. All USB drivers are available automatically through Windows® updates.
Microsoft, and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries.
Supported Windows® Operating Systems:
- Windows 7 (x86 and x64)
- Windows Server 2008 R2 (x64)
- Windows 8 (x86 and x64)
- Windows Server 2012 (x64)
- Windows 8.1 (x86 and x64)
- Windows 10 (x64)
RST USB DRIVER (VIEW SUPPORTED DEVICES BELOW):
RST USB Drivers (Ver 2.12.28.2)
Upon download completion, run “InstallRSTDrivers.exe” then follow instructions in device Software Host Manual.
SUPPORTED DEVICES:
** NOTE ** The RST USB DRIVER utility (above) is universal and will install drivers for the following RST devices:
- DT2011B
- DT2040
- DT2055
- DT2055B
- DTL201B Tilt Logger
- DTL202B Tilt Logger
- DT2306
- DT2350 Load Logger
- DT2485 DT-BUS Logger
- DT4205 4-20 mA Logger
- DT LINK Adapter
- RTU
- MTCM – Graphing Logger
- MTCM – Closure Station
- RST RS485 to USB Sensor Interface
- C109
- IC6656L Tilt Logger
- IR420
- IR5000
- LP100
- MA7 Readout
- QB120
- SG350
- TH2016 serial numbers TR5452 and greater
- TH2016B
- VW0420 serial numbers 2072 and greater
- VW2106 serial numbers VR0460 and greater
- VW2016B
- VW2110
- GAA2820
- DTSAA
Drivers Velleman Instruments Usb Devices Download
INCLINALYSIS™ AND GEOVIEWER DONGLE USB DRIVER:
Drivers Velleman Instruments USB Devices
Download the DongleInstall.zip file and from the extracted files, follow the instructions on the “Dongle Instructions.txt” file.
Comments are closed.