PLEORA TECHNOLOGIES INC.
iPORT™ NTx-W Embedded Video Interface
User Guide
Version 1.0.1
Installing, Uninstalling, and Starting the Software Applications
a
Copyright © 2016 Pleora Technologies Inc.
These products are not intended for use in life support appliances, devices, or systems where malfunction of these products can
reasonably be expected to result in personal injury. Pleora Technologies Inc. (Pleora) customers using or selling these products for
use in such applications do so at their own risk and agree to indemnify Pleora for any damages resulting from such improper use or
sale.
Trademarks
PureGEV, eBUS, iPORT, vDisplay, AutoGEV, AutoGen, and all product logos are trademarks of Pleora Technologies. Third party
copyrights and trademarks are the property of their respective owners.
Notice of Rights
All information provided in this manual is believed to be accurate and reliable. No responsibility is assumed by Pleora for its use.
Pleora reserves the right to make changes to this information without notice. Redistribution of this manual in whole or in part, by
any means, is prohibited without obtaining prior permission from Pleora.
Document Number
EX001-024-0001, Version 4.0, 6/10/16
Table of Contents
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Start Streaming Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Further Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
About the NTx-W Embedded Video Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Introducing the NTx-W Embedded Video Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
NTx-W Embedded Video Interface Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Feature Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Selected GenICam Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Connections and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Connector Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Mounting the 12-Pin Circular Connector to an Enclosure Backplate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
12-Pin Circular Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Power Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
20-Pin Connector on Wireless Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
12-Pin Circular Connector Mate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
100-Pin User Circuitry Connector Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
NTx-Mini Adapter Board Pinout Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Status LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Bulk Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Bulk Interfaces and Supported Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
UART Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
GenICam Interface for Serial Communication Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Pixel Bus Definitions and Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Pixel Bus Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Mono/RGB/Bayer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
YUV411_8_UYYVYY: 1 Tap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
YUV411_8_UYYVYY: 2 Tap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
YUV422_8_UYVY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
YUV8_UYV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Pixel Bus Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Pixel Bus Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Case 1: FVAL and LVAL are Level-Sensitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Case 2: FVAL and LVAL are Edge-Sensitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Case 3: FVAL is Edge-Sensitive and LVAL is Level-Sensitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Timing Values for All Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
i
Connecting to and Configuring the NTx-W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuring Your Computer’s Wireless Adapter for use with the NTx-W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring Wireless Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring the NTx-W for Wireless Connectivity using an Off-the-Shelf Router . . . . . . . . . . . . . . . . . . . . . . 50
Configuring the NTx-W Access Point Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Connecting over Wireless Ethernet and Confirming Image Streaming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Configuring the Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Providing the NTx-W with an IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Configuring an Automatic/Persistent IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Optimizing SDK Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Improving Stream Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Preventing Connection Loss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Encouraging Packet Resends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Increasing Time Period to Transfer Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Ensuring Adequate Storage for Multiple Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Viewing Wireless Link Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Stream Warning, Device Dropped Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Restoring Default Wireless Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Configuring How Images are Acquired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Modes Standard on Most GigE Vision-Compliant Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Recording and Readout Modes, Available on Pleora Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Understanding When Images are Removed from the Onboard Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
ContinuousRecording Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
ContinuousReadout Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
MultiFrameRecording Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
SingleFrameRecording Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
SingleFrameReadout Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Calculating How Many Images Can be Stored in Onboard Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Updating Firmware Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Reference: Supported Country Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
List of Valid Country Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Reference: Wireless Range Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Test #1: AccessPoint Mode, Distance 80 Feet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Test #2: StationForward Mode, Distance 80 Feet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Test #4: AccessPoint Mode, Distance 40 Feet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Test #5: AccessPoint Mode, Distance 0 Feet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Test #6: StationForward Mode, Distance 0 Feet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
ii
iPORT NTx-W Embedded Video Interface User Guide
Chapter 1
About this Guide
This chapter describes the purpose and scope of this guide, and provides a list of complementary guides.
The following topics are covered in this chapter:
• “About this Guide” on page 2
• “Start Streaming Video” on page 2
• “Related Documents” on page 2
• “Further Reading” on page 3
About this Guide
1
About this Guide
This guide provides you with the information you need to use the NTx-W Embedded Video Interface.
In this guide you can find a reference of GenICam features, instructions for establishing a connection
with the embedded video interface, and instructions for some of the key features.
The last section of this guide provides Technical Support contact information for Pleora Technologies.
Start Streaming Video
If you want to quickly start streaming video, you can jump to:
• “Configuring the NTx-W for Wireless Connectivity using an Off-the-Shelf Router” on page 50.
• “Connecting over Wireless Ethernet and Confirming Image Streaming” on page 52.
Related Documents
The NTx-W Embedded Video Interface User Guide is complemented by the following guides:
• eBUS Player Quick Start Guide
• eBUS Player User Guide
• eBUS SDK C++ API SDK Help File
• eBUS SDK .NET API Help File
2
iPORT NTx-W Embedded Video Interface User Guide
Further Reading
Although not required in order to successfully use the NTx-W Embedded Video Interface, you can find
details about industry-related standards and naming conventions in the following documents:
• GigE Vision Standard, version 2.0 available from the Automated Imaging Association (AIA) at
www.visiononline.org.
• GenICam Standard Features Naming Convention available from the European Machine Vision
Association (EMVA) at www.emva.org.
About this Guide
3
Chapter 2
About the NTx-W Embedded Video Interface
This chapter provides high-level information about the NTx-W Embedded Video Interface, including
descriptions of selected GenICam features.
The following topics are covered in this chapter:
• “Introducing the NTx-W Embedded Video Interface” on page 6
• “NTx-W Embedded Video Interface Models” on page 6
• “Feature Set” on page 8
• “Selected GenICam Features” on page 9
About the NTx-W Embedded Video Interface
5
Introducing the NTx-W Embedded Video Interface
Pleora’s iPORT™ NTx-W Embedded Video Interface provides system manufacturers and integrators with
a straightforward way to integrate GigE Vision 2.0® wireless video connectivity into cameras, X-ray
panels, and other imaging systems where cabling creates system design or usability challenges.
Using GigE Vision as its application-layer protocol, the embedded hardware delivers uncompressed video
with high sustained throughput up to 150 Mbps and low, consistent latency over an industry-standard
IEEE 802.11n wireless link. By eliminating the need for a desktop PC with an available peripheral card
slot, designers can reduce system size, cost, and power consumption by using computing platforms with
smaller form factors, such as tablets, laptops, and single-board computers.
The NTx-W ensures reliable image transport in controlled environments, with UDP video transport, a
flow control mechanism that adapts video transport to link speed, and packet resend capabilities. The
device supports 3x3 MIMO and Dual Band for improved range and noise immunity, standard encryption
modes for data security, and access point and station modes to allow flexible system configurations.
The ultra-compact hardware is easily embedded into small-body cameras, flat-panel X-ray detectors, and
imaging systems. To help speed development time and reduce costs, designers can choose from a selection
of antennae pre-certified for use in a wide range of geographies. The product is fully supported by Pleora’s
feature-rich eBUS™ SDK application tool kit and drivers. This software suite allows designers to rapidly
prototype and deploy production-ready software supporting video transmission over GigE, 10 GigE,
USB 3.0, and wireless, including future IEEE 802.11ac designs, using the same API.
The NTx-W Embedded Video Interface interacts seamlessly with Pleora’s other products in networked
or point-to-point digital video systems. It complies with the GigE Vision 2.0® and GenICam™ standards,
ensuring interoperability in a multi-vendor environment. The NTx-W is supported by a development kit
to help speed time-to-market by enabling the rapid design of prototypes and proof-of-concept
demonstrations.
NTx-W Embedded Video Interface Models
The iPORT NTx-W Embedded Video Interface is available in several models and is equipped with the
parts listed in the following table.
Table 2: iPORT NTx-W Embedded Video Interface Models
6
Order code
Model
Quantity
900-7001
iPORT NTx-W Embedded Video Interface
NTx-W OEM board set
1
GPIO board with unsoldered 12-pin circular connector
1
Flat flex cable
1
iPORT NTx-W Embedded Video Interface User Guide
Order code
Model
900-7002
iPORT NTx-W Development Kit
Quantity
NTx-W OEM board set
1
GPIO board with soldered 12-pin circular connector
1
Flat flex cables
4
NTx-Mini adapter board
1
Prober board
1
Dual-band antennae
3
Power supply
1
Pleora eBUS SDK, provided on USB stick (includes eBUS Player sample
application)
1
Order code
Model
Quantity
900-7003
iPORT NTx-W Development Kit with Router
NTx-W OEM board set
1
GPIO board with soldered 12-pin circular connector
1
Flat flex cables
4
NTx-Mini adapter board
1
Prober board
1
Dual-band antennae
3
Dual-band wireless router
1
Ethernet cable
1
Power supply
1
Pleora eBUS SDK, provided on USB stick (includes eBUS Player sample
application)
1
About the NTx-W Embedded Video Interface
7
Feature Set
Hardware
Frame Grabber
User circuitry interface
100-pin Samtec connector:
LSHM-150- 04.0-L-DV-A-N-TR
External interface
12-pin Hirose connector:
HR10A-10R- 12PB(71)
GigE PHY
Marvell 88E1510
FPGA
Altera Cyclone V
Image buffer
120 MByte 16-bit wide DDR3
Total image size should be smaller than
(120MB-32k)
Wireless interface
IEEE 802.11n
Antenna interface
U.FL connector
Wireless certifications
Certified for use in over 80 countries
(with compatible PIFA antennae)
Number of channels
1
Scan modes
Area Scan (Progressive) and Line
Scan
Pixel depth (bits)
8, 10, 12, 14, 16, 24, and 32
Pixel clock
Minimum: 20 MHz
Maximum: 120 MHz
Taps per data
channel
Up to 2
Image width (pixels)
Minimum: 8
Default: 640
Maximum: 16,376
Increment: 8
Image height
(pixels)
Inputs/Outputs on User Circuitry Interface
Video input
2.5V LVTTL/LVCMOS
GPIO inputs
2.5 V LVTTL/LVCMOS (for use with a
future firmware release)
GPIO outputs
2.5 V LVTTL/LVCMOS (for use with a
future firmware release)
UART
3 x 2.5 V LVTTL/LVCMOS
GPIO outputs
UART
8
4 connections routed to User Circuitry
Interface (for use with a future firmware
release)
3 connections routed to User Circuitry
Interface (for use with a future firmware
release)
3 connections routed to User Circuitry
Interface
Default: 480
Maximum: 16,383
Increment: 1
Windowing/region
of interest
Yes
Tap reconstruction
Interleaved only
Characteristics
Size (LxWxD)
37.0 mm x 37.0 mm x 25 mm
(approximate, excluding GPIO
board)
Weight
27.5 g (without antennae)
Operating
temperature
0°C to 55°C
Storage
temperature
-40°C to 85°C
Power supply
4.8 to 16 Volts nominal
Power consumption
6.7 W
GPIO on 12-Pin Circular Connector
GPIO inputs
Minimum: 1
iPORT NTx-W Embedded Video Interface User Guide
Selected GenICam Features
In addition to the mandatory GenICam features for any compliant GigE Vision device, the NTx-W
Embedded Video Interface provides a number of additional GenICam features.
Selected general GenICam features are listed in the first table below. Subsequent tables show the NTx-W
GenICam wireless features.
The Persistence column (in all tables) provides the persistence type available for each feature. There are
three different types of persistence: Streamable (S), UserSet (US) and PM (Persistent Memory):
• Streamable parameters can be saved on the computer using the .pvcfg file. The parameters are saved
using eBUS Player. The file can be applied after re-connecting to the device using eBUS Player.
When the .pvcfg file is applied, the saved parameters are written to the device.
• UserSet parameters are persistent and can be saved in the device Flash memory. Parameters are saved
to the UserSet specified by UserSetSelector. You can specify a UserSet to load by default when the
device starts.
For more detailed information about saving device settings, see the eBUS Player Quick Start Guide
available on the Pleora Support Center at http://www.pleora.com/support-center/documentationdownloads.
• Persistent Memory parameters are saved individually and automatically on the unit; they are not
part of the UserSets. These include the Persistent IP address or the WifiPrimaryChannelNext
features.
To view the description of a setting in eBUS Player, click the feature. A brief description appears at the
bottom of the eBUS Player window.
Table 1: Standard GenICam Features
Feature
Description
Persistence
DeviceReset
Resets the NTx-W to its default power-up state;
applies the settings saved as part of the user set
defined in UserSetDefault.
N/A
DeviceVersion
Version of the NTx-W firmware.
N/A
Width
Width of the image.
Userset, streamable
Height
Height of the image.
Userset, streamable
OffsetX
Horizontal image offset.
Userset, streamable
OffsetY
Vertical image offset.
Userset, streamable
PixelFormat
Format of the pixels provided by the device.
Userset, streamable
DeviceControl
ImageFormatControl
About the NTx-W Embedded Video Interface
9
Table 2: Acquisition-related Features, Including Features for Image Resend
Feature
Description
Persistence
Image acquisition mode of the NTx-W:
Userset, streamable
AcquisitionControl
AcquisitionMode
• Continuous
• SingleFrame
• MultiFrame
• ContinuousRecording
• ContinuousReadout
• SingleFrameRecording
• SingleFrameReadout
• MultiFrameRecording
Note: For information about how to configure
image acquisition, see “Configuring How Images
are Acquired” on page 60.
Table 3: UserSet Features
Feature
Description
Persistence
UserSetSelector
Select which UserSet to load/save.
Streamable
UserSetLoad[UserSetSelector]
Loads GenICam settings from the selected
UserSet.
N/A
UserSetSave[UserSetSelector]
Saves current GenICam settings to the selected
UserSet.
N/A
UserSetDefault
Specifies which UserSet to load by default when
the device starts.
Persistent memory
UserSetControl
Table 4: GenICam Features for Bulk0, Bulk1, and Bulk2
Feature
Description
Persistence
Selects which Bulk interface to configure:
Streamable
IPEngine\PortCommunication
BulkSelector
• Bulk0 (Default)
• Bulk1
• Bulk2
BulkMode[BulkSelector]
Selects the serial communication mode to use.
Userset, streamable
• UART
10
iPORT NTx-W Embedded Video Interface User Guide
Table 5: GenICam Features for High Watermark and Acquisition Pipe
Feature
Description
Persistence
iPORTEngine\Grabber\TriggerConfiguration
AcquisitionPipeBlockCount
Controls the number of frames that can be in the
acquisition pipe; relevant for AcquisitionMode
Continuous or MultiFrame. Settings are:
Userset, streamable
• One
• Two (default)
• LimitedByOnBoardMemory
Table 6: Wireless GenICam Features
Feature
Description
Persistence
WirelessControl
WifiDriverVersion
Reports the current version of the wireless
driver. Version includes an “-FS” suffix if the
failsafe load is running.
N/A
WifiPrimaryChannelCurrent
Reports the current wireless channel in use after
the last power cycle or device reset.
N/A
If the value displayed is not the same as
WifiPrimaryChannelNext when
WifiBridgeModeCurrent=StationForwarding, it
means that channel selection is automatic and
dictated by the access point to which the NTx-W
connects.
Alternatively, if the NTx-W is in Access Point
mode, you can set this value to the desired
channel for the wireless network.
WifiPrimaryChannelNext
Controls the next wireless channel after the next
power cycle or device reset.
Persistent memory
If the value displayed is not the same as
WifiPrimaryChannelNext when
WifiBridgeModeCurrent=StationForwarding, it
means that channel selection is automatic and
dictated by the access point to which the NTx-W
connects.
Alternatively, if the NTx-W is in Access Point
mode, you can set this value to the desired
channel for the wireless network.
Important: We recommend that you select a
channel that is in the 5.2 GHz range to avoid a
crowded signal. Channels 40, 42, and 44 are in
the 5.2 GHz range, for example.
About the NTx-W Embedded Video Interface
11
Table 6: Wireless GenICam Features (Continued)
Feature
WifiChannelWidthModeCurrent
Description
Reports the current wireless channel width (in
MHz) of the NTx-W when WifiBridgeModeNext is
set to StationForwarding.
Persistence
N/A
Reports the current wireless channel width (in
MHz) supplied by the NTx-W when
WifiBridgeModeNext is set to AccessPoint.
Options include:
• HT20
• HT40
WifiChannelWidthModeNext
Controls the next channel width (in MHz)
requested by the NTx-W after the next power
cycle or device reset.
Persistent memory
Options include:
• HT20
• HT40
WifiAccessPointSSIDCurrent
Reports the current SSID of the wireless network
to join after the last power cycle or device reset
when WifiBridgeModeNext StationForwarding
N/A
Also reports the SSID of the NTx-W when
WifiBridgeModeNext AccessPoint.
WifiAccessPointSSIDNext
Controls the next SSID of the wireless network to
join after the next power cycle or device reset
when WifiBridgeModeNext StationForwarding.
Persistent memory
Controls the next SSID of the NTx-W when
WifiBridgeModeNext AccessPoint.
WifiBridgeModeCurrent
Reports the current mode of the bridge after the
last power cycle or device reset.
N/A
Options include:
• AccessPoint
• StationWDS
• StationForwarding
WifiBridgeModeNext
Controls the next mode of the bridge after the
next power cycle or device reset.
Persistent memory
Options include:
• AccessPoint
• StationWDS
• StationForwarding
12
iPORT NTx-W Embedded Video Interface User Guide
Table 6: Wireless GenICam Features (Continued)
Feature
WifiSecurityModeCurrent
Description
Reports the current security mode for the
wireless link after the last power cycle or device
reset.
Persistence
N/A
Options include:
• WPA2
• None
WifiSecurityModeNext
Controls the next security mode for the wireless
link after the next power cycle or device reset.
Persistent memory
Options include:
• WPA2
• None
WifiPreSharedKey
Controls the next pre-shared key for the selected
security mode after the next power cycle or
device reset. The key should be between 8 to 64
characters in length. Note: Not available when
WifiSecurityModeNext None; the key is not
displayed in the graphical user interface.
Persistent memory
WifiSupportedCypherCurrent
Reports the current Wi-Fi encryption scheme
used by the wireless interface after the last
power cycle or device reset.
N/A
Options include:
• CCMP
• None
WifiLinkQualityThreshold
Specifies the link quality threshold below which
to trigger an LED to turn off. Threshold is defined
by WifiLinkQualityStatus.
Userset, streamable
WifiCountryCodeCurrent
Reports the current country code after the last
power cycle or device reset.
N/A
WifiCountryCodeNext
Controls the next country code. Setting a valid
country code will start a reboot of the device.
Persistent memory
WifiProtocolCurrent
Reports the current Wi-Fi protocol after the last
power cycle or device reset:
N/A
• bg
• bgn
WifiProtocolNext
About the NTx-W Embedded Video Interface
Controls the next Wi-Fi protocol after the next
power cycle or device reset.
Persistent memory
13
Table 6: Wireless GenICam Features (Continued)
Feature
WifiResetDefaults
Description
Resets the wireless driver to its default settings
after the next power cycle or device reset.
Persistence
N/A
Executing this feature is equivalent to pressing
the reset button on the wireless board. For more
information, see “Restoring Default Wireless
Configuration” on page 60.
WirelessControl\WirelessStatistics
(Note: All wireless statistic features are updated by WifiStatsUpdate and WifiStatsClear)
14
WifiStatsUpdate
Updates the wireless interfaces statistics.
N/A
WifiStatsClear
Clears all statistic counters of the wireless
interfaces.
N/A
WifiLinkFrequency
Reports the frequency of the current channel.
N/A
WifiLinkBitRate
Reports the wireless link bit rate in Megabits per
second.
N/A
WifiLinkTxPower
Reports the wireless link transmit power in dBm.
N/A
WifiLinkQualityStatus
Reports an overall characterization of wireless
link.
N/A
WifiLinkSignalLevel
Reports the average signal strength of the
received data in dBm.
N/A
WifiLinkNoiseLevel
Reports the level of noise floor detected by the
radio in dBm.
N/A
WifiTotalBytesTransmitted
Reports the total number of transmitted bytes.
N/A
WifiTotalBytesReceived
Reports the total number of received bytes.
N/A
WifiTotalTxPackets
Reports the total number of transmit packets.
N/A
WifiTotalRxPackets
Reports the total number of receive packets.
N/A
WifiReceiveEOLInterrupts
Reports the number of receive EOL interrupts.
N/A
WifiTxFramesWithNoAckMarked
Reports the number of transmit frames with no
acknowledges marked.
N/A
WifiTxFramesWithAlternateRates
Reports the number of transmit frames with
alternate rates.
N/A
WifiTxRSSIOfLastAck
Reports the received signal strength indicators
of the last acknowledge on the transmit side.
N/A
WifiRSSIFromHistogram
Reports the received signal strength indicator
from histogram.
N/A
WifiPeriodicCalibrations
Reports the number of periodic calibrations.
N/A
WifiTxWhenQueueIsLow
Reports the number of transmissions when the
queue is low.
N/A
iPORT NTx-W Embedded Video Interface User Guide
Table 6: Wireless GenICam Features (Continued)
Feature
Description
Persistence
WifiTxPktWhenQueueIsBusy
Reports the number of transmit packets when
the queue is busy.
N/A
WifiScheduledPktWhenQueueIsEmpty
Reports the number of scheduled packets when
the queue is empty.
N/A
WifiTxUnaggregatedFrameCompletion
Reports the transmit unaggregated frame
completion.
N/A
WifiTxBlockAckWindowAdvanced
Reports the transmit block acknowledge window
advanced.
N/A
WifiTxBlockAckWindowAddition
Reports the transmit block acknowledge window
addition.
N/A
WifiTxBlockAckWindowUpdate
Reports the transmit block acknowledge window
update.
N/A
WifiTxFrameNotAggregated
Reports the transmit frame not aggregated.
N/A
WifiRxAggregatedPkt
Reports the number of received aggregated
packets.
N/A
WifiRxNonQOSDataFrames
Reports the number of received non-QOS data
frames.
N/A
WifiRxBlockAckWindowAdvanced
Reports the receive block acknowledge window
advanced.
N/A
WifiRxPktCompletions
Reports the number of received packet
completions.
N/A
WifiDrainingTIDBufQueueOnError
Reports the draining TID buffer queue on error.
N/A
WifiDraningTIDBufQueueOnNode
Cleanup
Reports the draining TID buffer queue on node
clean up.
N/A
WifiBuffersDrainedFromPendingTID
Queue
Reports the number of buffers drained from
pending TID queue.
N/A
WifiAth0TxPackets
Reports the number of transmitted packets on
the wireless interface of the bridge.
N/A
WifiAth0TxBytes
Reports the number of transmitted bytes on the
wireless interface of the bridge.
N/A
WifiAth0TxErrors
Reports the number of transmitted errors on the
wireless interface of the bridge.
N/A
WifiAth0TxDropped
Reports the number of transmitted dropped
packets on the wireless interface of the bridge.
N/A
WifiAth0TxOverrun
Reports the number of transmitted overruns on
the wireless interface of the bridge.
N/A
WifiAth0TxQueueLength
Reports the transmitted queue length on the
wireless interface of the bridge.
N/A
About the NTx-W Embedded Video Interface
15
Table 6: Wireless GenICam Features (Continued)
Feature
16
Description
Persistence
WifiAth0RxPackets
Reports the number of received packets on the
wireless interface of the bridge.
N/A
WifiAth0RxBytes
Reports the number of received bytes on the
wireless interface of the bridge.
N/A
WifiAth0RxErrors
Reports the number of received errors on the
wireless interface of the bridge.
N/A
WifiAth0RxDropped
Reports the number of received dropped
packets on the wireless interface of the bridge.
N/A
WifiAth0RxOverrun
Reports the number of received overruns on the
wireless interface of the bridge.
N/A
WifiAth0Collision
Reports the number of collisions on the wireless
interface of the bridge.
N/A
WifiFpgaTxPackets
Reports the number of transmitted packets on
the FPGA interface of the bridge.
N/A
WifiFpgaTxBytes
Reports the number of transmitted bytes on the
FPGA interface of the bridge.
N/A
WifiFpgaTxErrors
Reports the number of transmitted errors on the
FPGA interface of the bridge.
N/A
WifiFpgaTxDropped
Reports the number of transmitted dropped
packets on the FPGA interface of the bridge.
N/A
WifiFpgaTxOverrun
Reports the number of transmitted overruns on
the FPGA interface of the bridge.
N/A
WifiFpgaTxQueueLength
Reports the transmitted queue length on the
FPGA interface of the bridge.
N/A
WifiFpgaRxPackets
Reports the number of received packets on the
FPGA interface.
N/A
WifiFpgaRxBytes
Reports the number of received bytes on the
FPGA interface of the bridge.
N/A
WifiFpgaRxErrors
Reports the number of received errors on the
FPGA interface of the bridge.
N/A
WifiFpgaRxDropped
Reports the number of received dropped
packets on the FPGA interface of the bridge.
N/A
WifiFpgaRxOverrun
Reports the number of received overruns on the
FPGA interface of the bridge.
N/A
WifiFpgaCollision
Reports the number of collisions on the FPGA
interface of the bridge.
N/A
iPORT NTx-W Embedded Video Interface User Guide
Chapter 3
Connections and Indicators
This chapter describes the NTx-W Embedded Video Interface connections. It also includes pinouts for
the Pixel bus and power connectors, as well as details about the status LEDs.
The following topics are covered in this chapter:
• “Connector Locations” on page 18
• “Mounting the 12-Pin Circular Connector to an Enclosure Backplate” on page 19
• “12-Pin Circular Connector” on page 20
• “100-Pin User Circuitry Connector Pinouts” on page 22
• “NTx-Mini Adapter Board Pinout Mapping” on page 27
• “Status LEDs” on page 30
Connections and Indicators
17
Connector Locations
The following images and table provide the descriptions and locations for the NTx-W Embedded Video
Interface connectors.
J3
J1
J1
J2
J2
Wireless Board
FPGA Board
GPIO Board
Table 7: NTx-W Connector Location and Descriptions
ID
Location
Type
Description
J3
Wireless
board
20-pin flat cable
connector for
GPIO board
Connects to GPIO board with a 20-pin FPC cable, providing
power to the device. You can connect a 20-pin FFC cable to
the GPIO board or to your own board.
J1
GPIO board
12-pin circular
Provides power to the embedded video interface. Receives
4.7V to 16V of unfiltered DC input.
J2
Wireless
board
PCIe SparkLan
Radio Module
Connector
Interfaces to the radio module.
J2
GPIO board
20-pin FFC
connector
Connects to wireless board with a 20-pin FPC cable.
J1
FPGA board
100-pin user
circuitry
interface
Interfaces directly to the camera head or other external
device.
The connector is hermaphroditic, meaning the same part is
used as the header and receptacle.
Samtec LSHM series 0.5mm pitch vertical 100-pin:
LSHM-150-04.0-L-DV-A-N-TR.
18
iPORT NTx-W Embedded Video Interface User Guide
Table 7: NTx-W Connector Location and Descriptions (Continued)
ID
Location
Type
Description
J3 (not
shown)
FPGA board
60-pin connector
Allows communication between the FPGA board and the
wireless board. In the photograph above, the connector is
located on the reverse side of the board.
J4 (not
shown)
Wireless
board
60-pin connector
Allows communication between the FPGA board and the
wireless board. In the photograph above, the connector is
located on the reverse side of the board.
Mounting the 12-Pin Circular Connector to an Enclosure
Backplate
The removable 12-pin circular connector and the corresponding GPIO board adapter board are suitable
for mounting to a client-sourced enclosure.
To mount the 12-pin circular connector to an enclosure backplate
1. Insert the 12-pin circular connector through the external side of the backplate.
2. Secure with washer and hex nut.
3. Connect the adapter board GPIO board (12 holes) to the base pins of the 12-pin connector through
the internal side of the backplate.
Lock washer
12-pin male connector
Insertion
Hex nut
Adapter board
Pins (soldered to adapter board)
Backplate of client-sourced enclosure
Connections and Indicators
Enclosure interior
20-pin FFC
19
4. Assemble the 12-pin circular connector to the GPIO board adapter board by lining up the pins with
the GPIO board adapter board.
When oriented correctly, the tab on the 12-pin circular connector is aligned with the small white dot on the
GPIO board, as shown in the following figure. Please disregard the white numbering on the back of the GPIO
board, as the pin numbers are labeled incorrectly in early versions of the product.
5. Solder the pins of the connector to the adapter board for a secure connection.
Tab
12-pin male
connector
White dot
GPIO board and 12-pin
male connector (assembled)
12-pin male connector
GPIO board
When lined up properly,
pin 9 and pin 1 on the 12-pin
connector are inserted through
the bottom two pinholes
Line up tab between
the two bottom pins
Tab location
GPIO board and 12-pin
male connector (assembled)
12-Pin Circular Connector
This section describes the pinouts for the 12-pin circular connector (J1 on the GPIO board).
For this release of the NTx-W Embedded Video Interface firmware, only the power pinouts are connected.
The remaining pins on the 12-pin circular connector are reserved for future use.
20
iPORT NTx-W Embedded Video Interface User Guide
Power Pinouts
Pins 1, 2, and 5 of the 12-pin circular connector are used to connect external power to the iPORT NTxW Embedded Video Interface.
The NTx-W Embedded Video Interface supports 4.7 to 16V input and requires <2.3W of external
power. The customer circuitry along with the NTx-W Embedded Video Interface can draw a maximum
of 1.5A.
The design includes reverse voltage protection, surge protection, and triple-filtering scheme on power
pins, which meets class-B EMC certification without a ferrite bead on the power cable.
Figure 1: 12-Pin Male Circular Connector
Tab location
20-Pin Connector on Wireless Board
The following table provides the pinout descriptions for the 20-pin connector (J3 on the wireless board).
Table 8: 20-Pin Connector — Pinout Descriptions
Pin
Function
Type
See table note...
1
RET
Power ground
1
2
RET
Power ground
1
3
RET
Power ground
1
4
VIN/PWR
Power input
1, 2, 3, 4
5
VIN/PWR
Power input
1, 2, 3, 4
6
VIN/PWR
Power input
1, 2, 3, 4
7
GND/EMI_GND
Signal ground
6, 7
8
Reserved
9
Reserved
10
Reserved
11
Reserved
12
Reserved
13
Reserved
Connections and Indicators
21
Table 8: 20-Pin Connector — Pinout Descriptions (Continued)
Pin
Function
14
Reserved
Type
See table note...
15
Reserved
16
DBG_LED0
Status LED, cathode, OC
6, 7
17
3.3V
Status LED, anode
7, 8
18
Reserved
Do not connect
19
Reserved
Do not connect
20
GND/EMI_GND
Signal ground
5
1. Maximum 0.5A per pin, 1.5A per 3 pins.
2. Protected by +/-30VDC, 600W @ 1.0 ms PP Zener TVS, +/- 16 kV per HBM.
3. Reverse voltage protected, up to -30VDC.
4. Triple filtering scheme is used to filter EMI and conduct emissions, to pass EMC class-B.
5. Ferrite bead 0.2A, 600 Ohm @ 100 MHz to the GND of the GigE PHY board.
6. Logical "0" (pulled-down) means that the backup load is used; logical "1" (3.3V) means that the
main load is used.
7. For information about the status LED, see the description of the Power/Firmware LED in “Status
LEDs” on page 17.
8. Not protected by a fuse; cannot be used as a power output.
12-Pin Circular Connector Mate
The mating connector to the 12-pin power circular connector is a Hirose 12-pin connector, part number
HR10A-10P-12P(73).
100-Pin User Circuitry Connector Pinouts
The following table provides the pinout descriptions for the 100-pin user circuitry connector (J1 on the
FPGA board).
22
iPORT NTx-W Embedded Video Interface User Guide
Pin 2
Pin 100
Pin 99
Pin 1
Table 9: 100-Pin User Circuitry Pinouts
Pin
Function
Type
Description
1
VCC_5V_30V
PWR OUT
VIN or VBUS.
2
VCC_5V_30V
PWR OUT
VIN or VBUS.
3
RET
RET (GND)
RET or GND
4
RET
RET (GND)
RET or GND
5
+2.5V
PWR OUT
2.5V output. Can supply up to 0.3A.
6
+3.3V
PWR OUT
3.3V output. Can supply up to 1.5A.
7
+2.5V
PWR OUT
2.5V output. Can supply up to 0.3A.
8
+3.3V
PWR OUT
3.3V output. Can supply up to 1.5A.
9
Reserved
10
Reserved
11
Reserved
12
Reserved
13
Reserved
14
Reserved
15
Reserved
16
Reserved
17
Reserved
18
Reserved
19
Reserved
20
Reserved
21
GND
GND
Connections and Indicators
23
Table 9: 100-Pin User Circuitry Pinouts (Continued)
Pin
Function
Type
Description
22
GND
GND
23
PWR_ON_RSTN
INOUT, OC
Power on Reset. See table note 1.
24
BULK_TX0
OUT
Bulk interface 0 and UART output.
25
Reserved
26
BULK_RX0
IN
Bulk interface 0 and UART input.
See important warning in table note 3.
27
Reserved
28
Reserved
29
Reserved
30
BULK_TX1
31
Reserved
32
BULK_RX1
33
Reserved
34
Reserved
35
Reserved
36
BULK_TX2
37
Reserved
38
BULK_RX2
OUT
Bulk interface 1 and UART output.
IN
Bulk interface 1 UART and UART output.
OUT
Bulk interface 2 and UART output.
IN
Bulk interface 2 and UART input.
See important warning in table note 3.
39
Reserved
40
Reserved
41
Reserved
42
GND
GND
43
FPGA_SEL
INOUT OC/N.C.
Selection of FPGA load. See table note 2.
This signal has been added to ensure consistency with
earlier Pleora products, such as the iPORT
NTx-Mini Embedded Video Interface. For newer products,
leave it N.C.
44
PB0_CLK
IN
Pixel bus clock.
See important warning in table note 3.
24
45
GND
GND
46
PB0_CLK_IN
IN
For future use. Connect to ground.
47
PB0_DATA0
IN
Pixel bus data 0. See important warning in table note 3.
iPORT NTx-W Embedded Video Interface User Guide
Table 9: 100-Pin User Circuitry Pinouts (Continued)
Pin
Function
Type
48
GND
GND
Description
49
PB0_DATA1
IN
Pixel bus data 1. See important warning in table note 3.
50
PB0_DATA8
IN
Pixel bus data 8. See important warning in table note 3.
51
PB0_GND
GND
52
PB0_DATA9
IN
Pixel bus data 9. See important warning in table note 3.
53
PB0_DATA2
IN
Pixel bus data 2. See important warning in table note 3.
54
GND
GND
55
PB0_DATA3
IN
Pixel bus data 3. See important warning in table note 3.
56
PB0_DATA10
IN
Pixel bus data 10. See important warning in table note 3.
57
GND
GND
58
PB0_DATA11
IN
Pixel bus data 11. See important warning in table note 3.
59
PB0_DATA4
IN
Pixel bus data 4. See important warning in table note 3.
60
GND
GND
61
PB0_DATA5
IN
Pixel bus data 5. See important warning in table note 3.
62
PB0_DATA12
IN
Pixel bus data 12. See important warning in table note 3.
63
Reserved
64
PB0_DATA13
IN
Pixel bus data 13. See important warning in table note 3.
65
PB0_DATA6
IN
Pixel bus data 6. See important warning in table note 3.
66
Reserved
67
PB0_DATA7
IN
Pixel bus data 7. See important warning in table note 3.
68
PB0_DATA14
IN
Pixel bus data 14. See important warning in table note 3.
69
GND
GND
70
PB0_DATA15
IN
Pixel bus data 15. See important warning in table note 3.
71
PB0_DATA16
IN
Pixel bus data 16. See important warning in table note 3.
72
GND
GND
73
PB0_DATA17
IN
Pixel bus data 17. See important warning in table note 3.
74
PB0_DATA24
IN
Pixel bus data 24. See important warning in table note 3.
75
PB0_FVAL
IN
Pixel bus frame valid.
See important warning in table note 3.
76
PB0_DATA25
IN
Pixel bus data 25. See important warning in table note 3.
77
PB0_DATA18
IN
Pixel bus data 18. See important warning in table note 3.
Connections and Indicators
25
Table 9: 100-Pin User Circuitry Pinouts (Continued)
Pin
Function
Type
Description
78
PB0_DVAL
IN
Pixel bus data valid.
See important warning in table note 3.
79
PB0_DATA19
IN
Pixel bus data 19. See important warning in table note 3.
80
PB0_DATA26
IN
Pixel bus data 26. See important warning in table note 3.
81
GND
GND
82
PB0_DATA27
IN
Pixel bus data 27. See important warning in table note 3.
83
PB0_DATA20
IN
Pixel bus data 20. See important warning in table note 3.
84
GND
GND
85
PB0_DATA21
IN
Pixel bus data 21. See important warning in table note 3.
86
PB0_DATA28
IN
Pixel bus data 28. See important warning in table note 3.
87
PB0_MVAL
IN
Pixel bus chunk data valid.
See important warning in table note 3.
88
PB0_DATA29
IN
Pixel bus data 29. See important warning in table note 3.
89
PB0_DATA22
IN
Pixel bus data 22. See important warning in table note 3.
90
PB0_LVAL
IN
Pixel bus line valid.
See important warning in table note 4.
91
PB0_DATA23
IN
Pixel bus data 23. See important warning in table note 3.
92
PB0_DATA30
IN
Pixel bus data 30. See important warning in table note 3.
93
GND
GND
94
PB0_DATA31
IN
95
Reserved
96
GND
97
Reserved
98
Reserved
99
GND
GND
100
GND
GND
Pixel bus data 31. See important warning in table note 3.
GND
Table Notes:
1. PWR_ON_RSTN is a bidirectional open collector pin with a 10Kohm resistor to 3.3V on the FPGA
board. This signal is high when power on the NTx-W Embedded Video Interface is at the appropriate
levels. You can leave this set to N.C.; or connect with the power ready signal of the user circuitry; or use
it to start configuration of user devices, such as FPGAs or CPUs; or use it to initiate a reset of the FPGA
on the NTx-W Embedded Video Interface.
26
iPORT NTx-W Embedded Video Interface User Guide
2. FPGA_SEL selects the FPGA load to be used. Setting this pin high (1) runs the main load; low (0)
forces the backup (factory) load. The FPGA board provides a 1Kohm pull-up to 2.5V and a DIP switch
to GND (normally off ). You can leave this pin set to N.C. (recommended); or monitor the load used; or
force the backup load by setting the DIP switch to GND or by using an open-collector signal.
3. IMPORTANT: If your electronics output 3.0 V or 3.3 V, place a 33 ohm serial resistor between the
following inputs on the 100-pin user circuitry connector and your electronics, to avoid damage to the
FPGA: PB0_DATAx, PB0_CLK, PB0_FVAL, PB0_LVAL, PB0_MVAL, PB0_DVAL, BULK_RXx, and
FPGA_GPIO_INx.
NTx-Mini Adapter Board Pinout Mapping
This section describes how the signals from the FPGA board are directly routed to the 60-pin FFC/FPC
connector on the NTx-Mini Adapter board. This board is intended to help you evaluate the NTx-W with
an existing camera connected to an iPORT NTx-Mini Embedded Video Interface.
Table 10: 60-Pin FFC/FPC Connector to FPGA Board
Signal on FPGA board
NTx-Mini Embedded Video Interface 60-pin connector
Function
Pin
Function
1
Not connected (See note 1)
2
Not connected
VIN
3
CAMERA_VIN
VIN
4
CAMERA_VIN
FPGA_SEL0
5
FPGA_SEL0
N.C (See notes 2 and 3)
6
FPGA_SEL1
PWR_ON_RST
7
PWR_ON_RST#
GND
8
GND
PB0_DATA0 (See note 2)
9
PIXEL_DATA0
PB0_DATA1 (See note 2)
10
PIXEL_DATA1
PB0_DATA2 (See note 2)
11
PIXEL_DATA2
PB0_DATA3 (See note 2)
12
PIXEL_DATA3
PB0_DATA4 (See note 2)
13
PIXEL_DATA4
PB0_DATA5 (See note 2)
14
PIXEL_DATA5
PB0_DATA6 (See note 2)
15
PIXEL_DATA6
PB0_DATA7 (See note 2)
16
PIXEL_DATA7
PB0_DATA8 (See note 2)
17
PIXEL_DATA8
PB0_DATA9 (See note 2)
18
PIXEL_DATA9
Connections and Indicators
27
Table 10: 60-Pin FFC/FPC Connector to FPGA Board (Continued)
28
Signal on FPGA board
NTx-Mini Embedded Video Interface 60-pin connector
Function
Pin
Function
GND
19
GND
PB0_DATA10 (See note 2)
20
PIXEL_DATA10
PB0_DATA11 (See note 2)
21
PIXEL_DATA11
PB0_DATA12 (See note 2)
22
PIXEL_DATA12
PB0_DATA13 (See note 2)
23
PIXEL_DATA13
PB0_DATA14 (See note 2)
24
PIXEL_DATA14
PB0_DATA15 (See note 2)
25
PIXEL_DATA15
PB0_DATA16 (See note 2)
26
PIXEL_DATA16
PB0_DATA17 (See note 2)
27
PIXEL_DATA17
PB0_DATA18 (See note 2)
28
PIXEL_DATA18
PB0_DATA19 (See note 2)
29
PIXEL_DATA19
GND
30
GND
PB0_DATA20 (See note 2)
31
PIXEL_DATA20
PB0_DATA21 (See note 2)
32
PIXEL_DATA21
PB0_DATA22 (See note 2)
33
PIXEL_DATA22
PB0_DATA23 (See note 2)
34
PIXEL_DATA23
PB0_MVAL (See note 2)
35
SPARE
PB0_LVAL (See note 2)
36
LVAL
PB0_FVAL (See note 2)
37
FVAL
PB0_DVAL (See note 2)
38
DVAL
BULK_RX2 (See note 2)
39
BULK2_RXD
BULK_TX2 (See note 2)
40
BULK2_TXD
GND
41
GND
PB0_CTRL_OUT0 (See note 2)
42
CC1
PB0_CTRL_OUT1 (See note 2)
43
CC2
PB0_CTRL_OUT2 (See note 2)
44
CC3
PB0_CTRL_OUT3 (See note 2)
45
CC4
BULK_RX0 (See note 2)
46
BULK0_RXD
BULK_TX0 (See note 2)
47
BULK0_TXD
Reserved
48
Reserved
BULK_RX1 (See note 2)
49
UART1_RXD
iPORT NTx-W Embedded Video Interface User Guide
Table 10: 60-Pin FFC/FPC Connector to FPGA Board (Continued)
Signal on FPGA board
NTx-Mini Embedded Video Interface 60-pin connector
Function
Pin
Function
BULK_TX1 (See note 2)
50
UART1_TXD
PB0_DATA24 (See note 2)
51
Reserved
GND
52
GND
PB0_DATA25 (See note 2)
53
Reserved
PB0_DATA26 (See note 2)
54
Reserved
PB0_DATA29
55
Reserved
PB0_DATA28
56
OUT_CLK0
PB0_CLK (See note 2)
57
PIXEL_CLK
Reserved
58
Reserved
PB0_DATA30 (See note 2)
59
Reserved
PB0_DATA31 (See note 2)
60
Reserved
1. If you require 2.5 V to power the camera, you can do so by installing a 0 ohm 0805 resistor at R17 on the NTx-Mini Adapter
board (shown below), and powering the camera using Pin 1. This pin can supply a maximum of 0.25 A at 2.5 V.
2. These signals are connected to the FPGA board through 33 R resisters.
3. To test a 32-bit wide pixel bus you can do the following:
a. On the adapter board, wire pin 26 on the J3 connector (30-pin) (which is not populated) to either of these pins:
• Pin 6 on the J4 connector (60-pin).
- Or -
• Test point TP2 (which is connected to pin 6 on the J4 connector).
b. Connect PB0_DATA27 from camera to pin 6 of the 60 pin connector.
NTx-Mini Adapter Board
Connections and Indicators
29
Status LEDs
The following image and table provide descriptions of the NTx-W status LEDs.
D14
D1
D17
Table 11: NTx-W Status LEDS
LED
ID
Description
Power and FPGA Config Done
D1
Green:
On: 2.5V power supply is working
Off: 2.5V power supply is off / not working
Yellow:
On: FPGA backup load is being used
Off: FPGA main load is being used
Atheros Status
D14
Green: Not implemented
Yellow: Not Implemented
Wireless Status
D17
Green:
On: Link quality is equal to or above the user-defined
threshold value.
Off: Link quality is below the user-defined threshold value,
or no link is established.
Yellow:
Local-Area-Network (LAN) Status Indicator LED from radio
card. For more information see “Description of W-LAN
Status Indicator LED” on page 31.
30
iPORT NTx-W Embedded Video Interface User Guide
The following table provides a description of the W-LAN status indicator LED.
Table 12: Description of W-LAN Status Indicator LED
State
Definition
Off
Emitting no light
Characteristics
Not powered
On
Emitting light in a stable
non-flashing state
Powered, associated and
authenticated but not
transmitting or receiving
Slow Blink
Flashing at a steady but
slow rate
250+/-25% milliseconds
ON period
0.2 +/-25% Hz blink rate
Intermittent Blink
Connections and Indicators
Flashing intermittently
proportional to the
activity on the interface
50% duty cycle
3 Hz minimum blink state
20 Hz maximum blink
state
Description
Powered but not
associated or
authenticated; searching
Activity proportional to
transmitting and
receiving speed
31
Chapter 2
Bulk Interfaces
This chapter describes the NTx-W Embedded Video Interface bulk interfaces and the supported
protocols.
The following topics are covered in this chapter:
• “Bulk Interfaces and Supported Protocol” on page 34
• “UART Interface” on page 34
• “GenICam Interface for Serial Communication Configuration” on page 35
Bulk Interfaces
33
Bulk Interfaces and Supported Protocol
The NTx-W Embedded Video Interface has three Bulk interface ports available for serial communication.
Each port supports the standard UART (Universal Asynchronous Receiver/Transmitter). A UART
interface consists of two port signals: TX and RX. In the NTx-W Embedded Video Interface, the three
Bulk interface ports are available on the 100-pin user circuitry connector.
The following table shows the connector pinout information for the Bulk interface port signals.
Table 13: Bulk Interface Signals and Connector Pinouts
Bulk signal
100-pin user circuitry connector pin number
BULK_TX0
24
BULK_RX0
26
BULK_TX1
30
BULK_RX1
32
BULK_TX2
36
BULK_RX2
38
GND
See “100-Pin User Circuitry Connector Pinouts” on page
22.
The Bulk interfaces on the NTx-W Embedded Video Interface are 2.5V IOs.
UART Interface
The NTx-W Embedded Video Interface UART interface supports:
• 8-bit data transfer
• 1 start bit
• Programmable stop bit(s): 1 or 2
• Parity: even, odd, or none
• Baud rates:
• Predefined rates: 9600, 14400, 19200, 28800, 38400, 57600, 115200
• Programmable
• Loop back mode from downstream to upstream
34
iPORT NTx-W Embedded Video Interface User Guide
GenICam Interface for Serial Communication Configuration
The following GenICam features are available for serial communication configuration.
Table 14: GenICam Features Available for Serial Communication
Bulk Interfaces
Feature
Description
BulkSelector
Selects Bulk0, Bulk1 or Bulk2 for configuration.
BulkMode
UART protocol.
BulkBaudRate
Defines the baud rate of the UART serial communication link. When set to
Programmable, the baud rate is defined according to the BulkBaudRateFactor feature.
BulkBaudRateFactor
Enables the programming of user defined baud rates. The actual baud rate is
provided by the BulkBaudRateValue feature.
BulkBaudRateValue
Represents the actual baud rate computed from the BulkBaudRateFactor
feature.
BulkLoopback
Loops back downstream data to upstream direction (loops the data back to the
computer).
BulkNumOfStopBits
Selects a stop bit option (either 1 or 2).
BulkParity
Selects a parity option (None, Even, or Odd).
BulkUpstreamFifoWatermark
Sets the level of upstream FIFO at which a GigE Vision event is generated.
35
Chapter 3
Pixel Bus Definitions and Timing
This chapter describes the interface responsible for transmitting data from the camera to the embedded
video interface.
The following topics are covered in this chapter:
• “Pixel Bus Definitions” on page 38
• “Pixel Bus Timing” on page 43
• “Pixel Bus Signals” on page 44
• “Timing Values for All Cases” on page 46
Pixel Bus Definitions and Timing
37
Pixel Bus Definitions
The tables in this section list the embedded video interface pixel bus definitions.
Mono/RGB/Bayer
Table 15: Mono/RGB/Bayer Pixel Bus Definitions
Mono8 /
Bayer8
Mono10 /
Bayer10
Mono12 /
Bayer12
Mono16 /
Bayer16
Mono14
BGR8
RGB8
Tap
Bit
Tap
Bit
Tap
Bit
Tap
Bit
Tap
Bit
Comp. Bit
Comp.
Bit
PB_Data 0
0
0
0
0
0
0
0
0
0
0
B0
0
R0
0
PB_Data 1
0
1
0
1
0
1
0
1
0
1
B1
1
R1
1
PB_Data 2
0
2
0
2
0
2
0
2
0
2
B2
2
R2
2
PB_Data 3
0
3
0
3
0
3
0
3
0
3
B3
3
R3
3
PB_Data 4
0
4
0
4
0
4
0
4
0
4
B4
4
R4
4
PB_Data 5
0
5
0
5
0
5
0
5
0
5
B5
5
R5
5
PB_Data 6
0
6
0
6
0
6
0
6
0
6
B6
6
R6
6
PB_Data 7
0
7
0
7
0
7
0
7
0
7
B7
7
R7
7
PB_Data 8
1
0
0
8
0
8
0
8
0
8
G0
0
G0
0
PB_Data 9
1
1
0
9
0
9
0
9
0
9
G1
1
G1
1
PB_Data 10
1
2
-
nc
0
10
0
10
0
10
G2
2
G2
2
PB_Data 11
1
3
-
nc
0
11
0
11
0
11
G3
3
G3
3
PB_Data 12
1
4
1
8
1
8
0
12
0
12
G4
4
G4
4
PB_Data 13
1
5
1
9
1
9
0
13
0
13
G5
5
G5
5
PB_Data 14
1
6
-
nc
1
10
-
nc
0
14
G6
6
G6
6
PB_Data 15
1
7
-
nc
1
11
-
nc
0
15
G7
7
G7
7
PB_Data 16
2
0
1
0
1
0
-
nc
1
0
R0
0
B0
0
PB_Data 17
2
1
1
1
1
1
-
nc
1
1
R1
1
B1
1
PB_Data 18
2
2
1
2
1
2
-
nc
1
2
R2
2
B2
2
PB_Data 19
2
3
1
3
1
3
-
nc
1
3
R3
3
B3
3
PB_Data 20
2
4
1
4
1
4
-
nc
1
4
R4
4
B4
4
PB_Data 21
2
5
1
5
1
5
-
nc
1
5
R5
5
B5
5
PB_Data 22
2
6
1
6
1
6
-
nc
1
6
R6
6
B6
6
PB_Data 23
2
7
1
7
1
7
-
nc
1
7
7
B7
7
38
R7
iPORT NTx-W Embedded Video Interface User Guide
Table 15: Mono/RGB/Bayer Pixel Bus Definitions (Continued)
Mono8 /
Bayer8
Mono10 /
Bayer10
Mono12 /
Bayer12
Mono16 /
Bayer16
Mono14
BGR8
Tap
Bit
Tap
Bit
Tap
Bit
Tap
Bit
Tap
Bit
Comp. Bit
PB_Data 24
3
0
-
nc
-
nc
-
nc
1
8
-
PB_Data 25
3
1
-
nc
-
nc
-
nc
1
9
PB_Data 26
3
2
-
nc
-
nc
-
nc
1
PB_Data 27
3
3
-
nc
-
nc
-
nc
PB_Data 28
3
4
-
nc
-
nc
-
PB_Data 29
3
5
-
nc
-
nc
PB_Data 30
3
6
-
nc
-
PB_Data 31
3
7
-
nc
-
RGB8
Comp.
Bit
nc
-
nc
-
nc
-
nc
10
-
nc
-
nc
1
11
-
nc
-
nc
nc
1
12
-
nc
-
nc
-
nc
1
13
-
nc
-
nc
nc
-
nc
1
14
-
nc
-
nc
nc
-
nc
1
15
-
nc
-
nc
YUV411_8_UYYVYY: 1 Tap
Table 16: YUV411_8_UYYVYY: 1 Tap Pixel Bus Definitions
Clock 1
Component
Clock 2
Bit
Component
Clock 3
Bit
Component
Clock 4
Bit
Component
Bit
PB_Data 0
Y11
0
Y11
4
Y13
0
Y13
4
PB_Data 1
Y11
1
Y11
5
Y13
1
Y13
5
PB_Data 2
Y11
2
Y11
6
Y13
2
Y13
6
PB_Data 3
Y11
3
Y11
7
Y13
3
Y13
7
PB_Data 4
U11
0
Y12
0
V11
0
Y14
0
PB_Data 5
U11
1
Y12
1
V11
1
Y14
1
PB_Data 6
U11
2
Y12
2
V11
2
Y14
2
PB_Data 7
U11
3
Y12
3
V11
3
Y14
3
PB_Data 8
U11
4
Y12
4
V11
4
Y14
4
PB_Data 9
U11
5
Y12
5
V11
5
Y14
5
PB_Data 10
U11
6
Y12
6
V11
6
Y14
6
PB_Data 11
U11
7
Y12
7
V11
7
Y14
7
PB_Data 12
through to
PB_Data 31
-
-
-
-
-
-
-
-
Pixel Bus Definitions and Timing
39
YUV411_8_UYYVYY: 2 Tap
Table 17: YUV411_8_UYYVYY: 2 Tap Pixel Bus Definitions
Clock 1
Clock 2
Clock 3
Clock 4
Component
Bit
Component
Bit
Component
Bit
Component
Bit
PB_Data 0
Y11
0
Y13
0
Y15
0
Y17
0
PB_Data 1
Y11
1
Y13
1
Y15
1
Y17
1
PB_Data 2
Y11
2
Y13
2
Y15
2
Y17
2
PB_Data 3
Y11
3
Y13
3
Y15
3
Y17
3
PB_Data 4
U11
0
V11
0
U15
0
V15
0
PB_Data 5
U11
1
V11
1
U15
1
V15
1
PB_Data 6
U11
2
V11
2
U15
2
V15
2
PB_Data 7
U11
3
V11
3
U15
3
V15
3
PB_Data 8
U11
4
V11
4
U15
4
V15
4
PB_Data 9
U11
5
V11
5
U15
5
V15
5
PB_Data 10
U11
6
V11
6
U15
6
V15
6
PB_Data 11
U11
7
V11
7
U15
7
V15
7
PB_Data 12
Y12
4
Y14
4
Y16
4
Y18
4
PB_Data 13
Y12
5
Y14
5
Y16
5
Y18
5
PB_Data 14
Y12
6
Y14
6
Y16
6
Y18
6
PB_Data 15
Y12
7
Y14
7
Y16
7
Y18
7
PB_Data 16
Y11
4
Y13
4
Y15
4
Y17
4
PB_Data 17
Y11
5
Y13
5
Y15
5
Y17
5
PB_Data 18
Y11
6
Y13
6
Y15
6
Y17
6
PB_Data 19
Y11
7
Y13
7
Y15
7
Y17
7
PB_Data 20
Y12
0
Y14
0
Y16
0
Y18
0
PB_Data 21
Y12
1
Y14
1
Y16
1
Y18
1
PB_Data 22
Y12
2
Y14
2
Y16
2
Y18
2
PB_Data 23
Y12
3
Y14
3
Y16
3
Y18
3
PB_Data 24
through to
PB_Data 31
-
-
-
-
-
-
-
-
40
iPORT NTx-W Embedded Video Interface User Guide
YUV422_8_UYVY
Table 18: YUV422_8_UYVY Pixel Bus Definitions
Clock 1
Clock 2
Clock 3
Clock 4
Component
Bit
Component
Bit
Component
Bit
Component
Bit
PB_Data 0
U11
0
V11
0
U13
0
V13
0
PB_Data 1
U11
1
V11
1
U13
1
V13
1
PB_Data 2
U11
2
V11
2
U13
2
V13
2
PB_Data 3
U11
3
V11
3
U13
3
V13
3
PB_Data 4
U11
4
V11
4
U13
4
V13
4
PB_Data 5
U11
5
V11
5
U13
5
V13
5
PB_Data 6
U11
6
V11
6
U13
6
V13
6
PB_Data 7
U11
7
V11
7
U13
7
V13
7
PB_Data 8
Y11
0
Y12
0
Y13
0
Y14
0
PB_Data 9
Y11
1
Y12
1
Y13
1
Y14
1
PB_Data 10
Y11
2
Y12
2
Y13
2
Y14
2
PB_Data 11
Y11
3
Y12
3
Y13
3
Y14
3
PB_Data 12
Y11
4
Y12
4
Y13
4
Y14
4
PB_Data 13
Y11
5
Y12
5
Y13
5
Y14
5
PB_Data 14
Y11
6
Y12
6
Y13
6
Y14
6
PB_Data 15
Y11
7
Y12
7
Y13
7
Y14
7
PB_Data 16
through to
PB_Data 31
-
-
-
-
-
-
-
-
Pixel Bus Definitions and Timing
41
YUV8_UYV
Table 19: YUV8_UYV Pixel Bus Definitions
Clock 1
Clock 3
Component
Bit
Component
Bit
PB_Data 0
U11
0
U12
0
PB_Data 1
U11
1
U12
1
PB_Data 2
U11
2
U12
2
PB_Data 3
U11
3
U12
3
PB_Data 4
U11
4
U12
4
PB_Data 5
U11
5
U12
5
PB_Data 6
U11
6
U12
6
PB_Data 7
U11
7
U12
7
PB_Data 8
Y11
0
Y12
0
PB_Data 9
Y11
1
Y12
1
PB_Data 10
Y11
2
Y12
2
PB_Data 11
Y11
3
Y12
3
PB_Data 12
Y11
4
Y12
4
PB_Data 13
Y11
5
Y12
5
PB_Data 14
Y11
6
Y12
6
PB_Data 15
Y11
7
Y12
7
PB_Data 16
V11
0
V12
0
PB_Data 17
V11
1
V12
1
PB_Data 18
V11
2
V12
2
PB_Data 19
V11
3
V12
3
PB_Data 20
V11
4
V12
4
PB_Data 21
V11
5
V12
5
PB_Data 22
V11
6
V12
6
PB_Data 23
V11
7
V12
7
PB_Data 24 through to
PB_Data 31
-
-
-
-
42
iPORT NTx-W Embedded Video Interface User Guide
Pixel Bus Timing
The embedded video interface pixel bus transmits data from the camera to the embedded video interface
in a format similar to deserialized Camera Link Standard data, as shown in the following image.
Table 20: Sub-Clock Delays on the Camera Interface
Parameter
Symbol
Minimum
Maximum
Notes
PB_CLK high-level width
tCH
4.1 ns
N/A
N/A
PB_CLK low-level width
tCL
4.1 ns
N/A
N/A
PB_CLK frequency
fCP
20 MHz
120 MHz*
N/A
PB_CLK clock period
tCP
8.3 ns
N/A
N/A
PB_DATAx setup time
tDS
2 ns
N/A
By design
PB_DATAx hold time
tDH
2 ns
N/A
By design
PB_CTRL_OUTx pulse width
tCCP
30 ns
N/A
*To ensure optimal performance, ensure that the output data rate does not exceed 3.2 Gbps.
Pixel Bus Definitions and Timing
43
Pixel Bus Signals
The output of the camera must match the format of the embedded video interface. You should select a
case for your application and then refer to “Timing Values for All Cases” on page 46.
Case 1: FVAL and LVAL are Level-Sensitive
Case 2: FVAL and LVAL are Edge-Sensitive
When FVAL is edge sensitive, a rising edge (when rising-edge sensitive), or a falling edge (when fallingedge sensitive) signals the start of a frame. The frame ends either when all of the pixels have been acquired
(as set in the image height and width settings) or the next FVAL valid edge (rising edge when rising-edge
sensitive or falling edge when falling-edge sensitive) occurs. If the next FVAL valid edge occurs before all
of the pixels have been acquired, the embedded video interface generates a Line Missing status or a Partial
Line Missing error.
44
iPORT NTx-W Embedded Video Interface User Guide
Case 3: FVAL is Edge-Sensitive and LVAL is Level-Sensitive
When LVAL is edge sensitive, a rising edge (when rising-edge sensitive) or a falling edge (when fallingedge sensitive) signals the start of a new line. The end of the line occurs either once all of the pixels have
been acquired (as set in the image width settings) or the next LVAL valid edge (rising edge when risingedge sensitive or falling edge when falling-edge sensitive) occurs. If the next LVAL valid edge occurs before
all of the pixels of a line have been acquired, the embedded video interface generates a Partial Line Missing
error.
Pixel Bus Definitions and Timing
45
Timing Values for All Cases
The TCP (PB0_CLK period) timing values listed in the following table are minimum values only.
Table 21: TCP Timing Values for All Cases
From
To
Symbol
Case 1 (level)
(tcp)
Case 2 (edge)
(tcp)
Case 3 (both)
(tcp)
FVAL valid
LVAL valid a
tFV2LV
0b
0
1
FVAL valid
Data valid a,c,d
tFV2DV
0b
16 f
1
LVAL valid
Data valid a,c,d
tLV2DV
0
1
0
LVAL valid
LVAL invalid a
tLV2LI
1
1
1
LVAL invalid
LVAL valid a
tLI2LV
1
1
1
Data invalid
LVAL invalid
tDI2LI
0
N/A
0
a,c,d
LVAL invalid
FVAL invalid a
tLI2FI
0e
N/A
N/A
Data invalid
FVAL invalid
tDI2FI
0e
N/A
N/A
a,c,d
FVAL invalid
FVAL valid a
tFI2FV
1
1
1
FVAL invalid
Data valid a,c,d
tFI2DV
1
N/A
N/A
Last LVAL invalid
Data valid
tLLI2DV
16 f
N/A
16 f
FVAL valid
FVAL invalid
tFV2FI
16 f
1
1
FVAL valid
FVAL valid
t2FV2FV
17 f
17 f
17 f
a. The valid state of FVAL and LVAL is high when they are set as level-high sensitive or rising-edge
sensitive. Their valid state is low when they are set as level-low sensitive or falling-edge sensitive.
b. If LVAL is valid before FVAL becomes valid, the grabber drops the full line.
c. Data valid is defined by FVAL valid (note a), LVAL valid (note a), and DVAL valid (note d).
d. The valid state of DVAL is high when it is set as level-high sensitive, and low when set as level-low
sensitive. DVAL is always valid in the grabber when the PixelBusDataValidEnabled feature is off.
e. If FVAL becomes invalid and LVAL is still valid, the line is truncated.
f. This is a worst-case value. Subtract 3 cycles if the pixel type is 8-bit, 1-tap. Subtract 1 cycle for all
other pixel types except 10/12- bit, 2-tap, unpacked, and RGB unpacked. Subtract up to 7 cycles if
the image size is a multiple of 32 bytes.
46
iPORT NTx-W Embedded Video Interface User Guide
Chapter 4
Connecting to and Configuring the NTx-W
This chapter describes how to connect to the NTx-W Embedded Video Interface and configure general
settings.
The following topics are covered in this chapter:
• “Configuring Your Computer’s Wireless Adapter for use with the NTx-W” on page 48
• “Configuring Wireless Connectivity” on page 50
• “Connecting over Wireless Ethernet and Confirming Image Streaming” on page 52
• “Configuring the Buffers” on page 54
• “Providing the NTx-W with an IP Address” on page 54
• “Configuring an Automatic/Persistent IP Address” on page 55
• “Optimizing SDK Settings” on page 56
• “Viewing Wireless Link Quality” on page 59
• “Stream Warning, Device Dropped Images” on page 59
• “Restoring Default Wireless Configuration” on page 60
• “Configuring How Images are Acquired” on page 60
• “Updating Firmware Remotely” on page 65
Connecting to and Configuring the NTx-W
47
Configuring Your Computer’s Wireless Adapter for use with
the NTx-W
This section explains how to configure your computer’s wireless adapter for optimal performance with
the NTx-W. For tested wireless adapters and routers, see the NTx-W Embedded Video Interface Release
Notes, available on the Pleora Support Center at www.pleora.com.
The instructions in this section are based on the Windows 7 operating system. The steps may vary
depending on your computer’s operating system.
To configure the wireless adapter for optimal performance
1. In the Windows Control Panel, click Network and Internet.
2. Click Network and Sharing Center.
48
iPORT NTx-W Embedded Video Interface User Guide
3. In the left-hand panel, click Change adapter settings.
4. Right-click the wireless adapter and then click Properties.
5. Click Configure.
6. On the Advanced tab, enable the following properties (if they are available for your wireless
adapter): IEEE802.11h, Multimedia/Gaming Environment, Radio On/Off, and WMM Capable.
The exact configuration procedure and the available properties depend on the wireless adapter.
7. On the Power Management tab, clear the Allow the computer to turn off this device to save power
check box.
8. Close the open dialog boxes to apply the changes and close the Control Panel.
Connecting to and Configuring the NTx-W
49
Configuring Wireless Connectivity
The NTx-W Embedded Video Interface can wirelessly communicate with your computer in two different
modes. In StationForwarding mode, the NTx-W connects to the eBUS SDK over a wireless router. In
AccessPoint mode, the NTx-W directly connects to the eBUS SDK.
When factory default settings are applied to the NTx-W, it is in AccessPoint mode with no security preshared key (PSK) enabled, allowing you to quickly connect to change settings.
After you connect to the device, you can customize the SSID and PSK settings. You can also stream
images by following the instructions, “Connecting over Wireless Ethernet and Confirming Image
Streaming” on page 52.
After the appropriate wireless GenICam settings are configured for the desired mode, power cycle the
NTx-W Embedded Video Interface.
For more information about the NTx-W Embedded Video Interface wireless network GenICam settings, see
“Wireless GenICam Features” on page 11.
Configuring the NTx-W for Wireless Connectivity using an Off-the-Shelf
Router
In StationForwarding mode, the NTx-W connects to the eBUS SDK through a wireless router that acts
as the access point, as shown in the following diagram.
If connecting through an off-the-shelf wireless access point, the SSID, channel, channel width, and
security settings must match the access point to which the device will connect. To do this, configure the
following GenICam settings according to the router settings:
• WifiBridgeModeNext StationForwarding
• WifiAccessPointSSIDNext. Specify the SSID that the wireless access point is expecting.
• WifiSecurityModeNext. Specify the security that the wireless access point is configured to use
(either WPA2 or None). If configured to use WPA2, also configure the WifiPreSharedKey feature
to the security key expected by the wireless access point.
• WifiPrimaryChannelNext. Specify the channel that the wireless access point is configured to use.
Important: We recommend that you select a channel that is in the 5.2 GHz range to avoid a
crowded signal. Channels 40, 42, and 44 are in the 5.2 GHz range, for example.
50
iPORT NTx-W Embedded Video Interface User Guide
• WifiChannelWidthModeNext. Specify the channel width that the wireless access point is
configured to use.
The default security mode is None, which allows you to set up the NTx-W Embedded Video Interface and
stream imaging and video data quickly.
Configuring the NTx-W Access Point Settings
In access point mode, the NTx-W connects wirelessly directly to the eBUS SDK, as shown in the
following diagram.
The NTx-W Embedded Video Interface is in AccessPoint mode by default. The following GenICam
AccessPoint parameters are programmed by Pleora:
• WifiPrimaryChannelNext: 6
• WifiChannelWidthModeNext: 20
• WifiAccessPointSSIDNext: Pleora prefix (PTNTXW-), followed by the radio module MAC
address. For example, PTNTXW-000E8E4DAE0F.
• WifiBridgeModeNext: AccessPoint
• WifiPreSharedKey: asdfg1234567890
• WifiSupportedCypherNext: None
• WifiSecurityModeNext: None
• WifiProtocolNext: gn
• WifiCountryCodeNext: 841
As mentioned previously, once you have established a connection you can update the GenICam
parameters. For information about how to restore the default settings, see “Restoring Default Wireless
Configuration” on page 60.
Connecting to and Configuring the NTx-W
51
Connecting over Wireless Ethernet and Confirming Image
Streaming
This section explains how to connect the NTx-W Embedded Video Interface to wireless Ethernet and
confirm that images are streaming. If connecting through a router, the wireless connection is made
automatically as soon as the NTx-W powers up. If the NTx-W is set up as an access point, you must
wirelessly connect to the NTx-W from your computer. Once the wireless connection has been established,
you can connect to the NTx-W using eBUS Player.
To wirelessly connect the computer to the NTx-W in AccessPoint mode
1. On the computer, open the Wireless Network Connection window.
2. Locate the NTx-W wireless network, for example, PTNTXW-000E8E3829DD, and click
Connect.
When the NTx-W is in AccessPoint mode, it does not have DHCP Server capabilities and will not
automatically provide an IP address. The Windows error message that appears stating that the connection
was unsuccessful is not valid in this case and the NTx-W is connected. The connection status in the
Wireless Network Connection window may also appear as limited for the same reason.
To connect over Wireless Ethernet and confirm video streaming
1. Start eBUS Player and click Select/Connect.
2. If the NTx-W does not appear in the list, click the Show unreachable GigE Vision Devices check
box to show all devices.
3. In the GigE Vision Device Selection dialog box, select the NTx-W.
52
iPORT NTx-W Embedded Video Interface User Guide
4. Click OK.
eBUS Player is now connected to the device.
5. Click Play to stream images.
6. After you confirm that images are streaming, close eBUS Player.
Connecting to and Configuring the NTx-W
53
Configuring the Buffers
You can increase the buffer count using eBUS Player to make streaming more robust. A high number of
buffers are needed in high frame rate applications, while a small number of buffers are needed for lower
frame rates. Latency increases as the number of buffers increases. For more information about
determining the values to specify, see “Ensuring Adequate Storage for Multiple Images” on page 58.
To configure the buffers
1. Start eBUS Player.
2. Click Tools > Buffer Options.
3. Click the buffer option that suits your requirements.
4. Click OK.
Default size for streaming is 16 buffers.
Providing the NTx-W with an IP Address
The NTx-W requires an IP address to communicate on a video network. This address must be on the
same subnet as the computer network interface card (NIC) that is performing the configuration and
receiving the image stream.
To provide the NTx-W with an IP address
1. Start eBUS Player and click Select/Connect.
54
iPORT NTx-W Embedded Video Interface User Guide
If the device does not appear in the list, click the Show unreachable GigE Vision Devices check box
to show all devices.
2. In the GigE Vision Device Selection dialog box, select the NTx-W.
3. Click Set IP Address.
4. Provide the NTx-W with a valid IP address and subnet mask. You can optionally provide a default
gateway.
If you are using a unicast network configuration, the management software/data receiver and the NTx-W
must be on the same subnet.
5. Click OK to close the Set IP Address dialog box.
6. Click OK to close the GigE Vision Device Selection dialog box.
Configuring an Automatic/Persistent IP Address
The Device Control dialog box in eBUS Player allows you to configure a persistent IP address for the
NTx-W. Alternatively, the NTx-W can be configured to automatically obtain an IP address using
Dynamic Host Configuration Protocol (DHCP) or Link Local Addressing (LLA). The NTx-W uses its
persistent IP address first, but if this option is set to False, it can be configured to attempt to obtain an
address from a DHCP server. If this fails, it will use LLA to find an available IP address. LLA cannot be
disabled and is always set to True.
To configure a persistent IP address
1. Start eBUS Player and connect to the NTx-W.
2. Click Device control in the Parameters and Controls section.
3. In the TransportLayerControl category, set the GevCurrentIPConfigurationPersistentIP feature
to True.
4. Set the GevPersistentIPAddress feature to a valid IP address in the GevPersistentIPAddress field.
5. Set the GevPersistentSubnetMask feature to a valid subnet mask address.
6. Optionally, enter a valid default gateway in the GevPersistentDefaultGateway field.
7. Close the Device Control dialog box.
8. Power cycle the NTx-W.
To automatically configure an IP address
1. Start eBUS Player and connect to the NTx-W.
2. Click Device control in the Parameters and Controls section.
3. In the TransportLayerControl category, set the GevCurrentIPConfigurationPersistentIP feature
to False.
4. Set the GevCurrentIPConfigurationLLA and/or GevCurrentIPConfigurationDHCP values to
True, depending on the type of automatic addressing you require.
5. Close the Device Control dialog box.
6. Power cycle the NTx-W.
Connecting to and Configuring the NTx-W
55
Optimizing SDK Settings
Some of the default SDK parameters may need to be modified depending on your network traffic profile
and topology. If you are experiencing imaging and video transfer issues due to lost packets or a poor
connection between the NTx-W and eBUS Player (or your custom application), we recommend that you
use customized SDK settings. These settings are based on the assumption that all acquired images can fit
in the NTx-W frame buffer.
Improving Stream Reliability
In situations where the network infrastructure cannot keep up with the packets coming from the device,
you can adjust the following two features: GevStreamThroughputLimit and GevSCPD. The
GevStreamThroughputLimit feature limits the peak bit rate that will be streamed out by the device. The
GevSCPD value (which controls the delay to insert between each packet) is calculated based on the value
of GevStreamThroughputLimit, and vice versa.
By default, the GevStreamThroughputLimit is set to 2000 Mbps, which provides a reliable data rate for
most systems.
To access the GevStreamThroughput feature, click Device control in eBUS Player. Ensure you select the
Expert or Guru visibility level.
Preventing Connection Loss
The connection between eBUS Player and the NTx-W can be lost if the configured eBUS Player heartbeat
timeout period expires. By default, eBUS Player has the following communication parameters: the
AnswerTimeout value is 1000 and the CommandRetryCount value is 3. Because the NTx-W uses a
wireless connection, which can lose packets, we recommend that you set the AnswerTimeout value to
100 and the CommandRetryCount value to 50.
To access the AnswerTimeout and CommandRetryCount features, click Communication control in eBUS
Player.
Encouraging Packet Resends
There is a higher possibility of packet loss over a wireless connection, and therefore a higher expectation
for packet resends. In some applications, images are not transferred continuously but rather via multiframe acquisition, with breaks between acquisitions. In some instances, the amount of time required to
transfer images is less important than image integrity.
The default eBUS Player settings are intended for continuous streaming applications with few resend
requests. The following settings are recommended for multi-frame acquisition as well as any readout
56
iPORT NTx-W Embedded Video Interface User Guide
mode, and remove the limit on the number of packet resends requested and sent, encouraging the system
to request resends when they are required.
Table 22: Recommended Packet Resend Settings
Parameter
eBUS Player default
Recommended setting
MaximumPendingResends
45
0
MaximumResendRequestRetryByPacket
3
0
MaximumResendGroupSize
15
0
ResendRequestTimeout
5000
200
To access the features described in the table above, click Image stream control in eBUS Player. Ensure
you select the Guru visibility level.
Increasing Time Period to Transfer Images
By default, the RequestTimeout value is 5000 ms. By increasing the value to 10000, you allow the system
more time to successfully send the complete image.
By default, the ResetOnIdle value is 200 ms. By increasing the value to 2000, you allow the computer
more time to receive all of the packets for a particular image before timing out.
These settings are not recommended for use when acquisitionmode=continuousacquisition.
To access the RequestTimeout and ResetOnIdle features, click Image stream control in eBUS Player.
Ensure you select the Guru visibility level.
Connecting to and Configuring the NTx-W
57
Ensuring Adequate Storage for Multiple Images
To ensure you have adequate space to store multiple images, you should adjust the buffer options using
eBUS Player. There are two buffer options that you should configure, which are described in this section:
Buffers used for streaming and Default buffer size.
You can configure the buffer options in eBUS Player by selecting Buffer Options on the Tools menu.
Calculating the Value for the Buffers Used for Streaming Option
You should ensure that the number of available buffers on the computer is set to at least as many images
as the NTx-W can store. This setting depends on the image size.
To understand how you calculate the number of images the NTx-W can store, review the following
example:
Example:
Height: 2000 pixels
Width: 2000 pixels
PixelFormat: Mono16
Payload size: The payload size, which is a function of height, width, and pixel format, can be viewed
by clicking Device control in eBUS Player. It appears under ImageFormatControl. Based on the
information above, the payload size (the amount of memory for one frame of the image) is 8000000
bytes (or 8 MB) in this example.
NTx-W available onboard memory: 120 MB
Using the payload size and available onboard memory, complete the calculation in “Calculating How
Many Images Can be Stored in Onboard Memory” on page 65. You will find that the NTx-W can store
up to 15 images in this example.
In this example, the Buffers used for streaming option should be set to 15 buffers.
58
iPORT NTx-W Embedded Video Interface User Guide
Calculating the Value for the Default Buffer Size Option
The Default buffer size is used to allocate pipeline buffers. To determine the value to enter for this option,
use the following formula:
Default buffer size (bytes) = height x width x bytes per pixel
Example:
Height: 2000 pixels
Width: 2000 pixels
PixelFormat: Mono16
*Bits per pixel: 16
*Bytes per pixel: 2
Default buffer size (bytes) = 2000 pixels x 2000 pixels x 2 bytes
* Tip: You can calculate the number of bytes per pixel by dividing the number of bits per pixel by 8. To
see the number of bits per pixel for the selected pixel format, click Device control in eBUS Player. The
bits per pixel appears under ImageFormatControl > PixelSize.
Viewing Wireless Link Quality
The NTx-W Embedded Video Interface provides a visible and configurable indication of wireless link
quality. The link quality can be read at any time from the WifiLinkQualityStatus parameter.
To program the visible indication, you can configure a link quality threshold in the
WifiLinkQualityThreshold GenICam node. The LINK_QUALITY output is active whenever there is a
valid wireless connection and the link quality is above that threshold.
Stream Warning, Device Dropped Images
In cases where the image data rate is too high for the wireless bandwidth, you will receive “device dropped
images” warnings. This indicates that the device has dropped blocks (images) and cannot transmit all of
the images received from the sensor.
Connecting to and Configuring the NTx-W
59
Restoring Default Wireless Configuration
The image below shows the location of the Restore Default Wireless Configuration button, which can be
used to reset the wireless driver to default values. This is useful to recover from an invalid wireless
configuration.
Restore Default Wireless
Configuration Button
You can also restore the default settings by clicking on the WifiResetDefaults GenICam node. You must
then power-cycle the device, for the new settings to take effect. To view the default settings, see
“Configuring the NTx-W Access Point Settings” on page 51.
Default wireless settings are initially programmed during production. However, if the radio module is
changed, you must update the WifiAccessPointSSIDNext setting. The default
WifiAccessPointSSIDNext value is automatically re-initialized with the new radio module MAC address
when the device is powered up with the new radio module; no user intervention is required.
You must click on the WifiResetDefaults GenICam node to use the default values, as described above.
Configuring How Images are Acquired
Depending on the device you use, eBUS Player provides you with a list of image acquisition modes. The
modes allow you to acquire images continuously or frame-by-frame. You can also save images to the
embedded video interface’s onboard memory so that you can retrieve them later.
60
iPORT NTx-W Embedded Video Interface User Guide
Modes Standard on Most GigE Vision-Compliant Devices
Continuous, SingleFrame, and MultiFrame modes are usually standard for embedded video interfaces.
Acquisition starts when the Play button is pressed (the AcquisitionStart command is executed).
Connecting to and Configuring the NTx-W
61
Continuous Mode
This mode allows you to acquire images continuously and is the default mode for most embedded video
interfaces.
Multiframe Mode
This mode allows you to acquire a fixed number of images. To configure the number of images, set the
embedded video interface’s AcquisitionControl > AcquisitionFrameCount feature.
You can set the AcquisitionControl > AcquisitionFrameCount feature in the Device Control dialog box,
as shown in the following image.
SingleFrame Mode
This mode allows you to acquire a single image.
62
iPORT NTx-W Embedded Video Interface User Guide
Recording and Readout Modes, Available on Pleora Devices
The recording acquisition modes allow you to capture images from a camera and store them in the
embedded video interface’s onboard memory. The readout acquisition modes allow images to be acquired
from the device’s memory at a slower rate, ensuring images are not lost.
These modes are helpful when you are working with a camera that transmits images at a rate that exceeds
the connection between the embedded video interface and the computer, resulting in dropped images. By
using the recording and readout modes, you can capture and stream images from the camera without
losing any images (as long as there is space in the onboard memory).
The recording acquisition modes (ContinuousRecording, MultiFrameRecording, and
SingleFrameRecording) support back-to-back recording, which allows you to click the Stop and Play
buttons multiple consecutive times without clearing the onboard memory.
Acquisition starts when the Play button is pressed (the AcquisitionStart command is executed) when one
of the recording modes is selected.
Images can be stored in the embedded video interface’s onboard memory as long as there is space or until
there are 512 images in memory. For information about calculating how many images you can store, see
“Calculating How Many Images Can be Stored in Onboard Memory” on page 41.
Understanding When Images are Removed from the Onboard Memory
The following actions remove the images from the embedded video interface’s onboard memory:
• Streaming images from the onboard memory using one of the readout acquisition modes
(ContinuousReadout or SingleFrameReadout).
• Power cycling the device, which clears all images from the onboard memory.
• Making any of the following AcquisitionMode changes and then clicking the Play button
(AcquisitionStart command):
Table 23: Changes that Clear Images from the Onboard Memory
First you acquire images with...
And then you change the Acquisition mode to...
ContinuousRecording, MultiFrameRecording, or
SingleFrameRecording
Continuous, MultiFrame, or SingleFrame
SingleFrameReadout or ContinuousReadout
SingleFrame, MultiFrame, or Continuous
SingleFrameReadout or ContinuousReadout
ContinuousRecording, MultiFrameRecording, or
SingleFrameRecording
ContinuousRecording Mode
With this mode, images are acquired continuously and are stored in the device’s onboard memory until
the memory is full (or 512 images are stored in onboard memory). When this limit is reached, the
embedded video interface stops acquiring new images from the camera.
Connecting to and Configuring the NTx-W
63
We recommend that you observe AcquisitionControl > BlockBufferCount (Expert or Guru visibility
level is required). When the value for this feature stops increasing, the memory is full. For information
about the actions that clear the images from onboard memory, see “Understanding When Images are
Removed from the Onboard Memory” on page 39.
To determine how many images can be stored in memory, see “Calculating How Many Images Can be
Stored in Onboard Memory” on page 41 .
ContinuousReadout Mode
With this mode, images are continuously read (and removed) from the device’s onboard memory. The
readout begins at the first image in memory. To see the number of images stored in onboard memory, see
AcquisitionControl > BlockBufferCount in the Device Control dialog box (Expert or Guru visibility
level is required).
Readout continues until the Stop button is pressed (AcquisitionStop command is executed) or until the
last image has been sent by the device (BlockBufferCount will be 0).
MultiFrameRecording Mode
With this mode, a fixed number of images are stored in the device’s onboard memory. To configure the
number of images, set the AcquisitionControl > AcquisitionFrameCount feature in the Device Control
dialog box. Images can be read out from memory using ContinuousReadout mode.
A maximum of 512 images can be acquired at one time in MultiFrameRecording mode.
To determine how many images can be stored in memory, see “Calculating How Many Images Can be
Stored in Onboard Memory” on page 41.
If AcquisitionControl > AcquisitionFrameCount is set to a value that exceeds the amount of available
memory, the embedded video interface stops acquiring new images when the onboard memory is full (or
512 images are stored in onboard memory).
BlockBufferCount shows the number of images currently in memory. In MultiFrameRecording mode,
this number is cumulative: If the memory is empty and you acquire an image, BlockBufferCount will
match the AcquisitionFrameCount. If you stop and restart recording, BlockBufferCount will increment
(to a maximum of 512 images, depending on the image size) and will no longer match the
AcquisitionFrameCount.
For information about the actions that clear the images from onboard memory, see “Understanding
When Images are Removed from the Onboard Memory” on page 39.
64
iPORT NTx-W Embedded Video Interface User Guide
SingleFrameRecording Mode
With this mode, a single image is saved in the embedded video interface’s onboard memory after each
AcquisitionStart command.
For information about the actions that clear the images from onboard memory, see “Understanding
When Images are Removed from the Onboard Memory” on page 39 .
SingleFrameReadout Mode
With this mode, a single image is acquired from the embedded video interface’s onboard memory.
Calculating How Many Images Can be Stored in Onboard Memory
First, take note of the PayloadSize, which appears under TransportLayerControl in the Device Control
dialog box. Expert or Guru visibility level is required to access this feature.
The PayloadSize is automatically calculated by the device based on the selected image settings, which
include Width, Height, OffsetX, OffsetY, PixelSize, any chunk data, as well as any padding that has to be
added to the image payload.
For example, for a device configured to use Mono10p with images that are 1920 x 1080, the PayloadSize
is equal to 2 592 000 bytes per image or 2 472 MB (2 592 000 / 1 048 576).
After determining PayloadSize, you can use the following equation to determine the number of images
that can be saved in onboard memory:
Available onboard memory MB / PayloadSize MB = Number of images that can be saved
Using our example, the equation is:
120 MB / 2 472 MB = 48 images
Updating Firmware Remotely
Update procedures for the NTx-W Embedded Video Interface are documented in the Updating Pleora
Firmware Application Note, available on the Pleora Support Center at www.pleora.com/support-center.
Connecting to and Configuring the NTx-W
65
Chapter 5
Reference: Supported Country Codes
This chapter provides a list of the country codes supported by the NTx-W Embedded Video Interface.
To change a country code
1. Start eBUS Player and connect to the NTx-W.
2. Click Device control in the Parameters and Controls section.
3. In the WirelessControl category, select WifiCountryCodeNext and enter a valid country code.
Reference: Supported Country Codes
67
The following error message appears if an invalid country code is entered.
After a valid country code is entered, the NTx-W Embedded Video Interface restarts.
List of Valid Country Codes
The following country codes are supported by the iPORT NTx-W Embedded Video Interface.
68
Albania, 8
Japan (J44), 4044
Algeria, 12
Japan (J45), 4045
Argentina, 32
Japan (J46), 4046
Armenia, 51
Japan (J47), 4047
Aruba, 533
Japan (J48), 4048
Australia, 5000
Japan (J49), 4049
Azerbaijan, 31
Japan (J50), 4050
Bahrain, 48
Japan (J51), 4051
Bangladesh, 50
Japan (J52), 4052
Barbados, 52
Japan (J53), 4053
Belarus, 112
Japan (J54), 4054
Belgium, 56
Japan (J55), 4055
Belgium/Cisco implementation 5002
Japan (J56), 4056
Belize, 84
Japan (J57), 4057
Bolivia, 68
Japan (J58), 4058
Bosnia and Herzegowina, 70
Japan (J59), 4059
Brazil, 76
Japan (J7), 4007
Brunei Darussalam, 96
Japan (J8), 4008
Bulgaria, 100
Japan (J9), 4009
Cambodia, 116
Japan (JE1), 396
Canada (2)5001
Japan (JE2), 397
Chile, 152
Japan (JP0), 394
Colombia, 170
Japan (JP1), 393
Costa Rica, 188
Japan (JP1-1), 395
Croatia, 191
Japan (JP6), 4006
Cypress, 196,
Japan, 392
Czech Republic, 203
Jordan, 400
Denmark, 208
Kazakhstan, 398
Dominican Republic, 214
Kenya, 404
iPORT NTx-W Embedded Video Interface User Guide
Ecuador, 218
Kuwait, 414
Egypt, 818
Latvia, 428
El Salvador, 222
Lebanon, 422
Estonia, 233
Liechtenstein, 438
Finland, 246
Lithuania, 440
France, 250
Luxembourg, 442
Georgia, 268
Macau SAR, 446
Germany, 276
Malaysia, 458
Greece, 300
Malta, 470
Greenland, 304
Mexico, 484
Grenada, 308
Montenegro, 499
Guam, 316
Morocco, 504
Guatemala, 320
Nepal, 524
Haiti, 332
Netherlands, 528
Honduras, 340
Netherlands-Antilles, 530
Hong Kong S.A.R., P.R.C., 344
New Zealand, 554
Hungary, 348
North Korea, 408
Iceland, 352
Norway, 578
India, 356
Oman, 512
Indonesia, 360
Panama, 591
Iran, 364
Papua New Guinea, 598
Ireland, 372
People’s Republic of China, 156
Islamic Republic of Pakistan, 586
Peru, 604
Israel, 376
Poland, 616
Italy, 380
Portugal, 620
Jamaica, 388
Principality of Monaco, 492
Japan (J10), 4010
Puerto Rico, 630
Japan (J11), 4011
Qatar, 634
Japan (J12), 4012
Republic of Serbia, 688
Japan (J13), 4013
Republic of the Philippines, 608
Japan (J14), 4014
Romania, 642
Japan (J15), 4015
Russia, 643
Japan (J16), 4016
Rwanda, 646
Japan (J17), 4017
Saudi Arabia, 682
Japan (J18), 4018
Singapore, 702
Japan (J19), 4019
Slovak Republic, 703
Japan (J20), 4020
Slovenia, 705
Japan (J21), 4021
South Africa, 710
Japan (J22), 4022
South Korea, 412
Japan (J23), 4023
Spain, 724
Japan (J24), 4024
Sri Lanka, 144
Japan (J25), 4025
Sweden 752
Reference: Supported Country Codes
69
70
Japan (J26), 4026
Switzerland, 756
Japan (J27), 4027
Syria, 760
Japan (J28), 4028
Taiwan, 158
Japan (J29), 4029
Thailand, 764
Japan (J30), 4030
The Former Yugoslav Republic of Macedonia, 807
Japan (J31), 4031
Trinidad y Tobago, 780
Japan (J32), 4032
Tunisia, 788
Japan (J33), 4033
Turkey, 792
Japan (J34), 4034
U.A.E., 784
Japan (J35), 4035
Ukraine, 804
Japan (J36), 4036
United Kingdom, 826
Japan (J37), 4037
United States, 841
Japan (J38), 4038
Uruguay, 858
Japan (J39), 4039
Uzbekistan, 860
Japan (J40), 4040
Venezuela, 862
Japan (J41), 4041
Vietnam, 704
Japan (J42), 4042
Yemen, 887
Japan (J43), 4043
Zimbabwe, 716
iPORT NTx-W Embedded Video Interface User Guide
Chapter 6
Reference: Wireless Range Testing
The reliability of, and bandwidth available on a wireless link is affected by numerous factors, including:
• The distance between the transmitter and receiver
• The number of devices operating on the same wireless band and channel
• The number and quality of antennae on all devices on the network (including wireless access points)
Pleora has performed characterization tests to determine the potential throughput of the NTx-W at a
variety of distances and resolutions. The following tables describe the results of these tests. In all cases, the
following equipment was used:
A computer with:
• Windows 7 operating system
• eBUS SDK version 4.04
• D-Link DWA-566 Wireless N 300 Dual Band PCIe Desktop Adapter
For all tests where WifiBridgeModeCurrent=AccessPoint:
• Wireless access point: Netgear N750 Wireless Dual Band Gigabit Router WNDR 4000
All tests used a RequestTimeout value of 100000 and a frequency of 5.18GHz. All measurements are in
feet.
Pleora performed these tests under specific conditions, which may differ from your test or production
environment. Your test results may not match the Pleora test results exactly.
Reference: Wireless Range Testing
71
Test Results
The following tables present the NTx-W wireless range test results.
Test #1: AccessPoint Mode, Distance 80 Feet
• WifiBridgeModeCurrent=AccessPoint
• ChannelWidth: HT40
• Channel: Channel 36
• Frequency: 5.18GHz
• Security: None
• PacketSize: 1444
• SCPD: 3034
• Distance: 80'
• RequestTimeout: 100000
• Voltage: 12
Table 24: Wireless Range Test #1 Results
72
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
640
480
Mono8
24.47
60.13
640
480
Mono8
25.52
62.72
640
480
Mono8
25.28
62.13
320
240
Mono8
99.83
61.34
320
240
Mono8
102.36
62.28
320
240
Mono8
107.96
66.33
1280
800
Mono8
7.6
62.28
1280
800
Mono8
7.58
62.09
1280
800
Mono8
7.62
62.45
1920
1080
Mono8
3.87
64.13
1920
1080
Mono8
3.91
64.91
1920
1080
Mono8
3.97
65.93
3840
2160
Mono8
0.99
65.54
3840
2160
Mono8
0.98
65.02
3840
2160
Mono8
0.93
61.91
5120
2160
Mono8
0.69
60.77
5120
2160
Mono8
0.66
58.51
iPORT NTx-W Embedded Video Interface User Guide
Table 24: Wireless Range Test #1 Results (Continued)
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
5120
2160
Mono8
0.7
62.09
5120
2160
RGB8
0.26
68.67
Test #2: StationForward Mode, Distance 80 Feet
• WifiBridgeModeCurrent=StationForward
• ChannelWidth: 40
• Channel: Channel 36
• Frequency: 5.18GHz
• Security: WPA2
• PacketSize: 1444
• SCPD: 3000
• Distance: 80
• RequestTimeout: 100000
• Voltage: 12
Table 25: Wireless Range Test #2 Results
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
640
480
Mono8
28.42
69.85
640
480
Mono8
29.33
72.08
640
480
Mono8
29.64
72.85
320
240
Mono8
119.36
73.33
320
240
Mono8
121.31
74.53
3200
240
Mono8
119.13
73.2
1280
800
Mono8
9.29
76.14
1280
800
Mono8
9.06
7425
1280
800
Mono8
9.19
75.29
1920
1080
Mono8
4.64
76.91
1920
1080
Mono8
4.72
78.22
1920
1080
Mono8
4.54
75.26
3840
2160
Mono8
0.93
61.59
3840
2160
Mono8
0.97
64.3
3840
2160
Mono8
0.97
65.2
5120
2160
Mono8
0.6
52.76
Reference: Wireless Range Testing
73
Table 25: Wireless Range Test #2 Results (Continued)
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
5120
2160
Mono8
0.8
70.59
5120
2160
Mono8
0.63
56.11
5120
2160
RGB8
0.23
59.88
Test #3: StationForward Mode, Distance 40 Feet
• WifiBridgeModeCurrent=StationForward
• ChannelWidth: 40
• Channel: 36
• Frequency: 5.18GHz
• Security: WPA2
• PacketSize: 1444
• SCPD: 3000
• Distance: 40
• RequestTimeout: 100000
• Voltage: 12
Table 26: Wireless Range Test #3 Results
74
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
640
480
Mono8
3.18
74.18
640
480
Mono8
30.69
75.44
640
480
Mono8
27.91
68.6
320
240
Mono8
122.36
75.18
320
240
Mono8
122.44
75.22
320
240
Mono8
130.47
80.16
1280
800
Mono8
9.01
83.78
1280
800
Mono8
9.09
84.47
1280
800
Mono8
6.76
55.26
1920
1080
Mono8
4.2
69.6
1920
1080
Mono8
3.51
58.27
1920
1080
Mono8
4.63
76.84
3840
2160
Mono8
1.03
69.67
3840
2160
Mono8
1.05
69.95
3840
2160
Mono8
0.71
47.14
iPORT NTx-W Embedded Video Interface User Guide
Table 26: Wireless Range Test #3 Results (Continued)
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
5120
2160
Mono8
0.74
65.09
5120
2160
Mono8
0.61
54.11
5120
2160
Mono8
0.79
69.65
5120
2160
RGB8
0.24
62.46
Test #4: AccessPoint Mode, Distance 40 Feet
• WifiBridgeModeCurrent=AccessPoint
• ChannelWidth: 40
• Channel: Channel 36/40
• Frequency: 5.18GHz
• Security: None
• PacketSize: 1444
• SCPD: 3000
• Distance: 40
• RequestTimeout: 100000
• Voltage: 12
Table 27: Wireless Range Test #4 Results
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
640
480
Mono8
50.16
123.27
640
480
Mono8
50.52
124.15
640
480
Mono8
48.8
119.93
320
240
Mono8
197.78
121.52
320
240
Mono8
169.11
103.9
320
240
Mono8
173.33
106.49
1280
800
Mono8
14.87
121.82
1280
800
Mono8
15.93
130.47
1280
800
Mono8
16.11
131.95
1920
1080
Mono8
4.82
79.91
1920
1080
Mono8
5.51
91.36
1920
1080
Mono8
5.54
91.98
3840
2160
Mono8
5.31
86.93
3840
2160
Mono8
1.14
75.62
3840
2160
Mono8
1.4
93.09
Reference: Wireless Range Testing
75
Table 27: Wireless Range Test #4 Results (Continued)
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
5120
2160
Mono8
0.92
81.1
5120
2160
Mono8
0.79
78.47
5120
2160
Mono8
0.92
81.66
5120
2160
RGB8
0.4
107.32
Test #5: AccessPoint Mode, Distance 0 Feet
• WifiBridgeModeCurrent=AccessPoint
• ChannelWidth: 40
• Channel: 40
• Frequency: 5.18GHz
• Security: None
• PacketSize: 1444
• SCPD: 3000
• Distance: 0
• RequestTimeout: 100000
• Voltage: 12
Table 28: Wireless Range Test #5 Results
76
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
640
480
Mono8
66
162.2
640
480
Mono8
51.45
126.44
640
480
Mono8
50.74
124.7
320
240
Mono8
267.49
164.34
320
240
Mono8
256.64
157.68
320
240
Mono8
266.27
163.6
1280
800
Mono8
20.16
165.16
1280
800
Mono8
19.17
157.02
1280
800
Mono8
19.08
156.34
1920
1080
Mono8
10.06
166.93
1920
1080
Mono8
9.5
157.54
1920
1080
Mono8
7.94
131.65
3840
2160
Mono8
2.1
139.22
3840
2160
Mono8
2.49
165.38
3840
2160
Mono8
2.49
165.03
iPORT NTx-W Embedded Video Interface User Guide
Table 28: Wireless Range Test #5 Results (Continued)
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
5120
2160
Mono8
1.38
122.42
5120
2160
Mono8
1.37
120.9
5120
2160
Mono8
1.51
133.29
5120
2160
RGB8
1.53
140.99
Test #6: StationForward Mode, Distance 0 Feet
• WifiBridgeModeCurrent=StationForward
• ChannelWidth: 40
• Channel: 40
• Frequency: 5.18GHz
• Security: WPA2
• PacketSize: 1444
• SCPD: 3000
• Distance: 0
• RequestTimeout: 100000
• Voltage: 12
Table 29: Wireless Range Test #5 Results
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
640
480
Mono8
49.86
122.54
640
480
Mono8
54.05
132.84
640
480
Mono8
53.52
131.53
320
240
Mono8
187.11
114.96
320
240
Mono8
192.98
118.57
320
240
Mono8
190.08
116.79
1280
800
Mono8
15.56
127.49
1280
800
Mono8
15.18
124.32
1280
800
Mono8
15.51
127.08
1920
1080
Mono8
7.56
125.41
1920
1080
Mono8
7.41
122.84
1920
1080
Mono8
7.2
119.37
3840
2160
Mono8
7.94
128.7
3840
2160
Mono8
7.88
124.97
3840
2160
Mono8
7.92
127.27
Reference: Wireless Range Testing
77
Table 29: Wireless Range Test #5 Results (Continued)
78
Width (Pixels)
Height (Pixels)
PixelFormat
FPS
BW (Mbps)
5120
2160
Mono8
1.32
117.09
5120
2160
Mono8
1.36
120.3
5120
2160
Mono8
1.3
114.74
5120
2160
RGB8
0.47
123.91
iPORT NTx-W Embedded Video Interface User Guide
Chapter 7
Technical Support
On the Pleora Support Center, you can:
• Download the latest software.
• Log a support issue.
• View documentation for current and past releases.
• Browse for solutions to problems other customers have encountered.
• Get presentations and application notes.
• Get the latest news and information about our products.
• Decide which of Pleora’s products work best for you.
To visit the Pleora Support Center
• Go to www.pleora.com and click Support Center.
If you have not registered yet, you are prompted to register.
Accounts are usually validated within one business day.
Technical Support
79