Controller to AGX Dynamics messaging
Project description
Click
The main idea behind click is to enable a non-Brick controller talking to a Brick enabled AGX Dynamics Simulation in a way configurable by Brick. The name comes from the sound two Bricks makes when connected.
There are three main considerations
- How the controller can send controls and receive sensor values in a similar fashion regardless of environment, ie real or sim.
- How Brick adds sensors or topology on top of urdf, and how this is communicated to the controller.
- How to communicate controls and sensors in an effective way.
The current solution is to introduce a Handshake, which enables the simulation to tell the controller what to expect in terms of how to control and what sensor data is being sent.
A typical flow is
- Client controller connects and sends HandshakeInit
- Server responds with Handshake
- Client receives Handshake and validates the setup.
- Client sends Controls
- Server responds with Sensors
- The loop 4-5 is repeated.
Run demo
python3.9 -m pclick.demo.server --trace
python3 -m pclick.demo.client
Use
import pclick
Usage Examples
Visit the GitHub repo for more info and usage examples.
License
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
pclick-0.1.39.tar.gz
(8.1 kB
view hashes)