Wiki

Analog Devices Wiki

English
English
简体中文
简体中文
日本語
日本語
Руccкий
Руccкий

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x [13 May 2022 16:05] – Joyce Velascoresources:eval:user-guides:circuits-from-the-lab:eval-adpd410x [22 Jun 2022 06:25] – Angelo Nikko Catapang
Line 8: Line 8:
  
 ===== Device Driver and Support ===== ===== Device Driver and Support =====
-A no-OS device driver and example program is provided, targeting the [[ADI>EVAL-ADICUP3029]] platform. The ADICUP3029 example application uses the ADPD410x no-OS driver and emulates the Linux IIO framework through the tinyiiod daemon library. The application communicates with the host computer via the serial backend over a USB-UART physical connection. This facilitates rapid application development on a host computer, independent from embedded code development.+A no-OS device driver and an example program are provided, targeting the [[ADI>EVAL-ADICUP3029]] platform. The ADICUP3029 example application uses the ADPD410x no-OS driver and emulates the Linux IIO framework through the tinyiiod daemon library. The application communicates with the host computer via the serial backend over a USB-UART physical connection. This facilitates rapid application development on a host computer, independent from embedded code development. 
 Similarly, utility software (such as iio_info, IIO Oscilloscope, PyADI-IIO, etc.) typically associated with Linux systems can be used with this no-OS implementation. Similarly, utility software (such as iio_info, IIO Oscilloscope, PyADI-IIO, etc.) typically associated with Linux systems can be used with this no-OS implementation.
  
Line 51: Line 52:
  
 ==== Prototyping Connectors ==== ==== Prototyping Connectors ====
-The board has two parallel 18-pin 100-mil pitch male connectors, which give access to the LED driver channels, the photodiode inputs, custom I/O pins from the AFE, and supply voltage for the LED. The user can use this along with the break-away protoboard to implement a custom circuit for testing. The pin assignment and functions are shown below. +The board has two parallel 18-pin, 100-mil pitch male connectors, which give access to the LED driver channels, the photodiode inputs, custom I/O pins from the AFE, and supply voltage for the LED. The user can use this along with the break-away protoboard to implement a custom circuit for testing. The pin assignment and functions are shown below. 
  
 {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pinassignment.jpg?nolink&400|}}{{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pinassignmentdiagram.png?nolink&400|}} {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pinassignment.jpg?nolink&400|}}{{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pinassignmentdiagram.png?nolink&400|}}
Line 57: Line 58:
 Pins labeled **XYC** (where X refers to LED 1, 2, 3, or 4, and Y refers to channel A or B) denote connections to the LED cathode which are voltage protected via transistors to the ADPD4100/1 LED inputs (denoted by **LXY**). It is recommended to connect LED cathodes to these pins instead of connecting directly to **LXY** pins. **PDXY** (X refers to photodiode 1, 2, 3, or 4 and Y refers to channel A or B) pins denote photodiode signal inputs to the AFE. **ACOM** and **BCOM** pins refer to the common cathode bias output for photodiode sensors. These should be connected to the cathodes of photodiodes in the matching channel (for example, photodiodes connected to PD1A, PD2A, PD3A, and PD4A should have their cathodes connected to ACOM). Pins labeled **XYC** (where X refers to LED 1, 2, 3, or 4, and Y refers to channel A or B) denote connections to the LED cathode which are voltage protected via transistors to the ADPD4100/1 LED inputs (denoted by **LXY**). It is recommended to connect LED cathodes to these pins instead of connecting directly to **LXY** pins. **PDXY** (X refers to photodiode 1, 2, 3, or 4 and Y refers to channel A or B) pins denote photodiode signal inputs to the AFE. **ACOM** and **BCOM** pins refer to the common cathode bias output for photodiode sensors. These should be connected to the cathodes of photodiodes in the matching channel (for example, photodiodes connected to PD1A, PD2A, PD3A, and PD4A should have their cathodes connected to ACOM).
  
-A simple circuit for testing LED driver outputs and photodiode current sensing using the break-away prototype board can easily be set up using optocouplers as shown below.+A simple circuit for testing LED driver outputs and photodiode current sensing using the break-away prototype board can easily be set up using optocouplers, as shown below.
  
 {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:testschematic.png?nolink&600|}} {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:testschematic.png?nolink&600|}}
Line 75: Line 76:
  
 ==== Dragging and Dropping the Hex File to the Daplink Drive ==== ==== Dragging and Dropping the Hex File to the Daplink Drive ====
-  - Ensure that the [[ADI>EVAL-ADICUP3029]] board switches are set to the correct configuration as detailed in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#general_connection|General Connection]].+  - Ensure that the [[ADI>EVAL-ADICUP3029]] board switches are set to the correct configuration, as detailed in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#general_connection|General Connection]].
   - Connect the [[ADI>EVAL-ADICUP3029]] board to the PC or laptop using the Micro USB to USB cable.   - Connect the [[ADI>EVAL-ADICUP3029]] board to the PC or laptop using the Micro USB to USB cable.
   - Drag and Drop the appropriate .hex file from the list below to the Daplink Drive. {{:resources:eval:user-guides:eval-adicup3029:tools:daplink_windows_explorer.png?550|}}   - Drag and Drop the appropriate .hex file from the list below to the Daplink Drive. {{:resources:eval:user-guides:eval-adicup3029:tools:daplink_windows_explorer.png?550|}}
Line 81: Line 82:
  
 <WRAP todo> <WRAP todo>
-Prerelease hex files can be found inside this zip archive: {{ :resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x-ardz_pre-release_hex_files.zip |}}. For the latest build, see [[repo>EVAL-ADICUP3029/releases/tag/Latest]]. +Pre-built hex files can be found inside this zip archive: [[repo>EVAL-ADICUP3029/releases/tag/Latest]]. The latest source code can be found in [[repo>EVAL-ADICUP3029/tree/master/projects/ADuCM3029_demo_adpd410x]]. 
-  * For EVAL-ADPD4100: EVAL-ADPD4100-ARDZ.hex +  * For EVAL-ADPD4100, use ADuCM3029_demo_adpd410x_spi.hex 
-  * For EVAL-ADPD4101: EVAL-ADPD4101-ARDZ.hex+  * For EVAL-ADPD4101, use ADuCM3029_demo_adpd410x_i2c.hex
 </WRAP> </WRAP>
  
 ==== Using CrossCore Embedded Studio ==== ==== Using CrossCore Embedded Studio ====
   - Acquire a copy of the project source files of the EVAL-ADPD410X-ARDZ by downloading the source files directly from the repository at [[repo>EVAL-ADICUP3029/tree/dev/cn0567/projects/ADuCM3029_demo_cn0567]] or you can clone the entire [[https://github.com/analogdevicesinc/EVAL-ADICUP3029 | EVAL-ADICUP3029 repository]] and check the projects folder for ADuCM3029_demo_cn0567.   - Acquire a copy of the project source files of the EVAL-ADPD410X-ARDZ by downloading the source files directly from the repository at [[repo>EVAL-ADICUP3029/tree/dev/cn0567/projects/ADuCM3029_demo_cn0567]] or you can clone the entire [[https://github.com/analogdevicesinc/EVAL-ADICUP3029 | EVAL-ADICUP3029 repository]] and check the projects folder for ADuCM3029_demo_cn0567.
-  - Open CrossCore Embedded Studio and import the project into your workspace as detailed in the [[:resources:eval:user-guides:eval-adicup3029:tools:cces_user_guide]]. This allows you to edit the software to fit your requirements. <WRAP important>If this is your first time using CrossCore Embedded Studio, check the [[:resources:eval:user-guides:eval-adicup3029:tools:cces_user_guide | user guide]] to get you started.</WRAP>+  - Open CrossCore Embedded Studio and import the project into your workspace, as detailed in the [[:resources:eval:user-guides:eval-adicup3029:tools:cces_user_guide]]. This allows you to edit the software to fit your requirements. <WRAP important>If this is your first time using CrossCore Embedded Studio, check the [[:resources:eval:user-guides:eval-adicup3029:tools:cces_user_guide | user guide]] to get started.</WRAP>
   - Once ready, you can opt to generate your own .hex file and use the first method to program the **[[ADI>EVAL-ADICUP3029]]** or you can use a debug session by following the quickstart guide.   - Once ready, you can opt to generate your own .hex file and use the first method to program the **[[ADI>EVAL-ADICUP3029]]** or you can use a debug session by following the quickstart guide.
  
Line 97: Line 98:
 You can configure the default timeslots and other settings of the [[ADI>ADPD4100]] or [[ADI>ADPD4101]] using [[https://github.com/analogdevicesinc/EVAL-ADICUP3029/blob/master/projects/ADuCM3029_demo_cn0567/src/cn0567_config.h|cn0567_config.h]]. You can configure the default timeslots and other settings of the [[ADI>ADPD4100]] or [[ADI>ADPD4101]] using [[https://github.com/analogdevicesinc/EVAL-ADICUP3029/blob/master/projects/ADuCM3029_demo_cn0567/src/cn0567_config.h|cn0567_config.h]].
   * You can set the default number of active timeslots and output data rate.\\ {{:resources:eval:user-guides:circuits-from-the-lab:activetimeslots_odr.png?nolink&400|}}   * You can set the default number of active timeslots and output data rate.\\ {{:resources:eval:user-guides:circuits-from-the-lab:activetimeslots_odr.png?nolink&400|}}
-  * Initial timeslot settings are configured using the **adpd410x_timeslot_init** data structure as shown below:\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_datastructure.png?nolink&400|}}+  * Initial timeslot settings are configured using the **adpd410x_timeslot_init** data structure, as shown below:\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_datastructure.png?nolink&400|}}
     * **Enabling ADC channel 2**\\ Each timeslot can use the two ADC input channels of the ADPD4100/1. By default, the timeslot only uses channel 1. Setting this to true will enable channel 2.     * **Enabling ADC channel 2**\\ Each timeslot can use the two ADC input channels of the ADPD4100/1. By default, the timeslot only uses channel 1. Setting this to true will enable channel 2.
-    * **Timeslot Inputs**\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_inputs.png?nolink&400|}}\\ Each timeslot input can be set to use a pair of input pins of the ADPD4100/1. Below are possible pair options\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_pairoptions.png?nolink&400|}}\\: Each of the input pins can be disabled or routed to any or both of the channels. Below are the possible configurations of the input pins.\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_inputoptions.png?nolink&400|}}+    * **Timeslot Inputs**\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_inputs.png?nolink&400|}}\\ Each timeslot input can be set to use a pair of input pins of the ADPD4100/1. Below are possible pair options:\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_pairoptions.png?nolink&400|}}\\ 
 +    * Each of the input pins can be disabled or routed to any or both of the channels. Below are the possible configurations of the input pins.\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_inputoptions.png?nolink&400|}}\\ 
     * **Timeslot Input Preconditioning**\\ Timeslot inputs have programmable connections, which precondition the sensor to set operating conditions before sampling. Below are the possible options:\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_precond.png?nolink&400|}}     * **Timeslot Input Preconditioning**\\ Timeslot inputs have programmable connections, which precondition the sensor to set operating conditions before sampling. Below are the possible options:\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_precond.png?nolink&400|}}
-    * **TIA Reference Voltage**\\ The reference voltage of the TIA (Trans-Impedance Amplifier) is configurable. Below are the possible values:\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_tiavref.png?nolink&400|}} +    * **TIA Reference Voltage**\\ The reference voltage of the Trans-Impedance Amplifier (TIA) is configurable. Below are the possible values:\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_tiavref.png?nolink&400|}} 
-    * **TIA Gain Resistor**\\ The gain resistor used by the TIA (Trans-Impedance Amplifier) is configurable for each input channel. Below are the possible values:\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_tiares.png?nolink&400|}}+    * **TIA Gain Resistor**\\ The gain resistor used by the TIA is configurable for each input channel. Below are the possible values:\\ {{:resources:eval:user-guides:circuits-from-the-lab:timeslot_tiares.png?nolink&400|}}
     * **Multiple Pulses and Integrator Chopping** The ADPD4100/1 is capable of improving SNR using multiple pulses per sample and integrator chopping, which have configurable settings.     * **Multiple Pulses and Integrator Chopping** The ADPD4100/1 is capable of improving SNR using multiple pulses per sample and integrator chopping, which have configurable settings.
       * **4-Pulse Reverse Pattern**\\ Each pulse from the LED in a set of 4 can be configured to either have an on-off or off-on integrator chopping sequence. This is a 4-bit value, 1 bit for each pulse. Setting a bit reverses the integrator chopping sequence for that pulse.       * **4-Pulse Reverse Pattern**\\ Each pulse from the LED in a set of 4 can be configured to either have an on-off or off-on integrator chopping sequence. This is a 4-bit value, 1 bit for each pulse. Setting a bit reverses the integrator chopping sequence for that pulse.
