repository: git://github.com/neobotix/neo_driver
Contents
This package is obsolete and will be replaced by cob_relayboard
Serial Relay Board
The Serial Relay Board does not only handle and publish error states (as a laser stop or emergency stop) or the robots state (temperature, battery volts and the battery current), it can also control can-motor-drivers and publish range measurements (ultra sonic or infra red).
For the Relay Board exist a couple of expansion boards:
- Gyro Board: publishes angular rates and acceleration on 3 axis.
- I/O Board:
- Radar Board: publishes velocities.
Topics to publish/subscribe and configuration parameters
Subscribed Topics
/cmd_drives (neo_msgs/DriveCmd)- sets joint velocities
- sets lcd output
- sets digital output
- starts the ultrasonic range board
- stops the ultrasonic board
- zeros the gyro
Published Topics
/drive_states (neo_msgs/DriveStates)- publishes joint states
- publishes digital input
- publishes digital output
- publishes analog input
- publishes ultrasonic sensor readings
- publishes radar sensor readings
- publishes gyro sensor readings
- publishes keypad pushbutton readings
- publishes infrared range sensor readings
Parameters
message_timeout (, default: 2.0)- sets the timeout for messages sent via serial port
- sets the rate for communicating with the serial relay board
- sets the serial relayboard version
- sets the comport (for example /dev/ttyUSB1)
- sets the canid of the first drive
- sets the canid of the second drive
- sets the drives jointname
- sets the drives jointname
- are motors connected to the serial relay board? [true/false]
- are motors connected to the serial relay board? [true/false]
- is the io-board connected? [true/false]
- is there an lcd display? [true/false]
- are us-sensors connected? [true/false]
- is the radarboard connected? [true/false]
- does the gyroboard exist? [true/false]
- is a keypad in use? [true/false]
- are there any ir-sensors? [true/false]
Troubleshooting
I can't communicate with the Serial Relay Board, though it powers on and displays stuff on the LCD:
Make sure that your config file does not enably any non existing expansion boards/motors and that you've choose the right relayboard version and poweroff the serial relay board afterwards.
Launching relayboard.launch fails because the $ROBOT_drive*.yaml files are missing:
Set the arg "loadDrives" to "false"
Add your own Problem and Solution here