Drivers Thuraya USB Devices

Please follow the below steps: Step 1. Download the below XT-PRO Upgrader program. XT-PRO upgrader. Run the setup file - the Upgrader program including the USB driver will be installed. Download the latest Thuraya XT-PRO firmware release to your hard disk. Run the setup file - the Upgrader program including the USB driver will be installed. Installing the SatSleeve modem on a PC or laptop: Connect your SatSleeve with the PC/laptop via USB data cable; Select Start Control Panel System Device Manager; Check the USB. If drivers were not downloaded automatically by Windows Update, use Device Manager to refresh the driver from Windows Update, or contact the device manufacturer. I’m Moli, your virtual agent. I can help with Moto phone issues. In that case, you should right-click on Unknown Device, click on Properties, then the Driver tab and then click Update Driver. If this doesn’t work, you can also try to download the driver for your device from the manufacturer’s website. If the USB device is just a flash drive, then it’s probably not a driver issue.

Thuraya SatSleeve + & Thuraya SatSleeve Hotspot FAQs

What is the difference between the SatSleeve+ and SatSleeve Hotspot?

SatSleeve+ is for users who mostly prefer to use their smartphone docked to the satellite unit, for walk-and-talk. It comes with a universal smartphone adaptor inside the package.
SatSleeve Hotspot is for users who prefer to use their smartphone separated from the satellite unit, and comes with a hotspot stand inside the package.

Which smartphone models can be used with the Thuraya SatSleeve+ and Hotspot?

Check if your smartphone is compatible with SatSleeve Hotspot and SatSleeve + here.

Which smartphones can be docked using the Universal adaptor?

The Universal adaptor can hold smartphones from between 58 – 85mm in width.

Can I use the Hotspot stand with the SatSleeve+ or the Universal adaptor with the SatSleeve Hotspot?

Yes, you can buy the Universal adaptor or Hotspot stand separately as accessories to convert your SatSleeve+ into a hotspot-style device and the SatSleeve Hotspot into a mobile device.

How do the Thuraya SatSleeve+ and Hotspot work? What are their features?

The Thuraya SatSleeve+ and Hotspot are devices that allow smartphone users to turn their phone into a satellite smartphone, giving them the ability to have reliable connectivity beyond the coverage of traditional terrestrial networks.
They work by using the SatSleeve Hotspot App that can be downloaded for free from the App Store or Google Play. Simply connect your smartphone to the Wi-Fi network of the SatSleeve unit and make calls and send messages in satellite mode. The smartphone can access email and popular social media and messaging apps such as Twitter and WhatsApp among many others. Thuraya SatSleeve+ and Hotspot users can post news updates, chat via message apps with their contacts as well as send and receive emails from the most remote locations in satellite mode.

Where can I download the Thuraya SatSleeve Hotspot App?

The SatSleeve Hotspot App is available as a free download. From the Apple App Store directly through your iPhone. From Google Play directly through your Android smartphone.

What is the difference between the SatSleeve App and SatSleeve Hotspot App which are both available on the app stores?

The SatSleeve Hotspot App is meant to be used only with the new generation SatSleeve+ and SatSleeve Hotspot devices. The SatSleeve App is meant to be used only with the previous generation SatSleeve models, i.e. SatSleeve Voice, SatSleeve iPhone and SatSleeve Android.

What network do the Thuraya SatSleeve+ and Hotspot run on, in which countries can I use them?

Drivers Thuraya Usb Devices Free

The Thuraya SatSleeve+ and SatSleeve Hotspot work in satellite mode throughout Thuraya’s entire network which covers two thirds of the globe across Europe, Africa, Asia and Australia. Verypc driver download for windows xp.

What is the data speed of the Thuraya SatSleeve+ and Hotspot?

The Thuraya SatSleeve+ and Hotspot provide you with access to emails, instant messaging, apps and basic Internet connectivity in satellite mode. If you choose to access the Internet in satellite mode with the SatSleeve+ or Hotspot, please note that satellite data speeds are not as fast as 3G or 4G terrestrial networks. Data download speeds in satellite mode are up to 60 kbps for downloads and up to 15 kbps for uploads on GmPRS.
For the best internet experience using your Thuraya SatSleeve+ or Hotspot: When emailing or messaging, reduce the size of images to decrease the overall message size. Use mobile versions of websites and Apps (e.g. Facebook, Twitter, etc.) rather than desktop versions of websites. Use web browsers that offer the option of text-only browsing or use websites that convert webpages into text-only pages, e.g. Opera Mini. Use websites such as textise.net to convert pages to text-only pages.

Does the smartphone work on terrestrial networks when it is connected to the SatSleeve+ or Hotspot?

Yes it does. Your smartphone can still be used to make non-satellite calls while connected to the SatSleeve unit. Please note that you will not be able to use data connectivity in terrestrial mode (e.g. 3G/LTE) while connected to the SatSleeve unit.

What are the dimensions and weight of the Thuraya SatSleeve+ and Hotspot?

The dimensions of the SatSleeve+ is 138 x 69 x 42 mm and it weighs 256g. The dimensions of the SatSleeve Hotspot is 142 x 69 x 38 mm and it weighs 290g.

What is included in the package?

The SatSleeve+ package contains the main satellite unit along with Universal adaptor, battery, travel charger (with four adapters for EU, UK, CN/JP, AUS), USB cable, a multi-language user manual and an accessories info sheet.
The SatSleeve Hotspot package contains the main satellite unit along with hotspot stand, battery, travel charger (with four adapters for EU, UK, CN/JP, AUS), USB cable, a multi-language user manual and an accessories info sheet.

How long does the battery last?

Usage time: 3 hours for talk and data usage

Standby time: 9 hours with Wi-Fi, 70hrs with Wi-Fi turned off with the ability to receive incoming calls and use the SOS function on the main unit continuously on and connected to the smartphone.

Does the SatSleeve main unit have its own microphone and speaker?

Yes, the SatSleeve unit comes with its own microphone and speaker, which can be used when using the SatSleeve unit in SOS mode or with Wi-Fi off, without the smartphone connected. When the SatSleeve is connected to smartphone, audio is routed to smartphone.

How can I turn off Wi-Fi to save battery and use the SatSleeve unit without being connected to the smartphone?

Go to the Wi-Fi settings in the SatSleeve Hotspot app and tap the Wi-Fi off button, you will then be disconnected from the smartphone and the App.

For incoming calls: the SatSleeve unit will give you a vibration alert when an incoming call is coming through and you can pick it up by pressing the SOS button. To disconnect the call, press the SOS button again.

For outgoing calls: the SOS button can be used to call one pre-programmed number of your choice.

Please note: to turn on the Wi-Fi functionality again in order to reconnect to your smartphone, please turn the SatSleeve unit off and then on again.

How do I know when the battery of the Thuraya SatSleeve+ or Hotspot is fully charged without having the Hotspot App open?

The LED on the SatSleeve unit will turn from red to blue.

Which languages does the Hotspot App support?

The Thuraya SatSleeve Hotspot App supports the following languages: English, Arabic, Bahasa Indonesia, Chinese (Simplified), French, German, Italian, Japanese, Korean, Portuguese, Russian and Spanish.

How do I change the language of the SatSleeve Hotspot App?

The language of the Hotspot App changes when the language of the smartphone is changed.

I’m connected to the Thuraya network but the GPS icon in the status bar keeps on flashing. What does it mean?

If the GPS icon flashes, it indicates that the device does not have a “GPS-fix” (i.e. the unit could not receive the GPS position from the GPS satellites). To rectify this, please move to a place with an unobstructed view of the sky that will allow the SatSleeve+ or Hotspot to receive its GPS position.

How can I receive incoming calls when the smartphone is connected but the Hotspot App is not open?

