Skip to content
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

Socket connection timeout #10

Open
ghost opened this issue May 3, 2020 · 2 comments
Open

Socket connection timeout #10

ghost opened this issue May 3, 2020 · 2 comments

Comments

@ghost
Copy link

ghost commented May 3, 2020

Hi, I am building a Robocar which is driven by Nvidia Jetson TX2 an Emlid Reach M+ which works with another Emlid Reach RS+. I connect the M+ and Nvidia Jetson TX2 through USB cable. This way, M+ is powered by the TX2 and I do not need addition battery for it. I setup the M+ position output with TCP following the instruction here https://community.emlid.com/t/gps-data-over-usb/6387 by bide Pro user. The code in this repo worked fine. I can also see the NMEA data with linux command

nc 192.168.2.15 7777

However, today, when I run this ros node, I am keeping getting error signal like:
[WARN] [1588526303.310905]: Device disconnected. Reconnecting...
[INFO] [1588526303.319201]: Successfully connected to device, starting publishing!
[WARN] [1588526308.328799]: Device disconnected. Reconnecting...
[INFO] [1588526308.332986]: Successfully connected to device, starting publishing!
[WARN] [1588526313.338880]: Device disconnected. Reconnecting...
[INFO] [1588526313.344649]: Successfully connected to device, starting publishing!
[WARN] [1588526318.351416]: Device disconnected. Reconnecting...
[WARN] [1588526323.360550]: Socket connection timeout. Retrying...

When I run

nc 192.168.2.15 7777

I did not see the NMEA data either.

What could be wrong?

Thanks,

@goldbattle
Copy link
Member

If you can't see any NMEA data then it is probably a misconfiguration in the reach.
Have you taken a look at this issue: #7

@oym1994
Copy link

oym1994 commented Oct 10, 2022

Have you solved this problem? I am also facing this error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants