Expand description
§Pilatus Framework
A modular, extendable application framework which is currently used for industrial and computervision projects. The core is not limited to engineering, but should suite other projects with autonomous configurable subsystems which interact with one another.
§Features
- Run asynchronous actors which communicate via message passing
- Switch between different sets of actor configurations without restarting the application using the built in recipe management
- Adding new extension don’t require changes in the core.
- Easily expose core functionality through apis like http, websockets, opcua
- Multi-platform (Linux, OSX, Windows), multi-architecture (x64, arm)
§Modules
Currently, just a few modules are publicly available
- Axum: Collects web-routes from other modules an serves them on a single http port
- Engineering: Working with images and other engineering-related stuff like angles, matrices
- Emulation of camera
- Leptos frontend available at pilatus-leptos (beta)
- Opencv integration at pilatus-opencv
- GigE/Ueye-Camera via aravis: Discovery, settings gige-params, image streams pilatus-aravis
Some extensions which are implemented, but not (yet) publicly available:
- Image-Coordinates to 3D: Intrinsic calibration assistant, calibration plate management, origin determination
- Matching: Find shapes in images, which can be teached entirely in the web-ui (inkl. collision-detection if part has to be grippable by robot)
- Halcon: perform image analysis using hdpl-procedures, manage licenses, rust-bindings
- Various Feeder-Hardware: Anyfeeder, Aflex, Flexibowl, …
- OpcUA: Let other modules define OpcUA endpoints
Reach out if you need such functionality
Re-exports§
pub use axum::http;
Modules§
Structs§
- Abort
Service Interface - Append
Headers - Append headers to a response.
- Body
- The body type used in axum requests and responses.
- Bytes
- A cheaply cloneable and sliceable chunk of contiguous memory.
- Device
Json Error - Device
Json Response - Device
Response - Device
Topic WebComponent Location - Html
- An HTML response.
- IoStream
Body - Method
Router - Router
- Script
Response - Stats
- WebComponent
Location - Specify locations for webcomponents of any kind Just the first part before the slash is considered for mapping
- WebComponent
Locations
Traits§
- Dependency
Provider - Into
Response - Trait for generating responses.
- Service
Collection Extensions
Type Aliases§
- Device
Message Json Response - Minfac
Router - Response
- Type alias for
http::Responsewhose body type defaults toBody, the most common body type used with axum.