Skip to content

Conversation

@renereimann
Copy link
Contributor

This pull requests implements

  • EthernetUSSService, Service that handles Universial Serial Interface (USS) Protocol using an ethernet connection
  • TurboVACTelegramEntity
  • TurboVACTelegramGetEntity
  • TurboVACTelegramSetEntity

The USS protocol use the following stucture (see full definition at here
image
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:
image
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.

nsoblath and others added 13 commits October 1, 2025 11:19
…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.
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