%% BioMed_Central_Tex_Template_v1.06
%%                                      %
%  bmc_article.tex            ver: 1.06 %
%                                       %

%%IMPORTANT: do not delete the first line of this template
%%It must be present to enable the BMC Submission system to
%%recognise this template!!

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                                     %%
%%  LaTeX template for BioMed Central  %%
%%     journal article submissions     %%
%%                                     %%
%%          <8 June 2012>              %%
%%                                     %%
%%                                     %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                                                                 %%
%% For instructions on how to fill out this Tex template           %%
%% document please refer to Readme.html and the instructions for   %%
%% authors page on the biomed central website                      %%
%% http://www.biomedcentral.com/info/authors/                      %%
%%                                                                 %%
%% Please do not use \input{...} to include other tex files.       %%
%% Submit your LaTeX manuscript as one .tex document.              %%
%%                                                                 %%
%% All additional figures and files should be attached             %%
%% separately and not embedded in the \TeX\ document itself.       %%
%%                                                                 %%
%% BioMed Central currently use the MikTex distribution of         %%
%% TeX for Windows) of TeX and LaTeX.  This is available from      %%
%% http://www.miktex.org                                           %%
%%                                                                 %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%%% additional documentclass options:
%  [doublespacing]
%  [linenumbers]   - put the line numbers on margins

%%% loading packages, author definitions

%\documentclass[twocolumn]{bmcart}% uncomment this for twocolumn layout and comment line below
\documentclass{bmcart}

%%% Load packages
%\usepackage{amsthm,amsmath}
%\RequirePackage{natbib}
%\RequirePackage[authoryear]{natbib}% uncomment this for author-year bibliography
%\RequirePackage{hyperref}
\usepackage[utf8]{inputenc} %unicode support
%\usepackage[applemac]{inputenc} %applemac support if unicode package fails
%\usepackage[latin1]{inputenc} %UNIX support if unicode package fails
\usepackage[T1]{fontenc}
\usepackage[english]{babel}
\usepackage[document]{ragged2e}


\usepackage{amssymb, amsmath, amsbsy}
\usepackage{booktabs}
\usepackage{graphicx}

\usepackage{subcaption}

%\usepackage[table]{xcolor} %for use in color links
%\usepackage{colortbl}
%\usepackage{ragged2e}
%\usepackage{tabu}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                                             %%
%%  If you wish to display your graphics for   %%
%%  your own use using includegraphic or       %%
%%  includegraphics, then comment out the      %%
%%  following two lines of code.               %%
%%  NB: These line *must* be included when     %%
%%  submitting to BMC.                         %%
%%  All figure files must be submitted as      %%
%%  separate graphics through the BMC          %%
%%  submission process, not included in the    %%
%%  submitted article.                         %%
%%                                             %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


%\def\includegraphic{}
%\def\includegraphics{}



%%% Put your definitions there:
\startlocaldefs
\endlocaldefs


%%% Begin ...
\begin{document}

%%% Start of article front matter
\begin{frontmatter}

\begin{fmbox}
\dochead{Research}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                                          %%
%% Enter the title of your article here     %%
%%                                          %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
%\title{A Reconfigurable Analog Back-End Based on Software-Defined Radio for CubeSat Applications}
\title{A Reconfigurable Analog Back-End for CubeSat Communications}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                                          %%
%% Enter the authors here                   %%
%%                                          %%
%% Specify information, if available,       %%
%% in the form:                             %%
%%   <key>={<id1>,<id2>}                    %%
%%   <key>=                                 %%
%% Comment or delete the keys which are     %%
%% not used. Repeat \author command as much %%
%% as required.                             %%
%%                                          %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 1st
\author[
   addressref={aff1},                   % id's of addresses, e.g. {aff1,aff2}
  corref={aff1},                       % id of corresponding address, if any
 %  noteref={n1},                        % id's of article notes, if any
   email={alvarez\_jose@ucol.mx}   % email address
]{\inits{JLA}\fnm{José L.} \snm{Alvarez-Flores}}
% 2nd
\author[
   addressref={aff2},
   email={jflorest@uaz.edu.mx}
]{\inits{JFT}\fnm{Jorge} \snm{Flores-Troncoso}}
% 3th
\author[
addressref={aff2},
email={rsandoval@uaz.edu.mx}
]{\inits{RSA}\fnm{Remberto} \snm{Sandoval-Arechiga}}
% 4th
\author[
addressref={aff2},
email={}
]{\inits{JAC}\fnm{Joel A.} \snm{Castillo}}
% 5th
\author[
addressref={aff3},
email={}
]{\inits{JSR}\fnm{Jorge} \snm{Simón}}
% 6
\author[
addressref={aff2},
email={}
]{\inits{MHC}\fnm{Manuel} \snm{Hernandez-Calviño}}
%7
\author[
addressref={aff1},
% corref={aff1},   
email={lsoriano@ucol.mx}
]{\inits{LSE}\fnm{Leonel} \snm{Soriano-Equigua}}




%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                                          %%
%% Enter the authors' addresses here        %%
%%                                          %%
%% Repeat \address commands as much as      %%
%% required.                                %%
%%                                          %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\address[id=aff1]{%                           % unique id
  \orgname{University of Colima, México}, % university, etc
  \street{333 University Ave.},              %
  %\postcode{}                                % post or zip code
  \city{Colima},                              % city
  \cny{Mx}                                    % country
}

\address[id=aff2]{%
	\orgname{Autonomous University of Zacatecas, México}, % university, etc
	\street{801 Ramon Lopez Velarde, Ave.},              %
	\postcode{98010}                                % post or zip code
	\city{Zacatecas},                           % city
	\cny{Mx}  
}


\address[id=aff3]{%
  \orgname{Catedras CONACYT, Autonomous University of Zacatecas, México}, % university, etc
  \street{801 Ramon Lopez Velarde Ave.},              %
  \postcode{98010}                                % post or zip code
  \city{Zacatecas},                           % city
  \cny{Mx}  
}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                                          %%
%% Enter short notes here                   %%
%%                                          %%
%% Short notes will be after addresses      %%
%% on first page.                           %%
%%                                          %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%\begin{artnotes}
%\note{Sample of title note}     % note to the article
%\note[id=n1]{Equal contributor} % note, connected to author
%\end{artnotes}

\end{fmbox}% comment this for two column layout

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                                          %%
%% The Abstract begins here                 %%
%%                                          %%
%% Please refer to the Instructions for     %%
%% authors on http://www.biomedcentral.com  %%
%% and include the section headings         %%
%% accordingly for your article type.       %%
%%                                          %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\begin{abstractbox}

\begin{abstract} % abstract
%\parttitle{} %if any
\justify

Current small satellite platforms such as CubeSats, require robust and versatile communication subsystems that allow the reconfiguration of the critical operation parameters such as carrier frequency, transmission power, bandwidth, or filter roll-off factor. In this paper, a reconfigurable Analog Back-End for CubeSat communications is proposed. This prototype is implemented using CAD software, on a 6-layer PCB of 10 cm$^{2}$ to implement a transceiver that operates from 0.070 to 6 GHz and complying with CubeSat and IPC-2221 standards. An Software-Defined Radio approach implemented on a baseband processor is used for control purposes. Measurements showed that the signal power at the output of the proposed analog back-end is suitable to feed the subsequent antenna subsystem.


\end{abstract}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                                          %%
%% The keywords begin here                  %%
%%                                          %%
%% Put each keyword in separate \kwd{}.     %%
%%                                          %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\begin{keyword}
\kwd{Radiofrequency}
\kwd{analog back-end}
\kwd{field-programmable gate arrays}
\kwd{CubeSat}
\kwd{transceiver.}
\end{keyword}

% MSC classifications codes, if any
%\begin{keyword}[class=AMS]
%\kwd[Primary ]{}
%\kwd{}
%\kwd[; secondary ]{}
%\end{keyword}

\end{abstractbox}
%
%\end{fmbox}% uncomment this for twcolumn layout

\end{frontmatter}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                                          %%
%% The Main Body begins here                %%
%%                                          %%
%% Please refer to the instructions for     %%
%% authors on:                              %%
%% http://www.biomedcentral.com/info/authors%%
%% and include the section headings         %%
%% accordingly for your article type.       %%
%%                                          %%
%% See the Results and Discussion section   %%
%% for details on how to create sub-sections%%
%%                                          %%
%% use \cite{...} to cite references        %%
%%  \cite{koon} and                         %%
%%  \cite{oreg,khar,zvai,xjon,schn,pond}    %%
%%  \nocite{smith,marg,hunn,advi,koha,mouse}%%
%%                                          %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%%%%%%%%%%%%%%%%%%%%%%%%% start of article main body
% <put your article body there>

%%%%%%%%%%%%%%%%
%% Background %%
%%

\section{INTRODUCTION}
\justify
Applying the new electronic communication technologies to spatial missions either for remote observation or surface exploration of the earth or other astronomical bodies, promises the improvement of sustainability, robustness, and truthfulness of the current missions when sharing spatial resources \cite{Golkar}. This new paradigm requires the use of diverse technologies to achieve a flexible reconfiguration capability of the communication systems between heterogeneous satellites. \smallskip

The trend in electronic design is governed by Moore's Law which establishes capacities of the General Purpose Processors (GPP's), Digital Signal Processors (DSP's), and Field Programmable Gate Arrays (FPGA's ) \cite{Bard}. As a result of this, the processing flow of radio signals –traditionally made with blocks of specialized hardware- could be defined and controlled by software, known as Software-Defined Radio (SDR). The embedded SDR technique used on a  System on a Chip (SoC) turns out to be suitable to implement a flexible, adaptable and reconfigurable satellite communication systems and eliminates the need to implement hardware for each application. Also, this technique allows reducing development time, costs, and system mass. \smallskip

Several examples of embedded SDR on a SoC for satellite applications are found in the literature. For example, in \cite{Akhty} a system based on a commercial BladeRFx115\textsuperscript{\textregistered}  is explained, this works with an LMS6002D Integrated Circuit (IC) from 0.30 to 3.8 GHz with a programmable bandwidth from 1.5 to 28 MHz. This one is controlled with a Raspberry Pi 2\textsuperscript{\textregistered} which is integrated in an embedded GNU-Radio way; all this with the purpose to integrate a launchable network based on Commercial-Off-The-Shelf (COTS) components and for emulating a network of federated satellites. This challenging implementation interconnects several external subsystems that use a SoC for improving performance, costs, and volume. In \cite{Mahesh} an SDR architecture is proposed in which the FPGA and SoC (FMCOMMS3 from Analog Devices\textsuperscript{\textregistered} ) are combined with a programmable radio frequency (RF) transceiver to solve the reconfiguration challenges of transmitter and the receiver. It involves the use and implementation of COTS such as the FMCOMMS3( using AD9361 IC for RF stage) and a ZYNQ 7020 from Xilinx\textsuperscript{\textregistered} among other devices. In \cite{Tian}, Tian et al. designed and implemented an AD9361 based platform for software radio exclusively for the receiver stage and a ZC706 applied to the digital baseband processing module of SoC. \smallskip

There are other implementations based on similar architecture (using COTS like FMCOMMS3) as the one presented on \cite{Mahesh2}, where SDR is applied to the ground segment and develops the Digital Down Converter (DDC) stage using the hardware descriptive language VHDL, in addition to some other baseband processes such as channel coding, and data interleaver, among others. The disadvantage of that proposal is that the IP-Cores involved are Xilinx\textsuperscript{\textregistered} intellectual property  and the transmission rates achieved are relatively low, 1.2 to 19.2 Kbps. Finally, it should be mentioned that there are companies in the market that offer satellite communications subsystems based on SDR, like the one commercialized by  \cite{GOMs}, which can be reconfigured to use different frequency bands such as L, S or K. Nevertheless, it has the drawbacks both of being expensive and proprietary architecture. \smallskip

The authors in \cite{kama} concluded that hardware reuse is a novel approach in the implementation of SDR systems, which results in better performance of communications schemes. In \cite{halder}, a design of an RF front-end for a nanosatellite is presented, using low-cost commercial components like the CC2510 IC, for both the reception and transmission stages. This IC works in a narrow bandwidth of 2.400 to 2.483 GHz. \smallskip

In \cite{Flor}, a communication system was implemented in a Zynq 7020 as part of the baseband processor (BBP), however, the RF stage was simulated. \smallskip 

As pointed, there are several applications based on digital implementations for SDR systems proposed in the literature and others offered as COTS components. However, the RF analog back end remains partially unexplored and represents an opportunity area for research. \smallskip

This document describes the design, implementation, and testing of a low-cost reconfigurable prototype of the communications subsystem, called the Reconfigurable Analog Back-End (RABE), for the space segment that meets the CubeSat standard. The proposed RABE consists of two stages; The first performs baseband processing, control, and reconfiguration for the second stage, and is implemented in a commercial SoC architecture. The RF stage (second stage), in which this work is focused, is based on the design, implementation, and testing, the protocol for this work which includes digital/analog conversion, mixer, and filters based on COTS, which operates from 0.070 to 6 GHz.\smallskip

The rest of the paper is organized as follows: in Section II the RABE system architecture, the design and development of the PCB for RF stage, the testbed design, and the software tools used are described; in Section III implementation and testing are shown;  in Section IV the main results obtained are presented and discussed; and in Section V, the conclusions are exhibited.\smallskip



\section{METHODS AND EXPERIMENTAL SETUPS}


\subsection*{A. System Architecture}

The RABE design features two interfaces, the first one is a digital I/O data, control, and communication interface between the prototype and the SoC, which is controlled by an FPGA, and which is part of the BBP; the connection interface with the RF stage is achieved through an FMC connector; the second one is an RF analog output with SMA connector as the interface to the RF filtering stages, power amplifier, and antenna. The main core of the RABE is powered by an AD9354 IC.\smallskip


%%%%%%%%%%%%%%%%%%%
%% proposed Fig 1 
%%%%%%%%%%%%%%%%%%%

Fig. 1 shows the communication model, which was implemented, the RF stage (this work) was designed, implemented, tested, and tuning for the RABE in yellow, which was the contribution of the paper.\smallskip

%%%%%%%%%%%%%%%%%%%
%% proposed Fig 2
%%%%%%%%%%%%%%%%%%%


The BBP stage consisted in the development and coupling of the Serial Communication Protocol (SPI), as well as the programming of the registers to control the flow of data, synchronization, and processing of the data from the BBP to the RABE through the FMC connector, which is responsible for carrying all the bits for the operation of both devices, including the voltage and ground lines.\smallskip

In the RF stage, the SPI was synchronized to program all the necessary registers in the IC, the DACs, the filtering stage, the preamplifiers, and the local oscillator, that were configured to be tuned at the required frequency, it is noteworthy that each of the configured actions corresponds to the programming of registers groups in order to obtain the correct result shown in yellow in Fig. 2.\smallskip 


\subsection*{B. RF stage design}

During the design stage of the RABE subsystem prototype, the necessary requirements for the development of the PCB (Printed Circuit Board) were specified to guarantee correct operation, allowing interoperability between the subsystem devices. The requirements are detailed in Table 1. \smallskip

%table 1


In general, the design of the RABE features two interfaces, the first one is the digital I/O data, control, and synchronization interfaces between the prototype and the SoC; the second one is the analog RF output with an SMA connector. \smallskip

The RABE has a read/write registers interface carry out via the Serial SPI. Therefore, one of the preliminary task to do was to implement the SPI port in the BBP, since it is not a native protocol in the FPGA.\smallskip



%%%%%%%%%%%%%%%%%%%
%% proposed Fig 3
%%%%%%%%%%%%%%%%%%%


The data lines for the PCB of the RF stage are divided into two sets: the differential and single-ended lines as shown in Fig.3 . The maximum data transfer frequency achieved is 245.76 and 61.44 MHz for the differential bus and single-ended respectively. However, it depends on the IP-Core processing speed of the SoC and FPGA used by the implementation. The RF output feeds the next stage (it is not the scope of the work)  comprised of power amplifiers, filters, and antennas, in order to achieve a high signal-to-noise ratio (SNR) and considering a link range of 2000 km in the free-space Low Earth Orbit(LEO) satellite.\smallskip

 \smallskip
 
%%%%%%%%%%%%%%%%%%%
%% proposed Fig 4
%%%%%%%%%%%%%%%%%%%
 
 
RF stage of the RABE prototype uses the AD9364 transceiver,  internally composed of ADC converters, DACs, filters, GPOs, PLLs, and an SPI communication control port \cite{AD9364ds}, as illustrated in Fig.4.\smallskip


In this work, the transmission, data entry, DAC, filters, and SPI serial communication stages are used. The radio transmitter is implemented with the ability to operate in various frequency bands, mainly S-band. In addition to this, the configuration to modify in the application of the IC data such as the transmission power, the filtering, and, most importantly, that the prototype design must comply with the size proposed for the CubeSat standard. The IC AD9364 from Analog Devices\textsuperscript{\textregistered} \cite{AD9364ds} is configured as an RF transceiver, operating in the 0.070 to 6.000 GHz frequency range with the ability to tune the bandwidths (BW) from 0.2 to 56.0 MHz and allowing applications proposed by the manufacturer such as point-to-point communication systems, base stations (BS) for femto/pico/microcells and general-purpose radio systems. \smallskip
 
Further, the AD9364 IC is set by reading/writing into the registers set described in \cite{AD9364rm}. According to the manufacturer, the IC has a list of almost 1,014 (0x3F6) 8-bit registers with configuration capabilities intended for diverse applications. These IC-specific application steps are initialization, configuration, transmission, reception, and analog records in reception (see Table 2). Record data flow modes can be: read, write, or both. The SPI port of the AD9364 operates at a recommended maximum speed of 50 MHz, according to the manufacturer's specifications  \cite{AD9364ds}. However, a frequency of 8 MHz was used for testing purposes in this work to ensure a safe transfer of information  to registers.\smallskip
 
 %table3
 
 
Regarding the operating and configuration modes of the registers, there are a relatively large number of reserved and/or empty positions, so, in order not to cause improper operation of the system, it is advisable not to refer to them. \smallskip
 
%%%%%%%%%%%%%%%%%%%
%% proposed Fig 5
%%%%%%%%%%%%%%%%%%%

 
 To reduce transients while changing the transmission frequency setting on the device, the power to the couplers on the transmission lines is directly connected to a 1.3V voltage source. The capacitors shown in Fig. 5 are intended for removing noise and transients at the transmitter output. \smallskip
 
It is worth mentioning that all the designs, measurements, and tests for the resulting devices were carried out in a test laboratory with a controlled environment (temperature, voltage levels, electromagnetic noise, electric shocks, among others) in such a way that the results obtained are completely similar to those obtained by simulations tools. \smallskip
 
Design rules concerning the CubeSat standard \cite{Cubesatstd} and PCB design \cite{IPC2221} were applied to the electronic design process. The final result was a 6-layer PCB, of 10 cm x 10 cm (see Fig. 6), on the other hand, the manufacturer suggests a fixing or soldering area on the PCB with the intention of achieving high performance and achieving adequate operation of the IC \cite{AD9364rm}. In Table 3, the thickness of the 6 PCB layers is shown.  \smallskip
 
%%%%%%%%%%%%%%%%%%%
%% proposed Fig 6
%%%%%%%%%%%%%%%%%%%

 % table3
 
 
%\subsection*{C. Software tools}

