Do not write 10 centimeters on the brief

By Airia Edge, Staff Writer, The Possible

The product page prints a 10 cm minimum[3]. The brief prints a minimum under 15 cm[1]. Those are not two ways of saying the same floor. Write 10 cm into a line that cites the brief, and you have left the file both pages offer as the download[2][3].

The family page, fetched the same morning, does not say 10 cm[2]. Its marketing copy says 12 cm[2]. Its table says under 12 cm[2]. The 18 June release says sub-15 cm at full resolution[4]. Four documents. Four floors. Ten centimeters is on the product page's paragraphs, and nowhere else I fetched[3].

Do not write 10 centimeters on the brief.

The file both pages call the brief

Both live pages link a download labeled D585 Product Brief, 193.76 KB[2][3]. I fetched that file this morning from the download path those links share[1]. It is a one-page PDF. The printed title is RealSense Depth Camera D585 Pro[1]. The file was 198,407 bytes. Divide 198,407 by 1,024 and round to two decimals and you get 193.76. That division is mine. It matches the label on the pages if KB there means 1,024[2][3]. It does not match if KB means 1,000. Do not reject the download because 198,407 is not 193,760.

The specification column is short. Copy it as printed[1].

Line on the brief	What it prints
Minimum depth distance (Min-Z)	< 15cm[1]
Ideal range	10m+ *[1]
Depth output resolution and frame rate	Up to 1280 × 960, and up to 90 FPS (480p)[1]
RGB resolution	Up to 1280 × 960. Up to 60 FPS[1]
Dual RGB support	Up to 1280 × 960. Up to 30 FPS[1]
Depth field of view	120° × 100° (±1°)[1]
RGB field of view	120° × 100° (±1°)[1]
Depth technology	Active Stereo[1]
Image sensor technology	Global shutter; 3 µm x 3 µm pixel size[1]
Camera module	RealSense Module D580[1]
Vision processor board	RealSense V5 SoC[1]
Interface	FAKRA (GMSL2) & USB-C 3[1]
Form factor	Camera peripheral[1]
Length × height × depth	130 mm × 40 mm × 40 mm[1]
IP grade	IP65[1]
Use environment	Indoor/Outdoor[1]

The prose adds one comparative claim the table does not. Close-range performance is 2.5x better than competing solutions[1]. The competitor is not named[1]. The brief does not print a 2x depth-quality claim[1]. It does not print a 5x claim[1]. It does not print a price[1]. It does not print a ship date[1]. It does not print an IMU line[1].

The ideal-range cell carries an asterisk[1]. On the rendered page, the footer says stereo cameras can see further, but accuracy degrades with distance and varies depending on scene and lighting conditions[1]. The text layer of the same file splits some of those footer words, so that sentence is the rendered line, not a cleaned extraction. Do not turn 10m+ * into "accurate at 10 meters."[1]

Ninety frames is the 480p line

The brief puts two values under one label, Depth Output Resolution & Frame Rate[1]. The first value is up to 1280 × 960[1]. The second is up to 90 FPS (480p)[1]. The parenthesis is the resolution for the 90 FPS line. 480p is not 1280 × 960. The brief does not print 640 × 480 either[1]. Leave the parenthesis as 480p.

The 18 June release does not mention 90 FPS, and it does not mention 480p[4]. It does print 60 FPS at 1280×960[4]. It also prints a 120×100° field of view at 60 FPS[4]. Those pairings live on the release. They do not live on the brief[1]. If you need the 60 FPS mode, cite the release[4]. Do not write it into the brief's frame-rate cell, and do not upgrade it to 90.

Both live pages split that paired cell into two rows[2][3]. Depth output resolution: up to 1280 × 960[2][3]. Depth frame rate: up to 90 fps, with the 480p qualifier gone[2][3]. The marketing copy on those same pages then prints 60 FPS at 1280×960[2][3]. Read together, the pages still do not say 90 FPS at 1280×960. They say 90 in a row that names no resolution, and 60 in a sentence that names 1280×960[2][3]. Join the rows and you have invented a mode. I did not find that mode on the brief[1]. I did not find it on the release, the family page, or the product page[2][3][4].

Dual RGB is a third clock. The brief prints dual RGB support at up to 1280 × 960 and up to 30 FPS[1]. The release says simultaneous 30 FPS RGB and 30 FPS depth, at up to 1280×960, merged on the camera[4]. The product page says the same pairing[3]. Two streams at 30 is not one stream at 60. Do not add the thirties.

RGB alone, on the brief, goes up to 60 FPS at up to 1280 × 960[1]. That 60 is the color line. It is not the depth line, and it is not the dual line[1].

Four floors

Put the minimum-depth lines next to each other. Do not average them.

Document	Minimum as printed
Product brief	< 15cm. The cell does not say "at full resolution."[1]
18 June release, key specs	Sub-15cm minimum range at full resolution[4]
18 June release, quoted range	from under 15 centimeters to more than 10 meters[4]
Family page, table	< 12cm[2]
Family page, marketing	12cm minimum range at full resolution[2]
Product page, table	< 12cm[3]
Product page, marketing	10 cm minimum range at full resolution[3]

Less than 15 cm is not 15 cm. Less than 12 cm is not 12 cm. A minimum of 12 cm is a floor at 12. A minimum of 10 cm is a floor at 10. Under 12 cm does not tell you the floor is 10. Under 15 cm does not tell you the floor is 12, or 10, or anything in between.

The product page disagrees with itself[3]. The table says under 12 cm[3]. The paragraphs say 10 cm[3]. A reader who thinks those agree, because 10 is less than 12, has stopped reading the inequality. The table did not print 10. The paragraphs did not print the less-than sign.

The family page disagrees with itself the other way[2]. The table says under 12 cm[2]. The hero prints an ideal range of 12cm – 10m+[2]. The blurbs say 12cm minimum at full resolution[2]. Under 12 and a minimum of 12 are not the same cell. Do not pick the shorter number because it sounds more capable. Do not pick the longer number because it sounds safer. Then cite the brief, which is the third number[1].

The release sits closer to the brief, and it is still not the brief[4][1]. Sub-15 cm at full resolution is a phrase the brief's Min-Z cell does not print[1][4]. The brief prints the inequality and stops[1]. If a drawing needs "at full resolution," that qualifier comes from the release and from the live marketing copy, not from the brief's cell[4][2][3]. The live marketing copy does not agree on the number in front of the qualifier[2][3].

I am not going to compute a midpoint. Thirteen centimeters is not on any of these pages. Neither is 11. Neither is 14.

Do not replace 10m+ with 20m+

The far end moves on one page, and the table on that page does not follow.

The brief prints 10m+[1]. The asterisk is part of the cell[1]. The compare card prints 10m+ and does not print a minimum beside it[7]. The family-page table prints 10m+[2]. The product-page table prints 10m+[3]. The release prints "more than 10 meters" in the quoted range, and "10m+ operating range at optimal accuracy" in the key specs[4]. "At optimal accuracy" is the release's phrase[4]. It is not a tolerance table. It is not a millimeter error at 10 meters. Do not invent one.

The product page's conveyor paragraph mentions sub-millimeter anomalies[3]. That sentence is not an accuracy spec at 10 meters, and it is not on the brief[1]. Leave it where you found it.

The product page's marketing copy then leaves its own table[3]. It says the camera extends to 20m and beyond[3]. It says 20m+ for corridor planning[3]. The broken hero line on that page says 20m+ max-Z[3]. The specification table on the same page still says 10m+[3]. Do not let the paragraph overwrite the table. Do not let either of them overwrite the brief[1].

The family page does not print 20m in the copy I fetched[2]. Its broken hero line says 10m+ max-Z[2]. Its hero ideal range is 12cm – 10m+[2]. Twenty meters is a product-page sentence[3]. It is not a family-page sentence, and it is not a brief sentence[1][2].

Do not add 10 and 10 and call it the range. The brief printed one far-end figure[1]. Twenty is not a second 10 the brief forgot.

Two times is not five times

The brief's only multiplier is 2.5x, and it modifies close-range performance against competing solutions[1]. The competitor is not named[1]. Do not divide some other camera's minimum by 2.5 and call the result a D585 spec. The compare page prints the D455's ideal range as .6 m to 6 m[7]. That is an ideal-range pair on a different card. It is not the competitor the brief named, because the brief named none[1]. I am not doing that division.

The 18 June release prints two depth-quality phrases, and neither of them is 5x[4]. The deck says the D585 Pro delivers 2x better depth quality and 2.5x better close-range performance[4]. The body says over 2x better depth quality than the previous generation of RealSense cameras, and 2.5x better close-range performance than competing solutions[4]. Keep the "over." Do not sand it down to 2x, and do not promote it to 5x. The key-spec line then says the sub-15 cm minimum is 2.5x better than the nearest competitor, and it names 2x noise reduction[4]. The nearest competitor is not named there either[4].

Both live pages print 2x and 5x for depth quality, on the same morning, on the same URL[2][3]. The hero says 2x better depth quality[2][3]. A later paragraph says the new depth engine and dual projectors deliver 5x better quality than the prior RealSense generation across the full 120×100° field of view[2][3]. Another says 5x better depth quality across the entire field of view compared to the current RealSense generation[2][3]. Prior generation and current generation are not defined on the page as a model number[2][3]. Do not decide they mean the D455, or the D435, or the D457, and then do arithmetic.

Two and five are not a range you get to average. 3.5x is not a printed claim. The brief refuses both numbers for depth quality[1]. If a requirements line needs a depth-quality multiplier, it does not have one on the brief. Say that. Do not borrow the page's larger number because a slide will like it.

Noise stays at 2x on the pages and on the release[2][3][4]. Do not let the 5x sentence swallow it.

The product page also says the camera competes with cameras that cost 10x the D585[3]. The brief and the release print no price[1][4]. The product page and the compare card do not print one for this camera either[3][7]. Ten times an unpublished price is not a number you can check. Do not invent the price so the 10x will compute.

The properties pane still says D457

The printed slide says RealSense Depth Camera D585 Pro[1]. The PDF info dictionary does not. pdfinfo, on the file I fetched, prints the title as D457 Product Brief Brochure-V4[1]. The creation stamp it prints is Wed Jun 17 20:43:39 2026 EDT[1]. The modification stamp is Thu Jun 18 01:17:31 2026 EDT[1]. The release is dated 18 June 2026, Chicago[4]. The properties pane was not updated when the slide title was.

Order from the printed name. Do not order a D457 because the title field still carries that brochure name[1]. The datasheets index links a December 2025 file named RealSense-D457-Datasheet-Dec-2025.pdf[8]. I did not read that file for any number in this post. It is not the brief. A D457 datasheet and a D585 brief that still says D457 in its properties are two different mistakes. Don't join them.

The brief's module line is a third name. Camera Module: RealSense Module D580[1]. The camera is the D585 Pro[1]. The module is the D580[1]. The processor is the RealSense V5 SoC[1]. Do not order a D580 camera. Do not call the module a D585. The live-page tech tables print the V5 SoC and do not print the D580 module name in the rows I read[2][3]. If the module name matters to the drawing, it is on the brief[1].

The URL on the brief does not resolve

The brief prints www.realsenseai.com/D585 at the bottom[1]. A request to that URL this morning returned HTTP 404, and the response title was "Page not found - RealSense."[5] The trailing-slash form and the lowercase form landed on the same 404.

The pages that resolve, and that link the brief, are the family page and the product page[2][3]. Use those. Do not bookmark the URL printed on the brief until it stops 404ing. And do not treat the two live URLs as copies of each other. The family page says Coming Soon[2]. The product page does not[3]. The product page says Contact Sales, and the copy I fetched has no Buy button[3]. Absence of Coming Soon is not an in-stock flag.

The pages paste other cameras into the D585

On the family page, a section headed for fleet range and speed is followed by a paragraph about the D436[2]. That paragraph says the D436 provides up to 1280 × 800 RGB at 60 fps, with approximately 90° × 65° RGB FOV[2]. Those numbers are not the D585 brief[1]. The brief's RGB line is up to 1280 × 960, and both fields of view are 120° × 100° (±1°)[1]. Do not copy 1280 × 800, or about 90 by 65, onto a D585 drawing because the paragraph sits under a D585 heading.