The main unit of the SatSleeve will give a vibration alert to indicate incoming calls. All you have to do is open the Hotspot App and then accept the call.

What happens if I am on a satellite call and there is an incoming GSM call?

When this happens, your satellite call will be disconnected.

Can I connect multiple smartphones to the Thuraya SatSleeve+ or Hotspot in parallel?

No, only one unit can be connected at a time.

Can I do a data session in parallel with a voice call?

No, only a voice call or a data session at a time can be established.

What is the maximum Wi-Fi range of the SatSleeve Hotspot?

The Wi-Fi range is up to 30 metres.

How long does it take to charge the Thuraya SatSleeve+ or Hotspot?

It takes approximately 2 hours and 30 minutes to charge an empty SatSleeve+ or Hotspot.

What accessories are available for the SatSleeve+ and Hotspot?

There are a number of accessories which complement the SatSleeve+ and Hotspot, such as car chargers, travel chargers, USB data cables, solar chargers, spare batteries, Universal adaptor and Hotspot stand.

-->

Summary

Opening the device and obtaining WinUSB handle.
Getting information about the device, configuration, and interface settings of all interfaces, and their endpoints.
Reading and writing data to bulk and interrupt endpoints.

Important APIs

This topic includes a detailed walkthrough of how to use WinUSB Functions to communicate with a USB device that is using Winusb.sys as its function driver.

If you are using Microsoft Visual Studio 2013, create your skeleton app by using the WinUSB template. In that case, skip steps 1 through 3 and proceed from step 4 in this topic. The template opens a file handle to the device and obtains the WinUSB handle required for subsequent operations. That handle is stored in the app-defined DEVICE_DATA structure in device.h.

For more information about the template, see Write a Windows desktop app based on the WinUSB template.

Note WinUSB functions require Windows XP or later. You can use these functions in your C/C++ application to communicate with your USB device. Microsoft does not provide a managed API for WinUSB.

Prerequisites

The following items apply to this walkthrough:

Drivers Thuraya Usb Devices Windows 10

This information applies to Windows 8.1, Windows 8, Windows 7, Windows Server 2008, Windows Vista versions of Windows.
You have installed Winusb.sys as the device's function driver. For more information about this process, see WinUSB (Winusb.sys) Installation.
The examples in this topic are based on the OSR USB FX2 Learning Kit device. You can use these examples to extend the procedures to other USB devices.

Step 1: Create a skeleton app based on the WinUSB template

To access a USB device, start by creating a skeleton app based on the WinUSB template included in the integrated environment of Windows Driver Kit (WDK) (with Debugging Tools for Windows) and Microsoft Visual Studio.You can use the template as a starting point.

For information about the template code, how to create, build, deploy, and debug the skeleton app, see Write a Windows desktop app based on the WinUSB template.

The template enumerates devices by using SetupAPI routines, opens a file handle for the device, and creates a WinUSB interface handle required for subsequent tasks. For example code that gets the device handle and opens the device, see Template code discussion.

Step 2: Query the Device for USB Descriptors

Next, query the device for USB-specific information such as device speed, interface descriptors, related endpoints, and their pipes. The procedure is similar to the one that USB device drivers use. However, the application completes device queries by calling WinUsb_GetDescriptor.

The following list shows the WinUSB functions that you can call to get USB-specific information:

Additional device information.
Call WinUsb_QueryDeviceInformation to request information from the device descriptors for the device. To get the device's speed, set DEVICE_SPEED (0x01) in the InformationType parameter. The function returns LowSpeed (0x01) or HighSpeed (0x03).
Interface descriptors
Call WinUsb_QueryInterfaceSettings and pass the device's interface handles to obtain the corresponding interface descriptors. The WinUSB interface handle corresponds to the first interface. Some USB devices, such as the OSR Fx2 device, support only one interface without any alternative setting. Therefore, for these devices the AlternateSettingNumber parameter is set to zero and the function is called only one time. WinUsb_QueryInterfaceSettings fills the caller-allocated USB_INTERFACE_DESCRIPTOR structure (passed in the UsbAltInterfaceDescriptor parameter) with information about the interface. For example, the number of endpoints in the interface is set in the bNumEndpoints member of USB_INTERFACE_DESCRIPTOR.
For devices that support multiple interfaces, call WinUsb_GetAssociatedInterface to obtain interface handles for associated interfaces by specifying the alternative settings in the AssociatedInterfaceIndex parameter.
Endpoints
Call WinUsb_QueryPipe to obtain information about each endpoint on each interface. WinUsb_QueryPipe populates the caller-allocated WINUSB_PIPE_INFORMATION structure with information about the specified endpoint's pipe. The endpoints' pipes are identified by a zero-based index, and must be less than the value in the bNumEndpoints member of the interface descriptor that is retrieved in the previous call to WinUsb_QueryInterfaceSettings. The OSR Fx2 device has one interface that has three endpoints. For this device, the function's AlternateInterfaceNumber parameter is set to 0, and the value of the PipeIndex parameter varies from 0 to 2.
To determine the pipe type, examine the WINUSB_PIPE_INFORMATION structure's PipeInfo member. This member is set to one of the USBD_PIPE_TYPE enumeration values: UsbdPipeTypeControl, UsbdPipeTypeIsochronous, UsbdPipeTypeBulk, or UsbdPipeTypeInterrupt. The OSR USB FX2 device supports an interrupt pipe, a bulk-in pipe, and a bulk-out pipe, so PipeInfo is set to either UsbdPipeTypeInterrupt or UsbdPipeTypeBulk. The UsbdPipeTypeBulk value identifies bulk pipes, but does not provide the pipe's direction. The direction information is encoded in the high bit of the pipe address, which is stored in the WINUSB_PIPE_INFORMATION structure's PipeId member. The simplest way to determine the direction of the pipe is to pass the PipeId value to one of the following macros from Usb100.h:
- The USB_ENDPOINT_DIRECTION_IN (PipeId) macro returns TRUE if the direction is in.
- The USB_ENDPOINT_DIRECTION_OUT(PipeId) macro returns TRUE if the direction is out.
The application uses the PipeId value to identify which pipe to use for data transfer in calls to WinUSB functions, such as WinUsb_ReadPipe (described in the 'Issue I/O Requests' section of this topic), so the example stores all three PipeId values for later use.

The following example code gets the speed of the device that is specified by the WinUSB interface handle.

The following example code queries the various descriptors for the USB device that is specified by the WinUSB interface handle. The example function retrieves the types of supported endpoints and their pipe identifiers. The example stores all three PipeId values for later use.

Step 3: Send Control Transfer to the Default Endpoint

Next, communicate with the device by issuing control request to the default endpoint.

Drivers Thuraya Usb Devices Download

All USB devices have a default endpoint in addition to the endpoints that are associated with interfaces. The primary purpose of the default endpoint is to provide the host with information that it can use to configure the device. However, devices can also use the default endpoint for device-specific purposes. For example, the OSR USB FX2 device uses the default endpoint to control the light bar and seven-segment digital display.

Control commands consist of an 8-byte setup packet, which includes a request code that specifies the particular request, and an optional data buffer. The request codes and buffer formats are vendor defined. In this example, the application sends data to the device to control the light bar. The code to set the light bar is 0xD8, which is defined for convenience as SET_BARGRAPH_DISPLAY. For this request, the device requires a 1-byte data buffer that specifies which elements should be lit by setting the appropriate bits.

The application can set this through the user interface (UI), such as by providing a set of eight check box controls to specify which elements of the light bar should be lit. The specified elements correspond to the appropriate bits in the buffer. To avoid UI code, the example code in this section sets the bits so that alternate lights get lit up.

Use the following steps to issue a control request.

Allocate a 1-byte data buffer and load the data into the buffer that specifies the elements that should be lit by setting the appropriate bits.
Construct a setup packet in a caller-allocated WINUSB_SETUP_PACKET structure. Initialize the members to represent the request type and data as follows:
- The RequestType member specifies request direction. It is set to 0, which indicates host-to-device data transfer. For device-to-host transfers, set RequestType to 1.
- The Request member is set to the vendor-defined code for this request, 0xD8. It is defined for convenience as SET_BARGRAPH_DISPLAY.
- The Length member is set to the size of the data buffer.
- The Index and Value members are not required for this request, so they are set to zero.
Call WinUsb_ControlTransfer to transmit the request to the default endpoint by passing the device's WinUSB interface handle, the setup packet, and the data buffer. The function receives the number of bytes that were transferred to the device in the LengthTransferred parameter.

The following code example sends a control request to the specified USB device to control the lights on the light bar.

Step 4: Issue I/O Requests

Next, send data to the device's bulk-in and bulk-out endpoints that can be used for read and write requests, respectively. On the OSR USB FX2 device, these two endpoints are configured for loopback, so the device moves data from the bulk-in endpoint to the bulk-out endpoint. It does not change the value of the data or add any new data. For loopback configuration, a read request reads the data that was sent by the most recent write request. WinUSB provides the following functions for sending write and read requests:

To send a write request

Allocate a buffer and fill it with the data that you want to write to the device. There is no limitation on the buffer size if the application does not set RAW_IO as the pipe's policy type. WinUSB divides the buffer into appropriately sized chunks, if necessary. If RAW_IO is set, the size of the buffer is limited by the maximum transfer size supported by WinUSB.
Call WinUsb_WritePipe to write the buffer to the device. Pass the WinUSB interface handle for the device, the pipe identifier for the bulk-out pipe (as described in the Query the Device for USB Descriptors section of this topic), and the buffer. The function returns the number of bytes that are actually written to the device in the bytesWritten parameter. The Overlapped parameter is set to NULL to request a synchronous operation. To perform an asynchronous write request, set Overlapped to a pointer to an OVERLAPPED structure.

Write requests that contain zero-length data are forwarded down the USB stack. If the transfer length is greater than a maximum transfer length, WinUSB divides the request into smaller requests of maximum transfer length and submits them serially.The following code example allocates a string and sends it to the bulk-out endpoint of the device.

To send a read request

Call WinUsb_ReadPipe to read data from the bulk-in endpoint of the device. Pass the WinUSB interface handle of the device, the pipe identifier for the bulk-in endpoint, and an appropriately sized empty buffer. When the function returns, the buffer contains the data that was read from the device. The number of bytes that were read is returned in the function's bytesRead parameter. For read requests, the buffer must be a multiple of the maximum packet size.

Zero-length read requests complete immediately with success and are not sent down the stack. If the transfer length is greater than a maximum transfer length, WinUSB divides the request into smaller requests of maximum transfer length and submits them serially. If the transfer length is not a multiple of the endpoint's MaxPacketSize, WinUSB increases the size of the transfer to the next multiple of MaxPacketSize. If a device returns more data than was requested, WinUSB saves the excess data. If data remains from a previous read request, WinUSB copies it to the beginning of the next read request and completes the request, if necessary.The following code example reads data from the bulk-in endpoint of the device.

Step 5: Release the Device Handles

After you have completed all the required calls to the device, release the file handle and the WinUSB interface handle for the device. For this, call the following functions:

CloseHandle to release the handle that was created by CreateFile, as described in the step 1.
WinUsb_Free to release the WinUSB interface handle for the device, which is returned by WinUsb_Initialize.

Step 6: Implement Main

The following code example shows the main function of your console application.

Next steps

If your device supports isochronous endpoints, you can use WinUSB Functions to send transfers. This feature is only supported in Windows 8.1.

For more information, see Send USB isochronous transfers from a WinUSB desktop app.