search

space-concordia-robotics / robotics-prototype

Teleoperated Mars rover with autonomous capabilities intended for robotics competitions.
https://spaceconcordia.github.io/robotics.html
25 stars 18 forks source link

Odroid takes forever to boot sometimes #468

Closed MartensCedric closed 1 year ago

MartensCedric commented 4 years ago

image

Sometimes the odroid takes more than 15 minutes to be able to SSH in.

PeterGhimself commented 4 years ago

Seriously, 15 min? I've seen it take a while sometimes but never that long... max a few minutes usually. Did you stop after 15 min or did it connect after 15 min?

Maybe if you're waiting this long (and the issue is not with the power) then it might be because you were switching back and forth between InternetHog and RoverOBC configurations and not selecting "Basestation Direct" fast enough?

When switching back from internet share mode you need to reboot the odroid and make sure to select "Basestation Direct" on the basestation as the odroid boots and as soon as the system lets you select an ethernet configuration.

Also I can't see but I'm assuming this was ping odroid which would resolve to ping 172.16.1.30, which wouldn't work if ROVER_OBC config wasn't up.

MartensCedric commented 4 years ago

Me and Koa quit testing because it took more than 15 mins at one occasion (most of the time at least 150 ping sequences). At the end we couldn't even connect anymore so we ended up not testing the arm

On Sat, Oct 3, 2020, 9:14 PM PeterGhimself, notifications@github.com wrote:

Seriously, 15 min? I've seen it take a while sometimes but never that long... max a few minutes usually. Did you stop after 15 min or did it connect after 15 min?

Maybe if you're waiting this long (and the issue is not with the power) then it might be because you were switching back and forth between InternetHog and RoverOBC configurations and not selecting "Basestation Direct" fast enough?

When switching back from internet share mode you need to reboot the odroid and make sure to select "Basestation Direct" on the basestation as the odroid boots and as soon as the system lets you select an ethernet configuration.

Also I can't see but I'm assuming this was ping odroid which would resolve to ping 172.16.1.30, which wouldn't work if ROVER_OBC config wasn't up.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/space-concordia-robotics/robotics-prototype/issues/468#issuecomment-703184769, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEOB46KINWRA6ADKPQ4P6CTSI7D5XANCNFSM4SDJIYNA .

MartensCedric commented 4 years ago

Keep in mind this was for just a boot with the Odroid. Internet sharing worked fine

On Sat, Oct 3, 2020, 9:16 PM Cedric Martens, cedricmartens98@gmail.com wrote:

Me and Koa quit testing because it took more than 15 mins at one occasion (most of the time at least 150 ping sequences). At the end we couldn't even connect anymore so we ended up not testing the arm

On Sat, Oct 3, 2020, 9:14 PM PeterGhimself, notifications@github.com wrote:

Seriously, 15 min? I've seen it take a while sometimes but never that long... max a few minutes usually. Did you stop after 15 min or did it connect after 15 min?

Maybe if you're waiting this long (and the issue is not with the power) then it might be because you were switching back and forth between InternetHog and RoverOBC configurations and not selecting "Basestation Direct" fast enough?

When switching back from internet share mode you need to reboot the odroid and make sure to select "Basestation Direct" on the basestation as the odroid boots and as soon as the system lets you select an ethernet configuration.

Also I can't see but I'm assuming this was ping odroid which would resolve to ping 172.16.1.30, which wouldn't work if ROVER_OBC config wasn't up.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/space-concordia-robotics/robotics-prototype/issues/468#issuecomment-703184769, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEOB46KINWRA6ADKPQ4P6CTSI7D5XANCNFSM4SDJIYNA .

PeterGhimself commented 4 years ago

I'm saying after having done internet sharing you need to make sure to in a monkaS fashion that your basestation ethernet profile is "Basestation Direct" while the odroid is booting, otherwise you can run into these types of issues of non-connectivity. I'm assuming that's what the problem was, but that's why I'm not sure what y'all did in the moment.

Do you smell me?

MartensCedric commented 4 years ago

Kk well I have no clue what profile we were on though. But we hit the kill switch a few times. Guess we might have been on the wrong profile while booting but we kept changing it

On Sat, Oct 3, 2020, 9:19 PM PeterGhimself, notifications@github.com wrote:

I'm saying after having done internet sharing you need to make sure to in a monkaS fashion that your basestation ethernet profile is "Basestation Direct" while the odroid is booting, otherwise you can run into these types of issues of non-connectivity. I'm assuming that's what the problem was, but that's why I'm not sure what y'all did in the moment.

Do you smell me?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/space-concordia-robotics/robotics-prototype/issues/468#issuecomment-703185176, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEOB46MJYUI2QZICSSIZHA3SI7ETHANCNFSM4SDJIYNA .