PCI Express SDR100 Board
version 2025-05-07*
This document is based on the latest test release.
Features may not be present in your current installed software. You may check their availability in change history or in your release documentation.
If you require an up to date release, ask for it in a ticket.

1 Features
2 Installation with the Amarisoft software
3 Troubleshooting
4 Miscellaneous utilities
5 C API
6 Physical specifications
7 Remote API
- 7.1 clock_tune
8 Change history
9 License

1 Features

Dual 2x2 RF transceiver (AD9371)
RF coverage: 300 MHz to 6.0 GHz
RF bandwidth: up to 100 MHz
Supports TDD and FDD operation
Integrated TX/RX switch for TDD operation
PCIe 8x standard connector
Integrated GPS for precise time and frequency synchronization
Clock/PPS inputs and outputs for easy synchronisation
Optional sample compression to reduce the PCI bandwidth

2 Installation with the Amarisoft software

2.1 Introduction

If you have bought the OTS (Off-The-Shelve) package, then you donât need to install anything. Everything has already been installed on your PC. Otherwise, please follow through the steps below.

Decompress the trx_sdr archive into a convenient directory specified by <trx_path>.

tar -xzf trx_sdr-linux-YYYY-MM-DD.tar.gz -C <trx_path>

You have two ways to install the TRX driver for the PCIe card:

automatic
manual

For both cases, the installation requires some specific packages to compile the kernel module. To do this, you need to be root. In Fedora and Cent OS, you need to install kernel-devel, make, gcc and elfutils-libelf-devel packages by running the following command:

dnf install kernel-devel-$(uname -r) make gcc elfutils-libelf-devel

For Ubuntu, use the following command:

apt-get install $(uname -a | awk '{print $3}') build-essential

Note that you’ll need equivalent packages for other Linux distributions if you do not use Fedora, Ubuntu or Cent OS.

Once you have finished the installation, you need to initialize (See Driver initialization) and upgrade your driver (See Firmware upgrade). Please make sure to initialize the driver after each system boot if you have not activates an automatic lte service.

2.2 Automatic Installation

Automatic installation is only available on Fedora, Ubuntu and CentOS distributions. Use manual install for other distributions. To start your automatic install, use the following command where <path> is the path to the directory where you have already installed your LTE component (eNB or UE) and type should be set to enb or ue accordingly.

./install <path> <type>

Notes:

the script would install some packages, so make sure you have root privileges when you run the script
this install creates a symlink for the TRX driver so please do not remove this directory afterwards.

2.3 Manual Installation

To manually install the driver, let’s note <path> the directory where Amarisoft eNB or UE software is installed. Then:

Compile kernel driver:
Go to the kernel/ directory under <trx_path> and start compilation:
```
cd kernel
make
```

Place driver:
Just copy the compiled driver into <path> directory

cd ..
cp trx_sdr.so <path>
cp libsdr.so <path>
cp libc_wrapper_sdr.so <path>

Config files:
Copy RF driver config file. Note that there are 2 separate config directories for eNB and UE called config.enb and config.ue under your <trx_path>. As a result, the <config_dir> should be set to config.enb or config.ue accordingly.
```
cp -r <config_dir> <path>/config/sdr
```
Select frontend:
```
<path>/config/rf_select.sh sdr
```

2.4 Driver initialization

Each time you boot your system, you need to perform this initialization. Note that if you are using OTS install, this step is already done by the lte service.

cd kernel
./init.sh

2.5 Firmware upgrade

Perform the following command to upgrade your PCIe card:

./sdr_util upgrade

Notes:

If you have several PCIe cards installed, this will upgrade all cards.
If the firmware is already up to date, this command will end directly.
When the upgrade is over, you need your system to be powered off for the changes to take effect (not only reset, real power off).

2.6 Multiple card installation

To make several cards work together, they must be time and frequency synchronized. For that purpose you need to plug a standard SATA cable between boards. Connect one of the three CLK_OUT connectors on the Master board (Figure 6.1) to the CLK_IN of the Slave board (Figure 6.1); connectors are on top of PCI boards. You can Slave up to three SDR100 boards to one SDR100 board.

Each SDR100 board is seen as two linux devices with consecutive minors. The secondary is automatically slaved to the primary for clock and PPS.

The primary device always has an even minor and the secondary has the next minor. For instance, if you install one SDR100 boards, it will appear as sdr0 and sdr1 devices

When you install several PCIe cards, the mapping between the PCI connectors and the Linux devices is not predictable (but it shouldn’t change after each boot). To identify the order please do the following:

./sdr_util -c 0 led 1

Then check inside PC on each board: the leds are visible on the top edge of the SDR100. One of them should have a led blinking, this is card 0 (/dev/sdr0).

Switch off the led:

./sdr_util -c 0 led 0

You can do the same for other cards:

./sdr_util -c <n> led 2

Where <n> is the index of the card.

Remember primary and secondary (sdr0 and sdr1) will have leds placed on the same SDR100 board.

To use all the cards, update eNB config file (config.cfg) using args parameter:

args: "dev0=/dev/sdrA,dev1=/dev/sdrB,..."

Note: this allow to change the order of the cards. For instance, if your card are from left to right have following indexes:

<2,3> <4,5> <0,1>

And you want first cells to be on left, then on the middle and then on right, use the following:

args: "dev0=/dev/sdr2,dev1=/dev/sdr3,dev2=/dev/sdr4,dev3=/dev/sdr5,
dev4=/dev/sdr0,dev5=/dev/sdr1"

2.7 TRX driver configuration options

The default TRX configuration used by your component is called config.cfg. It could be found under the directory config/sdr/ of your component (eNB or UE).
The following JSON properties are available:

argsrf_driver.args

String. Set the system device names for the boards. Example:

args: "dev0=/dev/sdr1,dev1=/dev/sdr2,dev2=/dev/sdr0"

sample_hw_fmtrf_driver.sample_hw_fmt

Optional enumeration (auto, ci16, cf8) (default = auto). Set the sample format used on the PCI bus. auto selects the best format depending on the available PCI bandwidth. ci16 selects 16 bit complex integers. cf8 selects 8 bit complex floats giving a 2:1 compression ratio while retaining the full 12 bit amplitude of the ADCs and DACs.

rx_antennarf_driver.rx_antenna

Optional enumeration (auto, tx_rx, rx) (default = auto). Select the connector on which the RX antenna is connected. By default it is connected on the RX connector for FDD and on the TX/RX connector for TDD. This parameter is useful to force the use of the RX connector in TDD.

fifo_tx_timerf_driver.fifo_tx_time

Optional number. Set the DMA TX buffer size in us.
Decreasing this value will improve latency but may lead to signal samples loss if the PCIe chain on the motherboard is not fast enough. This can be detected with the rf_info monitor command of your lteenb or lteue software. If such situation happens, the percentage of TX buffer Usage will be 100% which means the transmission path has encountered underflows.

fifo_rx_timerf_driver.fifo_rx_time

Optional number. Set the DMA RX buffer size in us.
Same as fifo_tx_time for RX chain but reducing it won’t improve latency.

syncrf_driver.sync

Optional enumeration: none, internal, gps, external (default = none). Set the time synchronization source. none and internal uses the internal PPS generated from the clock. internal synchronizes the RX timestamps on the internal PPS. none does not synchronize the RX timestamps on the internal PPS for a faster startup. gps uses the internal GPS. external uses the PPS from an external source (see below).

When several cards are selected (with the args property), sync only sets the time synchronization source of the first card. The other cards are implicitly set to external synchronization, assuming the previous card is used as source.

clockrf_driver.clock

Optional enumeration: internal, external (default = internal). Set the clock source. internal uses the internal clock (VCTCXO). If an external time source is used, the internal clock frequency is adjusted by the PPS signal.

Special cases:

If both clock and sync are external, the clock and PPS from the CLK_IN connector is used.
If clock is external and sync is internal, then an external reference clock is taken from the EXT_CLK UFL connector in the middle of the board (Figure 6.1). Two reference frequencies are supported on this connector: 38.40 MHz and 30.72 MHz (auto detect).
If clock is internal and sync is external, then the internal clock generator is synchronized to an external PPS signal connected on the FPGA0_PPS UFL connector (CMOS 3v3) (Figure 6.1).

gpio0rf_driver.gpio0

Optional enumeration. Selects the signal ouput on connector GPIO0. See below for possible values. Default = rf_dts1.

gpio1rf_driver.gpio1

Optional enumeration. Selects the signal ouput on connector GPIO1. See below for possible values. Default = rf_dts2.

gpio values:

Value	Description
zero	output a constant low level signal (OV)
one	output a constant high level signal (3.3V)
rf_dts1	in TDD mode, output a high level when the TX is active on channel 1. Polarity can be inverted by setting `dts_polarity`: low
rf_dts2	in TDD mode, output a high level when the TX is active on channel 2 Polarity can be inverted by setting `dts_polarity`: low
pps_selected	output a positive going Pulse per Second from the currently selected sync
pps_ext	output a positive going Pulse per Second from the EXT PPS UFL onboard connector
pps_prev	output a positive going Pulse per Second from the CLKIN inter board connector
pps_gps	output a positive going Pulse per Second from the onboard GPS module
pps_vcxo	output a positive going Pulse per Second from the onboard generator
dma_tx	output a positive front on each TX DMA packet (synced on current selected PPS)
dma_rx	output a positive front on each RX DMA packet
dma_tx_100Hz	output a 100 Hz signal synced with dma_tx
dma_rx_100Hz	output a 100 Hz signal synced with dma_rx

dts_polarityrf_driver.dts_polarity

Optional enumeration: high (default), low. Selects the polarity for both rf_dts1 and rf_dts2 signals and also on DTS UFL connectors.

pps_extra_delayrf_driver.pps_extra_delay

Optional float value in microseconds, range: [-10000.0 .. +10000.0] (-10ms to +10ms) Adds a delay between GPS pulse and start of DL frame. If the pps_extra_delay value is negative, the actual delay will be (10ms + pps_extra_delay). For instance, if you want to compensate for 250ns delay caused by cable length, you will set pps_extra_delay: -0.25, the software will add (10ms - 250ns) to the GPS pulse.

tdd_tx_modrf_driver.tdd_tx_mod

Optional number value: 0 (default) or 1. If set to 1, the TX amplifiers will be switched on and off according to the TDD state.

The range for the transmit gain (tx_gain parameter in eNodeB/UE) is from 16 to 90 dB. The range for the receive gain (rx_gain parameter in eNodeB/UE) is from 9 to 60 dB.

The maximum sample rate is 122.88 MHz. Not all sample rate are available: only 122.88 61.44 and 30.72 MHz.

2.8 FR2 support

The SDR100 card supports a frequency range of 300 MHz to 6.0 GHz. In order to provide a FR2 signal for mmwave testing, an external up down converter (UDC) should be used. Typically the UDC is connected by a RF cable to the TX and RX ports of the SDR card to up and down convert a sub-6 GHz signal to a mmwave signal.
Most UDCs should be configured first for the target output frequency. This configuration could be done automatically by setting config_script and config_script_params inside the rf_driver object. Amarisoft provides an example script udc-config.sh available under enb/config/sdr directory. This example script works with Amarisoft UDC and should be adapted if another type is used.

2.9 TDD support

The board integrates a TX/RX switch for TDD operation. When TDD operation is configured, the transmit and receive are done on a single RF port (the TX SMA connector). So you only need to connect antennas on the TX1 and TX2 SMA connectors for TDD operation.

2.10 GPS usage

You can check the GPS operation when the eNodeB/UE is stopped with

./sdr_util gps_state

The GPS takes a few minutes to lock if the GPS antenna is connected. Any active GPS antenna accepting a 3.3V DC supply can be used, for example: http://www.mouser.fr/Search/ProductDetail.aspx?R=ANT-GPS-SH-SMAvirtualkey59000000virtualkey712-ANT-GPS-SH-SMA

To ensure the PLL is correctly locked when launching the lte software, it is recommended to set the synchro to GPS beforehand with the command

./sdr_util sync_gps

2.11 Oscillator frequency automatic tuning from GPS

When the GPS is active, you can fine tune automatically the VCTCXO and store the adjustment value in flash to be used on all following sessions.

./sdr_util gps_cal -s

2.12 Oscillator frequency fine tuning

If you don’t have a GPS, it is still possible to manually fine tune the VCTCXO (Voltage Controlled, Temperature Controlled Crystal Oscillator) frequency provided you have a way to know the offset:

./sdr_util clock_tune n

where n is the offset in PPM (parts-per-million) from the nominal TCXO frequency. Note: the PPM offset n to voltage law is only approximative, so you should adjust it by successive approximation.

3 Troubleshooting

Below are a few tips on how to handle different errors.

The eNodeB does not start and the output of dmesg linux command resembles the following error message:
sdr: version magic '4.12.9-200.fc25.x86_64 SMP mod_unload' should be '4.12.11-200.fc25.x86_64 SMP mod_unload'
To resolve it, you need to recompile the SDR driver on the PC (See Manual Installation).

4 Miscellaneous utilities

4.1 sdr_util

usage: sdr_util [options] cmd [args...]

Options:
-h                         help
-c device_num              select the device (default = all)

Available commands:
version                    dump the FPGA version
sync_state                 dump the synchro and clock state
gps_state                  dump the GPS state
sync_gps                   select GPS as sync source, wait for stable state
gps_cal [-s]               uses the GPS sync to tune VCXO, optionnaly stores the value in flash
temp                       dump the temperature of the board components
led [0|1]                  enable/disable led blinking
clock_tune n               tune TCXO frequency offset to n ppm
upgrade [options]          upgrade the FPGA firmware
  upgrade options are:
  -force                   force upgrade even if identical or 
                           previous version

4.2 sdr_spectrum

sdr_spectrum is a real time spectrum analyzer, sample viewer and I/Q file recorder. It handles several channels at the same time. It can be invoked without arguments. The following options are available:

-h: help
-args str: set the device arguments (default="dev0=/dev/sdr0")
-rx_freq freq: set the RX frequency in Hz (default=2400000000)
-rate rate: set the sample rate to ’rate’ Hz (default=122880000 for SDR100)
-rx_gain gain: set the RX gain in dB (default=60)
-channels c: set the number of RX channels to ’c’ (default=1)
-rx_bw: set the analog receive bandwidth in Hz (default=same as sample rate)
-sync source: set the sync source to ’source’ (none, internal, gps, external) (default=none)
-clock source: set the clock source to ’source’ (internal, external) (default=internal)
-save_path path: set the directory where the recorded samples are saved (default=/tmp)
-duration d: set the recorded sample file duration in seconds when saving (default=1.0)
-save: starts recording samples automatically from program start.
-save-and-exit: same as -save but program will quit at end of recording.

When saving the recorded samples, one file is generated per channel. The filename contains the UTC date, the frequency and the channel number. The I/Q samples are saved as little endian 32 bit float values, in I/Q order. The sample values are between -1 and 1.

Invocation example:

./sdr_spectrum -channels 2 -rx_gain 50 -rx_freq 2680e6 -rate 122.88e6

Resulting output:

sdr_spectrum is interactive and allow actions during runtime:

keys: available keys are indicated in the left side text area.
left mouse button: select a range and the X-Y values are displayed on the bottom of the graph.
right mouse button: in spectrum mode, highlight a range and get a measure of the power inside the range.

4.3 sdr_play

sdr_play is an I/Q file player. Several channels can be played at the same time and they can be time synchronized on an external clock. One file must be provided per channel. The following options are available:

-h: help
-args str: set the device arguments (default="dev0=/dev/sdr0")
-tx_freq freq: set the TX frequency in Hz (default=2400000000)
-rate rate: set the sample rate to ’rate’ Hz (default=122880000 for SDR100)
-tx_gain gain: set the TX gain in dB (default=70)
-channels c: set the number of channels to ’c’ (default=1)
-tx_bw bw: set the analog transmit bandwidth in Hz (default=same as sample rate)
-loop: play the file in loop
-sync source: set the sync source to ’source’ (none, internal, gps, external) (default=none)
-clock source: set the clock source to ’source’ (internal, external) (default=internal)
-time_offset n: offset the output by n samples (default=0)

The sample files should contain the I/Q values as little endian 32 bit floats, in I/Q order. The sample values should be between -1 and 1.

4.4 sdr_test

sdr_test is a general diagnostic tool for SDR boards.
usage: sdr_test [options] cmd [args...]

-h

help

-c device_num

select the SDR device number (default=0)

-d channel

select the device channel (default = 0). useful for CPRI boards.

dma_loopback_test [n][sec]

test DMA loopback on 1 or n devices for sec seconds (def: 10)

rfic_tx_test sample_rate freq tx_gain waveform [tone_freq/ofdm_bw]

test RFIC TX (freq in Hz, tx_gain in dB from 0 to 90)
waveform can be:

 zero for no signal
 prbs for PRBS simulation,
 tone for CW at specified offset from center freq (default = 7.68e6)
 ofdm for OFDM simulation on specified bw (default = auto)

flash_check

verify checksum of code in onboard FPGA.

flash_reload

reload FPGA code from onboard flash

gps_read

GPS read test (best with GPS antenna)

led

blinks onboard led during 5 seconds for identification

synchro_set [src]

Set the source for PPS synchronisation

 0=internal
 1=GPS
 2=slave
 3=ext PPS
 4=CPRI
 5=ext CLK

synchro_state

Show current status of clock and synchro source for SDR device

Example:
 sync_source = 0 (internal)
 pps_locked = 1
 clock_source = 0 (internal)
 clock_pll_locked = 1

version

Show SDR device Hardware and firmware information

Example:
 Board ID:         0x4b21
 Board master:     0x1
 Board revision:   0x1
 FPGA revision:    2023-06-23 09:51:49
 FPGA status:      operational
 Software version: 2023-11-14

dump_info

dump fpga and RF chip information (similar to sdr_util version)

Example:
PCIe SDR TRX driver 2022-02-25
PCIe RFIC /dev/sdr0@0:
  Hardware ID: 0x4b21
  DNA: [0x29445505617111124]
  Serial: '123456789012'
  FPGA revision: 2023-06-23  09:51:49
  FPGA vccint: 1.02 V
  FPGA vccaux: 1.79 V
  FPGA vccbram: 1.02 V
  FPGA temperature: 50.1 Â°C
  AD9371 temperature: 30 Â°C
  AGC: Off
  Sync: internal (locked)
  Clock: internal (locked)
  Clock tune: 0.3 ppm
  NUMA: 0
  DMA: 1 ch, 64 bits, SMem index: On
  DMA0 TX_Underflows: 65535  RX_Overflows: 0
  PCIe bus: bus=0x67 FPGA PCI gen2 x4 (16.0Gb/s)  Bridge PCI gen2 x8 (32.0Gb/s)  OK

gpio 0|1 [value]

Get or set the signal available on GPIO points on the board
See gpio0 and gpio1 in chapter TRX driver configuration options;

5 C API

The PCIe SDR board can be used in other projects with its C API. The C API allows to send and receive I/Q samples and to change the various parameters (frequency, sample rate, bandwidth, gains, ...). The Amarisoft TRX driver, sdr_play and sdr_spectrum are built using this API.

The C API is described in libsdr.h. The corresponding Linux x86_64 dynamic library is libsdr.so.

Amarisoft does not provide any support for this API and can modify it without notice.

6 Physical specifications

6.1 Summary

RF power output < 15 dBm
Max RF input power: ~ +3 dBm RMS (+15dBm peak) with rx_gain < 39; 20 dB less with rx_gain > 39
8 SMA female (TX1, TX2, TX3, TX4, RX1, RX2, RX3, RX4), AC coupled
1 SMA female (GPS antenna with 3.3V DC power supply)
1 input + 3 output SATA connectors for inter-card time synchronization
PCIe gen2 x8, full height, full length
Uses single 12V power supply from PCI connector
ADC/DAC Sample Rate: 122.88 MS/s
ADC/DAC Resolution: 12 bits
Frequency Accuracy: < 1 ppm
LTE 20MHz 64QAM EVM < 2 %rms (f < 2.6 GHz)
LTE 20MHz 64QAM EVM < 4 %rms (f < 3.5 GHz)
Full size (L x W x H): 128mm x 220mm x 20mm
Weight: ~0.300 kg
Power (PCIe 12V): 1A idle => 12W, 2.8A maximum (4x4 max tx_gain) => 33.6W

6.2 Connectors

The following figure depicts the location and functionality of each connector in the PCIe board.

