Operating System: Mac (Sonoma) - most likely all OSs
What is happening: Flashing a Ping1D device with a different device type (Ping vs Ping2) does not get reflected in the Automatic Update version filtering until Ping Viewer gets restarted. Most likely the device information does not get re-checked until it's registered as a new connection to the device.
How to reproduce it: Manually flash a Ping1D device with the opposite device type (e.g. from Ping-V3.29_auto.hex to Ping2-V1.1.0_auto.hex), and notice that the firmware flasher does not update to show firmwares for the new device type in the Automatic Update section, but instead still shows firmwares for the previous device type (e.g. Ping -> Ping2 will still show Ping firmwares).
Technically a bug, but not a critical issue - users are not expected to change the device type by flashing the incorrect firmware onto a device that happens to have the same chip as a different device, and if they end up having done so then it seems ok if there are some minor inconveniences during the recovery
Summary
Version: 2.5.1
Operating System: Mac (Sonoma) - most likely all OSs
What is happening: Flashing a Ping1D device with a different device type (Ping vs Ping2) does not get reflected in the Automatic Update version filtering until Ping Viewer gets restarted. Most likely the device information does not get re-checked until it's registered as a new connection to the device.
How to reproduce it: Manually flash a Ping1D device with the opposite device type (e.g. from
Ping-V3.29_auto.hextoPing2-V1.1.0_auto.hex), and notice that the firmware flasher does not update to show firmwares for the new device type in the Automatic Update section, but instead still shows firmwares for the previous device type (e.g. Ping -> Ping2 will still show Ping firmwares).Additional information