Carl Hauser

OK. If it is working for most teams I can understand. And I certainly don't think it should be changed at this late date in 2025. For us, we really...

The robot code and shuffleboard were 2025.3.1 I agree, having error information from the client would be most helpful. But without radios configured as they are on the field I...

Looking at the Vivid hosting site about the radios I can't tell where the bandwidth limit is imposed. There's one mention of Team AP mode having a 7mbit/s limit in...

That's unfortunate and hopefully is something that can be changed, if not for this year then for next. Teams should be able to test in an environment that is as...

Could it be the client websocket timeout that's driving this? ``` ./cpp/NetworkClient.cpp:static constexpr uv::Timer::Time kWebsocketHandshakeTimeout{500}; ```

I tried this morning to reproduce the problem using an old radio configured with a bandwidth limit and high bandwidth background traffic. Elastic connected without difficulty every time. Details -...

Ah, yes. If the camera stream widget was already on the dashboard you wouldn't need NT for the streaming to start. Thanks!

Although I was not able to get an experiment set up with the competition AP firmware I was able to do experiments that targeted loss of particular messages in the...

Another observation during the course of the experiments is that Elastic makes and keeps open two NT4 connections to the robot. This may be intentional, but if not it should...

I think it is probably OK: the messages in the robot log are ``` NT: Got a NT4 connection from 127.0.0.1 port 37476 NT: CONNECTED NT4 client 'Elastic@1' (from 127.0.0.1:37476)...