-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reflex Takktile2 ethernet connection not working #43
Comments
Hi all, I am running Ubuntu 20.04 and ROS Noetic. I also setup the connection as described in the Quickstart guide and the ReFlex TakkTile is correctly recognized under the Ubuntu networking settings. However, I am having problems when launching the driver and the hand won't connect. @KiyanoushNazari, your problem sounded similar. Did you find a solution? Here is the log after running
|
Hello! I'm having very similar issues (although I have a Reflex Takktile as opposed to Takktile2). Here's my log:
Here's how network configuration and Ubuntu version looks like inside the container:
The connection itself looks very reasonable to me. I can't figure out what the issue might be. |
We figured out that our connection issue was somehow affected by tactile sensors. By replacing line 28 in |
Hi everyone,
I am using a reflex takktile2 hand, it was purchased about a year ago but no one has used it before. I successfully installed the ros package but when I connect the hand to the PC there is no connection and the system does not recognize the hand. I have tried various PCs with various ubuntu and ros versions but the one I am using now is my laptop with Ubuntu 18.04 with ros melodic. I set the static ip address as the quick start page says. I have also flashed the firmware successfully and the microcontroller board itself is recognized by the system when it's connected to the laptop by its micro usb port. But again when I connect the hand with Ethernet there is no connection. I have tried my ethernet with internet router and its working perfectly fine. So I came to the conclusion that the problem is coming from the ethernet port of the board but I have no idea how to fix this. I would really appreciate it if anyone could suggest something. Thanks
The text was updated successfully, but these errors were encountered: