These devices are not used to control external sound modules or virtual instruments within Studio One, but rather Studio One itself. Setting up an External MIDI Keyboard Controller A MIDI keyboard controller is a hardware device that is generally used for playing and controlling other MIDI devices, virtual instruments, and software parameters. When writing device drivers, developers must write a separate device driver for the Win 9x and the Win NTx kernels. Microsoft has developed a cross-platform operating system support for input devices, in order to provide a uniform way for code to access such devices across Plug-and-Play Windows platforms (Windows 98 and higher, not including. Power on the printer, connect USB to the computer, and the driver will be installed automatically. If can not install automatically, please open the 'Device Management', find a port with a yellow exclamation mark, right click 'Update Driver'. Select 'Browse my computer for driver software'. Find Cura driver and install it. If for some reason, the Firewire port stops working, just go into Device Manager and make sure the IEEE 1394 device drive is still set to Legacy. The Fix for Windows 7 For Windows 7 simply replace the new 1394 driver with the Legacy driver that comes with Windows 7.
Unpacking the .zip archive:
You will need to unzip the downloaded file in the location you have chosen to hold the executable files (perhaps somewhere like bin). I would NOT put them in Program Files, since spaces in directory or file names and command line environments are a very bad mix, and will cause you endless problems. The archive will create a top level directory Argyll_VX.X.X, where X.X.X is the version number, and the executables will be in Argyll_VX.X.Xbin.Making the tools accessible:
You should also configure your %PATH% environment variable to give access to the executables from your command line environment.For Windows 8, 8.1 & 10, look in
Desktop -> Settings -> Control Panel -> System And Security -> System -> Advanced System Settings -> Environment Variables
For Windows 7, look in
Start Menu -> Control Panel -> System And Security -> System -> Change Settings -> Advanced -> Environment Variables
For Vista, look in
Start Menu -> Control Panel -> System And Maintenance -> System -> Change Settings -> Advanced -> Environment Variables
For XP and 2000 look in
Start->Settings->Control Panel->System->Advanced->Environment Variables
For NT 4 look in
Start->Settings->Control Panel->System->Environment
You want to add the directory you've chosen to your %PATH%, which is a System Variable. Normally you would add this to the end of the current setting, separated by a ';'.
So if the current value of PATH is '%SystemRoot%system32;%SystemRoot%' and you unpacked Argyll version 1.8.0 in d:bin, then you would modify PATH to be '%SystemRoot%system32;%SystemRoot%;d:binArgyll_V1.8.0bin', - i.e. you append the path to the Argyll binaries to your PATH, separated by the ';' character. The change will take effect when you start a new command shell, which you start from Start Menu->Accessories->Command Prompt, or Start Menu->Programs->Accessories->Command Prompt. You can check that the environment variable has been set by running the command 'echo %PATH%' in the command shell.
The .zip file also contains several useful reference files (such as scanner chart recognition templates, sample illumination spectrum etc.) in the ref sub-directory, all the current documentation in a doc sub-directory, and instrument USB drivers in the usb directory.
NOTE: Vista 64/Windows 7, 8,8.1 & 10 64 bit and Beep prompt: Microsoft (in its infinite wisdom) has removed the built in speaker driver, and now relies on systems having a sound card and speakers's installed and turned on to hear system beeps. So if you're wondering where the beeps have gone when using chartread, now you know.
NOTE: Microsofts generic VGA Driver does not appear to support setting the display VideoLUTs. You will need to install a display driver for your specific display hardware to enable this. Note that it is possible in many cases to use Windows 7 video drivers on Windows 8 systems.
NOTE that if you wish to use Argyll tools (dispwin) to control display calibration, that you will have to disable any other display calibration loader programs.
There are other programs that will interfere with calibration loading, such as igfxpers.exe that gets installed with nVidia 'Optimus' technology.
You may have to disable both the igfx tray module (c:windowssystem32igfxtray.exe) and the igfxpph Module (c:windowssystem32igfxpph.dll) in addition to the persistence Module (c:windowssystem32igfxpers.exe).
A good tool for this is AutoRuns. Note that the igfxpph module may exist in several locations and you have to disable all of them. Reboot after changing settings.
Serial Instruments:
If you are using a serial connected instrument, then there is nothing special to do to enable this.USB Instruments:
If you are using a USB connected instrument, then suitable USB system drivers may need to be installed.Note that the Huey, i1 Display Pro, ColorMunki Display and ColorHug colorimeter appears as an HID (USB Human Interface Device Class) device, and hence will be assigned to the default MSWindows HID driver. You therefore don't need to install an Argyll usb system driver for these instruments, although it is possible to select the libusb0.sys driver as an alternative to the default HID driver.
If you are using the JETI specbos 1211, 1201, 1511, 1501 and the Klien K10A then you may need to install the FTDI Virtual COM Port Drivers (VCP), if they are not already on your system. You may have to update to the latest FTDI driver to work with the FTDI FT231XS chip that the JETI specbos 1511, 1501 use.
Jump to your operating system version:
Windows 8, 8.1 & 10
Windows 7
Windows Vista
Windows XP
Windows 2000
Windows 8, 8.1 & 10
Fresh Install of Instrument USB driver:
If you currently don't have any applications that talk to your instrument using USB, then it is relatively simple to use the drivers provided with Argyll, since you don't have to deal with the instrument already having an assigned driver.
Windows 8/8.1/10 does not automatically pop up a 'New Hardware' dialog, so you will have to open the Device Manager manually, and you will also have to temporarily disable UBS driver .inf signature enforcement.
Please NOTE that on some versions of Windows 10, you may have to temporarily disable secure boot in your UEFI BIOS to be able to Disable Driver Signature Enforcement.
To install the Argyll driver for the first instrument:
Settings -> Power -> Hold Shift Key down and click 'Restart' -> Troubleshoot -> Advanced Options -> Startup Settings -> Restart ->
(After Reboot) -> 'Disable Driver Signature Enforcement' (number 7 on the list)
(After system starts, Plug in instrument)
Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager ->
Other Devices -> <instrument being installed> -> right click -> Update Driver Software... -> Browse my computer for driver software -> Browse...
-> argyllusb folder -> Next -> Install this driver software anyway -> Close
On subsequent installation of other supported instrument types:
Simply plug the instrument in. The Argyll driver will be automatically selected.
Using Argyll drivers with existing OEM drivers:
If you currently have applications other than Argyll accessing your USB connected instrument, then you will have to manually install the Argyll driver, and then switch back and forth between the Argyll and other drivers if you want to switch between applications.
To install the Argyll Driver:
Settings -> Power -> Hold Shift Key down and click 'Restart' -> Troubleshoot -> Advanced Options -> Startup Settings -> Restart ->
(After Reboot) -> Disable Driver Signature Enforcement' (number 7 on the list)
(After system starts, Plug in instrument)
Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Update Driver Software... -> let me pick from a list of device drivers on my computer -> Have disk... -> Browse...
-> argyllusb folder -> select ArgyllCMS.inf -> Open -> OK -> Install this driver software anyway -> Close
To switch between drivers:
(Plug in the instrument)
Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Update Driver Software... -> let me pick from a list of device drivers on my computer
(Choose either the Argyll driver or another driver from the list)
-> Next -> Close
Un-installing Argyll driver:
If you are updating to a new version of Argyll which adds support for a new instrument that you want to use, then it may be necessary to uninstall all the existing Argyll USB driver and do a fresh re-install to update the relevant libusb system driver and .inf file. (This is true for updating to Argyll Version 2.0.0).
(Plug in the instrument)
Desktop -> Settings -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It will be underneath the Argyll LibUSB-win32 devices top level item.)
Right click on instrument -> Uninstall -> click 'Delete the driver software for this device' -> OK
Proceed then with either Fresh Install of Argyll USB driver or Adding Argyll drivers to existing drivers above.
Windows Vista & Windows 7
Fresh Install of Instrument USB driver:
If you currently don't have any applications that talk to your instrument using USB, then it is relatively simple to use the drivers provided with Argyll since you don't have to deal with the instrument already having an assigned driver.
To install the Argyll driver for the first instrument:
(Plug in instrument)
(Wait for the 'Found New Hardware' or 'Installing new device driver software - Device driver software was not successfully installed' popup and dismiss it)
Start -> Control Panel -> Hardware and Sound -> Device Manager ->
Other Devices -> <instrument being installed> -> right click -> Update Driver Software... -> Browse my computer for driver software -> Browse...
-> argyllusb folder -> Next -> Install this driver software anyway -> Close
On subsequent installation of other instrument types:
Simply plug the instrument in. The Argyll driver will be automatically installed.
Using Argyll drivers with existing OEM drivers:
If you currently have applications other than Argyll accessing your USB connected instrument, then you will have to manually install the Argyll driver, and then switch back and forth between the Argyll and other drivers if you want to switch between applications.
To install the Argyll Driver:
(Plug in instrument)
Start -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Update Driver Software... -> let me pick from a list of device drivers on my computer -> Have disk... -> Browse...
-> argyllusb folder -> select ArgyllCMS.inf -> Open -> OK -> Install this driver software anyway -> Close
To switch between drivers:
(Plug in the instrument)
Start -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Update Driver Software... -> let me pick from a list of device drivers on my computer
(Choose either the Argyll driver or another driver from the list)
-> Next -> Close
Un-installing Argyll driver:
If you are updating to a new version of Argyll which adds support for a new instrument that you want to use, then it may be necessary to uninstall all the existing Argyll USB driver and do a fresh re-install to update the relevant libusb system driver and .inf file. (This is true for updating to Argyll Version 2.0.0).
(Plug in the instrument)
Start -> Control Panel -> Hardware and Sound -> Device Manager
(Locate the instrument in the device list. It will be underneath the Argyll LibUSB-win32 devices top level item.)
Right click on instrument -> Uninstall -> click 'Delete the driver software for this device' -> OK
Proceed then with either
Velleman Instruments Port Devices Driver Windows 7
Fresh Install of Argyll USB driver or Adding Argyll drivers to existing drivers above.Windows XP
Fresh Install of Instrument USB driver:
If you currently don't have any applications that talk to your instrument using USB, then it is relatively simple to use the drivers provided with Argyll since you don't have to deal with the instrument already having an assigned driver.
To install the Argyll driver for the first instrument:
(Plug in instrument)
(Wait for the 'Welcome to the Found New Hardware Wizard' popups and dismiss it)
My Computer, Right Click -> Manage -> Device Manager
Other Devices -> <instrument being installed> -> right click -> Update Driver... -> No, not this time -> Next
->Install from a list or specific location (Advanced) -> Next -> Don't search. I will choose the driver to install -> Next
-> Have Disk... -> Browse -> argyllusb folder -> ArgyllCMS.inf -> Open -> OK -> Next -> Finish
On subsequent installation of other instrument types:
(Plug the instrument in, and wait for the 'Welcome to the Found New Hardware Wizard' to pop up.)
No, not this time -> Install the software automatically (Recommended) -> Next -> Finish
Using Argyll drivers with existing OEM drivers:
If you currently have applications other than Argyll accessing your USB connected instrument, then you will have to manually install the Argyll driver, and then switch back and forth between the Argyll and other drivers if you want to switch between applications.
To install the Argyll Driver:
(Plug in instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> right click -> Update Driver... -> No, not this time -> Next
->Install from a list or specific location (Advanced) -> Next -> Don't search. I will choose the driver to install -> Next
-> Have Disk... -> Browse -> argyllusb folder -> ArgyllCMS.inf -> Open -> OK -> Next -> Finish
To switch between drivers:
(Plug in the instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Update Driver... -> No, not this time -> Next
->Install from a list or specific location (Advanced) -> Next -> Don't search. I will choose the driver to install -> Next
->let me pick from a list of device drivers on my computer
(Choose either the Argyll driver or another driver from the list)
-> Next -> Finish
Un-installing Argyll driver:
If you are updating to a new version of Argyll which adds support for a new instrument that you want to use, then it may be necessary to uninstall all the existing Argyll USB driver and do a fresh re-install to update the relevant libusb system driver and .inf file. (This is true for updating to Argyll Version 2.0.0).
(Plug in the instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It will be underneath the Argyll LibUSB-win32 devices top level item.)
Right click on instrument -> Uninstall -> click 'Delete the driver software for this device' -> OK
Then you will have to delete the cached copy of the old Argyll driver .inf files, that MSWindows keeps.
cd to where Windows keeps it's cached driver information files, ie:
c:
cd windowsinf
identify all the system copies of the Argyll .inf files:
find /I 'ArgyllCMS' oem*.inf
then delete just the files that contain 'ArgyllCMS':
del /F oemXXX.inf
del /F oemXXY.inf
etc.
Proceed then with either Fresh Install of Argyll USB driver or Adding Argyll drivers to existing drivers above.
Windows 2000
Fresh Install of Instrument USB driver:
If you currently don't have any applications that talk to your instrument using USB, then it is relatively simple to use the drivers provided with Argyll since you don't have to deal with the instrument already having an assigned driver.
Velleman Instruments Port Devices Drivers
To install the Argyll driver for the first instrument:
(Plug in instrument)
(Wait for the 'Welcome to the Found New Hardware Wizard' pops up) -> Next
-> Search for a suitable driver for my device (recommended) -> Next -> Specify a location -> Next
-> Browse -> argyllusb folder -> ArgyllCMS.inf -> Open -> OK -> Next -> Finish
On subsequent installation of other instrument types:
Simply plug the instrument in. The Argyll driver will be automatically installed.
Using Argyll drivers with existing OEM drivers:
If you currently have applications other than Argyll accessing your USB connected instrument, then you will have to manually install the Argyll driver, and then switch back and forth between the Argyll and other drivers if you want to switch between applications.
To install the Argyll Driver:
(Plug in instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Properties -> Driver -> Update Driver this time
-> 'Welcome to the Found New Hardware Wizard' -> Next -> Display a list of known drivers for this device so that I can choose a specific driver -> Next
-> Have Disk -> Browse -> argyllusb folder -> ArgyllCMS.inf -> Open -> OK -> Next -> Next -> Finish
To switch between drivers:
(Plug in instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Properties -> Driver -> Update Driver... -> Next
-> Display a list of known drivers for this device so that I can choose a specific driver -> Next
(Choose either the Argyll driver or another driver from the list)
-> Next -> Next -> Finish
Un-installing Argyll driver:
If you are updating to a new version of Argyll which adds support for a new instrument that you want to use, then it may be necessary to uninstall all the existing Argyll USB driver and do a fresh re-install to update the relevant libusb system driver and .inf file. (This is true for updating to Argyll Version 2.0.0).
(Plug in the instrument)
My Computer, Right Click -> Manage -> Device Manager
(Locate the instrument in the device list. It may be underneath one of the top level items.)
Right click on instrument -> Uninstall -> OK
Then you will have to delete the cached copy of the old Argyll driver .inf files, that MSWindows keeps.
cd to where Windows keeps it's cached driver information files, ie:
c:
cd winntinf
identify all the system copies of the Argyll .inf files:
find /I 'ArgyllCMS' oem*.inf
then delete just the files that contain 'ArgyllCMS':
del /F oemXXX.inf
del /F oemXXY.inf
etc.
Proceed then with either Fresh Install of Argyll USB driver or Adding Argyll drivers to existing drivers above.
By Trent Jarvi, MathWorks
Many MATLAB users who analyze data, develop and verify algorithms, or create software applications leave the MATLAB environment to import data from external hardware. This extra step creates inefficiencies by forcing the user to manually transfer data from one environment to another and to learn and maintain multiple software tools.
Using a Garmin handheld Global Positioning System (GPS) receiver with an RS-232 serial interface as an example, this article demonstrates how you can use MATLAB and Instrument Control Toolbox to work with diverse external devices without leaving the MATLAB environment. It explains how to communicate with a serial device, interact with the device in MATLAB, and automatically generate a MATLAB script that can be shared, reused, or incorporated into a MATLAB application.
The MATLAB scripts used in this article are available for download.
RS-232 serial devices, such as GPS receivers, and instruments, such as oscilloscopes and signal generators, can be configured and controlled in MATLAB with Instrument Control Toolbox (Figure 1). Our example uses a consumer-grade Garmin ETrex 12-channel GPS device, typically used while hiking and boating. The example uses electrical and data communications specified by National Marine Electronics Association (NMEA) 183 communication, which should work with any GPS device capable of serial communication. You could use other protocols, including Garmin’s proprietary protocol, if you have access to the specifications.
To find out what serial devices and instruments are available for communication, we can use MATLAB command-line functions, such as instrhwinfo, instrfind, and serial. Alternatively, we can use TMTool, a graphical user interface provided by Instrument Control Toolbox that lets you locate, configure, and control serial devices and instruments without writing MATLAB script (Figure 2). First, we will explore available hardware assets using a hierarchical tree.
Communicating with a device to acquire data often requires establishing a connection to its communication interface. With TMTool we can configure, control, and acquire data from devices through well-established interfaces, including serial, GPIB, TCP/IP and UDP (Figure 3). We can also use TMTool to communicate with instruments using VISA, LXI, or IVI and VXIplug&play drivers.
In Figure 4, the serial node has been expanded to show the serial ports available for communication. The GPS is configured to broadcast NMEA format data, a common option in consumer-grade GPS receivers.
After connecting the GPS receiver to COM1, we select the Configure tab for COM1 and set it to match the serial port parameters. NMEA defines these parameters as baud rate 4800 bits per second, 8 data bits, 1 stop bit and no parity.
After configuring the serial port parameters, we open the connection via the serial port. The Connection status changes to Connected, indicating that communication with the GPS through the Communicate tab is now possible. The NMEA standard specifies that data must be transmitted as ASCII characters in new line-terminated strings. Using the dropdown menu, we set the “Receiving data” parameters to comply with this specification.
We can now send data to the hardware and read the responses. For our example, all we need to do is read the data broadcast from the GPS. We can confirm that we are communicating properly and that the data of interest is available by clicking the Read button several times to observe that properly formatted strings are being acquired in the sequential log. After a few attempts, the GPS coordinates of interest appear in the results, together with several other NMEA data types. Finally, we close the connection to the GPS device to capture the disconnect as MATLAB script in the session log for later reference.
Once we have configured the port, read the strings, and acquired the data in which we are interested, we can repeat this series of tasks in the future by simply exporting the generated script to a MATLAB file called get_gps_location.m. We can then execute the MATLAB script that was automatically generated when we interacted with TMTool (Figure 6).
So far, we have configured the hardware and acquired the data, but some of the data that we acquired, such as waypoints and time information, is not specific to the GPS location. With TMTool, we can automatically filter out this unwanted data, just as we automated the hardware configuration and data acquisition by adding MATLAB script to a MATLAB instrument driver. TMTool automatically updates the MATLAB script generated in the Session Log tab. Once we have exported the updated script MATLAB_GPS_example.m, we can insert MATLAB routines to filter the data stream.
To acquire and process the GPS data, simply execute the MATLAB_GPS_example.m file on the command line.
While the MATLAB workflow discussed so far will be sufficient for some applications, others might benefit from incorporating the MATLAB script into a reusable driver. We can incorporate the MATLAB script into a reusable driver by using MIDEdit, a driver development tool in Instrument Control Toolbox (Figure 7). MIDEdit lets you incorporate lower-level commands into higher-level commands that are easier to access. After launching MIDEdit from the command line, we create a new generic instrument driver through the File->New context menu.
To demonstrate the use of a self-contained, reusable driver in MATLAB, we will add just two pieces of functionality to the driver: configure the GPS device and acquire the GPS location. With MIDEdit we could also create more advanced drivers comprising hundreds of lines of code.
To configure the GPS device, we browse to the automatically generated MATLAB script in the TMTool session log. This script sets the baud rate and then opens the port. We can now copy this information into a driver. Within MIDEdit, we select the Connect tab from the Initialization and Cleanup node and set the Function Style to M-Code. We then paste the script from TMTool into the function created in the driver editor. Noting that the serial interface may be obtained from the variable obj passed into this function, the MATLAB script is adjusted to use the serial port interface.
To acquire the GPS location, we select the Function node in MIDEdit and add a new function called getLocation(). This function will obtain the latitude, longitude, and cardinals. In the MATLAB code editor pane, we paste in the MATLAB script that reads the NMEA lines. As in our first example, we modify the function to return an array representing the GPS location. We add logic that instructs getLocation() to find only the GPS coordinates in the NMEA stream and to return the location. More functions could be added for each type of NMEA information found in the stream. Finally, we save the driver to our workspace as nmeareceiver.mdd.
The driver is now ready to be used with the GPS device. We use TMTool to expand the Instrument Drivers node and create a new interface object by right-clicking the Interface Objects node under the Instrument Objects node. We select a serial port interface object and set the port to the serial port to which the GPS is connected. The interface object could be configured, opened, and read using the process described in the previous section, but this time we will use the instrument driver to perform our acquisition and analysis tasks.
We select the Instrument Objects node and enter the information for the instrument driver nmeareceiver.mdd by right-clicking and selecting new Device Object. We then connect the GPS to the serial port represented by the interface object. It is possible to change the interface if the device and driver support more than one interface. When completed, the nmeareceiver instance will appear under the Device Objects node.
We can now connect to the GPS using the Connect button. Under the Functions tab, we can execute the getLocation() function, resulting in the current location being acquired. We can export the results to the workspace for further analysis.
MATLAB script is automatically generated when you interact with the driver in TMTool. As when working with the GPS device without using a driver, this generated script lets you reuse your work later to communicate with the device
We can enhance the reusability of the driver by adding functions, such as the datum being used, date and time, or waypoints. The driver can be shared with users who do not need to understand in detail how to communicate with their device.
We used a GPS device to demonstrate how to configure and acquire data from external hardware without leaving the MATLAB environment. We used MATLAB and Instrument Control Toolbox to communicate with this hardware without writing a MATLAB script, demonstrated how to reuse our work using a MATLAB script automatically generated to communicate with the hardware, and how to incorporate functionality into MATLAB function calls through drivers. Using MATLAB improves work efficiency by eliminating the need to manually transfer data from one environment or learn and maintain multiple software tools.
Published 2007