Pfeiffer Endpoint: Implementation of Pfeiffer telegram protocol #224
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…We assemble and the command at each get / set and disensemble / format the response corresponding to the datatype defined by pfeiffer.
|
Apparently Paul has a device that needs this at UW, so we have another place to test this code |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implementation of Pfeiffer telegram protocol following documentation from Pfeiffer manuals.
The frame of the protocol is defined by:
Each parameter has a number (which may differ from device to device). For values Pfeiffer has a table of predefined datatypes and how they have to be formated:
Implementation works very nice with our pressure gauge of type HPT 200 from Pfeiffer.
The configuration file significantly improved in readability (see example folder).