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

Duckiebot Stuck in "Booting" Status, No SSH #20

Closed
ZeHolyQofPower opened this issue Sep 19, 2021 · 1 comment
Closed

Duckiebot Stuck in "Booting" Status, No SSH #20

ZeHolyQofPower opened this issue Sep 19, 2021 · 1 comment

Comments

@ZeHolyQofPower
Copy link

ZeHolyQofPower commented Sep 19, 2021

Running the command:
dts init_sd_card --hostname duck16 --type duckiebot -- configuration DB19
Then following the prompts gives no errors and no technical warnings. It even says:
"INFO:dts:Verified in 9 minutes, 30 seconds"
"INFO:dts:SD[/dev/sdb] successfully flashed!"
I was unable to verify that the card flashed correctly. The command:
dts init_sd_card --steps verify,setup --hostname duck16 --type duckiebot --configuration DB19
Returns a lengthy Python error I have recorded if needed.
If I attempt to reflash the same card again, it gives the error:
duck16 already exists

We have reproduced this with both the provided MicroSD card, a different SanDisk card, using the provided MicroSD to USB-A adapter, a different MicroSD to SDcard Adapter, and with multiple re-flashes to check combinations.

I do not know how to confirm if our card is flashed correctly.

This card is plugged into our duckiebot correctly, an ethernet wire is connected between bot and our system. This wire works correctly between different systems. The connection to the bot is detected by my laptop and named: "Realtek USB 10/100 LAN" strangely. This is configured to IPv4 Method: "Shared to Other Computers". The duckiebot's ethernet port is flashing with the connection.

I do not know if we are correctly connected to our bot.

The command:
ping duck16.local
Gives no packet loss.
dts fleet discover is now stuck in Status "Booting"
ssh duckie@duckie16.local Returns: ssh_exchange_identification: read: Connection reset by peer

@ZeHolyQofPower ZeHolyQofPower changed the title Can't Connect Bridge to Duckiebot Duckiebot Stuck in "Booting" Status, No SSH Sep 19, 2021
@ZeHolyQofPower
Copy link
Author

After another re-flash and a very careful startup process, we have succeeded in booting into the bot.
Here's the specific steps in specific order that worked:

  1. Re-Flash Card.
  2. Connect Ethernet Wire between systems.
  3. Configure correct ethernet connection correctly.
  4. Plug in power for duckiebot.
  5. Run dts fleet discover
  6. Wait for discovery to find bot. (Patience)
  7. Wait for status to change to "ready". If this takes >10 minutes, Restart process.
  8. Duckiebot is now available, do not attempt to SSH or ping until dts finishes with "Ready".

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

1 participant