Driver Station connects using old laptop but not new one

[Greg McKaskle]

Well I feel so much more secure knowing that is there. But seriously, thanks for sharing this.

Greg McKaskle

[MamaSpoldi]

Originally Posted by Greg McKaskle

Well I feel so much more secure knowing that is there. But seriously, thanks for sharing this.

Greg McKaskle

Unfortunately I spoke too soon. Although the driverstation on our Windows 10 laptop is now able to connect sometimes... many times it does not. It is unreliable at best, which we all know is not acceptable for competition. Still continuing to search for the definitive answer to making it work consistently.

[tcjinaz]

Hey Greg, here's another:

We had a W7 laptop running the robot, download and go no problem, dashboard behaving,

The we switch to another laptop, same configuration. Seems to download new code, but the dashboard is not what we expect, missing PID systems, some other oddities. We restart the db, what we expect shows up, things are OK for a while. Then we modify PID parameters in RoboBuilder, and we lose Robot Code. No deploy works. roboRIO responds appropriately to roborio-3853-frc.local.

Weirdness: new log starting every few seconds on DS.

Any idea what we screwed up this time?

Thanks,
Tim
(ya missed me, didn't ya

[Mark McLeod]

Tim, is your Dashboard LV or SmartDashboard?
What language are you deploying?

[tcjinaz]

Originally Posted by Mark McLeod

Tim, is your Dashboard LV or SmartDashboard?
What language are you deploying?

DOH
I know better.

We're using Java, and the (old) SmartDashboard.

[Mark McLeod]

The old Smartdashboard has a thing where if the handshake with the roboRIO doesn't go off correctly, then your variables won't show up on the Smartdashboard.

Try using the roboRIO reset button when this happens.

[tcjinaz]

Originally Posted by Mark McLeod

The old Smartdashboard has a thing where if the handshake with the roboRIO doesn't go off correctly, then your variables won't show up on the Smartdashboard.

Try using the roboRIO reset button when this happens.

That seemed to help some. LiveWindow is still a mess.
The really good news is that SFX is not crashing any more, after doing the startup via:
java -jar sfx.jar

Thanks!