We intended to do this a year ago, and seemingly didn't get around it.
Ping2 was1 a device name for a physical hardware revision of the Blue Robotics Ping Sonar. Both revisions use the same electronics, and the ping1d message set, so it makes more sense for both to pull from the ping1d folder, and just be represented by a major version number update.
The original variant uses Ping-V3.2*_*.hex, so I propose the Ping2-V1.*.hex firmware options should be renamed as Ping-V4.*.hex, which can then be used as the filtering correspondence in the place of the current folder-name check in Ping Viewer. Alternatively the current file naming could be maintained just within the ping1d folder, since the 2 does at least correspond to the internal device revision anyway.
We intended to do this a year ago, and seemingly didn't get around it.
Ping2 was1 a device name for a physical hardware revision of the Blue Robotics Ping Sonar. Both revisions use the same electronics, and the
ping1dmessage set, so it makes more sense for both to pull from theping1dfolder, and just be represented by a major version number update.The original variant uses
Ping-V3.2*_*.hex, so I propose thePing2-V1.*.hexfirmware options should be renamed asPing-V4.*.hex, which can then be used as the filtering correspondence in the place of the current folder-name check in Ping Viewer. Alternatively the current file naming could be maintained just within theping1dfolder, since the 2 does at least correspond to the internal device revision anyway.Footnotes
It was decided the 2 was confusing because the sensor is still a 1-dimensional echosounder, so the product name has returned to just "Ping Sonar", with the hardware changeover documented in the revision history on the product page. ↩