User Guide Evaluation Kit SimpleRadar

Transcription

1 Silicon Radar GmbH Im Technologiepark Frankfurt (Oder) Germany fon fax User Guide Evaluation Kit SimpleRadar preliminary Status: Date: Author: initial 12 Jul. 16 Silicon Radar GmbH Version: Document number: Filename: Page: 0.2 RS_120_05 User Guide SimpleRadar 1 of

2 TRX_120_01 Radar Sensor Evaluation Kit 1 Version T301 Alumina Cap Table of Contents 1 Overview and Package Contents Overview Features Application Installation Hardware Installation Standard operation connected via UART Wireless operation connected via WiFi Control Header Software Installation Connecting to the board using a wireless LAN connection Connecting the board via USB Getting Started with the SimpleRadar Sensor Evaluation Kit The User Interface Control Panel (Sensor Setup) COM Panel: Sys Config: RF params: BB processing: Target Recognition: Scene Controls: Camera Controls: Main Menu: FFT View Status field and Target list: Phase Diagramm Spectrogram: Understanding the display Signal processing flow Troubleshooting Target not recognized Too many targets -> CFAR doesn t work Firmware Update Microcontroller WiFi Module Hardware Schematics Board Layout Changing Hardware Parameters DC- Coupling or change high pass filter response Change low pass filter response Change Gain Communication Protocol

3 8.1 Compressed Data Format Extended data format Register Description Communication from sensor module to backend Disclaimer / License List of Figures Figure 1 SimpleRadar Sensor Evaluation Kit and screenshot of the GUI... 4 Figure 2 Standard operation mode connected via UART cable Figure 3 Wireless operation using WiFi module... 6 Figure 4 Screenshot of the Websocket-Server window... 8 Figure 5 Main window of the SimpleRadar WebGUI... 9 Figure 6 Screenshot of the main GUI window and elements in the display scene Figure 7 Signal flow of the firmware. Data can be extracted at various intermediate stages Figure 8 Firmware update config: Switch MP to ON. Connect cable TX (green) to µc RX (MR) and cable RX to µc TX (MT). Make sure to use a cable with 3.3V TTL levels! Figure 9 Jumper settings and program select switch for the WiFi module Figure 10 Assembly drawings of the module PCBs Figure 11 Signal chain in the Baseband amplifier Figure 12 Register definition of the sensor module Figure 13 Communication protocol definition

4 1 Overview and Package Contents Thank you for purchasing the Silicon Radar SimpleRadar sensor module. The module is an easy to use, state of the art 122GHz Radar sensor including a high performance target recognition algorithm and WLAN connectivity. What s in the box? Radar Sensor Eval Kit consisting of o TRX_120 Radar Frontend Board including microcontroller, PLL and WiFi module o Lens assembly Figure 1 SimpleRadar Sensor Evaluation Kit and screenshot of the GUI The SimpleRadar Evaluation Kit demonstrates the performance and parameters of the 122 Ghz Radar transceiver chips of Silicon Radar. The aim of the evaluation kit is to showcase the FMCW / CW radar mode using a beginner-friendly system. However, due to the great flexibility of the system it can be used to change virtually any parameter that is important for a Radar Sensor application and learn to know the basics of Radar Signal processing. Silicon Radar puts the focus on an easy-to-use approach and supports the customer with a set of default key parameters guaranteeing a proper operation of the sensor (including automatically set parameters of optimized operation mode). The sensor is not optimized to show the maximum ratings of all the chip properties

5 1.1 Overview The SimpleRadar Evaluation Kit is an experimental system for Silicon Radars 122GHz highly integrated IQ transceiver with antennas in package. For more information about the features of the transceiver chips, all data sheets are available on the Silicon Radar webpage. We developed the evaluation kit to demonstrate our millimeter-wave sensors to measure the distance and velocity using RADAR principles. Both - frequency modulated continuous wave (FMCW) or continuous wave (CW) - principles are applied. 1.2 Features The SimpleRadar Sensor Evaluation Kit feature set includes: Phase locked loop running the integrated low phase noise Push-Push VCO in the transceiver chip Frequency lock control to automatically adjust the start and stop frequencies of the generated FMCW RADAR frequency ramp Programmable FMCW parameters 122 GHz ISM band or 7 GHz high bandwidth FMCW operations for TRX120 chips Analog signal conditioning to amplify and filter the I and Q output signals of the transceiver Analog-to-Digital-converter to digitize the I and Q receiver signals Microcontroller to do PLL setup, ramp configuration, A-D conversion all the signal processing and target recognition for up to 16 targets simultaneously transfer to the host system, trigger configurable GP output pins A web-based GUI user interface to change all relevant parameters, plot the FFT of the baseband channels, display the distance and velocity measurements and the target list. Standard USB communication with PC or over wireless LAN DC-DC conversion to provide single supply from USB or an external DC supply 1.3 Application The SimpleRadar Sensor Evaluation Kit is supposed to be used in laboratory environments only. All regulations of the according Silicon Radar Evaluation Agreement may apply. IMPORTANT: The Radar frontends are able to use a larger bandwidth than allowed in the ISM bands. Therefore it is up to the customer to make sure that the frontend is not used in these conditions. The Evalkit is not supposed to be used as a customer product! It is solely designed for short-term evaluation purposes

6 2 Installation 2.1 Hardware Installation The hardware of the SimpleRadar Sensor Evaluation Kit consists of only one board and the lens assembly. For proper hardware installation, please follow the order given below: If you want to use the lens to increase the maximum range of the system, please install the lens at about 10 15mm away from the RFE surface. The lens has a focal length of 15mm with an opening angle of +/- 8 degrees at that distance. If it is installed closer to the RFE, the beam will be wider. You can use the provided spacers to mount the lens Standard operation connected via UART If the module is used on a PC or in a target application with a serial interface, connect the module like shown in Figure 2. Make sure to use a cable with 3.3V TTL levels! Figure 2 Standard operation mode connected via UART cable. Cable +5V is connected to 5V, Cable GND to GND, cable RX to µc TX (MT) and cable TX to µc RX (MR). Make sure both DIP switches are in their OFF positions and the power jumper for the WiFi module is open Wireless operation connected via WiFi If the module should be used in WiFi mode, close the power jumper for the WiFi module and connect jumpers between MT/WR and MR/WT. Apply 5V to the external header and follow the connection instructions below. Figure 3 Wireless operation using WiFi module - 6 -

7 2.2 Control Header The control header is used to connect to the board in different modes. In programming mode it is used to program the WiFi module or the µcontroller. In WiFi-mode it is used to connect the WiFi module to the µcontroller. And it also can be used to trigger the measurement via the external Trigger line. Pin 5V GD MT MR TR WT WR (*) 3.3V tolerant only!! Description 5V supply GND µcontroller TX(*) µcontroller RX(*) External Trigger(*) WiFi TX(*) WiFi RX(*) 2.3 Software Installation The evaluation software is displayed in a Web Browser which supports WebGL. We recommend the following Browsers: Chrome, Firefox. There are two ways to run the module. Either using the USB as a virtual COM port or connect via WLAN: Connecting to the board using a wireless LAN connection Due to the wireless LAN connectivity of the module, the installation process is very straightforward. On power-up the module searches for the last saved WiFi access point. This is indicated by the rapidly flashing blue LED. If there is no known WiFi access point (AP) accessible, the WiFi module opens an own AP. This is indicated by the slowly flashing blue LED on the module (40 secs). Please connect to this AP using the following login credentials: SSID: EasyRadar Password: Greetings The module is now in AP mode and waits for 40 seconds until it starts the Radar application. If the connection is successful, the blue LED is switched off. Please find out the IP of the module by checking your DHCP server (WLAN AP). If you want to run the module in AP mode, just wait for 40 seconds until it stops listening for http clients and starts the Radar application. The module can now be used as described in chapter

8 2.3.2 Connecting the board via USB Connecting the board via USB is only supported for Windows systems at this time. To connect the board via USB, the ST Microelectronics Virtual Com Port driver has to be installed first. Please download it from the ST Webpage: or from the Silicon Radar download page: [link] The second step is to install a 32-bit Java Runtime Environment from: Please make sure you select a 32-Bit driver or the communication will not work. Thirdly, run the Com2WebSocket application after changing the path in the runme.bat to your java.exe path. A small window with the available com ports will open: Figure 4 Screenshot of the Websocket-Server window Please select the appropriate COM port of your Evalkit, and select baud as the baudrate. Then click open. The program then opens a Websocket Server which is fed with the data from the com port. The Evalkit is now ready to run

9 3 Getting Started with the SimpleRadar Sensor Evaluation Kit 3.1 The User Interface The user interface is started by opening the index.html in the provided public_html folder. Please use Firefox or Chrome to display the GUI as there are known issues with other browsers. The Software is developed to demonstrate the functionality of Silicon Radars Transceiver chips as a millimeter-wave distance and velocity sensor front end. Once the WebGUI is launched the main window is displayed (see Figure 5). Figure 5 Main window of the SimpleRadar WebGUI The Silicon Radar WebGUI consists of four main panels: the control panel the main menu on the top of the screen, with the active view in orange the scene/canvas itself where the data is displayed the target list with the status field at the right side of the screen (draggable) - 9 -

10 3.2 Control Panel (Sensor Setup) On the left side of the GUI you will find the controls for the interface. It is used to connect to the server, send data to the server and to change the view. It contains the following elements: COM Sys Config Log RF Params BB Processing Target Recognition Scene Controls COM Panel: Type in the IP address and port of the WiFi module (without ), i.e.: :9090 or for communication via the USB port: localhost:

11 3.2.2 Sys Config: use pre trigger: can be used to synchronize measurements between multiple modules. If selected and the module is not in self trigger mode, the module expects two trigger commands to execute one measurement. The two triggers have to be sent with a maximum delay of about 40ms or the second trigger is ignored. self trigger: the module is set in continuous measurement mode, triggering itself repeatedly. Trigger delay: changes the delay time between two measurements when in self trigger mode. Sleep in idle: if the self trigger is off, and sleep mode is on, the module enters low power sleep mode after transmission of the measurement results and is woken up by the next trigger. DC cancellation on: DC offset compensation of ADC data. Frames: select what data to transfer Range-frame: A Frame containing the range spectrum given in db for each range bin (magnitude of the FFT output). CFAR: Constant false alarm rate operator. Adaptive algorithm to derive detection threshold for targets against noise. This frame contains the CFAR threshold. Phase-frame: A frame containing the values of the phase angles for each range bin (argument of the FFT output). Targetlist-frame: contains a list of targets and the following data for each target: number, distance, magnitude, phase and speed. Please note that the speed value is not calculated by a target tracking algorithm. It is calculated using the difference in distance from the last to the current measurement and the time since the last measurement for each row. Status frame: if this bit is selected, a status frame is transmitted after every measurement. If this bit is reset, a status frame is only transmitted after every change of the sensor setup. The status frame contains following information: distance format (currently set to mm) maximum range in mm measurement accuracy of the current setup gain setting of the baseband amp for the last measurement update rate of the measurements the bandwidth used in the current setup Extdata: alternative data format (currently not used) ser1 (WLAN): to be selected in order to work with WLAN ser2 (COM): to be selected in order to work with the USB-COM port

12 3.2.3 RF params: BB processing: Min / Max frequency: displays the result of the frequency scan. This scan is performed on every reset and when the scan frequency command is sent. Scan / Set Max: performs a frequency scan for the installed frontend to read the maximum achievable bandwidth. Sets the ramp bandwidth to this maximum value. bandwidth: bandwidth used for the frequency ramp (usually max 6000 MHz, sensor/board dependent) base-frequency: start-frequency of the ramp (sensor/board dependent) Important: these 2 values define the voltage ramp applied to the VCO. Care should be taken not to drive the voltage into saturation on either end. See troubleshooting section for further information. VCO Divider: 64, fixed, board dependent Frontend selection: use this to load standard values for the used frontend. Ramp time: is reported back by the module. Calculated using the selected sampling frequency and the number of samples ADC Clock Divider: sets the sampling frequency, a higher value means slower sampling. Number of samples: samples per ramp Number of ramps: number of ramps integrated (to improve S/N) -> higher values, slower measurements but better S/N. Too high values may smear out signal due to phase noise of the system. Downsampling: reduce number of samples after sampling. Fill void with zeroes. "1" means average of 2 values, "2" of 4 values, etc. Higher values improve accuracy but reduce max range. FFT size: number of FFT bins Average: averaging of FFT data. "1" means average of 2 FFTs, etc Target Recognition: CF-Guard: number of guard cells before and after cell under test CF-Size: number of FFT bins used on either side of the guard cells. CF-Threshold: detection threshold in db above noise floor. Format: in which format range data is sent/displayed. Values are 'bin', 'mm', 'cm': bin: the number of the pin which receives the data 'mm': the data is displayed in 'mm', meaning the bin number is converted into 'mm', depending on the accuracy 'cm': the data is displayed in 'cm', meaning the bin number is converted into 'cm', depending on the accuracy

13 3.2.6 Scene Controls: rotate scene: enable to let the camera rotate around the center of the drawing area LineCount: change to see more or less datasets going to the background in 3D -View X-axis Divider: change to divide the x-axis in more or less parts Camera Controls: Here you can see and change camera position and -rotation relative to the specified axis. In general, the camera can be changed using the mouse within the scene area. Left-click-drag pans the camera position. Right-click-drag changes the camera angle. Middle-click-drag or moving the mouse wheel changes the zoom setting (z-coordinate) of the camera. Reset view: resets camera rotation and position CamPosX: camera position on the X-axis, move, left(-) or right(+) CamPosY: camera position on the Y-axis, move up(+) or down(-) CamPosZ: camera position on the Z-axis, move to the front(-) or back(+) CamRotX: camera rotation on the X-axis, rotate up(+) or down(-), relative to the X-axis CamRotY: camera rotation on the Y-axis, rotate to the left(+) or right(-), relative to the Y-axis 3.3 Main Menu: Here you can select how the data should be displayed. You have three main options: FFT View Phase Diagram Spectrogram FFT View 2D-Chart: the x-axis shows the range the y-axis shows the magnitude in db at this range

14 3D- Chart: in 3D-view you can see the history of data, with the z-axis being the time line, so older values move to the back (higher z-values). X and Y like in 2D mode. Phasemarkers: as an extra option you can select to display phase markers on each recognized target. These markers show the phase angle of the detected target. The phase angle is very sensitive to slight changes of the target distance within one range bin. It can be used to display relative motion in the µm range. 3.4 Status field and Target list: Statusfield: distance in: [mm,cm, bin] the format which the sensor specifies in the statusframe. accuracy: the width of one range bin of the sensor. It is calculated using the following formula: update rate: calculated from the TSLM-value ( Time since last measurement ) which the sensor sends in milliseconds in the statusframe gain: gain setting of the baseband amplifier in db bandwidth: the chirp bandwith Target list: The target list is ordered by distance. With every new measurement having the CFAR operator enabled, the target