The PCB for the radio transmitter was designed using Altium\textsuperscript{\textregistered}, a high-end PCB design software package. The simulation of signal behavior on the PCB was carried out using Keysigth\textsuperscript{\textregistered} EMPro\textsuperscript{\textregistered} and Genesys\textsuperscript{\textregistered}  tools. The purpose of the simulation was both to validate low levels of electromagnetic interference (EMI) between interconnecting tracks and to avoid radiation to other components included in the board before PCB fabrication. \smallskip
 
\subsection*{C. Testbed design} 
 
 The testbed showed in Fig. 7 was integrated to measure the transmission power and frequency values, also to check the operation of the RABE prototype. The hardware devices and software used for the testbed implementation are: Keysigth\textsuperscript{\textregistered} N9030A Signal Analyzer, personal desktop computer, Digilent/Xilinx\textsuperscript{\textregistered}  brand Zedboard test card, RF cables with SMA connector, ethernet cable, RABE prototype, control and programming software for AD9364 IIO Oscilloscope, and IP address monitoring software. \smallskip

 
%%%%%%%%%%%%%%%%%%%
%% proposed Fig 7
%%%%%%%%%%%%%%%%%%%

The steps for running the testbed are as follows:

 \begin{itemize} 
	\item[Step 1.]Download and install the IIO Oscilloscope software on your PC.
	\item[Step 2.]Insert the ABE-R into the Zedboard through the FMC connector.
	\item[Step 3.]Connect the RF cable from the RABE SMA connector to the N9030A.
	\item[Step 4.]Connect the ethernet and USB cable between the PC and the Zedboard.
	\item[Step 5.]Run the IIO Oscilloscope software on your PC.
	\item[Step 6.]Use the IIO Oscilloscope to configure the transmission frequency, bandwidth, attenuation, and other parameters.
	\item[Step 7.]Configure the N9030A to perform a scan on parameters value close to those set in the previous step.
	\item[Step 8.]Save the data to the N9030A.
\end{itemize}
\smallskip	

 \section{RESULTS AND DISCUSSION}
 
 Using the configuration described in section 3.C, the testbed was implemented to test the RABE prototype, obtaining similar results to those from the IC manufacturer's test card AD9364 \cite{AD9364ds}. \smallskip
 
%%%%%%%%%%%%%%%%%%%
%% proposed Fig 8
%%%%%%%%%%%%%%%%%%%


 Two types of experimental measurements were carried out in order to verify the proper operation of the implemented prototype. In both scenarios, the same settings were used for output power, transmission frequency, and bandwidth parameters. As a result, it was noted that RABE output power (Fig. 8 (a)) was reduced by 2 dB compared to FMCOMMS4 (Fig. 8 (b)), which was 7 dB. It is important to mention that according to the AD9364 datasheet, it is able to transmit with a maximum power of 7.5 dBm when matched to 50 Ohms load at 2.4 GHz. \smallskip
  
 
 According to Nyquist's bandwidth equation, the maximum transmission rate equals two times bandwidth (BW) symbols per second. If each symbol can carry M different distinguishable levels, then each pulse carries log M bits of information, which is described by
 
 
  	
\begin{equation} \label{Bitrate}
 		  \textbf{C}= 2 \textrm{BW}\, \log_2(M) \quad \textrm{bps}
\end{equation}

 Since the bandwidth of the AD9364 ranges from 200 KHz to 56 MHz, the data rate capacity for quaternary modulation, M=4, will be between 0.800 and 224 Mbps.
 
\smallskip
 
%%%%%%%%%%%%%%%%%%%
%% proposed Fig 9
%%%%%%%%%%%%%%%%%%%

 
In Fig. 9, the graph of the data collected in the test bench shows the spectrum transmitted by a signal with a carrier frequency of 2.6095 GHz to verify the correct operation of the design. The output power available at the carrier frequency was -20 dBm, as shown. A Gaussian 3 dB resolution bandwidth (RBW) filter was applied into the signal analyzer followed by a Fast Fourier Transform (FFT) with a BW of 411.9 kHz. \smallskip
 
The BBP was set in a QAM modulation scheme at the testbed (as shown in fig. 10). The resulted modulation process was controlled and synchronized by the BBP to the RABE stage via the FMC connector.
 

%%%%%%%%%%%%%%%%%%%
%% proposed Fig 10
%%%%%%%%%%%%%%%%%%%


 \smallskip
 
 
 Total harmonic distortion (THD) percentage was measured as described in \cite{Briceno} and is given by
 
 
 \begin{equation}\label{thd}
    \textrm{THD}_n  =  \sqrt{ \frac{\sum_{n=2}^{\infty}  Po_n   }{ Po_1   }} \times 100 ,
 \end{equation}

where: $Po _n$ is the output power of the n-th harmonic in watts and $Po _1$ is the output power of the fundamental frequency in watts.


\smallskip

According to measurements made in the Lab using the N9030A Signal Analyzer,  for $n=10$ harmonics, as shown in Table 4, it was found that 

\smallskip

\begin{center}
$\textrm{THD}_n $ = 3.81\% .	
\end{center}
\smallskip

The distortion values due to the harmonics generated by the transmitter stage could reach values of up to 3.8\%, reducing the output power of the RF signal as shown in Table 4.

Communication systems with a low THD produce less interference between electronic devices connected to or close to the PCB.\smallskip
 
In fig. 11, the spectrum generated by the RABE is shown, which was taken directly from the RF output by the N9030A analyzer, all this at a frequency centered at 2,300 GHz, in which it is allowed by the Mexican government for experimental satellite links according to the frequency allocation table.\smallskip
 
Although the tests performed on the RABE were in a very small notch of the RF spectrum, the resulting device transmits from 0.070 to 6,000 GHz.\smallskip
 
On the other hand, it is worth mentioning that the development of the PCB was taking into account the CubeSat standard, with the idea of a possible inclusion as a payload in a satellite platform and carrying out transmission tests from space. \smallskip
 
%%%%%%%%%%%%%%%%%%%
%% proposed Fig 11
%%%%%%%%%%%%%%%%%%%

 \section*{CONCLUSIONS}
 
 
 In this paper, the design, construction, verification, and test of a prototype for a reconfigurable radio-transmitter called RABE were presented. The proposed prototype can be used as the communication subsystem in a nanosatellite based on the CubeSat standard. Construction and testing were performed under quality standards in a controlled environment. Results show the correct operation of our card similar to that one commercialized by the IC manufacturer.  \smallskip
 
 The resulting implementation of RABE guarantees the reconfiguration of a nanosatellite communication subsystem. Because of this reconfiguration capacity, it is possible to either have a communication with the terrestrial segment or with other devices orbiting in space, as in the BBP stage different processing stages can be selected (e.g. modulation scheme). Similarly,  the RF stage parameters can be modified (e.g. carrier frequency or transmitter power). \smallskip
 
 In short, this design allows reducing the number of unnecessary components, optimizing the dimensions of the PCB, and having a weight and size adequate to the specifications of the CubeSat standard. \smallskip
 
 
 It should be noted that power values achieved in the RF output stage of the RABE
 are sufficient for the subsequent stages of the nanosatellite communications subsystem, which include filters, power amplifiers, and antennas, among others.  \smallskip
 
 However, in the future, it will be necessary to carry out measurements of compatibility and electromagnetic susceptibility to the RABE prototype, in order to identify anomalies like interferences with other devices that make up the satellite. In addition to this, it is recommended to carry out vibration and thermal vacuum tests to verify the robustness of the design when it comes to being placed in orbit. Also, as future work, it is recommendable that both baseband processing, control, and reconfiguration stage, and the RF stage, could be integrated on a single PCB trying to minimize the size of the communication system, and at the same time optimizing the operating speed.
 
 \smallskip
 
 \section*{Abbreviations}
 
 
 \textbf{CAD:} Computer-Aided Design\\  
 \textbf{PCB:} Printed Circuit Board\\  
 \textbf{GPP:} General Purpose Processor  \\
 \textbf{DSP:} Digital Signal Processor  \\
 \textbf{FPGA:} Field Programmable Gate Array  \\
 \textbf{SDR:} Software-Defined Radio  \\
 \textbf{SoC:} System on a Chip \\
 \textbf{IC:} Integrated Circuit \\
 \textbf{GHz:} Gigahertz \\ 
 \textbf{MHz:} Megahertz \\
 \textbf{COTS:} Commercial-Off-The-Shelf 
 \textbf{RF:} Radio Frequency \\
 \textbf{DDC:} Digital Down Converter\\
 \textbf{VHDL:} Vhsic Hardware Description Language \\
 \textbf{BBP:} BaseBand Processor \\
 \textbf{RABE:} Reconfigurable Analog Back-End \\
 \textbf{SMA:} SubMiniature version A \\
 \textbf{FMC:} FPGA Mezzanine Card \\
 \textbf{SPI:} Serial Communication Protocol \\
 \textbf{DAC:} Digital-Analog Converter \\
 \textbf{I/O:} Input/Output \\
 \textbf{SNR:} Signal-to-Noise Ratio \\ 
 \textbf{LEO:} Low Earth Orbit \\
 \textbf{km:} Kilometer \\
 \textbf{GPO:} General-Purpose Output \\
 \textbf{PLL:} Phase-Locked Loop \\
 \textbf{BS:} Base Stations \\
 \textbf{EMI:} ElectroMagnetic Interference \\
 \textbf{BW:} BandWidth \\
 \textbf{KHz:} Kilohertz \\
 \textbf{RBW:} Resolution BandWidth \\
 \textbf{FFT:} Fast Fourier Transform \\
 \textbf{THD:} Total Harmonic Distortion \\
 


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                                          %%
%% Backmatter begins here                   %%
%%                                          %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\clearpage
\begin{backmatter}

\section*{Competing interests}
  The authors declare that they have no competing interests.

