Implementation Overview: S5066 Edition 2 Prototype

1 / 21
About This Presentation
Title:

Implementation Overview: S5066 Edition 2 Prototype

Description:

abstract object-oriented interface applicable to any modem ... USRP Motherboard. Four 64 MS/s 12-bit A/D Converters. Four 128 MS/s 14-bit D/A Converters ... –

Number of Views:526
Avg rating:3.0/5.0
Slides: 22
Provided by: Sel881
Category:

less

Transcript and Presenter's Notes

Title: Implementation Overview: S5066 Edition 2 Prototype


1
Implementation OverviewS5066 Edition 2
Prototype
  • prepared by
  • Donald G. Kallgren, Dr. Michael Street and
    Maarten Gerbrands
  • presented to
  • the High Frequency Industry Association
  • 19 July 2007
  • Rome, Italy

2
Agenda
  • Implementation Overview
  • hardware environment
  • software environment
  • Software Overview
  • code structure and size
  • availability
  • capability/PICs
  • Relation to other NC3A efforts
  • SDR
  • code repository
  • VHF / UHF Waveform Development
  • Summary

3
CORBA-ized S5066 Implementation
  • modified earlier hfstack design and
    implementation
  • separate SW modules for hfstack and route56
    synchronous serial interface
  • synchronous serial interface further abstracted
    as a CORBA resource in accordance with SCA design
    principles
  • CORBA interface specification
  • abstract object-oriented interface applicable to
    any modem
  • remains constant as modem implementations change
  • towards an SDR modem implementation
  • initial designs encapsulate route56 driver
    interface to external modem via
    synchronous-serial port
  • ultimately replaced by SDR modem
  • operates as independent
  • HF modem server, registered with CORBA name
    server
  • HF statck, which checks CORBA registry for
    available HF modem servers

4
Hardware Packaging as multi-band wireless router
  • MICROSPACE MPCX47 platform

16 cm
6.6 cm
30 cm
  • Back View

Synch/Serial Interface to external HF Modem
Antenna Interfaces for embedded WiFi, GSM/GPRS,
GPS
5
Synchronous Serial Interface Hardware
  • Currently limited to modified Route56 driver
    for Z16C32 chipset
  • Driver Modifications
  • implement BiSYNC protocol w/ 0x90EB sync word
  • hardware-assisted sync-word search
  • Low-Profile PCI form factor
  • Sealevel Systems ACB-Ultra.LPCI
  • PC-104 form-factor
  • Sealevel Systems ACB-104-Ultra

6
Capabilities Implementation of key (but NOT
all) S5066E2 features
7
Software Overview
  • Total Redesign of earlier prototype-SW
    development for S5066E2
  • Linux 2.6 kernel, RedHat Fedora Core 6
  • all POSIX / C STD implementation
  • eliminates earlier prototypes dependence on
    KDE/Qt libraries
  • Modularized/Object-Oriented Code

8
Source-Code Availability
  • software repository established
  • https//s5066.nc3a.nato.int/S5066loginreq/software
    /
  • accessible to NATO/PfP/CFBLNet nations with
    account / password, apply at https//s5066.nc3a.
    nato.int/authrequest.php
  • SRPMs available
  • hfstack, choose one of
  • hfstack-0.3.10-00.src.rpm 470K
  • hfstack-sdr-0.3.10-00.src.rpm 470K
  • serial-port driver
  • kernel-module-route56-0.1.3-9.src.rpm 30K
  • libnc3a-0.5.01-00.src.rpm 540K
  • sisetherclient-0.2.10-00.src.rpm 319K
  • other (optional utilities)
  • sisnetsim-0.4.00-0.src.rpm 313K
  • sispipe-0.1.19-15.src.rpm 304K
  • Licensing
  • GPL / LGPL for inherited Linux code
  • BSD for NC3A-generated code
  • additions/contributions/corrections to the code
    in the NC3A repository are not required (but
    would be appreciated! by all!)

9
Source-Code Browser
  • Browse-able Code
  • generated directly from the code using Doxygen
    tool
  • code-changes directly reflected in browser files
    whenever the SW is re-built
  • various reports available
  • viewable source code
  • inheritance and dependency diagrams
  • Class-, Function-, variable, lists
  • Class-overview w/ embeddable source code and
    called-by/call-lists
  • browse-able code documentation at
    ltproject_dirgt/docs/html/index.html
  • documentation outputs controllable by modifying
    file ltproject_dirgt/docs/doxygen/doxygen.conf

10
Class Reference (1) e.g., DPDU Class Inheritance
and code structure
hyper-linked inheritance diagrams
hyper-linked file reference
expanded/interpreted code structure and embedded
programmer comments
documentation page includes embedded source code
11
Relationship to other NC3A/NATO Developments
  • support to SDR project
  • GPP-based code of NATO STANAGs
  • development roadmap for HF / VHF / UHF SDR
    software
  • exploration of low-cost base waveform
    implementations
  • explore mechanics / legalisms of a NATO sponsored
    code repository

