English
繁體中文
简体中文
日本語
한국어
Русский
Español
Other Language

3.5” Fire Shield SSD

Product Features
  • Compliant with MIL-STD-810-G
  • NANDs can survive 800°C of direct fire burn for 30 minutes
  • High Random R/W performance
  • iSMART disk health monitoring
  • Intelligent error recovery system
  • Conformal coating
  • Standard 3.5” HDD Design
Featured Technologies:
Application:
Overview Specs Order Information Related Resource ADD TO INQUIRY

Overview:

Innodisk’s 3.5” Fire Shield SSD is a fully fire-resistant Solid State Drive module. With its triple-layered protection design, the Fire Shield SSD can withstand direct flames at 800°C for up to 30 minutes. The Fire Shield SSD provides the toughest protection for your data in the face of devastating accidents. Also, as a SATA III 6.0Gb/s Flash-based disk, the Fire Shield SSD delivers excellent performance and reliability. The Fire Shield SSD is set to acquire compliance with MIL-STD-810G and IEC 62625-2:2016 code FB standards. It is developed with Innodisk proprietary technical knowhow to ensure data integrity and the highest levels of reliability.

Specifications:

Model Name3.5” Fire Shield SSD
InterfaceSATA III 6.0 Gb/s
Flash TypeiSLC, SLC
Capacity8GB~128GB
Sequential R/W (MB/sec, max.)520/360
Max. Power Consumption1.1 W (5V x 220 mA)
Max. Channels4
Thermal SensorY
S.M.A.R.T.Y
Dimension (WxLxH/mm)146.0 X 101.6 X 25.4
Fire ResistantIEC 62625-2:2016 code FB
VibrationMIL-STD-810G Method 516.7 Procedure I
Impact ShockIEC 62625-2:2016 code SB
Static CrushIEC 62625-2:2016 code CB
MTBF>3 million hours
Storage Temperature-55°C ~ +95°C

Order Information:

Operation Temp. 8GB 16GB 32GB 64GB 128GB
Standard Grade (0°C ~ +70°C) TBD TBD TBD TBD TBD
Industrial Grade (-40°C ~ +85°C) TBD TBD TBD TBD TBD

Related Resources:



VIDEOS
DOWNLOAD
RELATED NEWS
SmartFilter ™
Want to learn more ?
Close
×

Innodisk and Cookies

We use cookies on this website to provide you with the better user experience. By accepting cookies, you agree to our use of cookies. For more information on how we use cookies, please see our Privacy Policy.