26-03-2021

Sensoray Driver

Available in either serial digital interface (SDI) or digital video interface (DVI), the Model 3364 USB 3.0 video capture board from Sensoray requires no device-specific driver and captures uncompressed SD/HD video in resolutions up to 1080p60 and uses H.264 video compression for inputs up to 1080p30, both with very low latency. After loading driver it should state that s626 driver initialized the card and it was attached. Before loading driver consult lspci if the Sensoray 626 I/O board is visible! Also if you are going to use more than one s626 card you have to consult lspci for slot and bus number on which each card is present. Within the repository is a folder named s626-1.0.1, which contains the Sensoray's Linux SDK files (v1.0.1) that are also available on the product website. The README file in this folder has instructions for building and installing the kernel level driver for the 626.

Sensoray released its Model 518, a smart 8-channel sensor measurement system on a PC/104 board that has a newly added Linux driver, offering excitation for passive sensors and signal conditioning for thermocouples, RTDs, thermistors, and strain and pressure gauges.

Trying a reinstall of the Sensoray SDK software and the 2250 AV Capture driver (in the Device Manager) does not help. The solution is one of two different things- Go to the Program Files/Sensoray/2250/API folder and copy ALL of the files - Go to the Program Files/Huntron Workstation folder and paste all of the copied files there - Restart the PC. The unit is a UVC (USB Video Class) device, which means it does not require a device-specific driver and can be easily controlled using popular video APIs such as DirectShow and Video4Linux. Sensoray provides Software Development Kits (SDKs) for several operating systems to accelerate application development.

Sensory driven behaviorDriver

It is designed so individual channels can be structured independently for measuring voltage, resistance, or any kind of supported sensor.

Features of the Model 518 sensor board include:

  • Excitation – applied during measuring, diminishing sensor self-heating and overall board power consumption.
  • Lossless measurement – provisioning for elimination of lead loss errors from RTD, thermistor, and resistor measurements.
  • Thermocouples – Uses cold junction compensation along with an elective, external temperature transducer.
  • Calibration – guarantees reliable functionality in high-vibration environments. Factory-programmed calibration data are stored on-board for accelerated installation.
  • Sensor Connections – All field wiring signals are at hand via a 40-pin header, with the options to connect the header to a custom termination system or to any of Sensoray’s breakout boards.
Typical Application

For more information, visit www.sensoray.com.

-->

This topic shows you how to install the sensor driver on a development board, after you update the secondary system description table (SSDT) for the development board.

This topic uses the Sharks Cove development board and an ADXL345 accelerometer as a case study, to help explain the process of installing a sensor driver on a development board. So if you want to perform the tasks presented in this topic, you must first install an operating system on the Sharks Cove. For more information about how to do that, see Download kits and tools for Windows 10, and follow the instructions to install Windows 10.

After you finish installing the operating system on the Sharks Cove, See Build the sensor driver to learn how to build a driver in Microsoft Visual Studio. Then return here to continue.

The accelerometer is attached to the Sharks Cove via the I2C bus. Peripherals that are connected to the I2C bus are enumerated via the Advanced Configuration and Power Interface (ACPI). So the sample driver for the accelerometer was developed to support ACPI instead of Plug and Play.

To make the Sharks Cove's ACPI driver aware of the new device (the accelerometer) on the I2C bus, you must add information about the accelerometer to the SSDT on the Sharks Cove. This table describes the hardware resources and interrupt requirements for a hardware platform's devices, including attached peripherals like the accelerometer.

Before you begin

Before you start performing the tasks outlined below, please make sure that your Sharks Cove is set up as shown in the following image:

Retrieve and review the default SSDT

This section shows you how to use the ACPI Source Language (ASL) compiler to retrieve the factory default SSDT for the Sharks Cove, and then review it. You will also learn how to replace the default SSDT with an updated one.

  1. On your development computer, navigate to the following location to copy the ASL compiler:c:Program Files (x86)Windows Kits10Toolsx86ACPIVerify

  2. Copy the Asl.exe file, and save it to a flash drive.

  3. On the Sharks Cove, create a Tools folder in the root directory. Then Attach the flash drive to the Sharks Cove's USB hub, and copy the Asl.exe file to the Tools folder.

  4. Open a Command prompt window as an administrator, and enter the following commands:cdtoolsdirMake sure that the Asl.exe file is listed in the directory.

  5. Invoke the ASL compiler and create an ASL file by entering the following command:asl /tab=ssdt

  6. Make sure that the ASL file was created successfully by entering the following command:dir ssdt.asl

  7. Open the ASL file in Notepad by entering the following command:notepad ssdt.aslReview the ASL file, and notice that there are no references to the accelerometer, or the I2C bus.

  8. Close Notepad. Then enter the following command in the Command prompt window, to rename the ssdt.asl file.ren ssdt.asl ssdt-old.aslThen use the dir command to make sure that the file is now listed as ssdt-old.asl.

