Difference between revisions of "WiDig-801 QuickStart Windows"

From I-CubeX Wiki
Jump to: navigation, search
Line 17: Line 17:
 
If the WiDig is running [[WiConnect]] 1.1xx, [[Connect]] can communicate with the WiDig via USB while it is communicating via BLE. If running [[WiConnect]] 1.0xx on the WiDig, [[Connect]] is not useful as it cannot communicate with the WiDig while it is operating in BLE mode. The Connect software is only able to connect to devices via USB or "Classic" Bluetooth (ie. not BLE).  
 
If the WiDig is running [[WiConnect]] 1.1xx, [[Connect]] can communicate with the WiDig via USB while it is communicating via BLE. If running [[WiConnect]] 1.0xx on the WiDig, [[Connect]] is not useful as it cannot communicate with the WiDig while it is operating in BLE mode. The Connect software is only able to connect to devices via USB or "Classic" Bluetooth (ie. not BLE).  
  
These instructions assume the WiDig's BLE is enabled. The WiDig's blue LED will blink slowly to indicate its BLE is enabled and available for a connection. Once connected via BLE the blue LED will be steady on. If the blue LED not slowly blinking BLE is not enabled. To enable the WiDig's BLE, see [[Connect]] QuickStart.
+
These instructions assume the WiDig's BLE is enabled. The WiDig's blue LED will blink slowly (~1 sec interval) to indicate its BLE is enabled and available for a connection. Once connected via BLE the blue LED will be steady on. If the blue LED not slowly blinking BLE is not enabled. To enable the WiDig's BLE, see [[Connect]] QuickStart.
  
  

Revision as of 01:46, 9 July 2025

WiDig BLE on Windows

On Windows, configuration of the WiDig must be done through USB, or using the WIDI Bud adapter, as these communication methods allow both sending and receiving of messages to/from the WiDig.

To only receive sensor data with a generic BLE interface once it is configured in Standalone mode with EditorX (via USB or using a WIDI Bud), the computer must run Windows 10 or higher.

You will need:

- A WiDig configured in Standalone mode, and USB power source

- loopMIDI virtual MIDI application

- MIDIBerry BLE to MIDI bridge application (Windows 10 only)

Also, we need to route the BLE MIDI port to a virtual MIDI port, hence the need for loopMIDI.

If the WiDig is running WiConnect 1.1xx, Connect can communicate with the WiDig via USB while it is communicating via BLE. If running WiConnect 1.0xx on the WiDig, Connect is not useful as it cannot communicate with the WiDig while it is operating in BLE mode. The Connect software is only able to connect to devices via USB or "Classic" Bluetooth (ie. not BLE).

These instructions assume the WiDig's BLE is enabled. The WiDig's blue LED will blink slowly (~1 sec interval) to indicate its BLE is enabled and available for a connection. Once connected via BLE the blue LED will be steady on. If the blue LED not slowly blinking BLE is not enabled. To enable the WiDig's BLE, see Connect QuickStart.


Pairing the WiDig

1. Go to system Settings->Bluetooth & Other Devices, and click on add:


Widig win10 bluetooth add.png


2. Then, select the WiDig device:


Widig win10 bluetooth select.png


3. Connect to the device (If it fails once, try again and eventually it should connect):


Widig win10 bluetooth ready.png


4. Make sure loopMIDI is running and there is at least one virtual port available:


Widig win10 loopMIDI.png


5. Finally, open MIDIBerry and select the WiDig as input, and the "MIDI" virtual device as output.

Now, you will be able to access WiDig sensor data from any MIDI application via the virtual loopMIDI port!


Widig win10 midiberry.png


In the event that the WiDig's BLE is disconnected, its blue LED will blink slowly.