Closed adamanov closed 10 months ago
Can you export HUSKY_PORT=/dev/ttyUSB0
and launch husky_base? Looks like /dev/prolific
isn't point to the correct device.
export HUSKY_PORT=/dev/ttyUSB0
did it, I guess now the port is found but appears the following error, the COMM light on husky is still red colored
husky@prodigies:~$ export HUSKY_PORT=/dev/ttyUSB0
husky@prodigies:~$ roslaunch startup husky_main.launch
... logging to /home/husky/.ros/log/a67fb4a2-9f20-11ee-a8fa-c13a5b2109a2/roslaunch-prodigies-6614.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://prodigies:34611/
SUMMARY
========
PARAMETERS
* /diagnostic_aggregator/analyzers/husky/expected: ['husky_base: pow...
* /diagnostic_aggregator/analyzers/husky/find_and_remove_prefix: husky_base:
* /diagnostic_aggregator/analyzers/husky/path: Husky A200
* /diagnostic_aggregator/analyzers/husky/timeout: 5.0
* /diagnostic_aggregator/analyzers/husky/type: diagnostic_aggreg...
* /husky_node/control_frequency: 10.0
* /husky_node/diagnostic_frequency: 1.0
* /husky_node/max_acceleration: 3.0
* /husky_node/max_speed: 1.0
* /husky_node/polling_timeout: 10.0
* /husky_node/port: /dev/ttyUSB0
* /husky_node/wheel_diameter: 0.3302
* /robot_description: <?xml version="1....
* /rosdistro: noetic
* /rosversion: 1.16.0
NODES
/
diagnostic_aggregator (diagnostic_aggregator/aggregator_node)
husky_node (husky_base/husky_node)
robot_state_publisher (robot_state_publisher/robot_state_publisher)
auto-starting new master
process[master]: started with pid [6670]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to a67fb4a2-9f20-11ee-a8fa-c13a5b2109a2
process[rosout-1]: started with pid [6703]
started core service [/rosout]
process[robot_state_publisher-2]: started with pid [6710]
process[husky_node-3]: started with pid [6711]
process[diagnostic_aggregator-4]: started with pid [6712]
EXCEPTION: TransportException 3: Unacknowledged send
[ERROR] [1703067309.072421549]: Error configuring velocity and accel limits: Unacknowledged send
EXCEPTION: TransportException 3: Unacknowledged send
[ERROR] [1703067310.027771866]: Error configuring velocity and accel limits: Unacknowledged send
here is also output of rosnode info husky_nod
husky@prodigies:~$ rosnode info /husky_node
--------------------------------------------------------------------------------
Node [/husky_node]
Publications:
* /diagnostics [diagnostic_msgs/DiagnosticArray]
* /rosout [rosgraph_msgs/Log]
Subscriptions: None
Services:
* /husky_node/get_loggers
* /husky_node/set_logger_level
contacting node http://prodigies:46365/ ...
Pid: 5854
Connections:
* topic: /rosout
* to: /rosout
* direction: outbound (40675 - 127.0.0.1:34516) [13]
* transport: TCPROS
* topic: /diagnostics
* to: /diagnostic_aggregator
* direction: outbound (40675 - 127.0.0.1:34524) [14]
* transport: TCPROS
* topic: /diagnostics
* to: /rostopic_6069_1703067035322
* direction: outbound (40675 - 127.0.0.1:40656) [12]
* transport: TCPROS
Hello again,
I found that the cable was broken, by changing it and assigning HUSKY_PORT to correct PORT the problem is gone :)
Thanks for help Asan
Please provide the following information:.
Platform Husky, Noetic, Ubuntu 20.04
Expected behaviour A COMM light on robot being green, and able to send cmd velocity on motors.
Actual behaviour
by launching husky_node is gives me an error, due to not able to connect to MCU
not able to establish communication with MCU
I tried to another FTDI cable but still could not resolve the problem..
The MCU USB cable has a chip on it, and its light is green.
I hope you can help to to resolve the problem. Thanks in advance.
Some additional outputs:
Other notes Add anything else you thing is important.