Skip to content
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

Fix reply for Ordinate Axis #4

Open
stuwilkins opened this issue Feb 13, 2019 · 1 comment
Open

Fix reply for Ordinate Axis #4

stuwilkins opened this issue Feb 13, 2019 · 1 comment

Comments

@stuwilkins
Copy link
Contributor

During testing at IOS, we found that our analyzer when presented with the command

?0145 GetSpectrumDataInfo ParameterName:"OrdinateRange"

Only returns

!0145 OK: ValueType:double Unit:""

Missing are the optional Min: and Max: values. The change in stuwilkins/specsAnalyser@d939df1 traps the case where the units are a null string and does not continue (returns asynError). There is probably more of an issue with the function cleanString() which throws an exception to the above response.

@stuwilkins
Copy link
Contributor Author

Note: fixed this a different way with stuwilkins/specsAnalyser@06dc7ab

Now, it doesn't call cleanString() if the string is ""

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

No branches or pull requests

1 participant