Skip to content

Conversation

@patrickelectric
Copy link
Member

@patrickelectric patrickelectric commented Dec 14, 2023

Alternative to #161

Copy link
Contributor

@ES-Alexander ES-Alexander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks ok to me :-)

I am a little concerned about future-proofing, because some of the fields (e.g. transmit frequency and sample number) have been defined for our specific sensor rather than being generic protocol things with each sensor defining its own limits, but I'm not sure how feasible that is to change at this stage, since those limits are already in place in Ping Viewer and whatnot anyway, and I'm assuming we don't have a lot of development resources available to work on this at the moment.

"type": "u8",
"description": "Analog gain setting (0 = low, 1 = normal, 2 = high)"
"description": "Analog gain setting",
"enum": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we have a default value with enum?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

default is 0

"type": "u8",
"description": "Analog gain setting (0 = low, 1 = normal, 2 = high)"
"description": "Analog gain setting",
"enum": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

default is 0

@patrickelectric patrickelectric marked this pull request as draft July 29, 2024 17:09
@patrickelectric
Copy link
Member Author

Need to update to support Default values

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants