Elastic 2025: A Lot of Little Things

Technical Programming
82

Elastic 2025.0.2

The next release of Elastic is now available! The update can be downloaded from here, or if you open the app while connected to the internet, you will receive a download link for this update.

The WPILib version of Elastic will not automatically check for updates, users of the WPILib version of Elastic will have to update their WPILib tools in the next release of WPILib.

Update Highlights

There’s only one new feature in this update:

Field 2d Struct Support

Elastic now supports Pose2d structs for field objects! With the current WPILib APIs, this has very little difference in how the user will interact with the field, but if a struct object is published in the same table as a Field2d widget, it will render on the field.

Bug Fixes

This update has more bug fixes than new features

Camera Stream Speed Fix

A critical issue was fixed where not all images were properly processed in an image stream, leading to low FPS, miscalculated bandwidth, and invalid images/glitch effects.

Camera stream performance should significantly improve.

Widget Dragging Fixes

Previously, if a widget was being dragged into the grid and a new Network Tables topic was announced, the widget would get stuck on the screen until a new widget was being dragged in. This has been fixed.

Leading Slash Fixes

Widgets that are created from a topic without a leading / will now be created properly. A fix for this was implemented in a previous update, however this only worked for individual topics, such as a boolean box. All widgets can be created regardless of whether or not they have a leading /

Full Changelog: https://github.com/Gold872/elastic-dashboard/compare/v2025.0.1...v2025.0.2

8 Likes
83

I just switched to Elastic (got tired of shuffleboard dying). I’m attempting to program an arm with combined feedforward and feedback control. Whenever I update my reference in Elastic, my driver station reports that there was a DS A-Stop Disable. Everything else works normally and the arm moves, I’m just not sure if this is intended to happen.

image
image1920×1040 153 KB

image
image1919×203 23.7 KB

84

Are you hitting the space bar while the robot is enabled? If so then it will E-stop the robot, the driver station has a global keyboard listener for the space bar for E-stopping the robot

85

I’m not. The A-Stop doesn’t do anything since I’m running in teleop. The issue is I’m not sure why an A-Stop is being sent since all I’m doing is updating my reference in Elastic.

86

That’s really odd, since Elastic doesn’t send any data to the driver stafion. Are you using the keyboard at all? That’s the only thing I could think of causing it

I’ll look more into this though, this is a strange one

87

Is there a way to send A-stop from the team driver station? I’m not sure I have seen that feature, just disable and e-stop.

88

I’m using the keyboard to type in the reference value I want and then pressing the widget submit button. I’m not pressing enter or space bar.

89

Backspace will do an A stop. Something new this year.

3 Likes
90

Ohhhhh, that’s probably it.

91

That seems like a feature no one asked for, why would they add that when we already have enter and space bar.

It’s now just that much harder to edit dashboard values for tuning.

92

Practice mode. Enter/space will disable/estop the robot, but not allow the match timer to continue and reenable for teleop

Edit to your edit: I agree that a different key might’ve been a better choice

2 Likes
93

I think it would have made more sense to only enable the backspace A-stop in practice mode, since that’s the only time you would ever even need to use it

1 Like
94

Several people asked for it. A-Stop Button

2 Likes
95

I’m literally going to immediately implement a feature with this that I wanted to do yesterday! Thank you for another amazing update

1 Like
96

I believe the A-Stop print is a red herring. The backspace for A-Stop only disables when the robot is in practice mode. It just prints otherwise. The Important thing is the last print, which does say that enter was hit, which would disable.

97

I am unsure where this issue is coming from, but the robot pose visualization in Elastic reports that my robot is fazing into the reef. My limelight visualization looks correct and the robot pose (values) displayed numerically the same as the limelight’s reading.

image
image907×536 68.7 KB

image
image1014×475 66.9 KB

98

What does the same pose look like when visualized in Glass or AdvantageScope? One possibility is that the different field dimensions between Crescendo and Reefscape are causing issues

100

it was similar in advantage scope.

101

Have you seen this thread? Limelight not matching 2025 field

102

Is it possible to run two instances of elastic at a time? My team is trying to have a side screen connected to our driver station laptop and we would like to run elastic for our operator to choose scoring locations.

1 Like