Line 125: Line 128:
  
 ==== Connection ==== ==== Connection ====
-The device must be able to create a context. Context creation in the software depends on the backend used to connect the device. This guide covers the device communication using the currently supported platform, a serial backend through a USB-UART connection. A simple way of checking, if the device is connected, is through the **[[:resources:tools-software:linux-software:libiio:iio_info | iio_info]]** command. Specifically, it reports all IIO attributes of a detected device and context. To do this, simply enter the command shown below to a terminal / command line.+The device must be able to create a context. Context creation in the software depends on the backend used to connect the device. This guide covers the device communication using the currently supported platform, a serial backend through a USB-UART connection. A simple way of checking, if the device is connected, is through the **[[:resources:tools-software:linux-software:libiio:iio_info | iio_info]]** command. Specifically, it reports all IIO attributes of a detected device and context. To do this, simply enter the below command to a terminal or command line.
 <code> <code>
 iio_info -u serial:<serial port> iio_info -u serial:<serial port>
Line 155: Line 158:
 The -d option of the **[[:resources:tools-software:linux-software:libiio:iio_attr | iio_attr]]** command allows reading or writing (only for specific items) of device attributes. For example, the //sampling_frequency// attribute is readable and writeable. The command to read and write to this attribute is shown below: The -d option of the **[[:resources:tools-software:linux-software:libiio:iio_attr | iio_attr]]** command allows reading or writing (only for specific items) of device attributes. For example, the //sampling_frequency// attribute is readable and writeable. The command to read and write to this attribute is shown below:
 <code> <code>
-For reading: iio_attr -u <URI> -d <DEVICENAME> <ATTRIBUTE> +For reading, use iio_attr -u <URI> -d <DEVICENAME> <ATTRIBUTE> 
-For writing: iio_attr -u <URI> -d <DEVICENAME> <ATTRIBUTE> <VALUE> +For writing, use iio_attr -u <URI> -d <DEVICENAME> <ATTRIBUTE> <VALUE> 
-E.g. for a Windows Machine+e.g., for a Windows Machine
 iio_attr -u serial:COM4 -d adpd410x sampling_frequency 40 iio_attr -u serial:COM4 -d adpd410x sampling_frequency 40
 </code> </code>
Line 167: Line 170:
  
 ==== IIO Oscilloscope ==== ==== IIO Oscilloscope ====