15 list is updated. Everytime the range bin crosses the CFAR threshold from below, the local maximum is searched and a target is generated. If two target peaks cross the CFAR threshold from below before the range bin goes back underneath the CFAR threshold, then only the first target is marked. distance: the distance of the target in the selected format. db: magnitude of the target peak phi: phase angle of the target, meaning the phase shift between outgoing wave and incoming wave. If the target is moving, this value should change rapidly. Speed: Radial velocity of the target [m/s] calculated as a range difference since the last measurement. 3.5 Phase Diagramm A widget to emphasize the display of phase angles. Every target from the target list is displayed here on a circle with a radius equal to its distance and an angle determined by its phase angle. 3.6 Spectrogram: The spectrogram is another time- dependent display of range data. When you select colorize db in the Dropdown-menu, the signal magnitude is colorized When you select colorize phaseangle in the Dropdown-menu, the phaseangles are colorized if the magnitude is larger than -120 db

16 4 Understanding the display Figure 6 Screenshot of the main GUI window and elements in the display scene. Viewing a radar target spectrum for the first time might be confusing for the beginner. However, with some practice, it is easy to find targets and understand why some things work while others might not. The above picture shows a typical spectrum output of the sensor when placed on a tabletop and looking to the ceiling. There is some DC component on the left side. If this DC offset is high, it might trigger a false target detection of the CFAR operator. Around 60 cm to 180 cm there might be some clutter which is rejected by the CFAR operator. Around 200cm there is the first ceiling echo, which should be quite high versus the neighboring noise floor. Using a lens will make this target peak thinner and higher and more easily detectable by the CFAR operator. Due to the adaptive nature of the CFAR operator it might happen that if two targets are too near to each other or are very different in magnitude, one of them is rejected by the CFAR operator. Playing around with the target recognition settings might help in this situation. For the interested reader we will dig a little deeper into the signal processing flow of the sensor

17 4.1 Signal processing flow Figure 7 Signal flow of the firmware. Data can be extracted at various intermediate stages. t.b.d. 5 Troubleshooting 5.1 Target not recognized A common trouble with Radar sensors is the misalignment of the sensor parameters to the application. There are too many different parameters which can be optimized, to give a one-fits-all setting from the beginning Too many targets -> CFAR doesn t work No targets detected although there are plenty of targets around 2m. If there are too many targets adjacent to each other in the field of view, the CFAR operator may treat those targets like noise floor and calculates an envelope around those targets. Increasing the number of guard cells may help in such a scenario

18 Increasing the guard size may help in such a situation. 6 Firmware Update 6.1 Microcontroller To update or change the microcontroller firmware, the board has to be put in bootloader mode. This is done by switching the DIP switch MP to the ON position. Then connect the module to the PC via a USB to UART cable using the external header. Make sure cable TX is connected to MR (µc RX) and cable RX is connected to MT (µc TX). Make sure to use a cable with 3.3V TTL levels! Figure 8 Firmware update config: Switch MP to ON. Connect cable TX (green) to µc RX (MR) and cable RX to µc TX (MT). Make sure to use a cable with 3.3V TTL levels! Edit the batch file in the Install_Package\Microcontroller folder and replace COM7 with your com port setting for the USB to UART cable. Run the batch file and the microcontroller gets programmed. After about 30 seconds programming is finished. Switch the DIP switch MP back to the OFF position and do a power cycle to reset the module

19 6.2 WiFi Module Connect the sensor using a USB to UART cable like shown in the below figure. Make sure cable TX is connected to WR (wireless RX) and cable RX is connected to WT (wireless TX). Switch SW1 to the PROG position. Make sure to use a cable with 3.3V TTL levels! Then connect the power Jumper J2 to enable the supply voltage for the WiFi module. Figure 9 Jumper settings and program select switch for the WiFi module. Edit the batch file run_esptool.bat under Install_Package\WiFi Module\websocket_mini and replace COM7 with your com port setting for the USB to UART cable. Run the batch file and the WiFi module gets programmed, indicated by a flashing blue LED. After about 40 seconds programming is finished. Switch SW1 back to the OFF position and connect a jumper between MT and WR and MR and WT. 7 Hardware 7.1 Schematics The schematics of the board are provided separately under a non-disclosure agreement. 7.2 Board Layout [assy drawings] Figure 10 Assembly drawings of the module PCBs. 7.3 Changing Hardware Parameters Depending on the type of application it may be necessary to change the filter characteristics and gain settings of the baseband amplifier. The standard configuration of the baseband circuitry can be seen in Figure 11. Figure 11 Signal chain in the Baseband amplifier DC- Coupling or change high pass filter response Change input Caps and second filter to zero ohm. [fotos]

