Trouble deploying code from new laptop

[Hsifeulbhsifder]

Our team had originally began deploying code via the classmate, but since have updated to another laptop, running Windows 7 with an i7 4700 processor. The laptop had worked wonderfully during actual competition and driving, but it did not allow me to deploy code, stating that there were 'Too many authentication failures". This also occurred with another laptop, which was a Mac-book. However, only with the classmate, did the code successfully deploy, so I'm wondering if it even is possible to use another laptop for building. It may have to do with the fact that I had changed the admin password on the roboRIO, but then again, it only affected the new laptops, and not the classmate. Any help would be appreciated. Thanks.

[Jared]

Originally Posted by Hsifeulbhsifder

Our team had originally began deploying code via the classmate, but since have updated to another laptop, running Windows 7 with an i7 4700 processor. The laptop had worked wonderfully during actual competition and driving, but it did not allow me to deploy code, stating that there were 'Too many authentication failures". This also occurred with another laptop, which was a Mac-book. However, only with the classmate, did the code successfully deploy, so I'm wondering if it even is possible to use another laptop for building. It may have to do with the fact that I had changed the admin password on the roboRIO, but then again, it only affected the new laptops, and not the classmate. Any help would be appreciated. Thanks.

It is likely because you changed the password on the roboRIO. Messing with these settings has caused problems for other teams, and I would really recommend changing it back. It'll only make it easier for others to help you when you get to competition - plus, if you forget the password, there's no easy way to change it without contacting NI.

I think you (or your team) changed settings on the classmate that use your new password but didn't make these changes on your new laptop or your macbook.

[Alan Anderson]

You should definitely remove the admin password. Having it there complicates things. Unfortunately, I don't think you will be able to do that without completely reimaging the roboRIO.

[Hsifeulbhsifder]

Thanks for the help, but is there anyway to input the password into eclipse, or possibly the build files, so that it can deploy using the password, or is there an easier way of removing the password without having to re-flash the rio. Thanks.

[Alan Anderson]

You can put the password in the build preferences. You probably have already done that on the Classmate.

According to a couple of the Beta Test teams, you cannot remove the password without reloading the roboRIO image. The option to do so is not part of the BusyBox Linux shell.

[plnyyanks]

Originally Posted by Alan Anderson

You can put the password in the build preferences. You probably have already done that on the Classmate.

According to a couple of the Beta Test teams, you cannot remove the password without reloading the roboRIO image. The option to do so is not part of the BusyBox Linux shell.

I don't have access to a RIO to test with, but it seems possible to change a password with a config file and chpasswd. Although chpasswd isn't available in the busybox version on my phone (v1.23.1), so go figure...

[Alan Anderson]

Originally Posted by plnyyanks

...it seems possible to change a password with a config file and chpasswd.

Changing a password is simple. Doing so is what caused the deployment failures described in the original post. Removing a password is not supported.

[ozrien]

Is there a reason to change the Rio's password? It makes csa-ing more difficult and breaks code deployment. There is no upside, even if you hack the scripts to make it work

[virtuald]

Originally Posted by ozrien

Is there a reason to change the Rio's password? It makes csa-ing more difficult and breaks code deployment. There is no upside, even if you hack the scripts to make it work

I suspect that people are (correctly) conditioned to change passwords when there's an option to do so, particularly if the password is empty. It's "more secure", after all.

Of course, since you can anonymous FTP on the roborio with impunity, seems like it's a silly thing to do.