Feature/turbovac #231
Open
Feature/turbovac #231
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
…mand entity that we can use e.g. to degas our pressure gauges
…s already defined in FormatEntity in init and on_get function.
…e to apply the asteval function to the dict value not the dict itself.
…ormatEntityAsteval into AstevalFormatEntity, checking of input at constructor, improving doc strings
…We assemble and the command at each get / set and disensemble / format the response corresponding to the datatype defined by pfeiffer.
no message
…odule of the TurboCtl package.
…vac/telegram to load the telegram parameters, warnings and errors. If they are not included in the site-packages the module can not find the files and load them
…s a start character and extracts the length from the telegram header. The commands are expected in bytes and the response is in bytes as well
… and its builder and reader provided by the subfolder telegram for correct formatting and extraction of information from the telegram.
…led via the control word. Since this has to be send by every message, I had to store the state in the service and each endpoints uses it. To not stop running I had to use the scheduler to schedule regular telegrams. I made a new endpoint to enable / disable control and to start and stop the pump
CommandEntity and FormatEntity with asteval supports
…d parts of the disensembled message. Nicer formarting of long dict.
Pfeiffer Endpoint: Implementation of Pfeiffer telegram protocol
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.
This pull requests implements
The USS protocol use the following stucture (see full definition at here
The USS protocol has variable length and no terminator. The USS protocol was developed by Siemens and e.g. used by Laybolds TurboVac Telegram.
The Turbopums of laybold TurboVAC have a serial telegram defined following the USS protocol with a fixed length of 24 bytes.
The telegram follows this structure:
See documentation here
For the implementation of the TurboVac control I reuse the TurboCtl/telegram submodule from thie TurboCtl github repository.
I implemented and tested the service and entity and its working with our turboVac 350/450i pump by Laybold.
Till now I could not test the "set" method since we need to have the pump running for this.