20 7.3.2 Change low pass filter response Change feedback caps [fotos] Change Gain Change feedback resistors [fotos] 8 Communication Protocol The serial communication protocol is divided in two classes: compressed data format (default) and extended data format (can be activated). A detailed description of the communication protocol is provided in the Install_Package folder. 8.1 Compressed Data Format The compressed format is based on readable ASCII characters (valid values range from 0x20 to 0xFF). A single packet starts with a start marker (! ), followed by a single character packet indicator. It is delimited by CRLF characters (0x13 0x10). See Figure 14 for details. 8.2 Extended data format The extended format is used to transmit large number formats. It is based on hexadecimal presentation in ASCII format (characters 0..9 and A..F). This format is available for raw data output. See [] for details. 8.3 Register Description Figure 12 Register definition of the sensor module The sensor accepts commands and setup data as input. The registers are 32 bit wide and configured as shown in []. The register definition is as follows: SYS_Config: o Pre-Trigger bit: 0= single trigger mode; 1= use pre trigger, wait for second trigger edge o Self-Trigger bit: 0= external trigger; 1 = measure continuously o Sleep Mode bit: 0= stay in run mode while in idle state; 1= go to sleep during idle state o DC-Cancellation: 0=off; 1= perform digital DC cancellation after sampling

21 o Range/CFAR/Phase: 0=off; 1= output Range/CFAR/Phase information frames after processing o Target List: 0=off; 1= output Target List frame after processing o Status Frame: 0=output status frame after every change of configuration; 1= output status frame after each measurement o Extended Data format: 0: output data in compressed format, not available for format[0,1,2]; 1= output data in extended data format RFE_Config: o Base frequency of the frontend [uint19]. This frequency should be within the ISM band. o VCO divider value [uint13]: ratio of RF frequency to divider output PLL_Freq: o Ramp bandwidth in MHz as RF frequency [int16], can be positive or negative. BB_Setup: o F_Smp [uint3]: ADC sample frequency selection. F_Smp * #Smp = ramp time o #Samples [3 bits as n ]: number of samples per ramp o #Ramps [3 bits as 2 n ]: number of ramps to integrate before FFT is calculated o Downsample [uint3]: number of downsampling steps before FFT is calculated o FFT Size [3 bits as n ]: Size of FFT in points o CFAR guard interval [uint2]: number of guard cells around cell under test o CFAR size [uint4]: number of cells to integrate for CFAR operator o Threshold [uint5]: target threshold value for CFAR operator in db o Format [uint3]: output format for the target / sample data Programming Mode: t.b.d.; intended use is to enter programming mode from software Communication from sensor module to backend Depending on the activated output frames the module can output the following data fields: Range Frame and CFAR Frame: both are activated by the R/C bit in the RFE_CONFIG register. The range spectrum is returned as magnitude in db for the target data and the CFAR operator threshold. Target List Frame: activated by the TL bit in RFE_CONFIG. The target list is returned consisting of the o selected format, o the baseband amp gain used for the last measurement, o the target number, o the distance, o the magnitude in db, o the phase angle phi and o the velocity (delta distance since last measurement) for each target. Status Frame: returns the current measurement parameters. This frame is returned every time the configuration is changed, or after every measurement. o Selected format o baseband amp gain used for the last measurement, o accuracy in mm x 10 o current maximum range (dependent on FFT size and number of samples/downsampling) o current ramp time in µs o current bandwidth in MHz o time since last measurement as overflowing 16-Bit counter. Max. is 164 ms. Timebase is 400kHz. This value is only available if sleep mode is disabled. Error frame: This frame is returned after every measurement or setup frame that sets at least one of the error bits. o CRC error flag: is asserted when a CRC error in the setup data is detected