12
NATO aims for SDR
  • as a development platform
  • to interoperate with legacy systems
  • to share waveforms and enable interoperability

13
SDR as a development platform
  • New waveform for land tactical domain
  • A new, efficient, sharable narrow band is being
    developed
  • Current V/UHF waveforms are not NNEC ready
  • Using work conducted by several nations
  • SDR provides a fast, flexible development
    platform
  • National work on layers 1, 2 and 4
  • All developed in software
  • Low-cost NC3A SDR platform to host national work
  • Fill in gaps to produce a working waveform
  • Resulting waveform / software can be shared
  • With NATO / PfP
  • Following STANAG 5066 model for collaborative
    development
  • Improved dissemination and implementation

14
NC3A development
  • NC3A has established an SDR development system
  • Host system for multi-national effort
  • National developments offered to NATO
  • NC3B request contributions to w/f development
  • From active programmes to develop waveform
    components which can be shared
  • NC3A hosting first meeting in early July for
    nations
  • Coordination of SDR development
  • Multiple nations involved
  • RTO provides a useful forum for technical
    cooperation
  • NC3A support to SDR UG provides coordination

15
SDR to interoperate with legacy
  • SDR is the choice for many national procurements
  • Current and future
  • Software definitions of legacy waveforms
  • will provide backward compatibility
  • can be shared easily
  • ACT funded EPOW at NC3A
  • Coordination with SDRUG via NC3A support to NC3B

16
NC3A and existing radio standards
  • SCA based version of STANAG 5066
  • Based on SCA standard for SDR
  • Easily ported to SCA compliant platforms
  • (and most platforms are SCA based)
  • Tested on-air during STANAG 5066 trials at
    Combined Endeavor
  • Software has no IPR or security restrictions
  • RF data acquisition during Combined Endeavor
  • Software modules developed for RF receive
  • Real RF signals available in the lab for
    development and test
  • Developing SCA-based versions of
  • US Mil-Std 188-141A for 2nd generation ALE
  • STANAG 4539 in conjunction with CRC
  • STANAG 4205c UHF
  • (RTO developing SCA-based STANAG 4285)
  • SCA Software Communications Architecture

17
NC3A and software / waveform sharing
  • Waveform / software definition sharing
  • Benefits from a standard format
  • Eases porting
  • SCA the likely candidate
  • But SCA does not address all aspects
  • Security still needs much work
  • Technical work needed to address multi-national
    issues
  • Waveform sharing mechanisms
  • Address technical aspects of NC3B business model
  • Lessons learned from NC3A SDR testbed and
    multi-national waveform development work
  • NC3A updates to SDRUG

18
Activities for RTO
  • Multi-national technical work needed on SCA
  • Address issues arising for non-US work e.g.
    security
  • Single-nation issues fixed e.g. JTRS
  • RTO planned activities will identify (and solve
    ?) issues
  • Technicalities of software sharing
  • Multi-national SDR collaboration via RTO can
    provide benefits for operational sharing /
    interoperability
  • Building a waveform library
  • NC3A work on legacy standards in SCA form
  • RTO plans will add to the library content

19
SDR Testbed
  • Low-cost / low-profile approach to testbed
  • GNU-Radio GPP DSP implementations
  • http//gnuradio.org/trac
  • Universal Software Radio Peripheral (USRP)
  • http//www.ettus.com/downloads/ettus_broch_trifold
    _v3b.pdf
  • USRP Motherboard
  • Four 64 MS/s 12-bit A/D Converters
  • Four 128 MS/s 14-bit D/A Converters
  • Four programmable digital downconverters
  • Two programmable digital upconverters
  • High-speed USB 2.0 interface (480 Mb/s)
  • Signal processing capability to 16 MHz wide

20
SDR Issues under consideration
  • relevance of GNU-Radio to SCA and vice versa
  • GNU-radio based on
  • Python scripts as specification of the
  • does implementation of a Base Waveform
    specification (i.e., a functional exemplar of a
    waveform) for SDR even require a standard
  • may be non-real-time
  • must be open source
  • presumed to provide unambiguous specification,
    design, and guidance to Target Waveform
    implementers
  • its Target Waveforms that require SDR-code
    portability!

21
Summary
  • NC3A developed S5055E2 prototype SW code is
    available for download, review, comment, use
  • software repository established
  • https//s5066.nc3a.nato.int/S5066loginreq/software
    /
  • accessible to NATO/PfP/CFBLNet nations with
    account / password, apply at https//s5066.nc3a.
    nato.int/authrequest.php
  • Initial entires in NC3A SDR software repository
  • provides initial support/exploration-of-use for
    SDR SCA
  • to be expanded to support NATO efforts in
    developing a VHF/UHF STANAG
Write a Comment
User Comments (0)
About PowerShow.com