-<note important>Make sure to download/update to the latest version of IIO-Oscilloscope found on this link[[https://github.com/analogdevicesinc/iio-oscilloscope/releases]]</note>+<note important>Make sure to download/update to the latest version of IIO-Oscilloscope found on this link[[https://github.com/analogdevicesinc/iio-oscilloscope/releases]].</note>
   - Install and start IIO-Oscilloscope. There are two options you can use to select IIO contexts. First, you can use the Serial option and input the correct port settings of the board from the Device Manager. Another way is by manually entering the URI used in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#connection | Connection]]. \\ {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:iio-oscilloscopeserialcontext.png?nolink&400|}}{{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:iio-oscilloscopemanualcontext.png?nolink&400|}}   - Install and start IIO-Oscilloscope. There are two options you can use to select IIO contexts. First, you can use the Serial option and input the correct port settings of the board from the Device Manager. Another way is by manually entering the URI used in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#connection | Connection]]. \\ {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:iio-oscilloscopeserialcontext.png?nolink&400|}}{{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:iio-oscilloscopemanualcontext.png?nolink&400|}}
   - Press Refresh to display available IIO Devices, and once adpd410x is detected, press Connect. It may take several presses to Connect before the software proceeds and opens the Debug Panel and Waveform Panel\\. {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:iio-oscilloscopedetecteddevice.png?nolink&400|}}   - Press Refresh to display available IIO Devices, and once adpd410x is detected, press Connect. It may take several presses to Connect before the software proceeds and opens the Debug Panel and Waveform Panel\\. {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:iio-oscilloscopedetecteddevice.png?nolink&400|}}
Line 176: Line 179:
  
 === Waveform Panel === === Waveform Panel ===
-The Waveform panel, also known as the Capture window, displays the real-time waveform of selected photodiode channels of the ADPD410x. Select the desired channels to display in the upper left section. You can also edit the plot settings in the left section\\  +The Waveform panel, also known as the Capture window, displays the real-time waveform of selected photodiode channels of the ADPD410x. Select the desired channels to display in the upper left section. You can also edit the plot settings in the left section.\\  
 <WRAP important>You cannot use the Debug Panel and the Waveform Panel simultaneously. Using the Waveform Panel will freeze the Debug Panel.</WRAP> <WRAP important>You cannot use the Debug Panel and the Waveform Panel simultaneously. Using the Waveform Panel will freeze the Debug Panel.</WRAP>
 {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:iio-oscilloscopeplotinstructions.png?nolink&400|}}{{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:iio-oscilloscopeplot.png?nolink&400|}} {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:iio-oscilloscopeplotinstructions.png?nolink&400|}}{{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:iio-oscilloscopeplot.png?nolink&400|}}
Line 185: Line 188:
  
 === Installing the Packages === === Installing the Packages ===
-<note important>PyADI-IIO requires a Python installed on your computer. It is recommended to install Python 3.7 or higher</note>+<note important>PyADI-IIO requires a Python installed on your computer. It is recommended to install Python 3.7 or higher.</note>
 Install PyADI-IIO using one of the methods in [[/resources/tools-software/linux-software/pyadi-iio|PyADI-IIO]]\\.  Install PyADI-IIO using one of the methods in [[/resources/tools-software/linux-software/pyadi-iio|PyADI-IIO]]\\. 
  
Line 198: Line 201:
 ...\pyadi-iio\>python setup.py install ...\pyadi-iio\>python setup.py install
 </code> </code>
-<note important> One of the packages in //requirements_adiplot.txt// is the PyQt5. If you already have a pre-installed PyQt5 prior to the installation of the packages, we suggest that you uninstall the said package in the virtual environment. Duplicate installations may sometimes cause errors that inhibit the system from displaying the real-time plot. This can easily be done by inputting the command: //pip uninstall PyQt5// while the virtual environment is active. </note>+<note important> One of the packages in //requirements_adiplot.txt// is the PyQt5. If you already have a pre-installed PyQt5 prior to the installation of the packages, it is suggested that you uninstall the said package in the virtual environment. Duplicate installations may sometimes cause errors that inhibit the system from displaying the real-time plot. This can easily be done by inputting the command: //pip uninstall PyQt5// while the virtual environment is active. </note>
  
 === Running the Examples === === Running the Examples ===
Line 206: Line 209:
   - Connect the EVAL-ADICUP3029 to the PC using the micro-USB cable and note the serial port from the Device Manager as in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#connection | Connection]].   - Connect the EVAL-ADICUP3029 to the PC using the micro-USB cable and note the serial port from the Device Manager as in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#connection | Connection]].
   - Open command prompt or terminal and navigate to the examples folder inside the downloaded or cloned //pyadi-iio// directory.   - Open command prompt or terminal and navigate to the examples folder inside the downloaded or cloned //pyadi-iio// directory.
-  - Run the example using the command: <code>...\pyadi-iio\examples>python adpd410x_example.py.</code>+  - Run the example using the command: <code>...\pyadi-iio\examples>python adpd410x_example.py</code>
   - Input the noted serial port and press //Connect//\\  {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pyadiiio_example1_comport.png?nolink&400|}}.   - Input the noted serial port and press //Connect//\\  {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pyadiiio_example1_comport.png?nolink&400|}}.
   - Once connected, press //Read//\\ {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pyadiiio_example1_read.png?nolink&400|}}.   - Once connected, press //Read//\\ {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pyadiiio_example1_read.png?nolink&400|}}.
Line 214: Line 217:
   - Connect the EVAL-ADICUP3029 to the PC using the micro-USB cable and note the serial port from the Device Manager as in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#connection | Connection]].   - Connect the EVAL-ADICUP3029 to the PC using the micro-USB cable and note the serial port from the Device Manager as in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#connection | Connection]].
   - Open command prompt or terminal and navigate to the examples folder inside the downloaded or cloned //pyadi-iio// directory.   - Open command prompt or terminal and navigate to the examples folder inside the downloaded or cloned //pyadi-iio// directory.
-  - Run the example script using the command: <code>...\pyadi-iio\examples>python adpd410x_plot.py</code>.+  - Run the example script using the command: <code>...\pyadi-iio\examples>python adpd410x_plot.py</code>
   - The script will ask for a serial port. Input the noted serial port and press Enter. In cases when the board is not found, press the reset button (S1) on the EVAL-ADPD4100-ARDZ or EVAL-ADPD4101-ARDZ and input the noted serial port again.\\ {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pyadiiio_example2_comport.png?nolink&400|}}   - The script will ask for a serial port. Input the noted serial port and press Enter. In cases when the board is not found, press the reset button (S1) on the EVAL-ADPD4100-ARDZ or EVAL-ADPD4101-ARDZ and input the noted serial port again.\\ {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pyadiiio_example2_comport.png?nolink&400|}}
   - When the board is detected, you will be asked to specify the number of channels (1 to 8) you want to read. Then, you need to specify the desired channel numbers (1 to 8).\\ {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pyadiiio_example2_inputchannels.png?nolink&400|}}   - When the board is detected, you will be asked to specify the number of channels (1 to 8) you want to read. Then, you need to specify the desired channel numbers (1 to 8).\\ {{:resources:eval:user-guides:circuits-from-the-lab:adpd410x:pyadiiio_example2_inputchannels.png?nolink&400|}}
Line 220: Line 223:
 \\  \\ 
 For example 3, follow these steps: For example 3, follow these steps:
-  - Connect the EVAL-ADPD4100-ARDZ or EVAL-ADPD4101-ARDZ to the EVAL-ADICUP3029+  - Connect the EVAL-ADPD4100-ARDZ or EVAL-ADPD4101-ARDZ to the EVAL-ADICUP3029.
   - Connect the EVAL-ADICUP3029 to the pc using the micro-USB cable and note the serial port from the Device Manager as in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#connection | Connection]].   - Connect the EVAL-ADICUP3029 to the pc using the micro-USB cable and note the serial port from the Device Manager as in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#connection | Connection]].
   - Open command prompt or terminal and navigate to the examples folder inside the downloaded or cloned //pyadi-iio// directory.   - Open command prompt or terminal and navigate to the examples folder inside the downloaded or cloned //pyadi-iio// directory.
-  - Run the example script using the command: <code>...\pyadi-iio\examples>python adpd410x_test.py</code>.+  - Run the example script using the command: <code>...\pyadi-iio\examples>python adpd410x_test.py</code>
   - A GUI window will appear, as shown below. There are four buttons at the top right for each test namely, open onboard LED test, covered onboard LED test, no load test, and mounted jig test. **Before pressing a button to start the test, select the noted COM port on the dropdown list at the top left.**\\ {{:resources:eval:user-guides:circuits-from-the-lab:softwarewindow.png?nolink&600|}}   - A GUI window will appear, as shown below. There are four buttons at the top right for each test namely, open onboard LED test, covered onboard LED test, no load test, and mounted jig test. **Before pressing a button to start the test, select the noted COM port on the dropdown list at the top left.**\\ {{:resources:eval:user-guides:circuits-from-the-lab:softwarewindow.png?nolink&600|}}
     * **Open Onboard LED Test**\\ The test samples raw ADC values from the onboard photodiode and checks whether it is consistent with the standard. Make sure that all shunts on jumper header P10 are present and connected. A sample passing result is shown below\\ {{:resources:eval:user-guides:circuits-from-the-lab:openledresult.png?nolink&600|}}     * **Open Onboard LED Test**\\ The test samples raw ADC values from the onboard photodiode and checks whether it is consistent with the standard. Make sure that all shunts on jumper header P10 are present and connected. A sample passing result is shown below\\ {{:resources:eval:user-guides:circuits-from-the-lab:openledresult.png?nolink&600|}}
     * **Covered Onboard LED Test**\\ Place your finger above the onboard photodiode and LED.\\ {{:resources:eval:user-guides:circuits-from-the-lab:coveredled.jpg?nolink&400|}}\\ This test checks if the sampled raw ADC value has significantly increased from the standard uncovered value. A sample passing result is shown below.\\ {{:resources:eval:user-guides:circuits-from-the-lab:coveredledresult.png?nolink&600|}}     * **Covered Onboard LED Test**\\ Place your finger above the onboard photodiode and LED.\\ {{:resources:eval:user-guides:circuits-from-the-lab:coveredled.jpg?nolink&400|}}\\ This test checks if the sampled raw ADC value has significantly increased from the standard uncovered value. A sample passing result is shown below.\\ {{:resources:eval:user-guides:circuits-from-the-lab:coveredledresult.png?nolink&600|}}
-    * **No Load Test**\\ Remove all shunts on jumper header P10. This test checks the photodiode input when no external sensor is connected. A sample passing result is shown below\\ {{:resources:eval:user-guides:circuits-from-the-lab:noloadtestresult.png?nolink&600|}}.+    * **No Load Test**\\ Remove all shunts on jumper header P10. This test checks the photodiode input when no external sensor is connected. A sample passing result is shown below.\\ {{:resources:eval:user-guides:circuits-from-the-lab:noloadtestresult.png?nolink&600|}}.
     * **Mounted Jig Test**\\ Using the simple test schematic shown in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#connection | Connection]], a test board was fabricated using [[https://www.onsemi.com/pdf/datasheet/moc217m-d.pdf | MOC207M]] optocouplers. Remove all shunts on jumper header P10 and connect the test jig to the EVAL-ADPD4100-ARDZ or EVAL-ADPD4101-ARDZ, as shown below. **(The test jig shown below was fabricated with female headers for easy mounting)**\\ {{:resources:eval:user-guides:circuits-from-the-lab:testjig_connection.jpg?nolink&600|}}\\ A sample passing result is shown below.\\ {{:resources:eval:user-guides:circuits-from-the-lab:mountedjigtestresult.png?nolink&600|}}     * **Mounted Jig Test**\\ Using the simple test schematic shown in [[resources:eval:user-guides:circuits-from-the-lab:eval-adpd410x#connection | Connection]], a test board was fabricated using [[https://www.onsemi.com/pdf/datasheet/moc217m-d.pdf | MOC207M]] optocouplers. Remove all shunts on jumper header P10 and connect the test jig to the EVAL-ADPD4100-ARDZ or EVAL-ADPD4101-ARDZ, as shown below. **(The test jig shown below was fabricated with female headers for easy mounting)**\\ {{:resources:eval:user-guides:circuits-from-the-lab:testjig_connection.jpg?nolink&600|}}\\ A sample passing result is shown below.\\ {{:resources:eval:user-guides:circuits-from-the-lab:mountedjigtestresult.png?nolink&600|}}
  
resources/eval/user-guides/circuits-from-the-lab/eval-adpd410x.txt · Last modified: 03 Mar 2023 07:42 by Joyce Velasco

Page Tools