FLIR
LEPTON® Engineering Datasheet
The information contained herein does not contain technology as defined by the EAR, 15 CFR 772, is publicly available,
and therefore, not subject to EAR. NSR (6/14/2018).
Information on this page is subject to change without notice.
Lepton Engineering Datasheet, Document Number: 500-0659-00-09 Rev: 203
54
4.2.3
VoSPI Protocol
–
Lepton 3.0 and 3.5
The Lepton 3 VoSPI is built on a collection of object types as defined hierarchically below.
▪
VoSPI Packet
:
The Lepton 3 VoSPI protocol is based on a single standardized VoSPI packet, the minimum
“transaction” between master and slave. Each video packet contains data
for a single video line or
telemetry line. In addition to video packets, the VoSPI protocol includes discard packets that are provided
when no video packets are available.
▪
VoSPI Segment
: A VoSPI segment is defined as a continuous sequence of VoSPI packets consisting of
one quarter of a frame of pixel data. To maintain synchronization, it is necessary to read out each
VoSPI segment before the next is available.
▪
VoSPI Stream
: A VoSPI stream is defined as a continuous sequence of VoSPI segments.
, the packet length and number of packets per frame vary depending upon two
runtime user selections, telemetry mode and bit resolution.
▪
Telemetry mode:
▪
Telemetry disabled (default)
▪
Telemetry enabled
▪
Video Format mode:
▪
Raw14 (default)
▪
RGB888
Table 12 - Packet Length and Number of Video Packets per Frame as a Function of User Settings
Video Format Mode
Telemetry Mode
Telemetry Disabled
Telemetry Enabled
Raw14
Packet length: 164 bytes
Video packets per frame: 60
Packet length: 164 bytes
Video packets per segment:
61
RGB888
Packet length: 244 bytes
Video packets per frame: 60
N/A
4.2.3.1
VoSPI Packets
As depicted in
, each packet contains a 4-byte header followed by either a 160-byte or 240-byte
payload. Note that because the payload size differs between video formats, the setting should be selected
before