Figure 6.1

Figure 6.2

Figure 6.3

6.2.1 SMA connectors

On Figure 6.1, the connector names are:

TX3: TX3 (and RX3 for TDD): first RF port of secondary device on this board (sdr1)
RX3: RX3 (for FDD)
RX4: RX4 (for FDD)
TX4: TX4 (and RX4 for TDD): second RF port of secondary device on this board
TX1: TX1 (and RX1 for TDD): first RF port of primary device on this board (sdr0)
RX1: RX1 (for FDD)
RX2: RX2 (for FDD)
TX2: TX2 (and RX2 for TDD): second RF port of primary device on this board
GPS: connector for active GPS antenna

6.2.2 SATA PPS/Clock connectors

Clock sync connectors

CLK_IN: Input to sync this board as slave.
CLK_OUT0: Output to use this board as master for other SDR100 board
CLK_OUT1: Output to use this board as master for other SDR100 board
CLK_OUT2: Output to use this board as master for other SDR100 board

On each SATA connector:

pin 2,3: LVDS signal: 122.88MHz clock
pin 6,5: LVDS signal: 38.40MHz bursts. each burst starts indicates the PPS
pins 1,4,7: Ground

6.2.3 UFL connectors

`EXT_CLK`	Analog Input for external clock: see section 2.7: high level from 350mV to 3.3V
`EXT_PPS`	CMOS Input for external sync: see section 2.7
`FPGA0_DTS1`	CMOS output for TX1/RX1 TDD mode: 3.3V in TX mode, 0V in RX mode
`FPGA0_DTS2`	CMOS output for TX2/RX2 TDD mode: 3.3V in TX mode, 0V in RX mode
`FPGA1_DTS1`	CMOS output for TX3/RX3 TDD mode: 3.3V in TX mode, 0V in RX mode
`FPGA1_DTS2`	CMOS output for TX4/RX4 TDD mode: 3.3V in TX mode, 0V in RX mode

The DTS signals can be used to control external TX amplifiers.
They are available also when ’rx_antenna: rx’ is selected.
The polarity can be changed with parameter ’dts_polarity’ indicating the level of the TX mode: dts_polarity can be set to ’high’ (default) or ’low’.

6.2.4 GPIO connectors

On Figure 6.3, the connector names are:

CN22

connector for TX1/TX2 GPIO signals

pin 1: gpio0 (square solder pad)
pin 2: gpio1 (center pin)
pin 3: Ground

CN23

connector for TX3/TX4 GPIO signals

pin 1: gpio0 (square solder pad)
pin 2: gpio1 (center pin)
pin 3: Ground

see gpio0 and gpio1 in chapter TRX driver configuration options;

6.3 TX power

Maximum TX Power versus RF frequency, measured on OFDM BW = 100MHz.

RF Frequency	dBm/MHz	dBm
500	-8.0	12.0
1000	-8.0	12.0
1500	-11.0	9.0
2000	-12.0	8.0
2500	-16.0	4.0
3000	-15.0	5.0
3500	-17.0	3.0
4000	-23.0	-3.0
4500	-29.0	-9.0
5000	-30.0	-10.0
5500	-32.0	-12.0
6000	-40.0	-20.0

7 Remote API

SDR driver implements the trx remote API.

Message definition:

commandtrx.command

Optional string. Can be:

clock_tune

Exemple:

{
    "message": "trx",
    "command": "clock_tune"
}

Here are the additional request and response field depending on command value:

7.1 clock_tune

Request fields:

offset: Optional number. If command is clock_tune, defines the clock drift to set in ppm.

8 Change history

8.1 Version 2024-06-14

Added remote API support

8.2 Version 2023-09-08

Added NUMA support

8.3 Version 2023-06-10

Added tdd_tx_mod configuration parameter
New FPGA firmmware version 2023-05-24

9 License

trx_sdr100 is available without any express or implied warranty. In no event will Amarisoft be held liable for any damages arising from the use of this software.

For more information on licensing, please refer to license terms.

License terms

Amarisoft SAS - www.amarisoft.com
16-18 rue Rivay, 92300 LEVALLOIS PERRET, France SAS with a capital of 300,000 Euros - VAT FR21753998269 - SIREN: 753998269 (RCS Nanterre) - NAF 6201Z – DUNS 264482426

SOFTWARE LICENSE TERMS
NOTICE: THE AMARISOFT SOFTWARE PRODUCT, TOGETHER WITH ITS ACCOMPANYING DOCUMENTATION,
(THE "PRODUCT") IS THE PROPERTY OF AMARISOFT. THE PRODUCT IS MADE AVAILABLE TO YOU, THE
PURCHASER, SUBJECT TO THE FOLLOWING LICENSE AGREEMENT ("LICENSE AGREEMENT"). PLEASE READ
THIS LICENSE CAREFULLY BEFORE INSTALLING OR USING THE PRODUCT. A COPY OF THIS LICENSE IS
AVAILABLE FOR YOUR FUTURE REFERENCE IN THE "LICENSE.TXT" FILE PROVIDED WITH THE PRODUCT.
IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW,
THEN YOU MAY NOT USE THE PRODUCT. ANY USE BY YOU OF THIS PRODUCT OR INSTALLATION OF THE
PRODUCT ALSO CONSTITUTES YOUR ACCEPTANCE OF THESE TERMS.
AMARISOFT is only willing to grant you a license under this License Agreement if you obtained the Product
from AMARISOFT or an AMARISOFT authorized distributor or reseller, a list of which is available on
AMARISOFT website. If you obtained the Product from any other source you may not install or use the
Product.

1. GRANT OF LICENSE AND SCOPE OF USE
For each license that you acquire to use the Product, you will be provided with a License Certificate (a "License
Certificate"), which may be either a certificate, the installation and licensing instructions, your invoice, or an
activation file and which may be provided to you either with the Product media or separately by AMARISOFT
or its authorized distributors or resellers. The License Certificate will contain information specific to the
Product, the type of license under which you may use the Product and the number of licenses that you have
acquired. In order to activate and use the Product as set forth in this License Agreement, you must follow the
instructions when prompted by the Product.
The type of license you may acquire is a Standard License or a Floating License, all defined in Sections 1.1 and
Section 1.2 of this License Agreement. Unless your License Certificate identifies your acquisition of another
license type, you have acquired a Standard License. For more information on which license types, if any, is
included with the Product media, you should contact AMARISOFT or your AMARISOFT authorized distributor or
reseller.
Unless otherwise agreed, one (1) AMARISOFT license provides the right to use only one instance of the Product
software at a time.
Subject to the other terms and conditions of this License, you may make a reasonable number of copies of the
Product to backup devices such as hard disks, optical media, or tape and one (1) physical CD media backup
copy of the Product solely to replace the original copy provided to you if the original copy is damaged or
destroyed. All rights not specifically granted to you herein are retained by AMARISOFT.

1.1 Standard License
The terms of this Section 1.1 are applicable to you only if you have purchased a Standard License, as defined
below, for the Product directly from AMARISOFT or an AMARISOFT authorized distributor or reseller.
Subject to the terms and conditions of this License, AMARISOFT grants you, if you are an individual or if you
are an entity, a personal, non-exclusive, non-transferable and limited license to use the Product solely with
one (1) designated single hardware in your organization (a "Standard License"). This hardware is either a
Personal Computer that you hold in your organization or that AMARISOFT has supplied you. This hardware can
also be a USB device supplied by AMARISOFT.
You may purchase from AMARISOFT or an AMARISOFT authorized distributor or reseller additional licenses to
permit multiple hardware to use the Product. This right shall be agreed in writing. The Standard License shall
provide you with the right to access and use the Product, only for the number of hardware for which you have
paid the applicable license fees and obtained a License Key Certificate. The Product may be used exclusively by
the specifically designated hardware, subject to all the terms and conditions of this License Agreement. You
agree that you will not designate more hardware than the number of Standard Licenses that AMARISOFT or an
AMARISOFT authorized distributor or reseller has expressly granted you and you will not allow the Product to
be used by any hardware other than the hardware designated by you.

1.2 Floating License
The terms of this Section 1.2 are applicable to you only if you have purchased a Floating License, as defined
below, for the Product directly from AMARISOFT or an AMARISOFT authorized distributor or reseller.
Subject to the terms and conditions of this License, AMARISOFT grants you, if you are an individual or if you
are an entity, a personal, non-exclusive, non-transferable and limited license to use the Product from our
floating license server in your organization ("FLS"). Our floating license server will allow you to run the license
on a virtual machine and thus use it on any hardware in your organization (an "FLS License").
You may purchase from AMARISOFT or an AMARISOFT authorized distributor or reseller additional licenses
and place them on our license server to permit multiple hardware to use the Product.

2. SPECIAL TERMS
The following terms and conditions ("Special Terms") are specific to certain editions, versions and components
of the Product and are in addition to the provisions of Section 1. If any provision of the Special Terms
applicable to the Product conflicts with any other provision of this License, then the provision of the Special
Terms will supersede and control.

2.1 Additional license terms applicable to third party software
Certain components of the Product use or incorporate third-party software programs and/or libraries ("Third-
Party Software"), which are loaded or integrated (in both object and source code form) on the Product. You
agree that AMARISOFT's third-party licensors and suppliers are intended third party beneficiaries of all terms
and conditions of this License intended to protect intellectual property rights in the Product (including the
Third-Party Software) and limit certain uses thereof.

3. LIMITATIONS
You may not:
(a) modify, adapt, alter, translate or create derivative works of the Product or merge the Product with other
software other than as described in the Product's accompanying documentation or as approved of in writing
by AMARISOFT;
(b) lease, rent or loan the Product to any third party;
(c) sublicense, distribute or otherwise transfer the Product or any component thereof to any third party except
as expressly authorized in this Agreement;
(d) reverse engineer, decompile, disassemble or otherwise attempt to derive the source code of the Product;
(e) remove, alter or obscure any confidentiality or proprietary notices (including copyright and trademark
notices) of AMARISOFT or its licensors or suppliers on or accompanying the Product;
(f) allow third parties to access or use the Product including but not limited to using the Product in a time-
sharing arrangement, operating the Product as part of a service bureau or, except as expressly authorized
under Sections 1 and 2 otherwise using the Product for the use or benefit of third parties;
(g) reproduce or use the Product except as expressly authorized under Sections 1 and 2;
(h) use the Product with any other hardware than the hardware designated in your organization; or
(i) disclose or publish performance benchmark results for the Product. The rights granted under this License
apply only to this Product.
You must procure a separate license to use other AMARISOFT software. Furthermore, you may not permit end
users of the Product ("End Users") to conduct the restricted activities limited by items (a) through (e), (g) and
(i) above insofar as they apply to certain files, libraries and/or source code specifically designated as
"redistributables" by AMARISOFT in the accompanying printed or on-line documentation and that are
necessary to use your own application programs and other works created using the Product
("Redistributables"), and such End User's sublicense rights to the Redistributables are conditioned upon
compliance with such limitations. The limitations in this Section 3 apply equally to your use of the Product, in
whole or in part, including any component or Redistributable.

4. LIMITED WARRANTY AND DISCLAIMER
AMARISOFT warrants you, the initial purchaser and no other party, that any physical media included with the
Product, as and when provided to you, will be free of physical defects in materials and workmanship for a
period of thirty (30) days after the date that you initially acquire the Product.
Your exclusive remedy and AMARISOFT's sole liability for breach of this warranty is that AMARISOFT will
replace any defective media returned to AMARISOFT within the thirty (30) day warranty period. This warranty
does not apply to damages resulting from misuse, abuse or neglect. Any replacement media will be warranted
as above for the remainder of the original warranty period or twenty (20) days from the date we ship it to you,
whichever is longer.
EXCEPT FOR THIS EXPRESS LIMITED WARRANTY, THE PRODUCT IS PROVIDED "AS IS" AND WITHOUT
WARRANTY OF ANY KIND. AMARISOFT HEREBY EXCLUDES AND DISCLAIMS ALL IMPLIED OR STATUTORY
WARRANTIES, INCLUDING ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
QUALITY, NONINFRINGEMENT, TITLE, RESULTS, EFFORTS OR QUIET ENJOYMENT. THERE IS NO WARRANTY
THAT THE PRODUCT WILL BE ERROR-FREE OR WILL FUNCTION WITHOUT INTERRUPTION. YOU ASSUME THE
ENTIRE RISK FOR THE RESULTS OBTAINED USING THE PRODUCT. TO THE EXTENT THAT AMARISOFT MAY NOT
DISCLAIM ANY WARRANTY AS A MATTER OF APPLICABLE LAW, THE SCOPE AND DURATION OF SUCH
WARRANTY WILL BE THE MINIMUM PERMITTED UNDER SUCH LAW.

5. SERVICES, UPDATES AND PRODUCT CHANGES
AMARISOFT is not required under this License Agreement to provide any installation, maintenance service,
training or other services to you, except those expressly provided herein. Such services, if available, must be
purchased separately.
If, pursuant to a separate support agreement or otherwise, AMARISOFT provides you with a new release, error
correction, update, upgrade or other modification to the Product, such modification will be deemed part of the
Product, and subject to the terms of this License Agreement, unless the modification is expressly provided
subject to a separate License Agreement.
AMARISOFT reserves the right at any time not to release or to discontinue release of any Product and to alter
prices, features, specifications, capabilities, functions, licensing terms, release dates, general availability or
other characteristics of any future releases of the Product.

5.1 Support extension
Unless otherwise indicated, AMARISOFT License includes a one-year email support period and update.
You can subscribe to an additional one-year support and update period, at the latest within the four months
following the expiry date of the initial purchase. You can then renew subscription to this extension every year,
with the same four-month deadline. The extended support and update period starts on the day after the initial
expiry date.
Once this four-month deadline is over, an extra administrative reactivation fee is invoiced in addition to the
extension cost. The extended support and update period starts when payment of the corresponding invoice is
received.

6. REGISTRATION
You must register the Product with AMARISOFT as a condition to your rights to use the Product.
For all concerned, you will be asked to provide identification information on the hardware (serial number,
internal inventory number, other) you plan to install the Product on.

7. CONFIDENTIALITY
You acknowledge that if part of the Product in source code form exists, it remains a confidential trade secret of
AMARISOFT. You agree to hold this information in confidence, not to disclose it to any person, and not to use it
for any purpose other than the use and operation of the Product as permitted under this License Agreement.

8. LIMITATION OF LIABILITY
IN NO EVENT WILL AMARISOFT BE LIABLE TO ANY PARTY FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL,
EXEMPLARY, SPECIAL OR PUNITIVE DAMAGES, INCLUDING ANY LOSS OF PROFIT, REVENUE, BUSINESS
OPPORTUNITY OR DATA, ARISING FROM OR RELATING TO THIS LICENSE AGREEMENT OR THE PRODUCT,
WHETHER IN CONTRACT, IN TORT, NEGLIGENCE OR OTHERWISE, EVEN IF AMARISOFT KNEW, SHOULD HAVE
KNOWN OR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. AMARISOFT'S TOTAL CUMULATIVE
LIABILITY ARISING FROM OR RELATED TO THIS LICENSE AGREEMENT OR THE PRODUCT, WHETHER IN
CONTRACT, IN TORT OR OTHERWISE, WILL NOT EXCEED THE FEES ACTUALLY PAID BY YOU UNDER THIS
LICENSE AGREEMENT. THIS SECTION 8 WILL APPLY EVEN IF AN EXCLUSIVE REMEDY HEREUNDER HAS FAILED
OF ITS ESSENTIAL PURPOSE.

9. TERM AND TERMINATION

9.1 Term
The term of this License Agreement will begin as of the date that you receive the Product and will remain in
effect unless terminated under this Section 9.

9.2 Termination for Convenience
You may terminate this License Agreement for any reason, or for no reason, by giving AMARISOFT a five-day
(5) written notice. You shall not be entitled to request repayment of any fee or payment made to AMARISOFT.

9.3 Termination for Cause
AMARISOFT may terminate this License Agreement if you breach your obligations hereunder. AMARISOFT will
affect such termination by giving you notice of termination, specifying therein the alleged breach. If your
breach is curable, you will have a grace period of thirty (30) days after such notice is served to cure the breach
described therein. If the breach is cured within the thirty (30) day grace period, then this License Agreement
will remain in effect; otherwise, this License Agreement will automatically terminate upon the conclusion of
the thirty (30) day grace period.

9.4 Effect of Termination
Upon the termination of this License Agreement for any reason the following terms shall apply:
(a) all rights granted under this License Agreement will immediately terminate and you must stop all use of the
Product and any Redistributables;
(b) you must return to AMARISOFT or destroy all copies of the Product provided to or made by you, and will,
within ten (10) days after the effective date of termination, provide AMARISOFT with written certification that
all such copies have been returned or destroyed; and
(c) all provisions of this License Agreement with the exception of the licenses granted in Sections 1 and 2, will
survive termination of this License Agreement for any reason.

10. GENERAL PROVISIONS

10.1 Audit
If you are entering into this License Agreement as an entity other than an individual (e.g., as a corporation, a
partnership, or other organization), during the term of this License and for three (3) years thereafter,
AMARISOFT or its outside auditors will have the right to conduct an audit of your records and computer
systems to verify that you have paid to AMARISOFT the correct amounts owed under this License Agreement
and determine whether the Products are being used in accordance with the terms of this License Agreement.
Any audit will be conducted during regular business hours at your facilities, with reasonable notice. You agree
to provide the audit team access to the relevant records and facilities and to provide reasonable assistance to
AMARISOFT in connection with this provision. You agree to pay the cost of the audit if any underpayments
during the period covered by the audit amount to more than five percent (5%) of the fees actually owed or if
the number of deployments of the Products is more than five percent (5%) of that licensed.

10.2 Hazardous Uses
The Product is not intended for use in connection with any application requiring fail-safe performance such as
the operation of nuclear power facilities, air traffic control or navigation systems, weapons control systems,
life support systems, or any other system whose failure could lead to injury, death, environmental damage or
mass destruction. You agree that AMARISOFT will have no liability of any nature, and you are solely
responsible, for any expense, loss, injury or damage incurred as a result of such use of the Product.

10.3 Entire License and Severability
This License Agreement constitutes the entire, final and exclusive agreement between you and AMARISOFT
regarding the specific license transaction described herein. If any provision of this License Agreement is held to
be illegal, invalid or unenforceable for any reason, then such provision will be enforced to the maximum extent
permissible and the remainder of the provisions of this License Agreement will remain in full force and effect.

10.4 Assignment
You may not transfer the Product, assign this License Agreement or assign any of your rights or delegate any of
your obligations under this License Agreement, by operation of law or otherwise (including by merger, sale of
assets or consolidation), without AMARISOFT's prior written consent. Any attempted assignment in violation
of this Section 10.4 will be void.

10.5 Export Control
You may not directly or indirectly transfer the Product, including its documentation, to any country if such
transfer would be prohibited by applicable law. You agree to the foregoing and you are representing and
warranting that you are not located in, under the control of, or a national or resident of any such country. You
will be solely responsible for identifying and complying with all laws of any jurisdiction regarding the import,
export or use of Products and technical data supplied by AMARISOFT. You will obtain at your own expense all
licenses, permits or approvals required by any government to use the Product.

10.6 Waiver and Modifications
All waivers must be in writing. Any waiver or failure to enforce a provision of this License Agreement on one
occasion shall not be deemed a waiver of any other provision or such provision on any other occasion. This
License Agreement may only be amended by a written document signed by both parties.

11. CRYPTOGRAPHY
The Product and the content provided by AMARISOFT may contain encryption software. The country in which
you are currently may have restrictions on the import, possession, and use, and/or re-export to another
country, of encryption software. BEFORE using any encryption software, please check the country's laws,
regulations and policies concerning the import, possession, or use, and re-export of encryption software, to
see if this is permitted.

12. NON-RECURRING ENGINEERING
The intellectual property of all items designed, developed and manufactured by AMARISOFT resides and
remains with AMARISOFT. The payment of Non-Recurring Engineering (NRE) charges by you does not confer
any rights to the intellectual property of any designs which emanate directly or indirectly from the
development. As part of any contract, whether it includes the payment of NRE or not, you must accept
without reservation that AMARISOFT is the rightful owner of all intellectual property rights for the Product
and/or other products which are supplied under this Licence Agreement or standard supplies to you. You must
not copy, or allow any third party to copy the designs of any AMARISOFT's products.

Table of Contents