• Support Home
  • Getting Started
    • Connecting Your Camera
    • 3rd Party Software Getting Started Guides
  • Tech Ref Manuals
    • Arena SDK Documentation
    • HTP003S – Helios2+ ToF 3D
    • HLT003S – Helios2 ToF 3D
    • HLS003S – Helios ToF 3D
    • HLF003S – Helios Flex ToF 3D
    • ATX245S – Atlas10 24.5 MP
    • ATX204S – Atlas10 20.4 MP
    • ATX162S – Atlas10 16.2 MP
    • ATX124S – Atlas10 12.3 MP
    • ATX081S – Atlas10 8.1 MP
    • ATX051S – Atlas10 5.0 MP
    • ATL314S – Atlas 31.4 MP
    • ATL196S – Atlas 19.6 MP
    • ATL168S – Atlas 16.8 MP
    • ATL120S – Atlas 12.3 MP
    • ATL089S – Atlas 8.9 MP
    • ATL071S – Atlas 7.1 MP
    • ATL050S – Atlas 5.0 MP
    • ATL028S – Atlas 2.8 MP
    • ATP200S – Atlas IP67 20 MP
    • ATP120S – Atlas IP67 12.3 MP
    • ATP089S -Atlas IP67 8.9 MP
    • ATP071S – Atlas IP67 7.1 MP
    • ATP028S – Atlas IP67 2.8 MP
    • TRI200S – Triton 20.0 MP
    • TRI120S – Triton 12.3 MP
    • TRI122S – Triton 12.2 MP
    • TRI089S – Triton 8.9 MP
    • TRI071S – Triton 7.1 MP
    • TRI064S – Triton 6.3 MP
    • TRI054S – Triton 5.4 MP
    • TRI050S-P/Q – Triton 5.0 MP Polarized
    • TRI050S – Triton 5.0 MP
    • TRI032S – Triton 3.2 MP
    • TRI028S – Triton 2.8 MP
    • TRI023S – Triton 2.3 MP
    • TRI016S – Triton 1.6 MP
    • TRI005S – Triton 0.5 MP
    • TRI004S – Triton 0.4 MP
    • TRI02KA – Triton 2K Line Scan
    • PHX200S – Phoenix 20.0 MP
    • PHX120S – Phoenix 12.3 MP
    • PHX122S – Phoenix 12.2 MP
    • PHX089S – Phoenix 8.9 MP
    • PHX064S – Phoenix 6.3 MP
    • PHX050S-P/Q – Phoenix 5.0 MP Polarized
    • PHX050S – Phoenix 5.0 MP
    • PHX032S – Phoenix 3.2 MP
    • PHX023S – Phoenix 2.3 MP
    • PHX016S – Phoenix 1.6 MP
    • PHX004S – Phoenix 0.4 MP
  • Application Notes
    • Bandwidth Sharing in Multi-Camera Systems
    • Combine Helios 3D Point Cloud with RGB Color
    • I2C Support on LUCID Cameras
    • Using GPIO on LUCID Cameras
    • Using PTP & Scheduled Action Commands
    • Helios2 And Triton Synchronization
    • Product Change Notifications (PCN)
  • Knowledge Base
  • Contact Support
  • Log In
  • Support Home
  • Getting Started
    • Connecting Your Camera
    • 3rd Party Software Getting Started Guides
  • Tech Ref Manuals
    • Arena SDK Documentation
    • HTP003S – Helios2+ ToF 3D
    • HLT003S – Helios2 ToF 3D
    • HLS003S – Helios ToF 3D
    • HLF003S – Helios Flex ToF 3D
    • ATX245S – Atlas10 24.5 MP
    • ATX204S – Atlas10 20.4 MP
    • ATX162S – Atlas10 16.2 MP
    • ATX124S – Atlas10 12.3 MP
    • ATX081S – Atlas10 8.1 MP
    • ATX051S – Atlas10 5.0 MP
    • ATL314S – Atlas 31.4 MP
    • ATL196S – Atlas 19.6 MP
    • ATL168S – Atlas 16.8 MP
    • ATL120S – Atlas 12.3 MP
    • ATL089S – Atlas 8.9 MP
    • ATL071S – Atlas 7.1 MP
    • ATL050S – Atlas 5.0 MP
    • ATL028S – Atlas 2.8 MP
    • ATP200S – Atlas IP67 20 MP
    • ATP120S – Atlas IP67 12.3 MP
    • ATP089S -Atlas IP67 8.9 MP
    • ATP071S – Atlas IP67 7.1 MP
    • ATP028S – Atlas IP67 2.8 MP
    • TRI200S – Triton 20.0 MP
    • TRI120S – Triton 12.3 MP
    • TRI122S – Triton 12.2 MP
    • TRI089S – Triton 8.9 MP
    • TRI071S – Triton 7.1 MP
    • TRI064S – Triton 6.3 MP
    • TRI054S – Triton 5.4 MP
    • TRI050S-P/Q – Triton 5.0 MP Polarized
    • TRI050S – Triton 5.0 MP
    • TRI032S – Triton 3.2 MP
    • TRI028S – Triton 2.8 MP
    • TRI023S – Triton 2.3 MP
    • TRI016S – Triton 1.6 MP
    • TRI005S – Triton 0.5 MP
    • TRI004S – Triton 0.4 MP
    • TRI02KA – Triton 2K Line Scan
    • PHX200S – Phoenix 20.0 MP
    • PHX120S – Phoenix 12.3 MP
    • PHX122S – Phoenix 12.2 MP
    • PHX089S – Phoenix 8.9 MP
    • PHX064S – Phoenix 6.3 MP
    • PHX050S-P/Q – Phoenix 5.0 MP Polarized
    • PHX050S – Phoenix 5.0 MP
    • PHX032S – Phoenix 3.2 MP
    • PHX023S – Phoenix 2.3 MP
    • PHX016S – Phoenix 1.6 MP
    • PHX004S – Phoenix 0.4 MP
  • Application Notes
    • Bandwidth Sharing in Multi-Camera Systems
    • Combine Helios 3D Point Cloud with RGB Color
    • I2C Support on LUCID Cameras
    • Using GPIO on LUCID Cameras
    • Using PTP & Scheduled Action Commands
    • Helios2 And Triton Synchronization
    • Product Change Notifications (PCN)
  • Knowledge Base
  • Contact Support
  • Log In
home/Knowledge Base/Camera Features/Comparing LUCID’s IMX490 Cameras: TRI054S vs. TDR054S with AltaView

Comparing LUCID’s IMX490 Cameras: TRI054S vs. TDR054S with AltaView

754 views 0 October 13, 2023 Updated on December 1, 2023

This knowledge base article compares the technical specifications of the two LUCID cameras (TDR054S and TRI054S) that feature the Sony IMX490 image sensor. 

  • TDR054S: Equipped with the AltaView™ on-camera tone mapping engine, this camera is designed for mobile applications such as automotive applications, rail inspection, and mobile robotics. 
    USER BENEFIT: The camera automatically converts raw 24-bit HDR images and outputs 8-bit RGB tone mapped images with flicker mitigation. Speed up development time by not having to develop a custom tone mapping algorithm on the host PC.
  • TRI054S: The predecessor to the TDR054S. Able to output raw 24-bit HDR images that can be further processed off camera. 
    USER BENEFIT: Users can obtain raw 24-bit HDR images with flicker mitigation for maximum user flexibility in developing custom off camera image processing.

For a high-level overview of the two cameras and the AltaView tone mapping engine, see the following resources:  

  • TRI054S product page 
  • TDR054S product page 
  • HDR Imaging for Automotive Sensing White Paper 
  • AltaView Tone Mapping product page 

TDR054S: The AltaView Pixel Pipeline

LUCID’s AltaView is a specialized on-camera tone mapping engine that works in conjunction and ISP to effectively convert 24-bit raw image streams into 8-bit RGB image streams.

Above: A schematic of the AltaView™ ISP Pixel Pipeline 

HDR Processing Controls

The table below shows the HDR-related nodes. The generic IMX490 nodes are available on both the TDR054S and the TRI054S. The AltaView controls are available on the TDR054S only.

CategoryNode NameDescription
Sony IMX490 Sensor Controls
(TRI054S and TDR054S) 
HDROutputSelects the HDR output channel.
HDRTuningEnableEnables HDR tuning.
HDRTuningChannelSelectorEnable ability to change exposure time for individual HDR channels.
HDRChannelExposureTimeControls the selected HDR channel exposure time in microseconds (μs).
HDRChannelAnalogGainControls the selected HDR channel analog gain in dB.
HDRChannelDigitalGainControls the selected HDR channel digital gain in dB.
HDRDigitalClampingEnableEnables Digital Clamping to compensate for black level fluctuations.
HDRImageEnhancementEnableEnables HDR image enhancement.
AltaView Output Controls
(TDR054S only) 
HDRSaturationHDR Saturation setting in percent.
HDRContrastHDR Contrast setting in percent.
HDRBrightnessHDR Brightness setting in percent.
HDRDetailHDR Detail Setting in percent.
HDRAverageNumSelects the number of frames used for adjusting the brightness of images.

TDR054S Framerates

  Frame rate at different resolutions (Default1 | Max2)
Pixel Format / Bit Depth 2880×1860 1920×1080 1440×928 (2×2 binning)
RGB8 24 bit 6.9 | 7.7 FPS 17.0 | 18.9 FPS  26.4 | 29.3 FPS
YCbCr422_8 16 bit 10.4 | 11.5 FPS  24.7 | 24.7 FPS  30.06 | 30.06 FPS
YCbCr411_8 12 bit 13.8 | 15.4 FPS 24.7 | 24.7 FPS 30.1 | 30.1 FPS

The results above were obtained with the following values for DeviceLinkThroughputReserve:

  • 1Default: 10%
  • 2Max.: 0%

The DeviceLinkThroughputReserve node sets the percentage of the maximum bandwidth reserved for packet retransmission. LUCID recommends 10% reserve for reliable streaming.

Note that the IMX490 sensor has a maximum frame rate: Standard = 24.7 FPS | Binning = 30.1 FPS


The table below compares the TDR054S to the TRI054S, which can both be used in applications requiring HDR imaging.  Whereas the TRI054 is more flexible in off-camera image processing thanks to its raw 24-bit HDR output, the TDR054 reduces development time and is easier to use because of the on-camera AltaView tone mapping engine, which outputs 8-bit RGB tone mapped images. 

 LUCID TRI054SLUCID TDR054S (AltaView Tone Mapping)
  
SensorIMX490 5.4MP, 1/1.55” HDR sensorIMX490 5.4MP, 1/1.55” HDR sensor
Resolution2880 x 1860 px2880 x 1860 px
Maximum FrameratesRAW 24 bit: 6.9 FPS
RAW 8 bit: 20.8 FPS
RGB8 24 bit: 6.9 FPS
YCbCr422 16 bit: 10.4 FPS
YCbCr411 16 bit: 13.8 FPS
Field of View (FOV)Lens dependentLens dependent
Interface1 GigE / M121 GigE / M12
HDROff-camera (software)In-camera AltaView™ adaptive tone mapping engine
Dimensions29 x 29 x 45.3mm29 x 29 x 45.3mm
Pixel formatsMono8 / Mono12p / Mono16 / Mono24 / BayerRG8 / BayerRG12p / BayerRG16 / BayerRG24 / RGB8 / RGB12p / RGB16 / RGB24 / BGR8 / BGR12p / BGR16 / BGR24 / YCbCr422_8_CbYCrY / YCbCr422_16_CbYCrY / YCbCr422_24_CbYCrY / YCbCr411_8_CbYYCrYY / YCbCr411_16_CbYYCrYY / YCbCr411_24_CbYYCrYY

BayerRG8 / BayerRG12p / BayerRG16 / BayerRG24 / RGB8 / BGR8 / YCbCr422_8_CbYCrY / YCbCr422_16_CbYCrY / YCbCr411_8_CbYYCrYY / YCbCr411_16_CbYYCrYY

Note: Bayer formats have no White Balance and are primarily for LUCID’s manufacturing processes.

Manual Fixed Exposure SettingYesYes
Auto ExposureYesNo
Auto GainYesNo
Auto White BalanceYesNo (Automatically processed via AltaView engine)
Color Correction Matrix (CCM)YesNo (Automatically processed via AltaView engine)
Look-up Table (LUT)YesNo (Automatically processed via AltaView engine)
Tone MappingNoYes. Provided by the AltaView on-camera tone mapping engine.
Price$460$590

Raw Output vs Tone-mapped Output in the TDR054S


Triton HDR RAW output (fixed WB) 

Triton HDR RGB output (tone mapped)

The Triton HDR TDR054S also outputs raw formats, but these raw outputs use a fixed preset white balance and are primarily used for verification in our manufacturing processes. If you require White Balance in the raw image, consider purchasing a TRI054S instead.


TDR054S User Benefits

  • Single exposure in-camera HDR tone mapping
    • Dynamic range compression optimized for AI based processing (8bit bitmap input).
    • Fixed exposure time adapts to most imaging condition and enables LED flicker mitigation.
    • Built-in 24 bit auto white balance for excellent color reproduction.
    • No motion artifacts due to simultaneous multiple exposures.
  • Low latency, in-camera HDR processing
    • HDR processing optimized for mobile platform application.
    • User selectable exposure time with temporal backward flow filtering avoids brightness flicker.
    • Increased framerate and lower latency over off-camera tone mapping with color space compression.

Additional Links

  • TRI054S product page 
  • TDR054S product page 
  • HDR Imaging for Automotive Sensing White Paper 
  • AltaView Tone Mapping product page 

 

Was this helpful?

Yes  No
Related Articles
  • Using QOI with LUCID Cameras
  • Using Multiple Helios Cameras Simultaneously
  • Shading Correction Control (Atlas10)
  • Save Image on LUCID Camera’s File System
  • Multicast Device Discovery with LUCID Cameras
  • Precision Time Protocol (PTP)

Didn't find your answer? Contact Us

  Precision Time Protocol (PTP)

Multicast Device Discovery with LUCID Cameras  

© 2024 LUCID Vision Labs Inc.
Looking to purchase our cameras?
Visit the LUCID Webstore at thinklucid.com
LUCID Support & Help
Welcome to LUCID

We use cookies to facilitate online purchases and analyze our traffic. By clicking "Accept", you consent to our use of cookies.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}
LUCID Support & Help
Welcome to LUCID

We use cookies to facilitate online purchases and analyze our traffic. By clicking "Accept", you consent to our use of cookies.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}