\section*{Author's contributions}
    All authors have read and approved the manuscript. JLAF has completed the design and manufacture of the prototype, with the accompaniment of JAAA and under the supervision of JFT, JSR, MHC and LSE. JLAF, JFT, RSA, LSE, MHC and JSR made the translation for the present work. JLAF, JFT and JSR participated in the design of this paper.

\section*{Acknowledgements}
\justify
The authors would like to thank the Mexican National Council for Science and Technology (CONACYT) and the Mexican Space Agency (AEM) for supporting project 292793 through the AEM-CONACYT Sectorial Fund for Research and Development in Space Activities, from which this article emerged as a result. Similarly, the authors would like to thank the Center for Research, Innovation and Development in Telecommunications (CIDTE) of the Autonomous University of Zacatecas (UAZ) for the support provided for the use of the necessary infrastructure for the development of this project.



 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                  The Bibliography                       %%
%%                                                         %%
%%  Bmc_mathpys.bst  will be used to                       %%
%%  create a .BBL file for submission.                     %%
%%  After submission of the .TEX file,                     %%
%%  you will be prompted to submit your .BBL file.         %%
%%                                                         %%
%%                                                         %%
%%  Note that the displayed Bibliography will not          %%
%%  necessarily be rendered by Latex exactly as specified  %%
%%  in the online Instructions for Authors.                %%
%%                                                         %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% if your bibliography is in bibtex format, use those commands:
\bibliographystyle{bmc-mathphys} % Style BST file (bmc-mathphys, vancouver, spbasic).

\justify
\bibliography{bmc_article}      % Bibliography file (usually '*.bib' )
% for author-year bibliography (bmc-mathphys or spbasic)
% a) write to bib file (bmc-mathphys only)
% @settings{label, options="nameyear"}
% b) uncomment next line
%\nocite{label}

% or include bibliography directly:
% \begin{thebibliography}
% \bibitem{b1}
% \end{thebibliography}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                               %%
%% Figures                       %%
%%                               %%
%% NB: this is for captions and  %%
%% Titles. All graphics must be  %%
%% submitted separately and NOT  %%
%% included in the Tex document  %%
%%                               %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%%
%% Do not use \listoffigures as most will included as separate files
\clearpage
\section*{Figures}

	\begin{figure}[h!]
	%	\includegraphics[scale=0.3]{/fig1}
		\label{fig1}
		\caption{\csentence{ Communication system model.}
			A block sequence about the communication system model and its architecture.}
	\end{figure}

	\begin{figure}[h!]
	%	\includegraphics[scale=0.3]{/fig2}
		\label{fig2}
		\caption{\csentence{ Radio Frequency model.}
			RF PCB scheme and AD9364 architecture.}	
	\end{figure} 

	\begin{figure}[h!]
	%	\includegraphics[scale=0.3]{/fig3}
		\label{fig3}
		\caption{\csentence {Schematic design of the RABE.}
			In this figure shown how is get AD9364 connected with FMC connector to the FPGA and RF Output to the power amplifier stage (not shown at this work).}	
	\end{figure} 

	\begin{figure}[h!]
 	%	\includegraphics[scale=0.3]{/fig4}
 		\label{fig4}
 		\caption{\csentence{Block diagram of the IC AD9364.}
 			In this figure, the manufacturer of the AD9364 describes how it is connected internally.} 
 	\end{figure}
  
 	\begin{figure}[h!]
	%	\includegraphics[scale=0.4]{/fig5}
		\label{fig5}
		\caption{\csentence{RF coupling.}
			The RF coupling stage, designed to avoid interferences for 2-3 GHz.}
	\end{figure}

 	\begin{figure}[h!]
	%	\includegraphics[scale=0.3]{/fig6}
		\label{fig6}
		\caption{\csentence{ RABE Printed Circuit Board.}
			3D model of the RABE (top and bottom layers).	}
	\end{figure}

	\begin{figure}[h!]
	%	\includegraphics[scale=0.4]{/fig7}
		\label{fig7}
		\caption{\csentence{Testbed block diagram.}
			Configuration for the connection of the test bed for the prototype.}	
	\end{figure}

	\begin{figure}[h!]
		\begin{subfigure}[b]{0.47\textwidth}
		%	\includegraphics[width=\textwidth, height=4.5 cm]{/fig8a}
			\caption{Testbed implemented for ABE-R test.}
			\label{fig8a}
		\end{subfigure}
		\hfill
		\begin{subfigure}[b]{0.45\textwidth}
		%	\includegraphics [width=\textwidth]{/fig8b}
			\caption{Testbed implemented for FMCOMMS4 test.}
			\label{fig8b}
		\end{subfigure}
		\caption{Measurements from (a) RABE and FPGA and (b) FMCOMMS4 and FPGA (only COTS) card.}
	\end{figure}

 	\begin{figure}[h!]
	%	\includegraphics[scale=0.3]{/fig9}
		\label{fig9}
		\caption{\csentence{Spectrum of signal transmitted at 2.6095 GHz.}
			Further processing of the data shows the spectrum of the carrier signal transmitted at 2.6095 GHz}
	\end{figure}

 	\begin{figure}[h!]
	%	\includegraphics[width=\textwidth]{/fig10}
		\label{fig10}
		\caption{\csentence{Signal analyzer, RABE and Zedboard on QPSK.}
			The RABE prototype transmitting with 4-tone QPSK modulation, with 1MHz frequency separations.}
	\end{figure}

 	\begin{figure}[h!]
	%	\includegraphics[scale=0.4]{/fig11}
		\label{fig11}
		\caption{\csentence{Spectrum radiated by RABE at 2.300 GHz.}
			Image obtained from the signal analyzer with the prototype transmitting a single tone with a frequency of 2.300 GHz.}
	\end{figure}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                               %%