22 o RFE setup error flag: is asserted when RFE setup data is out of range (max / min frequency hit) o PLL setup error flag: is asserted when PLL setup data is out of range o BB setup error flag: is asserted when baseband setup was wrong (saturation at lowest gain,..) o PRC error flag: is set high when a processing error occurred (FFT_size,..) UID[uint96]: 96-bit UID extracted from the processor s UID bit field. This frame is returned after a successful change of configuration. Figure 13 Communication protocol definition

23 9 Disclaimer / License License ======= All software in the 3RDPARTY folder is copyrighted by their respective owners and covered by their respective licenses. Please see the corresponding websites or the package information for details. Radar software in folder RADAR is provided solely for demonstration and testing purposes "as is" under the terms of the GPLv2 or later license. See for details. Disclaimer ========== This software is provided "as is" for testing purposes only. While hoping it will be useful there is NO WARRANTY of any kind, including, but not limited to, the implied warranties of merchantibility and fitness for a particular purpose. In no event shall the distributor, the authors, any of the contributers, or any third party be liable for any direct, indirect, incidental, or consequential damages (including, but not limited to, procurement of substitute goods and services, loss of use, damage to hardware, loss of data, loss of profits, or business interruption). Silicon Radar GmbH 2015 The information contained herein is subject to change at any time without notice. Silicon Radar GmbH assumes no responsibility or liability for any loss, damage or defect of a Product which is caused in whole or in part by (i) (ii) (iii) (iv) use of any circuitry other than circuitry embodied in a Silicon Radar GmbH product, misuse or abuse including static discharge, neglect or accident, unauthorized modification or repairs which have been soldered or altered during assembly and are not capable of being tested by Silicon Radar GmbH under its normal test conditions, or improper installation, storage, handling, warehousing or transportation, or (v) being subjected to unusual physical, thermal, or electrical stress. Silicon Radar GmbH makes no warranty of any kind, express or implied, with regard to this material, and specifically disclaims any and all express or implied warranties, either in fact or by operation of law, statutory or otherwise, including the implied warranties of merchantability and fitness for use or a particular purpose, and any implied warranty arising from course of dealing or usage of trade, as well as any common-law duties relating to accuracy or lack of negligence, with respect to this material, any Silicon Radar product and any product documentation. products sold by Silicon Radar are not suitable or intended to be used in a life support application or component, to operate nuclear facilities, or in other mission critical applications where human life may be involved or at stake. all sales are made conditioned upon compliance with the critical uses policy set forth below. CRITICAL USE EXCLUSION POLICY BUYER AGREES NOT TO USE SILICON RADAR GMBH'S PRODUCTS FOR ANY APPLICATION OR IN ANY COMPONENTS USED IN LIFE SUPPORT DEVICES OR TO OPERATE NUCLEAR FACILITIES OR FOR USE IN OTHER MISSION-CRITICAL APPLICATIONS OR COMPONENTS WHERE HUMAN LIFE OR PROPERTY MAY BE AT STAKE. Silicon Radar GmbH owns all rights, title and interest to the intellectual property related to Silicon Radar GmbH's products, including any software, firmware, copyright, patent, or trademark. The sale of Silicon Radar GmbH products does not convey or imply any license under patent or other rights. Silicon Radar GmbH retains the copyright and trademark rights in all documents, catalogs and plans supplied pursuant to or ancillary to the sale of products or services by Silicon Radar GmbH. Unless otherwise agreed to in writing by Silicon Radar GmbH, any reproduction, modification, translation, compilation, or representation of this material shall be strictly prohibited