Velodyne HD HDL-64E S2.1 User manual

HDL-64E S2
and S2.1
High Definition LiDAR™Sensor
USER’S MANUAL AND
PROGRAMMING GUIDE
Firmware Version 4.07

i
1
2
3
3
4
5
6
6
6
6
7
8
10
10
11
11
11
13
13
13
14
15
S A F T Y N O T I C S
INTRODUCTION
In The Box
PRINCIPL S OF OP RATION
INSTALLATION OV RVI W
Front/Back Mounting
Side Mounting
Top Mounting
Wiring
USAG
Use the Included Point-cloud Viewer
Develop Your Own Application-specific
Point-cloud Viewer
db.xml Calibration Parameters
Change Run-Time Parameters
Control Spin Rate
— Change Spin Rate in Flash Memory
— Change Spin Rate in RAM Only
Limit Horizontal FOV data Collected
Define Sensor Memory IP Source
and Destination Addresses
Upload Calibration Data
External GPS Time Synchronization
— GPS Receiver Option 1:
Velodyne Supplied GPS Receiver
— GPS Receiver Option 2:
Customer Supplied GPS Receiver
Packet Format and Status Byte
for GPS Time Stamping
Time Stamping Accuracy Rules
Laser Firing Sequence and Timing
FIRMWAR UPDAT
A P P N D I X A : Mechanical Drawings
A P P N D I X B : Wiring Diagram
A P P N D I X C : Digital Sensor Recorder (DSR)
Install
Calibrate
Live Playback
Record Data
Playback of Recorded Files
DSR Key Controls
DSR Mouse Controls
A P P N D I X D : Matlab Sample Code
Reading Calibration and Sensor Parameter Data
A P P N D I X : Data Packet Format
Last Six Bytes Examples
A P P N D I X F : Dual Two Point Calibration Methodology
A P P N D I X G : thernet Transmit Timing Table
A P P N D I X H : Laser and Detector Arrangement
A P P N D I X I : Angular Resolution
TROUBL SHOOTING
S RVIC AND MAINT NANC
SP CIFICATIONS
16
17
17
17
17
18
18
19
19
20
22
23
27
30
34
36
37
38
38
39

[ i ]

Caution
To reduce the risk of electric shock and to avoid violating the warranty, do not open sensor body. Refer servicing
to qualified service personnel.
The lightning flash with arrowhead symbol is intended to alert the user to the presence of uninsulated
“dangerous voltage” within the product’s enclosure that may be of sufficient magnitude to constitute a risk of
electric shock to persons.
The exclamation point symbol is intended to alert the user to the presence of important operating and
maintenance (servicing) instructions in the literature accompanying the product.
1. Read Instructions — All safety and operating instructions should be read before the product is operated.
2. Retain Instructions — The safety and operating instructions should be retained for future reference.
3. Heed Warnings — All warnings on the product and in the operating instructions should be adhered to.
4. Follow Instructions — All operating and use instructions should be followed.
5. Servicing — The user should not attempt to service the product beyond what is described in the operating
instructions. All other servicing should be referred to Velodyne.
1

Congratulations on your purchase of a Velodyne HDL-64 S2 or S2.1 High Definition LiDAR Sensor. These sensors represent a
breakthrough in sensing technology by providing more information about the surrounding environment than previously possible.
The HDL-64 S2 or S2.1 High Definition LiDAR sensors are referred to as the sensor throughout this manual.
This manual and programming guide covers:
• Installation and wiring
• HDL-64-ADAPT (GPS Adaptor Box)
• The data packet format
• The serial interface
• Software updates
• GPS installation notes
• Viewing the data
• Programming information
This manual applies to the two versions of the HDL-64 sensor, the S2 and S2.1, unless otherwise indicated. The table below compares the
laser layout, vertical field of view (VFOV) and primary application of the two versions.
HDL-64E Version Lower Laser Block Upper Laser Block Vertical Field of View (VFOV) Primary Application
S2 32 lasers separated by 32 lasers separated by +2 to -24.8° Autonomous navigation
½° vertical spacing 1/3° vertical spacing
S2.1 32 lasers separated by 32 lasers separated by 31.5° 3D mapping
(dual lower block) ½° vertical spacing ½° vertical spacing
For the latest updates to this manual – check www.velodynelidar.com.
In the Box
ach shipment contains:
• Sensor
• HDL-64-ADAPT (GPS Adaptor Box)
• Wiring harness
• CD with user manual, calibration file (db.xml), timing table calculation file (.xls) and DSR viewer
[ 1 ]
HDL-64E S2 and S2.1 User’s Manual


The sensor operates, instead of a single laser firing through a rotating mirror, with 64 lasers fixed mounted on upper and lower laser blocks,
each housing 32 lasers. Both laser blocks rotate as a single unit. With this design each of the lasers fires tens of thousands of times per
second, providing exponentially more data points/second and a more data-intensive point cloud than a rotating mirror design. The sensor
delivers a 360° horizontal Field of View (HFOV) and a 26.8° vertical FOV (31.5° VFOV for the S2.1).
Additionally, state-of-the-art digital signal processing and waveform analysis are employed to provide high accuracy, extended distance
sensing and intensity data. The sensor is rated to provide usable returns up to 120 meters. The sensor employs a direct drive motor
system with no belts or chains in the drive train.
See the specifications at the end of this manual for more information about sensor operating conditions.
Figure 1. HDL- 64E S2 design overview.
[ 2 ]
HDL-64E S2 and S2.1 User’s Manual
Hous ng
( ntire unit spins
at 5-20 Hz)
Laser
Em tters
(Groups of 16)
Laser
Rece vers
(Groups of 32)
Motor
Hous ng


Two M8-1.25mm x
12mm deep mounting
points. (Two per side,
for tot l of 8.)
Mount ng
Base
[152.4mm]
6.00
[203.2mm]
8.00 [21mm]
.83
[25.4mm]
1.00
The sensor base provides the following mounting options:
• Front/Back mount (Figure 2)
• Side mount (Figure 3)
• Top mount (Figure 4)
The sensor can be mounted at any angle from 0 to 90° with respect to its base. Refer to Appendix A for complete dimensions. For all
mounting options, mount the sensor to withstand vibration and shock without risk of detachment. Although helpful for longer life, the unit
doesn’t need to be shock proofed as it’s designed to withstand standard automotive G-forces.
The sensor is weatherproofed to withstand wind, rain and other adverse weather conditions. The spinning of the sensor helps it shed excess
water from the front window that could hamper performance.
Front/Back Mount ng
Figure 2. Front nd b ck HDL mounting illustr tion.
[ 3 ]
HDL-64E S2 and S2.1 User’s Manual


Mount ng
Base
[25.4mm]
1.00
[152.4mm]
6.00
[203.2mm]
8.00
[21mm]
.83
S de Mount ng
Figure 3. Side HDL mounting illustr tion.
[ 4 ]
HDL-64E S2 and S2.1 User’s Manual


Top Mount ng
Figure 4. Top HDL mounting illustr tion.
[ 5 ]
HDL-64E S2 and S2.1 User’s Manual

Four 0.41” [10.3mm] through
holes for top mount option to
secure the HDL to the vehicle.
[33.8mm]
1.33
[177.8mm]
7.00
[12.7mm]
.50 [12.7mm]
.50
[177.8mm]
7.00

W r ng
The sensor comes with a pre-wired connector, wired with power, DB9 serial and standard RJ45 thernet connectors. The connector wires are
approximately 10’ [3 meters] in length.
Power. Connect the red and black wires to vehicle power. Be sure red is positive polarity. TH S NSOR IS RAT D ONLY FOR 12 - 16
VOLTS. Any voltage applied over 16 volts could damage the sensor. The sensor draws 4-6 AMPS during normal usage.
The sensor doesn’t have a power switch. It spins whenever power is applied.
Lockout Circuit. The sensor has a lockout circuit that prevents its lasers from firing until it achieves approximately 300 RPMs.
Ethernet. This standard thernet connector is designed to connect to a standard PC.
The sensor is only compatible with network cards that have either MDI or AUTO MDIX capability.
Serial Interface RS-232 DB9. This standard connector allows for a firmware update to be applied to the sensor. Velodyne may release
firmware updates from time to time. It also accepts commands to change the RPM of the unit, control HFOV, change the unit’s IP address,
and other functions described later in this manual.
Wiring Diagram. If you need to wire your own connector for your installation, refer to the wiring diagram in Appendix B.
The sensor needs no configuration, calibration, or other setup to begin producing usable data. Once the unit is mounted and wired, supplying
it power causes it to start scanning and producing data packets.
Use the Included Po nt-cloud V ewer
The quickest way to view the data collected as an image is to use the included Digital Sensor Recorder (DSR). DSR is Velodyne’s point-cloud
processing data viewer software. DSR reads in the packets from the sensor over thernet, performs the necessary calculations to determine
point locations and then plots the points in 3D on your PC monitor. You can observe both distance and intensity data through DSR. If you
have never used the sensor before, this is the recommended starting point. For more on installing and using DSR, see Appendix C.
Develop Your Own Appl cat on-spec f c Po nt-cloud V ewer
Many users elect to develop their own application-specific point cloud tracking and plotting and/or storage scheme, which requires these
fundamental steps:
1. stablish communication with the sensor.
2. Create a calibration table either from the calibration data included in-stream from the sensor or from the included db.xml data file.
3. Parse the packets for rotation, block, distance and intensity data
4. Apply the calibration factors to the data.
5. Plot or store the data as needed.
[ 6 ]
HDL-64E S2 and S2.1 User’s Manual



The following provides more detail on each of the above steps.
1. Establish communication with the sensor.
The sensor broadcasts UDP packets. By using a network monitoring tool, such as Wireshark, you can capture and observe the
packets as they are generated by the sensor. See Appendix for the UDP packet format. The default source IP address for the
sensor is 192.168.3.043, and the destination IP address is 192.168.3.255. To change these IP addresses, see page 11.
2. Create an internal calibration table either from the calibration data included in-stream from the sensor or from the included
db.xml data file.
This table must be built and stored internal to the point-cloud processing software. The easiest and most reliable way to build the
calibration table is by reading the calibration data directly from the UDP data packets. A MatLab example of reading and building
such a table can be found in Appendix D and on the CD included with the sensor named CALTABLEBUILD.m.
Alternatively, the calibration data can be found in the included db.xml file found on the CD included with the sensor. A description of the
calibration data is shown in the following table.
db.xml Cal brat on Parameters
Parameter Unit Description Values
rotCorrection degree The rotational correction angle for each laser, Positive factors rotate to the left.
as viewed from the back of the unit. Negative values rotate to
the right.
vertCorrection degree The vertical correction angle for each laser, Positive values have the laser
as viewed from the back of the unit. pointing up.
Negative values have the laser
pointing down.
distCorrection cm Far distance correction of each laser distance Add directly to the distance value
due to minor laser parts’ variances. read in the packet.
distCorrectionX cm Close distance correction in X of each laser due to
minor laser parts variances interpolated with far
distance correction then applied to measurement in X.
distCorrectionY cm Close distance correction in Y of each laser due to
minor laser parts variances interpolated with far
distance correction then applied to measurement in Y.
vertOffsetCorrection cm The height of each laser as measured from One fixed value for all upper
the bottom of the base. block lasers.
Another fixed value for all lower
block lasers.
horizOffsetCorrection cm The horizontal offset of each laser Fixed positive or negative value
as viewed from the back of the laser. for all lasers.
Maximum Intensity Value from 0 to 255. Usually 255.
Minimum Intensity Value from 0 to 255. Usually 0.
Focal Distance Maximum intensity distance.
Focal Slope The control intensity amount.
The calibration table, once assembled, contains 64 instances of the calibration values shown in the table above to interpret the packet data to
calculate each point’s position in 3D space. Use the first 32 points for the upper block and the second 32 points for the lower block. The
rotational info found in the packet header is used to determine the packets position with respect to the 360° horizontal field of view.
[ 7 ]
HDL-64E S2 and S2.1 User’s Manual


3. Parse the packets for rotation, block, distance and intensity data. ach sensor’s LIFO data packet has a 1206 byte payload consisting
of 12 blocks of 100 byte firing data followed by 6 bytes of calibration and other information pertaining to the sensor.
ach 100 byte record contains a block identifier, then a rotational value followed by 32 3-byte combinations that report on each laser fired
for the block. Two bytes report distance to the nearest 0.2 cm, and the remaining byte reports intensity on a scale of 0 -255. 12 100 byte
records exist, therefore, 6 records exist for each block in each packet. For more on packet construction, see Appendix .
4. Apply the calibration factors to the data. ach of the sensor’s lasers is fixed with respect to vertical angle and offset to the rotational
index data provided in each packet. For each data point issued by the sensor, rotational and horizontal correction factors must be applied to
determine the point’s location in 3D space referred to by the return. Intensity and distance offsets must also be applied. ach sensor comes
from Velodyne’s factory calibrated using a dual-point calibration methodology, explained further in Appendix F.
The minimum return distance for the sensor is approximately 3 feet (0.9 meters). Ignore returns closer than this.
A file on the CD called “HDL Source xample” shows the calculations using the above correction factors. This DSR uses this code to
determine 3D locations of sensor data points.
5. Plot or store the data as needed. For DSR, the point-cloud data, once determined, is plotted onscreen. The source to do this can be
found on the CD and is entitled “HDL Plotting xample.” DSR uses OpenGL to do its plotting.
You may also want to store the data. If so, it may be useful to timestamp the data so it can be referenced and coordinated with other sensor
data later. The sensor has the capability to synchronize its data with GPS precision time. For more in this capability, see page 11.
Change Run-T me Parameters
The sensor has several run-time parameters that can be changed using the RS-232 serial port. For all commands, use the following
serial parameters:
• Baud 9600
• Parity: None
• Data bits: 8
• Stop bits: 1
All serial commands, except one version of the spin rate command, store data in the sensor’s flash memory. Data stored in flash memory
through serial commands is retained during firmware updates or power cycles.
The sensor has no echo back feature, so no serial data is returned from the sensor. Commands can be sent using a terminal program or by
using batch files (e.g. .bat). A sample .bat file is shown below.
Sample Batch File (.bat)
MODE OM3: 9600,N,8,1 OPY SER MD.txt OM3 Pause
Sample SERCMD.txt file
This command sets the spin rate to 300 RPM and stores the new value in the unit’s flash memory.
#HDLRPM0300$
[ 8 ]
HDL-64E S2 and S2.1 User’s Manual


[ 9 ]
HDL-64E S2 and S2.1 User’s Manual

Available commands
The following run-time commands are available with the sensor:
Command Description Parameters
#HDLRPMnnnn$ Set spin rate from 300 to 1200 RPM nnnn is an integer between 0300 and 1200
n flash memory (default is 600 RPM)
#HDLRPNnnnn$ Set spin rate from 300 to 1200 RPM nnnn is an integer between 0300 and 1200
in RAM (default is 600 RPM)
#HDLIPAssssssssssssdddddddddddd$ Change source and/or destination • ssssssssssss is the source 12-digit IP address
IP address • dddddddddddd is the destination 12-digit
IP address
#HDLFOVsssnnn$ Change horizontal Field of View (HFOV) • sss = starting angle in degrees; sss is an integer
between 000 and 360
• nnn = ending angle in degrees; nnn is an
integer between 000 and 360
You can also upload calibration data from db.xml into flash memory and use GPS time synchronization.
.

Control Sp n Rate
Change Spin Rate in Flash Memory
The sensor can spin at rates ranging from 300 RPM (5 Hz) to 1200 RPM (20 Hz). The default is 600 RPM (10 Hz). Changing the spin rate
does not change the data rate – the unit sends out the same number of packets (at a rate of ~1.3 million data points per second) regardless
of its spin rate. The horizontal image resolution increases or decreases depending on rotation speed.
See the Angular Resolution section found in Appendix I for the angular resolution values for various spin rates.
To control the sensor’s spin rate, issue a serial command of the case sensitive format #HDLRPMnnnn$ where nnnn is an integer between
0300 and 1200. The sensor immediately adopts the new spin rate. You don’t need to power cycle the unit, and the new RPM is retained
with future power cycles.
Change Spin Rate in RAM Only
If repeated and rapid updates to the RPM are needed, such as for synchronizing multiple sensors controlled by a closed loop application,
you can adjust the sensors’ spin rates without storing the new RPM in flash memory (this preserves flash memory over time).
To control the sensor’s spin rate in RAM only, issue a serial command of the case sensitive format #HDLRPNnnnn$ where nnnn is an
integer between 0300 and 1200. The sensor immediately adopts the new spin rate. You shouldn’t power cycle the sensor as the new RPM
is lost with future power cycles, which returns to the last known RPM.
L m t Hor zontal FOV Data Collected
The sensor defaults to a 360° surrounding view of its environment. It may be desirable to reduce this horizontal Field of View (HFOV) and,
hence, the data created.
To limit the horizontal FOV, issue a serial command of the case sensitive format #HDLFOVsssnnn$ where:
• sss = starting angle in degrees; sss is an integer between 000 and 360
• nnn = ending angle in degrees; nnn is an integer between 000 and 360
The HDL unit immediately adopts the new HFOV angles without power cycling and will retain the new HFOV settings upon power cycle.
Regardless of the FOV setting, the lasers will always fire at the full 360° HFOV. Limiting the HFOV only limits data transmission to the HFOV
of interest.
The following diagram shows the HFOV from the top view of the sensor.
Examples
Case 1: FOV 0° to 360°
FOV command: #HDLFOV000360$
Case 2: FOV 0° to 90°
FOV command: #HDLFOV000090$
Case 3: FOV -90° to 90°
FOV command: #HDLFOV270090$
Top view of Sensor
[ 10 ]
HDL-64E S2 and S2.1 User’s Manual


Def ne Sensor Memory IP Source and Dest nat on Addresses
The HDL- 64 comes with the following default IP addresses:
• Source: 192.168.3.043
• Destination: 192.168.3.255
To change either of the above IP addresses, issue a serial command of the case sensitive format #HDLIPAssssssssssssdddddddddddd$
where,
• ssssssssssss is the source 12-digit IP address
• dddddddddddd is the destination 12-digit IP address
Use all 12 digits to set an IP address. Use 0 (zeros) where a digit would be absent. For example, 192168003043 is the correct syntax for IP
address 192.168.3.43.
The unit must be power cycled to adopt the new IP addresses.
Upload Cal brat on Data
Sensors use the db.xml file exclusively for calibration data. The calibration data found in db.xml can be uploaded and saved to the unit’s
flash memory by following the steps outlined below.
1. Locate the files HDLCAL.bat, loadcal.exe, and db.xml on the CD and copy them to the same directory on your PC
connected to the sensor.
2. dit HDLCAL.bat to ensure the copy command lists the right COM port for RS-232 communication with the sensor.
3. Run HDLCAL.bat and ensure successful completion.
4. The sensor received and saved the calibration data.
To verify successful load of the calibration data, ensure the date and time of the upload have been updated. Refer to Appendix for where in
the data packets this data can be located.
External GPS T me Synchron zat on
The sensor can synchronize its data with precision GPS-supplied time pulses so you can ascertain the exact firing time of each laser in any
particular packet. The firing time of the first laser in a particular packet is reported in the form of microseconds since the top of the hour, and
from that time each subsequent laser’s firing time can be derived via the table published in Appendix H and included on the CD.
Calculating the exact firing time requires a GPS receiver generating a sync pulse and the $GPRMC NM A record over a dedicated RS-232
serial port. The output from the GPS receiver is connected to an external GPS adaptor box supplied by Velodyne that conditions the signal
and passes it to the sensor. The GPS receiver can either be supplied by Velodyne or the customer can adapt their GPS receiver to provide
the required sync pulse and NM A record.
GPS Receiver Option 1: Velodyne Supplied GPS Receiver
Velodyne provides an optional pre-programmed GPS receiver (HDL-64-GPS) This receiver is pre-wired with an RS-232 connector that
plugs into the GPS adapter box. To obtain a pre-programmed GPS receiver, contact Velodyne sales or service.
GPS Receiver Option 2: Customer Supplied GPS Receiver
You can supply and configure your own GPS device. If using your own GPS device:
• Issue a once-a-second synchronization pulse, typically output over a dedicated wire.
• Configure an available RS-232 serial port to issue a once-a-second $GPRMC NM A record. No other output can be accepted
from the GPS device.
• Issue the sync pulse and NM A record sequentially.
• The sync pulse length is not critical (typical lengths are between 20ms and 200ms)
• Start the $GPRMC record between 50ms and 500ms after the end of the sync pulse.
• Configure the $GPRMC record either in the hhmmss or hhmmss.s format.
[ 11 ]
HDL-64E S2 and S2.1 User’s Manual


The images below show the GPS adaptor box, included with the HDL-64 , and optional GPS receiver.
[ 12 ]
HDL-64E S2 and S2.1 User’s Manual

GPS EQUIPMENT
GPS Ad ptor Box Front & B ck View
GPS Adaptor Box
Model No.
HDL-64-ADAPT
(Included)
1 2 3 4 5 6 7 8
# COLOR SIGNAL NAME
1 Red +12V DC Power
2 Bl ck Power Ground
3 Yellow 1 PPS (positive edge only)
4 Red Vin (+5V)
5 Bl ck Ground
6 White Tr nsmit D t
7 Brown Ground (Dr in Wire)
8 Green Receive D t
DB-9 M
Connect to Interface
Ca le from
HDL-64E Unit
DB-9 F
Connect to Host
Computer Serial Port
GPS Receiver
Model No.
HDL-64-GPS
(Optional)

Packet Format and Status Byte for GPS T me Stamp ng
The 6 bytes at the end of the data packet report GPS timing and synchronization data. For every packet, the last 6 bytes are formatted
as follows:
Timestamp Bytes in Reverse Order in Microseconds
Bytes Description otes
4 GPS timestamp 32 bit unsigned integer timestamp. This value represents microseconds from the top
of the hour to the first laser firing in the packet.
1 Status Type 8 bit ASCII status character as described in Appendix . The status byte rotates
through many kinds of sensor information.
1 Status Value 8 bit data as described in Appendix .
Within the GPS status byte, there are 4 GPS status indicators:
• 0: no GPS connection.
• A: both PPS and GPS command have signal.
• V: only GPS command signal, no PPS.
• P: only PPS signal, no GPS time command.
T me Stamp ng Accuracy Rules
The following rules and subsequent accuracy apply for GPS timestamps:
GPS Connection Timestamp Info Accuracy otes
GPS isn’t connected The sensor starts running on xpect a drift of about 5 The sensor clock does not correct
(GPS Status 0) its own clock starting at midnight seconds/day for leap years. See Appendix for
Jan 1 2000. This date and time data more information.
is reflected in the H, M, S, D, N,
and Y data values.
GPS is connected The H, M, S, D, N, and Y data values GPS time synching runs in
are obtained from the $GPRMC one of two modes:
NM A record. • The GPS has an internal clock
that runs for several weeks that
is used first. The accuracy is that
of the GPS device employed.
• When the GPS achieves lock,
the sensor clock is then within
+/-50µs of the correct time at
all times.
GPS is disconnected The sensor continues to run on xpect drift of about 5 seconds/day
after being connected its own clock.
Laser F r ng Sequence and T m ng
If the GPS timestamp feature is used, it can be useful to determine the exact firing time for each laser so as to properly time-align the sensor
point cloud with other data sources.
The upper block and lower block collect distance points simultaneously, with each block issuing one laser pulse at a time. That is, each upper
block laser fires in sequence and in unison with a laser from the lower block.
[ 13 ]
HDL-64E S2 and S2.1 User’s Manual


Lasers are numbered sequentially starting with 0 for the first lower block laser to 31 for the last lower block laser; and 32 for the first upper
block laser to 63 for the last upper block laser. For example, laser 32 fires simultaneously with laser 0, laser 33 fires with laser 1, and so on.
The sensor has an equal number of upper and lower block returns. Hence, when interpreting the delay table, each sequential pair of data
blocks represents the upper and lower block respectively. ach upper and lower block data pair in the thernet packet has the same
delay value.
The first firing of a laser pair occurs 419.3 µs after the issuance of the fire command. Six firings of each block takes 139 µs and then the
collected data is transmitted. It takes 100 µs to transmit the entire 1248 byte thernet packet. This is equal to 12.48 Bytes/µs and
0.080128 µs/Byte. See Appendix for more information.
A timing table, shown in Appendix G, shows how much time elapses between the actual capturing of a distance point and when that point is
output from the device. By registering the event of the thernet data capture, you can calculate back in time the exact time at which any
particular distance point was captured.
From time to time Velodyne issues firmware updates. To update the sensor’s firmware:
1. Obtain the update file from Velodyne.
2. Connect the wiring harness RS-232 cable to a standard Windows compatible PC or laptop serial port.
3. Power up the sensor.
4. xecute the update file; the screen below appears.
Figure 5. HDL softw re upd te screen c pture.
5. Select the appropriate COM port.
6.Click Update.
7. The firmware is uploaded and check summed before it is applied to the flash memory inside the sensor. If the checksum is corrupted,
no update occurs. This protects the sensor in the event of power or data loss during the update.
• If the update is successful, the sensor begins to spin down for a few seconds and then powers back up with the new
firmware running.
• If the update is not successful, try the update several times before seeking assistance from Velodyne.
[ 14 ]
HDL-64E S2 and S2.1 User’s Manual



6.00
152.4
4.50
114.3
1.27 32.3
.83
21
(2 PER SIDE FOR A TOTAL OF 8) TWO M8-1.25X12MM DEEP MOUNTING POINTS
1.70 43.2
10.24 260.2
6.00
152.4
.83
21
1.93
49
.71
17.9
C
L
8.00
203.2
7.00
177.8
7.00
177.8
8.80
223.5
FOUR
.41
[10.3] THRU
FOR TOP MOUNT OPTION
8.00
203.2
ISOMETRIC VIEW
C
L
[ 15 ]
HDL-64E S2 and S2.1 User’s Manual


[ 16 ]
HDL-64E S2 and S2.1 User’s Manual

Harting Technology Group Metal Version, Standard Straight Style Model No. 10-12-005-2001

Digital Sensor Recorder (DSR)
DSR is a 3D point-cloud visualization software program designed for use with the sensor. This software is an “out of the box” tool for the
rendering and recording of point cloud data from the HDL unit.
You can develop visualization software using the DSR as a reference platform. A code snippet is provided on the CD to aid in understanding
the methods at which DSR parses the data points generated by the HDL sensor. See page 20 for more information.
Install
To install the DSR on your computer:
1. Locate the DSR executable program on the provided CD.
2. Double-click this DSR executable file to begin the installation onto a computer connected to the sensor. We recommend that you use
the default settings during the installation.
3. Copy the db.xml file supplied with the sensor into the same directory as the DSR executable (defaults to c:\program files\ Digital
Sensor Recorder). You may want to rename the existing default db.xml that comes with the DSR install.
Failure to use the calibration db.xml file supplied with your sensor will result in an inaccurate point cloud rendering in DSR.
Calibrate
The db.xml file provided with the sensor contains correction factors for the proper alignment of the point cloud information gathered for each
laser. When implemented properly, the image viewable from the DSR is calibrated to provide an accurate visual representation of the
environment in which the sensor is being used. Also use these calibration factors and equations in any program using the data generated by
the unit.
Live Playback
For live playback:
1. Secure and power up the sensor so that it is spinning.
2. Connect the RJ45 thernet connector to your host computer’s network connection. You may wish to use auto DNS settings for your
computers network configuration.
3. Open DSR from your desktop icon created during the installation.
DSR desktop icon =
4. Select Options from the menu.
5. Select the proper input device.
6. Go to Options again.
7. Deselect the Show Ground Plane option. (Leave this feature off for the time being or until the ground plane
has been properly adjusted).
8. (Optional) Go to Options > Properties to change the individual settings for each LAS R channel.
9. Provided that your computer is now receiving data packets, click the Refresh button to start live viewing of a point cloud. The initial image
is of a directly overhead perspective. See page 19 for mouse and key commands used to manipulate the 3D image within the viewer.
REFRESH button =
The image can be manipulated in all directions and become disorienting. If you lose perspective, simply press F1 to return to the
original view.
[ 17 ]
HDL-64E S2 and S2.1 User’s Manual