On the product page, a heading that says ready for your next project is followed by a D455 sentence: the D455 provides more accuracy and flexibility, no matter the use case[3]. That sentence does not give you a D585 accuracy figure. The brief does not print an accuracy in millimeters[1]. Do not invent one from a pasted line.

The same product page puts the heading "75% less bandwidth. Zero compromise on quality." in front of the 5x depth-quality paragraph, not in front of the compression explanation[3]. The compression explanation sits earlier. It says depth compression reduces depth-stream bandwidth by 75%, collapsing four pixels into one datapoint[3]. The family page puts the mechanism under the heading: a 2×2-pixel block becomes one depth datapoint, a cut of 75%, with no loss of detail or accuracy, in RealSense's words[2]. The release says the same 75% cut[4]. The brief does not mention depth compression[1].

Four samples down to one is a 75% reduction if the stream keeps a quarter. That reading matches "by 75%"[2][3][4]. It does not match "to 75%," which would be a 25% cut. The documents say by, not to[2][3][4]. Do not flip the preposition. And do not put the 75% on the brief. It is not there[1].

One more paste is easier to miss. Both live pages contain a broken sentence that starts "120." and ends "×100° FOV"[2][3]. The family version inserts global shutter, IMU, GMSL2, IP65, 12cm Min-Z, and 10m+ max-Z[2]. The product version inserts the same list with 10 cm Min-Z and 20m+ max-Z[3]. The 120 and the ×100° are the field of view, split around a feature list. IMU appears in that split. I found the word once on each page, and nowhere in either tech-spec table. The brief has no IMU line[1]. Do not add an IMU to the bill of materials because a broken sentence says the word.

Active is not optional, and the axis names swapped

The brief's depth-technology line says Active Stereo[1]. Both live tables say Stereoscopic[2][3]. Stereoscopic does not say whether a projector is in the path. The brief does[1]. The release describes dual IR projectors and dual active projectors as the reason the camera holds up under harsh ambient light[4]. If a requirements line cites the brief, write Active Stereo[1]. Do not drop Active because the web table did.

The size numbers agree. The labels do not. The brief says Length x Height x Depth: 130 mm × 40 mm × 40 mm[1]. Both pages say Length x Depth x Height, and the same three numbers[2][3]. The middle name and the last name swapped. The two 40 mm dimensions are equal, so the bounding box does not change. A CAD note that treats the page's Depth as the brief's Height has renamed an axis. It has not found a thinner camera. Write the brief's label if you are citing the brief[1].

The pixel size is only on the brief: 3 µm x 3 µm, under Image Sensor Technology, next to Global Shutter[1]. The line does not say whether that pitch is the depth pair, the RGB imager, or both[1]. Do not assign it. Do not multiply 3 by 3 and call 9 µm² a printed spec. That multiplication would be mine, and it does not belong in the table.

The interface line on the brief is FAKRA (GMSL2) & USB-C 3[1]. The release says GMSL2 + USB-C, and stops[4]. It does not print USB 3.1, and it does not print Gen 1. Those generation strings show up on other cameras' connector lines[7]. They are not on the D585 brief[1]. Do not copy a neighbor's USB generation onto this camera.

Do not borrow Perception Studio's centimeters

Perception Studio is a different page, and its current feature lines name other cameras[6].

The VIO line says drop-in VIO via cuVSLAM on D455 / D436 global-shutter cameras[6]. It does not name the D585[6]. The 18 June release used a different string, cuSLAM, and it said that VIO is executed on an NVIDIA host[4]. The same release said planned SDK releases would add VIO, among other items, to existing D585 hardware after general availability[4]. So the June sentence puts a future VIO on D585 hardware, and it puts the execution on a host, not on the Gen 5 SoC[4]. The current Studio page names the D455 and the D436, and it says cuVSLAM, not cuSLAM[6]. Do not merge the names. Do not tell anyone the D585 runs that Studio line today.

The live pages list VIO on the roadmap, delivered to existing hardware via the SDK after release[2][3]. Their sentence is that the camera you buy in 2027 is not the camera you will have in 2028[2][3]. That is a vendor promise about later software. It is not a feature you can require in a drawing this morning.

The Studio close-range line is the one that will get pasted onto the wrong camera, because the number looks familiar. It extends depth sensing to under 3 cm on the D401 and the D405, and under 12 cm across the D400-series family using an NVIDIA Jetson, and it says that path runs natively on the edge for D500s[6]. Under 3 cm is not a D585 number[1]. Under 12 cm on that line is a D400-series figure, and the sentence names the host[6]. The June Studio paragraph said under 15 cm across the D400-series, not under 12, and it did not put that clause on the D585 Min-Z line[4]. Do not update one sentence from the other by memory. Do not paste either figure into the brief's < 15cm cell[1].

Person detection is the line the release keeps on the camera. It says the D585 Pro ships with on-camera person detection in beta at launch, running on the Gen 5 SoC, without host compute[4]. The live pages say the same beta-at-launch claim, and they also list person detection among roadmap items delivered later by SDK[2][3]. Do not mark it finished. Do not give it the host requirement that belongs to the VIO sentence[4].

The host names matter only so you do not treat a Studio centimeter as an on-camera D585 spec[6]. They are not a brief for anyone else's board.

What the compare page will actually sell you

The compare page's D585 card prints a 120° × 100° (±1°) field of view, an ideal range of 10m+, and global shutter[7]. It prints the line that this camera is not an incremental update[7]. From that card to the next product, Module D421, the block I read had no dollar figure[7]. Other cards on the page print a price and a Buy link. I am not copying one of those prices onto the D585. The brief has no price[1]. The release has no price[4]. The product page has Contact Sales[3]. A quote that fills the blank with a neighbor's price is not on these documents.

Shipping is the other blank the brief leaves empty[1]. The release says the D585 Pro is expected to begin shipping in Q1 2027[4]. The family page says Coming Soon[2]. The product page says the camera you buy in 2027[3]. This post is dated 15 October 2026. Q1 2027 has not started. Do not write "available now." Do not write a dock date the release did not print. Expected is the release's word[4]. Keep it.

The six datasheet PDFs linked from the datasheets index are not this file either[8]. None of those filenames is a D585 datasheet. The document both product pages offer is a product brief[2][3]. Call it a brief. Do not call it a datasheet, and do not fill its blanks from the D457 file the properties pane will tempt you to open[1][8].

What to write in the drawing

If you are specifying this camera from the brief, write the brief[1].

Name it RealSense Depth Camera D585 Pro[1]. Not D457. Not D580. D580 is the module line[1].

Minimum depth: < 15cm, as the cell prints it[1]. In the notes, say the family page and the product page print < 12cm in the table, the family marketing copy prints 12 cm, and the product marketing copy prints 10 cm[2][3]. Say the 18 June release prints sub-15 cm at full resolution[4]. Do not resolve that note by picking 10.

Depth modes: up to 1280 × 960, and up to 90 FPS (480p)[1]. Do not join those into 90 FPS at 1280 × 960. If you also need the release's 60 FPS at 1280×960, cite the release, and do not let it replace the 480p line[4][1].

Ideal range: 10m+ with the asterisk[1]. Note that the product page's paragraphs say 20m+ and that its table still says 10m+[3]. Do not write 20m+ on a line that cites the brief.

Depth technology: Active Stereo[1]. Field of view, depth and RGB: 120° × 100° (±1°)[1]. Do not copy the D436's approximately 90° × 65°[2].

RGB: up to 1280 × 960, up to 60 FPS[1]. Dual RGB: up to 30 FPS at that resolution[1]. Do not add the dual streams into 60.

Interface: FAKRA (GMSL2) and USB-C 3[1]. Size: 130 mm × 40 mm × 40 mm, labeled length × height × depth[1]. IP65. Indoor and outdoor[1]. Global shutter[1]. The pixel size stays on the brief, unassigned to a named imager[1].

No IMU, unless a later document adds a row the brief and both tables do not have[1][2][3]. No price[1]. No ship date on the brief[1]. The release's expectation is Q1 2027[4].

The pages will keep moving. The family page and the product page already disagree with each other, and each one disagrees with its own table[2][3]. The brief is the file they both still offer as the download[2][3]. When the page and the brief conflict, write the brief, and put the page in the note. Do not write the page into the brief.

Sources