Update the default SSDT

Perform the following tasks to update the SSDT, and load it to replace the factory default version. The updated SSDT will be stored in a potion of memory called battery-backed RAM. So make sure that the button cell (battery) that came with your Sharks Cove is plugged into its socket.

  1. Copy the following updated SSDT and paste it into a new instance of Notepad.

  2. In Notepad, select File > Save As. Then select the Save as type dropdown box, and select All Files.

  3. In the File name box, type ssdt.asl, then select Save, and close Notepad.

  4. In the Command prompt window, use the dir command to make sure that you can see the default file now listed as ssdt-old.asl, and the new file listed as ssdt.asl.

  5. Compile the ssdt.asl file into a format that the Sharks Cove can understand by entering the following command:asl ssdt.asl

  6. Verify that the compiled file was successfully created in Step 3 by entering the following command:dir ssdt.amlYou should see the ssdt.aml file listed in the tools directory.

  7. Load the compiled file into battery-backed RAM by entering the following command:asl /loadtable ssdt.aml

Turn on testsigning

Driver

Before you install the sample sensor driver, you must turn on testsigning. Perform the following tasks to turn on testsigning. Perform the following steps to install the sensor driver via Device Manager.

  1. In the Command prompt window, enter the following command to see whether testsigning is already turned on.
    bcdedit /enum

  2. If you see a listing similar to the following, showing an entry for testsigning, with its value set to yes then skip to Step 5.

  3. If you need to turn on test signing, then enter the following command:bcdedit /set testsigning on

  4. Repeat Step 1 (in this exercise) to verify that the value of the testsigning system variable is now set to 'yes' in the Windows Boot Loader list.

  5. Restart the Sharks Cove. As the board restarts, hold the Volume-up button for about 2 seconds, to enter system setup (UEFI) window.

  6. In the UEFI window, select Device Manager > System Setup > Boot, and make sure that UEFI Security Boot is set to <Disable>.

  7. Save your changes and exit the UEFI window.

Install the sensor driver

There are four main methods for installing a driver on the Sharks Cove board:

  • Download the driver from a network source directly onto the Sharks Cove.
  • Develop the sensor driver on a host computer, with your Sharks Cove connected as a provisioned client. Then deploy the driver from the host computer to the Sharks Cove.
  • Copy the driver package to a flash drive and attach the flash drive to the Sharks Cove. Then use the devcon command from a Command prompt window to install the driver manually.
  • Copy the driver package to a flash drive and attach the flash drive to the Sharks Cove. Then install the driver manually via Device Manager.

For simplicity, we will use the last method in the preceding list. Perform the following steps to manually install the sensor driver via Device Manager.

You must connect your sensor to the Sharks Cove before you install the sensor driver. For information about how to modify the ADXL345 accelerometer breakout board from SparkFun, to get it to work with the sample sensor driver, see Prepare your sensor test board. And for information about how to connect the sensor breakout board to the Sharks Cove, see Connect your sensor to the Sharks Cove board.

Driver

  1. Make sure that the ADXL345 accelerometer is connected to the Sharks Cove J1C1 connector, then power up the Sharks Cove.

  2. Attach a flash drive with the sensor driver to the powered USB hub connected to the Sharks Cove. For example, this can be the flash drive onto which you saved the driver that you built by following the steps in Build the sensor driver.

  3. Open Device Manager, and look for an 'Unknown device' in the Other devices node with a yellow bang symbol against it (see the following screen shot).

  4. Select and hold (or right-click) the device with the yellow bang (listed as Unknown device), and select Update Driver Software, and select Browse my computer for driver software.

  5. Browse to the ADXL345 driver on the flash drive, then select Next. Follow the screen prompts to install the sensor driver.

  6. After the sample sensor driver is successfully installed, Device Manager displays the sensor as shown in the following screen shot.

Sensory Drive

For information about how to use Visual Studio to deploy a driver to a client computer (like the Sharks Cove), see Deploying a Driver to a Test Computer.

Sensory Driven Behavior

After successfully installing the sample sensor driver, see Test your universal sensor driver for information about how to test a sensor.