Repository navigation
v5.5.0
v5.5.0
-
Fixed the large IMU publishing delay caused by the IMU being read in step with
grab()(stereo and mono). Withgeneral.grab_frame_rate: 15andgeneral.grab_compute_capping_fps: 5the samples arrived in 5 Hz bursts several hundred milliseconds late; the mono node, which has no compute capping, was delayed by the grab rate alone. Both nodes now read the sensors stream independently ofgrab(), polling well above the hardware ODR so that no sample is lost. Measured on a ZED X on an AGX Orin: median publish delay 411 ms -> 10.5 ms, output rate 92.6 -> 100.0 Hz, and the delay no longer depends ongeneral.grab_compute_capping_fps. SVO and simulation are unchanged. -
Fixed
sensors.sensors_pub_ratenot being honored on cameras whose IMU does not run at the rate the ZED SDK advertises (stereo and mono). A ZED X One GS reports 400 Hz but delivers 200 Hz, sosensors_pub_rate: 100produced a steady 50 Hz. Both nodes now decimate against the measured sample interval instead of the advertised one. Cameras that report correctly now produce exactly the requested rate rather than the nearest sub-multiple of the real one (a ZED 2i publishes 100.0 Hz instead of 101.1 Hz). -
Reduced the CPU usage of both nodes by counting topic subscribers through the publisher instead of a ROS graph query, and by refreshing the sensors thread counts every 250 ms instead of on every poll. On an AGX Orin this cuts the sensors thread overhead from ~5% to ~2-3% of a CPU core, whether or not the IMU topics are subscribed. Two consequences: a new subscriber to a sensors topic can wait up to 250 ms for its first message, and a subscriber whose QoS is incompatible with the publisher no longer triggers publishing (it could never receive the data anyway).
-
Added the
general.bus_typeparameter to theZedCameraOnenode (AUTOdefault,USB,GMSL, and with ZED SDK >= 5.5MIPIandHOLOSCAN), used when the camera is selected withgeneral.camera_id. The bus was hard-coded toGMSL, so a ZED X One Core on a MIPI capture card, or reached over Camera-over-Ethernet through a Holoscan sensor bridge, could not be opened by ID at all. -
Added the
pause_svo_recservice (stereo and mono,std_srvs/srv/SetBool) to pause and resume an SVO recording without closing the file. It returnssuccess: falsewhen no recording is active, and the diagnostic reportsSVO Recording: PAUSEDwhile paused. -
Added the
general.max_system_clock_step_msparameter (stereo and mono) to set how fast the SDK follows a backward host-clock adjustment (NTP/PTP step, manual date change):4.0is the ZED SDK default and suits slew-only setups, a negative value makes step corrections land instantly as PTP deployments expect, and0.0freezes the offset captured on first use. Applied only whengeneral.sdk_timestamp_clockisSYSTEM_CLOCK. Requires ZED SDK >= 5.3. -
Added the
general.sdk_timestamp_clockparameter (stereo and mono) to select the clock behind every SDK timestamp:SYSTEM_CLOCK(default),MONOTONIC_CLOCK, orMONOTONIC_RAW_CLOCK(ZED SDK >= 5.4), which is immune to NTP/PTP frequency slewing as well as to clock steps. It replaces the booleangeneral.sdk_use_monotonic_clock, which is still read and still works, but now logs a deprecation warning. -
Added the
svo.encryption_keyparameter (stereo and mono) to encrypt the SVO files created bystart_svo_rec(AES-256-CTR); playback was already supported throughsvo.decryption_key. It accepts a path to a 32-byte key file, a 64-character hex key or a passphrase, and is never written to the log. Requires ZED SDK >= 5.3 and OpenSSL at runtime. -
Added the positional tracking pose confidence, a [0,100] quality metric filled by
POSITIONAL_TRACKING_MODE::GEN_3where 0 means tracking is lost. It is reported asPose confidencein the diagnostic and published as the newpose_confidencefield ofPosTrackStatuson~/pose/status. Requires ZED SDK >= 5.4 andzed_msgsv5.5. -
Fixed the
distortion_modeland the distortion coefficients published in thecamera_infotopics. They were chosen from a hard-coded per-model table that the lens does not follow: a fisheye ZED X One was published asrational_polynomialinstead ofequidistant, and the ZED X HDR models were missing from the table entirely, so theircamera_infocarried no distortion model at all. Both nodes now read the model from the ZED SDK (>= 5.4) and fall back to the old heuristic on older versions. Rectified parameters are reported asplumb_bobwith zero coefficients. -
Aligned the
zed_debugconfiguration files with thezed_wrapperones: five parameters were missing andcustom_object_detection.yamllagged four per-class tracking parameters behind. Both directories now declare the same parameters; only the debug-specific values differ. -
Fixed
general.sdk_use_monotonic_clocksitting in thedebugsection ofzed_wrapper/config/common_mono.yamlandzed_debug/config/common_stereo.yaml, where it was read under the wrong name and silently ignored. -
Added the missing
advanced.change_thread_prioritytocommon_stereo.yamland to bothcommon_mono.yamlfiles. It gates every otheradvanced.*parameter and defaults tofalse, so the thread scheduling policy and priorities listed next to it were never applied unless it was added by hand. -
Fixed the
sports ballclass incustom_object_detection.yaml, whose label was corrupted topesports ballrsonby a bad search and replace. The other 79 labels and everymodel_class_idwere verified against the COCO 2017 order. -
Improved the per-class defaults of
custom_object_detection.yaml:is_groundedis now set only for objects that really lie on the floor (it was set on tableware, food and laptops, whose 3D position was then projected onto the floor) andis_staticonly for objects fixed in the world, and the tracking timeout, 3D box bounds, velocity settings and confirmation and prediction times are now set per object type instead of being identical for all 80 classes. -
Fixed
object_detection.class_XXX.min_box_height_metersbeing documented for every class but never read by the node, so the minimum 3D height was never applied. -
Added
CUSTOM_RFDETRLIKE_BOX_OBJECTSandCUSTOM_BOX_OBJECTS_AUTODETECTas validobject_detection.detection_modelvalues (ZED SDK >= 5.5). They were accepted by the parameter parser but treated as built-in models, so the ONNX file was never passed to the ZED SDK and enabling object detection failed. -
Fixed the ONNX input shape sent to the ZED SDK for custom object detection models:
object_detection.custom_onnx_input_sizeproduced asize x 0resolution instead of a square one, so the shape never matched the one a model had been optimized with and the engine had to be rebuilt. -
Added the camera health status to the diagnostic output: image quality, lighting, depth reliability, motion sensors reliability and, with ZED SDK >= 5.5 and
zed_msgsv5.5, duplicated images. The diagnostic goes to WARN and names the issues while any of them is raised, and reportsDISABLEDwhengeneral.enable_image_validity_checkis off. -
Added the
duplicated_imagefield to theHealthStatusStampedmessage published on~/status/health, raised by the ZED SDK when a frame repeats the content of an earlier one under a new timestamp, i.e. a repeating or stalled stream. Requires ZED SDK >= 5.5 andzed_msgsv5.5; with an olderzed_msgsthe node runs as before, without the field. -
Added the
general.timestamp_referenceparameter (IMAGEdefault,IMAGE_CENTER_OF_EXPOSURE) to both nodes.IMAGE_CENTER_OF_EXPOSUREstamps the published data with the middle of the frame exposure instead of the start of the sensor readout, which is what aligns frames with sensors timestamped at the instant they measure (LiDAR, robot joints). It needs an input carrying a per-frame exposure (ZED X, ZED X Mini, ZED X One GS, ZED X One 4K): on USB and HDR models the node warns once and falls back toIMAGE. Requires ZED SDK >= 5.5. -
Changed the default
body_tracking.body_formatfromBODY_38toBODY_34, andbody_tracking.enable_body_fittingfromfalsetotrue. OnlyBODY_18andBODY_34have aGEN_2network, so the previous default silently fell back to the olderGEN_1. Skeletons published on~/body_trk/skeletonsnow carry 34 keypoints instead of 38: setbody_formatback toBODY_38to keep the previous topology, at the cost of runningGEN_1. -
Added the
body_tracking.model_genparameter (GEN_1,GEN_2; defaultGEN_2) to select the body tracking network.GEN_2is more robust in crowded scenes and to unusual body orientations, detects people further from the camera, and is up to 18% faster and 14% more accurate thanGEN_1.body_tracking.allow_reduced_precision_inferencehas no effect onGEN_2, which always runs in FP16. Requires ZED SDK >= 5.5. -
Added the
pos_tracking.compute_preferenceparameter (AUTOdefault,PREFER_CPU,PREFER_GPU) to control how much GPU the positional tracking may use:PREFER_GPUmakes tracking faster and shortensgrab(),PREFER_CPUkeeps the GPU free for your own workloads.GEN_1computes depth and so uses the GPU whatever the setting. Requires ZED SDK >= 5.5. -
Added the
depth.allow_depth_cuda_graphparameter (defaultfalse): the ZED SDK records the depth computation once and replays it at every grab, lowering the CPU cost of launching it, which matters most on Jetson. The depth output is unchanged. It applies to theNEURALdepth mode family only, and the SDK reverts to the regular computation if the recording fails. Requires ZED SDK >= 5.5. -
Added the
depth.depth_precisionparameter to select the precision of the neural depth inference:FP16(default, unchanged behavior) orINT8, which is faster and uses less GPU memory for a small accuracy cost.INT8requiresdepth.depth_mode: 'NEURAL'; the ZED SDK falls back toFP16when the depth mode or the GPU does not support it. Requires ZED SDK >= 5.5. -
Fixed a
zed_msgsversion check that blockedscene_illuminanceinformation in health status messages. -
Fixed
scene_illuminancereporting a value frozen at start-up in both the health status message and theScene Illuminancediagnostic. It is now refreshed while grabbing and tracks the actual scene light level. -
Improved simulation mode to match the features of the ZED extension for NVIDIA Isaac Sim:
- The grab resolution and framerate are no longer forced to
HD1080@ 60 Hz, but read from the simulated camera, so a simulation running at the extension default of 30 FPS is reported and published correctly. This also removes the bogus "general.grab_frame_ratevalue is not valid" warning printed at every start-up, and the capture diagnostics reporting half the expected rate. general.pub_frame_rate: 0("no limit") now follows the real grab rate even when it is only known after the input is open.- Fixed the unstable IMU publishing rate in simulation: the stereo node now drains the IMU FIFO as the mono node already did, instead of polling only the latest sample. (Live cameras no longer take this path: see the IMU delay entry above.)
- Fixed the simulation connection timeout never expiring when
use_sim_time:=trueand no/clockpublisher was running yet. The timeout error now reports the configuredsimulation.sim_address/simulation.sim_portto check. - A simulated Virtual Stereo Camera (
camera_model:=virtual) no longer requiresserial_numbersorcamera_ids: the simulator streams the already paired stereo images. - The "system overloaded" diagnostic now points to the simulator
FPS/Resolutionfields instead of node parameters that have no effect in simulation. - Silenced the spurious
SENSORS_NOT_AVAILABLEwarnings produced by a simulated camera without an IMU.
- The grab resolution and framerate are no longer forced to
-
Added simulation mode support for the ZED X One monocular cameras: launch
ZedCameraOnewithsim_mode:=true(plus the optionalsim_address,sim_portanduse_sim_timeoptions) to publish images and IMU data from the simulated camera. Withuse_sim_timethe node waits for a valid/clockand stamps every topic with the simulation time.