You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
Re-Flash Card.
Connect Ethernet Wire between systems.
Configure correct ethernet connection correctly.
Plug in power for duckiebot.
Run dts fleet discover
Wait for discovery to find bot. (Patience)
Wait for status to change to "ready". If this takes >10 minutes, Restart process.
Duckiebot is now available, do not attempt to SSH or ping until dts finishes with "Ready".
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
The text was updated successfully, but these errors were encountered: