I’m currently running Windows 10 trying to install Robotpy 2019.0.1 on the robot via Command Prompt. I’m getting an SSH error where the connection is timing out. The same thing is happening when trying to install WPILIBSo far, I’ve installed Python 3 .7.2 (latest version as of now) and the FRC Suite 2019. I’ve imaged the Roborio twice, once via USB and the other via Ethernet. No luck making the SSH connection with either of those. When connecting the laptop to the Roborio either via ethernet or Wi-Fi, FRC Driver Station reports a green status indicator for “Communications” and “Robot code”. So there’s a connection using both of those. I find it confusing that it has robot code. I haven’t even written or deployed any code yet. This is my first year switching from Java to Python. Any idea why it can’t connect via SSH using the terminal, which has administrative privileges and is pointed towards the directory containing installer.py?
Are you connected to the robot over the wireless? It looks like in your screenshot that you’re connected to a network connected to the internet, which presumably your roboRIO is not on.
I see that it’s trying to connect to the robot at 10.41.66.2 (which is the default that the robotpy installer connects to… we need to update it). Is that the robot’s IP address? If it isn’t, then the connection will fail.
To fix it, you can do one of two things:
- Fix the RoboRIO so its IP is 10.41.66.2 – you need to browse to http://roborio-4166-frc.local and fix it there
- Remove the installer configuration (
.installer_config) and when it asks you for the robot hostname use ‘roborio-4166-frc.local’
One of those two things should fix it. I’ve been meaning to make the installer be smarter about connecting to the roborio, so this is probably a good reason for me to do it. 
I’ve fixed the robotpy-installer so it will be smarter about connecting to the roboRIO. Thanks for reminding me of this issue!
See this pull request for details. If you just want to try an updated installer file, you can download it via this link.
Thank you. That makes things easier.
~Mr.R^2
I was connected via Ethernet and Wi-Fi over the internet. I actually got it fixed by running the FRC Radio Configuration Utility, which I didn’t realize I had to do because I wasn’t the main programmer last year. I got past the SSH error, but now I get error 127. How do I fix this? Do I have to clear some caches or something?
I tried the new code and using that hostname roborio-4166-frc.local and no luck with that. Still getting non-zero status 127.
I tried another copy I found on GitHub (GitHub - robotpy/robotpy-installer: RobotPy installer program) and that is reporting error 11001.
The IP address 10.41.66.2 is the correct one because the RoboRIO Imaging Tool and the radio seem to be reporting that. I’ve re-imaged it again and that doesn’t fix anything. Any ideas?
You need to install RobotPy using the install-robotpy command.
@robotstangs did that address your issue?
I finally got it working. Thanks!
The problem was that I could not get it working because the Roborio was using the wrong version. I thought the “Firmware Update” would image the Roborio with the latest update. Turns out it doesn’t actually update the firmware at all. “Format Target” does. “Firmware Update” does what I believe “Format Target” should: Reformatting and resetting the robot. “Format Target” should do what “Firmware Update” does. I believe it has misleading titles for their functionality. Either way, I got the latest update on the Roborio and all the programming libraries installed successfully!