Repository navigation
Conversation
Keep main's driver submodule pointers; only lightel is new Update PLC ip addresses Add target keyword Add a camserver config update Change from HTTP to using libby Updates to the camera server
This branch has not been deployed
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
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.
daemons/hsfibers/fiberswitch, with one instance per channel (hsfibers_fiberswitchred,hsfibers_fiberswitchblue). Each holds the three classes of the design: MechanicalSwitch (the PLC), MechanicalSwitchCamera (the DI-2000) and MechanicalSwitchController (connection policy, inspect-and-clean, reference images).camserver.pyserves a DI-2000 plugged into another machine as a libby peer (ex: fiberswitchbluecam), and the daemon reaches it viacamera.remote. Frames are sent compressed in chunks to stay under libby’s 512 KB message limit