Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • M mitsubishi_controller
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mitsubishi
  • mitsubishi_controller
  • Wiki
  • Home

Home · Changes

Page history
petrivl3 created page: home authored Nov 09, 2015 by Vladimír Petrík's avatar Vladimír Petrík
Show whitespace changes
Inline Side-by-side
home.markdown
View page @ e55ed5ba
......@@ -4,7 +4,7 @@ Mitsubishi_controller package provides an actionlib (joint trajectory action) in
A tcp/ip communication protocol is used. This controller can be directly integrated with an MoveIt! environment.
## Settings
Communication is based on tcp/ip protocol which requires a local network. The computer IP address can be arbitrary but controller IP address have to be set to a specific-static value, which is set in the controller parameters as well as in the ros-node, designed for the communication on the PC side. The chosen controller IP address is 192.168.0.20 in our case and the gateway is set to 192.168.0.1 in our network. These addresses may depend on local network settings and can be adjusted in provided controller interface.
Communication is based on tcp/ip protocol which requires a local network. The computer IP address can be arbitrary but controller IP address have to be set to a specific-static value, which is set in the controller parameters as well as in the ros-node, designed for the communication on the PC side. The chosen controller IP address is 192.168.0.20 in our case and the gateway is set to 192.168.0.1 in our network. These addresses may depend on local network settings and can be adjusted in our implementation.
### Controller settings
The following parameters need to be set in the controller:
......@@ -20,4 +20,6 @@ The following parameters need to be set in the controller:
| COMDEV | RS232, OPT12, OPT13, OPT14, ... |
| NETMODE | 1,1,...,1 |
After these settings are done and controller is connected into the local network, the command "ping 192.168.0.20" should succeed.
### PC settings
\ No newline at end of file
Clone repository
  • Home