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

Linux: cannot connect to simulation #309

Open
prensing opened this issue Jan 12, 2025 · 3 comments
Open

Linux: cannot connect to simulation #309

prensing opened this issue Jan 12, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@prensing
Copy link

Describe the bug
When I run a robot simulation, and try to connect, it never does.

To Reproduce
Start simulation
Start AS, use "Connect to simulation", it never connects.

I see lots of connection messages in the simulation output, but it does a new one every ~1 second, so presumably, AS does not think it worked.

I tried the 2024 version, and it connected immediately.

Some output from the simulation:

`....
[phoenix] Library initialization is complete.

[phoenix-diagnostics] Server 2025.1.0 (Jan 3 2025, 16:39:33) running on port: 1250

[PathPlanner] PathfindingCommand finished warmup
NT: Got a NT4 connection from 127.0.0.1 port 41548
NT: Got a NT4 connection from 127.0.0.1 port 41566
NT: Got a NT4 connection from 127.0.0.1 port 41588
NT: Got a NT4 connection from 127.0.0.1 port 41606
NT: Got a NT4 connection from 127.0.0.1 port 41622
NT: Got a NT4 connection from 127.0.0.1 port 40992
NT: Got a NT4 connection from 127.0.0.1 port 41016
NT: Got a NT4 connection from 127.0.0.1 port 41038
NT: Got a NT4 connection from 127.0.0.1 port 41054`

Version (required):
Version: 4.1.1
Distributor: WPILib
Platform: linux-x64
Build Date: 1/9/2025, 20:11:28 UTC
Electron: 32.0.2
Chromium: 128.0.6613.84
Node: 20.16.0

Simulation is using WPILIb 2025.2.1. Note that this is on Linux. I have not tried Windows.

@prensing prensing added the bug Something isn't working label Jan 12, 2025
@jwbonner
Copy link
Member

To clarify, 2025 AdvantageScope can't connect to a 2025 WPILib project but 2024 AdvantageScope can connect to the same project? This a particularly odd issue, since AdvantageScope's NT client hasn't changed for 2025. I also haven't been able to recreate this on a Linux device using this code, so anything that helps narrow down the issue would be useful. Here are some things you could test:

  • Can 2025 AdvantageScope connect to a different 2025 project? What about a 2024 project?
  • Does this happen on other devices? What if you run AdvantageScope and the simulator on different devices?

@prensing
Copy link
Author

prensing commented Jan 13, 2025

To clarify, 2025 AdvantageScope can't connect to a 2025 WPILib project but 2024 AdvantageScope can connect to the same project?

Yes correct. I will try to reproduce it and get you more info, test results.

@prensing
Copy link
Author

More info. I see the same issue with our 2024 robot code: I can't connect with the AS.
I can connect with version 3.0.1.
I will try a different machine when I can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants