Search results

OMNISCAN450_SET_SPEED_OF_SOUND message ID is incorrect

Status: Open.

#222 In bluerobotics/ping-protocol;

· Maexerich opened on Mar 24, 2026

Refactor and re-focus to device-type functionalities

enhancementNew feature or requestNew feature or request

Status: Open.

#220 In bluerobotics/ping-protocol;

· ES-Alexander opened on Aug 6, 2025

Expand ping1d message set to cover more single-transducer functions

enhancementNew feature or requestNew feature or request

Status: Open.

#219 In bluerobotics/ping-protocol;

· ES-Alexander opened on Aug 6, 2025

Feature: Add min/max fields for device field definitions

Status: Open.

#216 In bluerobotics/ping-protocol;

· RaulTrombin opened on Jun 17, 2025

Omniscan450: missing device type

Status: Open.

#208 In bluerobotics/ping-protocol;

· ES-Alexander opened on May 23, 2024

Add support to enums on message variables

Status: Open.

#201 In bluerobotics/ping-protocol;

· patrickelectric opened on Jan 13, 2023

Ping360 should not send auto_transmit message if no message is received by it for X seconds

Status: Open.

#191 In bluerobotics/ping-protocol;

· patrickelectric opened on Jul 14, 2021

Add information about ping360 auto message mechanism

Status: Open.

#190 In bluerobotics/ping-protocol;

· patrickelectric opened on Jul 14, 2021

Add information about ping1d range of valid values

Status: Open.

#189 In bluerobotics/ping-protocol;

· patrickelectric opened on Jul 13, 2021

Add information about order of profile points

Status: Open.

#185 In bluerobotics/ping-protocol;

· patrickelectric opened on Jun 10, 2021

Requesting device_data from ping360 results in an empty profile:

Status: Open.

#178 In bluerobotics/ping-protocol;

· patrickelectric opened on Mar 20, 2020

Update documentation to information that SRC and DST ID 0 is reserved

Status: Open.

#176 In bluerobotics/ping-protocol;

· patrickelectric opened on Feb 20, 2020