Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
G
GEPARD
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GEPARD
  • GEPARD
  • Wiki
  • working principle

working principle · Changes

Page history
Update working principle authored Feb 21, 2020 by Lars Bittrich's avatar Lars Bittrich
Hide whitespace changes
Inline Side-by-side
Showing with 1 addition and 1 deletion
+1 -1
  • working-principle.md working-principle.md +1 -1
  • No files found.
working-principle.md
View page @ 38ecdb50
......@@ -14,7 +14,7 @@ As long as you don't do anything with your WITec software GEPARD won't be able t
Make sure that you have at least Version 5.0 of WITec-Control installed. In versions prior to 5.1 activate Default Tree mode (right click in the left control panel). Then activate "Allow Remote Access". This remote access can be revoked at any time with a large button in WITec Control. After the access is denied again your WITec Control should run as before. Now, try the witectest.py sample first with objectives turned away from the samples to avoid damage by uncontrolled movement.
To activate the WITec backend for GEPARD set the 'raman_interface' variable to 'WITEC_CONTROL' in `gepard.cfg`. Restart GEPARD to activate the new configuration. If GEPARD is still running with the simulated interface this fact will be shown in the window title. If the WITec interface import fails for example due to missing win32com packages GEPARD will still use the simulated interface.
To activate the WITec backend for GEPARD set the 'raman_interface' variable to 'WITEC_CONTROL' in `gepard.cfg`. Restart GEPARD to activate the new configuration. If GEPARD is still running with the simulated interface this fact will be shown in the window title. If the WITec interface import fails for example due to missing win32com packages GEPARD will still use the simulated interface. If you forgot to allow the remote access before starting GEPARD you have to manually connect GEPARD by clicking `Connect to Microscope` after allowing the remote access in WITec Control.
**Creating and performing a measurement**
......
Clone repository
  • Basics of command line navigation
  • OpticalScan
  • ParticleDetection
  • RamanScan
  • Step by step installation guide
  • Home
  • working principle