-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Ping2 support #1081
Add Ping2 support #1081
Conversation
patrickelectric
commented
Jun 11, 2024
•
edited by ES-Alexander
Loading
edited by ES-Alexander
- Use device information over "deprecated" ping1D firmware version message
- Fix CI
- Add Ping2 support
- Fixes Ping1 firmware update options showing for a Ping2 device #1079
…SION Signed-off-by: Patrick José Pereira <[email protected]>
Signed-off-by: Patrick José Pereira <[email protected]>
Signed-off-by: Patrick José Pereira <[email protected]>
Signed-off-by: Patrick José Pereira <[email protected]>
Signed-off-by: Patrick José Pereira <[email protected]>
Signed-off-by: Patrick José Pereira <[email protected]>
Signed-off-by: Patrick José Pereira <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some usage notes:
- Firmware flashing (still) works 👍
- Firmware filtering for the Automatic Update works 👍, but only for the device type that was initially connected to 🫤
- If a firmware with a different device type is manually flashed, the filtering is still based on the old device type until Ping Viewer restarts
- In principle this is a bug, but we also don't expect users to change their device type, so I don't think it's a big deal 🤷♂️
- If a firmware with a different device type is manually flashed, the filtering is still based on the old device type until Ping Viewer restarts
-
Once flashed, thePing2-V1.1.0
firmware registers as1.0
(instead of1.1
) in the "Current Firmware" indicator, in both the debug window and the firmware flashing windowEDIT
: FixedI confirmed with ping-python that this is at least partially a problem with the firmware not having an internally updated version, which makes it unclear whether Ping Viewer will display the value correctly
- The debug menu doesn't show the patch version (just major, minor), even though newer firmwares (Ping2, Ping360) are specified with one
- This isn't new, so may not need to be handled in this PR
Ping2 firmwares seem to only show up as 115200 baud options, whereas original Ping firmwares show up as both 9600 and 115200 optionsEDIT
: both were showing up, 9600 just took much longer to appear 🤷♂️No idea if this was an intentional change in the firmware, or a problem, just noting that it's different
- The interplay between the "Firmware Update" button and the progress bar is currently confusing
- This isn't new, so doesn't necessarily need to be handled in this PR
- Specifically, when a firmware is not being flashed the indefinite progress bar seems unnecessary, and has consistently made me think it's indicating that flashing has started once I select a manual firmware file, before realising I have to press the "Firmware Update" button to confirm
I just fixed it, can you take a look ? |
Confirmed that this is fixed - thanks :-) |
It's fine over here, try to connect and disconnect to restart the ABR procedure. |
Just tried again, and 9600 did show up eventually, it just took about twice as long as 115200 🤷♂️ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My remaining previous suggestions/comments still stand, but they don't need to be handled in this PR.
Approving, since this is already mergeable :-)