%% Tables                        %%
%%                               %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%% Use of \listoftables is discouraged.
%%

\clearpage

\section*{Tables}

%%% table 1
\begin{table}[h!]
	\caption{General requirements of the ABE-R.}
	\begin{tabular}{|l|c|c|}
		\hline
		\hline
		Request & Value &  Units \\
		\hline
		\hline
		
		Power Suply Vcc & 5 & volts \\
		PCB size & 95x95 & mm \\
		Working frequency & 2.2 - 2.3 & GHz \\
		Input connector & FMC ASP-134604-01 &  \\
		RF connector & female SMA  & \\
		Reference CK & Integrated & \\
		IC & AD9364 & \\
		PCB & 6 layers & \\
		\hline
		\hline
	\end{tabular}%
	
\end{table}
% Table 2
\begin{table}[h!]
	\caption{Functions of the AD9364 registers.}
\begin{tabular}{|l|ccc|}
	\hline
	\hline
	Modes & Initial &       & Final \\
	\hline
	\hline
	
	Initialization & 0x000 & …     & 0x017 \\
	Setting & 0x018 & …     & 0x05F \\
	Transmitter Configuration & 0x060 & …     & 0x0D7 \\
	Receiver Configuration & 0x0F0 & …     & 0x1FC \\
	Rx Analog Registers & 0x230 & …     & 0x3F6 \\
	\hline
	\hline
\end{tabular}%

\end{table}
% table 3
\begin{table}[h!]
	\caption{RABE PCB layers.}
	\begin{tabular}{|c|c|c|c|c|}
		\hline
		\hline
		Layer & Type & Material & thickness & thickness \\
		      &      &          &  (mm)     & (mil) \\
		\hline
		\hline
		      & Surface 	     & Air	    &           &      \\
		  Top & Conductor plane	 &  Copper  & 0.0514    & 2.025\\
  		      & Dielectric 		 & 	FR-4	& 0.2032    & 8    \\
  	   L1\_PWR& Conductor plane  & Copper	& 0.0342    & 1.35 \\
  		      & Dielectric		 & BT-epoxy	& 0.1524    & 6    \\
  	  L2\_SIG & Conductor plane  & Copper	& 0.0342    & 1.35 \\
  		      & Dielectric		 & 	FR-4	& 0.2032    & 8    \\  		      
  	L3\_SIG   & Conductor plane	 & Copper	& 0.0342    & 1.35 \\  		      
  		      & Dielectric		 &  BT-epoxy& 0.1524    & 6    \\  		      
  	L4\_PWR   & Conductor plane	 & Copper	& 0.0342    & 1.35 \\  		      
  		      & Dielectric		 & 	FR-4	& 0.2032    & 8    \\  		      
  	Bottom    & Conductor plane  & Copper	& 0.0514    & 2.025 \\  		      
  		      & Surface		 	 & 	Air		&           &  \\  		      
		\hline
		\hline
	\end{tabular}
\end{table}
%Table 4
\begin{table}[h!]
	\caption{Total Harmonic Distortion.}
	\begin{tabular}{@{}cccc@{}}
		\hline
		\hline
		\multicolumn{1}{l}{Harmonic} & \multicolumn{1}{l}{Frequency } & \multicolumn{1}{l}{Amplitude } &
		\multicolumn{1}{l}{Power }
		  \\ 
		\multicolumn{1}{l}{} & \multicolumn{1}{l}{( GHz )} & \multicolumn{1}{l}{( dBm )} &
		\multicolumn{1}{l}{( watts )} 
		  \\ 
		\hline
		\hline
		1      & 2.3  & -12.01 & $6.30E^{-5}$        \\
		2      & 4.6  & -40.4  & $9.12E^{-8}$       \\
		3      & 6.9  & -72.25 & $5.96E^{-11}$       \\
		4  	   & 9.2  & -81.3  & $7.41E^{-12}$       \\
		5      & 11.5 & -80.9  & $8.13E^{-12}$       \\
		6      & 13.8 & -79.9  & $1.02E^{-11}$       \\
		7      & 16.1 & -79.7  & $1.07E^{-11}$       \\
		8      & 18.4 & -76.9  & $2.04E^{-11}$       \\
		9      & 20.7 & -75.11 & $3.08E^{-11}$       \\
		10     & 23   & -74.32 & $3.70E^{-11}$       \\ 
		\hline
		\hline
	\end{tabular}
\end{table}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%                               %%
%% Additional Files              %%
%%                               %%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%



\end{backmatter}
\end{document}
