Software Change Log
Contact us or post to CD to suggest upgrades for Limelight!
2020.4 is another critical update that eliminates the intermittent 2-4 second crash that could occur during an abrupt mjpeg stream disconnection. This often happened at the very end of the match, and in some cases could happen during matches.
2020.3 is a critical update that addresses intermittent networking-related software restarts, and addresses a crash that would occur upon USB camera disconnection.
2020.2 pushes Limelight's hardware even further by adding the ability to pan and zoom to any point. It also adds a brand new video mode and important bug fixes. Let us know what features you would like to see in future updates!
3x Hardware Zoom at 60 FPS
Our last update added 2x Hardware Zoom for all Limelight models at no cost whatsoever. We’ve managed to push our hardware zoom even further with 3x Hardware Zoom. All Limelight models are now capable of 3x Hardware Zoom at 60fps. This makes full-court tracking even easier for every team.
The following gif shows 1x, 2x, and 3x Hardware Zoom from the sector line (full court shot line):
This gif shows only 1x and 3x Hardware Zoom from the full-court sector line shot location:
Robots capable of shooting from both long and short distances in 2020 would have found it difficult to use Hardware Zoom on their Limelights without the use of an active, adjustable Limelight mount. We have incorporated Hardware Panning to solve this problem.
This gif shows Hardware Panning while using 3x Hardware Zoom. This should simplify mounting for teams who wish to use Hardware Zoom:
Hardware Panning on the X and Y axes at 3x Hardware Zoom
- Address driver issues that were breaking the color balance sliders
- Revert all networking-related drivers to 2019 season variants to address a small number of network performance reports from teams
2020.1 adds one of Limelight's coolest features yet: 2x Hardware Zoom. This is not digital zoom, and it is now enabled for all Limelight versions.
2x Hardware Zoom
Not Digital zoom
Enable 2x Hardware zoom to achieve vastly improved tracking at long range, and stable tracking at full-court distances.
This feature comes with absolutely no latency or framerate cost - tracking continues to execute at 90fps with no additional overhead.
Zoom from the autonomous starting line (~127" away):
Zoom from the front of the trench run (~210" away):
Zoom from the front of the color wheel (~310" away):
Zoom from the very back of the trench run (~420" away):
Zoom from the sector line (nearly full-court):
New SolvePNP / 3D features (Still experimental)
We have added the "Force Convex" option to use only the outermost points of a target - this is necessary in 2020 due to the thin tape used for the hexagonal target.
The "bind target" option has been added. This feature binds "tx" and "ty" to the 3D target. This is required to guide robots to score using 3D targets.
Finally, add the "Goal Z-Offset" option to automatically offset your desired target location in 3D space on the Z-axis.
In Infinite Recharge, the "Goal Z-Offset" would be used to track the center of the small, circular goal behind the hexagonal goal.
SolvePnP is still an experimental feature! We believe there are creative ways to play this game without SolvePnP, but we will continue to improve this feature.
Color sensing with "tc"
- Read the new "tc" array in Network Tables to obtain Red, Green, and Blue values at the crosshair's location. Adjust "Blue Balance" and "Red Balance" on the input tab to achieve perfect color sensing.
- USB Camera functionality broken in 2020.0 is now fixed in 2020.1
- SolvePnP functionality broken in 2020.0 is now fixed in 2020.1
- SolvePnP properly uses the model center as the axis visualization center
2019.7 adds two new features.
160x120 30fps streaming
Smoother, lower-bandwidth streaming for teams that use wide-angle USB cameras. Our 180-degree camera stream bandwidth dropped from ~3.7mbps to ~1.8 mbps.
Change the stream resolution in the settings tab.
Smart Speckle Rejection
Teams that have mounted their cameras in-line with the target this year have had to deal with unwanted LED reflections.
The area slider does not always solve this problem, as teams want to track small vision targets at large distances.
This new feature will automatically reject relatively small contours that have passed through all other filters.
As a robot moves away from a vision target (decreasing its size), SSR will automatically adjust to only reject relatively small contours.
2019.6.1 Hotfix (3/14/19)
2019.6.1 fixes Grip uploads.
2019.6 is all about reliability.
- Address issue that could cause some USB cameras to fail on boot.
- Make Limelight more (if not completely) resistant to FMS restarts and field / laptop networking changes.
- Limelight will no longer hang after a sudden client networking change.
Raw Contour Sorting (BREAKING CHANGE)
- Intersection filters no longer affect raw contour sorting.
*LL auto-posts certain pieces of information to SmartDashboard (IP Address, Interface url, etc.). The names of these values now contain the hostname.
Features & Changes
- Significantly increase precision and stability of the compute3d feature. Translation and rotation measurements are stable at larger distances.
- Max Black Level Offset increased to 40 (from 25) for even darker images.
- New "Closest" sort options in the "Output" tab while "Dual Crosshair" mode is enabled.
- Standard - Current "closest" sorting implementation with "Dual Crosshair" mode.
- Standard V2 - Experimental, smart "closest" sorting implementation with "Dual Crosshair" mode.
- Average of Crosshairs - "Closest" sort origin with "Dual Crosshair" mode is the average of the two crosshairs.
- Crosshair A - "Closest" sort origin with "Dual Crosshair" mode is crosshair A.
- Crosshair B - "Closest" sort origin with "Dual Crosshair" mode is crosshair B.
- New "LED Mode" pipeline options: "Left Half", "Right Half"
- Floating-point raw corner values while compute3D is enabled.
- Hide image decorations while using magic wands
- Larger stream in web interface
With 2019.5 we are introducing the brand new compute3D camera localization feature. Only a handful of teams have ever attempted to add this feature to their vision systems, and now it is available to all Limelight 1 and Limelight 2 users.
This is not a silver bullet for this year's game. We highly recommend thinking of creative ways to use the standard high-speed 90 fps tracking unless this feature is absolutely necessary.
All example gifs were created with an LL2 mounted on the side of a kitbot. This is why you will see slight changes in translation during turns.
High-Precision Mode and PnP
With 2019.4, we introduced corner sending. This allowed advanced teams to write their own algorithms using OpenCV's solvePNP(). With 2019.5, this is all done on-board.
Upload a plain-text csv file with a model of your target. We have pre-built models of 2019 targets hosted on our website. All models must have a centered origin, and use counter-clockwise point ordering with inch scaling.
Enable the new high-res 960x720 mode, and then enable "Solve 3D" to aquire the position and rotation of your Limelight relative to your target.
Corner numbers are now displayed on the image for easier model creation and threshold tuning.
Read all 6 dimensions of your camera's transform (x,y,z,pitch,yaw,roll) by reading the "camtran" networktable number array.
- The reported vertical FOV for LL2 has been fixed to match the listed value of 49.7 degrees. This will change your "ty" values
- Fix stream-only crash that could occur when fisheye USB cameras were attached.
- Fix rare hang caused by networking-related driver.
- Corner approximation is now always active.
We believe all critical bug reports are covered with this release.
- Send the corners of your target as two arrays (tcornx, tcorny) by enabling "send corners" in the "Output" tab. This will further enable teams that are interested in advanced pipelines with methods like solvePNP().
- Adjust corner approximation with the "corner approximation" slider in the "Output" tab.
- Fix hang + rare crash that would occur when two targets had exactly the same area, x coordinate, or y coordinate.
- Fix area calculation in dual- and tri-target modes.
- Optimize contour sorting for better performance.
2019.3 addresses a number of bugs and feature requests.
Stream Rate (bandwidth reduction)
- Set the stream rate to "low" in the settings page for a lower-bandwidth 15fps video stream.
Raw Contours disabled in NetworkTables (bandwidth reduction)
- Raw contours are now disabled by default. This will further reduce Limelight's overall bandwidth.
- There are now ~180 fewer networktables entries submitted per second by default.
- See the new "Raw Contours" pipeline option in the "Output" tab to re-enable raw contours.
Active Pipeline Index
- Read the networktable key "getpipe" to get the true active pipeline index of the camera. This is updated at 90hz.
- The active pipeline index is now written to the videostream underneath the FPS display.
Left and Right Intersection Filters
- Teams may now choose between "left" and "right" dual-contour intersection filters. The "above" and "below" intersection filters were added in 2019.2.
- Fix LabView Dashboard streaming bug introduced in 2019.2
- The webpage no longer requests icon fonts from a the internet. All fonts are stored locally. This should speed up interface loading.
- Reduce "driver mode" exposure.
- Fix "Distance Transform" GRIP implementation
- Fix 20-second communication delays caused by changing the hostname.
2019.2 adds new features to better equip teams for the 2019 season.
Additional Changes and Fixes
- IP Address is auto-posted to SmartDashboard/Shuffleboard for easier event troubleshooting. We have had almost no reports of this being an issue, but this serves as another contingency feature.
- Pipeline name is auto-posted to SmartDashboard/Shuffleboard
- Access the width and height of the rough bounding box in pixels with new networktables keys.
- Access the longest side and shortest side of the perfect bounding box in pixels with new networktables keys.
- "Sort Mode" now applies to dual-contours
- "Sort Mode" is now fixed
- 5802 stream is less taxing on the camera
2019.1 fixes all major bugs reported during the beta
- Performance is back to a steady 90fps. A driver issue was the root cause of our performance problems during beta
- IP and hostname settings actually apply and "stick"
- Magic Wands have been re-ordered to match those of Limelight 2018 software
- We now support Grip inputs like masks through the web interface
- NetworkTables freeze fixed
With 2019, we are introducing GRIP support, a brand-new interface, and a cleaner flashing procedure.
- Build pipelines with GRIP For Limelight, and export "LL Script" files to upload to your camera.
- Masks and NetworkTables support will be added in a future update
- Expose a bare video stream at http://<limelighturl>:5802 for testing in grip
All-new web interface
- Smaller controls
- More tooltips
- Add the ability to turn off the LEDs from the interface
- Move display combobox underneath stream for easier display switching
- Faster communication to Limelight. New web tech allowed us to simplify other parts of our code.
- We have migrated to "Balena Etcher"
- Etcher is twice as fast and works on all platforms
- Flash popups are fixed with the migration.
- The LED Mode has been modified to allow for pipeline-specific LED Modes. LED MODE 0 is now "pipeline mode", while mode 1 is "force off"
- Faster boot times in automatic IP assignment mode.
- Optimizations and minor bug fixes
2018.5 fixes a critical issue that would prevent users from tuning pipelines on snapshots.
2018.4 adds new contour sorting options. These are fairly important for cube tracking this year, as teams don't necessarily want to track the largest cube in view. In many cases, teams want to track the cube that is closest to their intakes. Many users have had to use the raw contours feature to implement their own sorting, so we want to make this as easy as possible.
Contour Sort Mode
2018.3 fixes a major networktables reconnection bug which would cause NetworkTables settings changes to not propagate to Limelight. Thanks to Peter Johnson and the WPILib team for pinpointing and fixing the underlying NT bug. This was (as far as we know) the last high-priority bug facing Limelight.
Settings changes such as ledMode, pipeline, and camMode should always apply to Limelight. You should no longer need workarounds to change Limelight settings while debugging, after restarting robot code, and after rebooting the roborio.
Fix major NT syncing issue which broke settings changes (ledMode, pipeline, and camMode) during LabView debugging, and after a reset/reboot of the roborio.
- The eye dropper wand uses the same 10 unit window for Hue, but now uses a 30 unit window for saturation and value. This means that thresholding is more often a one-click operation, rather than a multi-step process.
2018.2 fixes all known streaming bugs with various FRC dashboards. It also makes Limelight easier to tune and more versatile during events.
Snapshots allow users to save what Limelight is seeing during matches or event calibration, and tune pipelines while away from the field.
Save a snapshot with the web interface, or by posting a "1" to the "snapshot" NetworkTables key
To view snapshots, change the "Image Source" combo box on the input tab. This will allow you to test your pipelines on snapshots rather than Limelight's camera feed
Limelight will store up to 32 snapshots. It will automatically delete old snapshots if you exceed this limit.
New Streaming options
- We've introduced the "stream" NetworkTables key to control Limelight's streaming mode. We've received requests for PiP (Picture-in-Picture) modes to better accomodate certain dashboards.
- 0 - Standard - Side-by-side streams if a webcam is attached to Limelight
- 1 - PiP Main - The secondary camera stream is placed in the lower-right corner of the primary camera stream.
- 2 - PiP Secondary - The primary camera stream is placed in the lower-right corner of the secondary camera stream.
Increase streaming framerate to 22fps
- Look out for faster streams in an upcoming update
Erosion and Dilation
- Enable up to one iteration of both erosion and dilation.
- Erosion will slightly erode the result of an HSV threshold. This is useful if many objects are passing through a tuned HSV threshold.
- Dilation will slightly inflate the result of an HSV threshold. Use this to patch holes in thresholding results.
- Restart Limelight's vision tracking from the web interface. This is only useful for teams that experience intermittent issues while debugging LabView code.
- Drop steady-state pipeline execution time to 3.5-4ms.
- Fix Shuffleboard streaming issues
- Fix LabView dashboard streaming issues
- Red-Balance slider
- Blue-Balance slider
- Better default color balance settings
- Increased max exposure setting
On top of a ton of new case studies, more detailed documentation, and a full example program for an autonomous STEAMWORKS shooter, the software has received a major upgrade.
New Vision Pipeline interface:
Add up to 10 unique vision pipelines, each with custom crosshairs, thresholding options, exposure, filtering options, etc.
Name each vision pipeline.
Mark any pipeline as the "default" pipeline.
Instantly switch between pipelines during a match with the new "pipeline" NetworkTables value. This is useful for games that have multiple vision targets (eg. the gear peg and boiler from 2017). This is also useful for teams that need to use slightly different crosshair options per robot, field, alliance, etc.
Download vision pipelines from Limelight to backup or share with other teams.
Upload vision pipelines to any "slot" to use downloaded pipelines.
- New Crosshair Calibration interface:
- "Single" and "Dual" crosshair modes.
- "Single" mode is what Limelight utilized prior to this update. Teams align their robots manually, and "calibrate" to re-zero targeting values about the crosshair.
- "Dual" mode is an advanced feature for robots that need a dynamic crosshair that automatically adjusts as a target's area / distance to target changes. We've used this feature on some of our shooting robots, as some of them shot with a slight curve. This feature will also be useful for robots with uncentered andor misaligned Limelight mounts.
- Separate X and Y calibration.
Add Valid Target "tv" key to Network Tables.
Add Targeting Latency "tl" key to Network Tables. "tl" measures the vision pipeline execution time. Add at least 11 ms for capture time.
Draw additional rectangle to help explain aspect ratio calculation.
Remove throttling feature, and lock Limelight to 90fps.
Disable focusing on most web interface buttons. Fixes workflow problem reported by teams who would calibrate their crosshairs, then press "enter" to enable their robots.
- Post three "raw" contours and both crosshairs to Network Tables.
- Access a raw contour with tx0, tx1, ta0, ta1, etc.
- Access both raw crosshairs with cx0, cy0, cx1, cy1.
- All x/y values are in normalized screen space (-1.0 to 1.0)
Add "suffix" option to web interface. Allows users to add a suffix to their Limelights' hostnames and NetworkTables (e.g. limelight-boiler). This feature should only be utilized if teams intend to use multiple Limelights on a single robot.
Display image version on web interface
- Decrease networking-related latency to ~0.2 ms from ~10ms (Thanks Thad House)
- Move stream encoding and jpg compression to third core, eliminating 10ms hitch (25 - 30ms hitch with two cameras) seen every six frames.
- Drop steady-state pipeline execution time to 5ms with SIMD optimizations.
- New Latency testing shows 22 ms total latency from photons to targeting information.
- Upgrade Network Tables to v4 (Thanks Thad House)
- Optimize contour filtering step. Latency no longer spikes when many contours exist.
- Much improved hysterisis tuning.
- Significantly improve responsiveness of webinterface<->limelight actions.
- Fix minor area value inaccuracy which prevented value from reaching 100% (maxed ~99%).
- Fix half-pixel offset in all targeting calculations
- Fix camera stream info not populating for NT servers started after Limelight's boot sequence. Regularly refresh camera stream info.
- Fix bug which caused aspect ratio to "flip" occasionally.
- Force standard stream output (rather than thresholded output) in driver mode.
- Fix bug which prevented LEDs from blinking after resetting Networking information
- Improved contour sorting. Was favoring small contours over larger contours.
- New Coordinate system: Center is (0,0). ty increases as the target moves "up" the y-axis, and tx increases as the target moves "right" along the x-axis.
- More accurate angle calculations (Pinhole camera model).
- Display targeting info (tx, ty, ta, and ts) on webpage
- Default targeting values are zeros. This means zeros are returned if no target is in view.
- New side-by-side webpage layout. Still collapses to single column on small devices.
- Continuous slider updates don't hurt config panel performance.
- Aspect ratio slider scaled such that 1:1 is centered.
- New Imaging tool. Tested on Win7, Win8 and Win10.
- Post camera stream to cameraserver streams. Works with smart dashboard camera streams, but shuffleboard has known bugs here
- Quartic scaling on area sliders, quadratic scaling on aspect ratio sliders. This makes tuning much easier
- Organize controls into “input”, “threshold”, “filter”, and “output” tabs
- Continuous updates while dragging sliders
- Area sent to NT as a percentage (0-100)
- Image size down to 700MB from 2.1GB
- Image size down to 2.1GB from 3.9GB
- Add driver mode and led mode apis
- Set ledMode to 0, 1, or 2 in the limelight table.
- Set camMode to 0 or 1 in the limelight table.
- Add ability to toggle between threshold image and raw image via web interface (will clean up in later release)
- Post camera stream to network tables under CameraPublishing/limelight/streams (will need a hotfix)
- Add skew to targeting information (“ts” in limelight table)
- Add base “CommInterface” in anticipation of more protocols
- Lots of boot and shutdown bullet-proofing
- Hue range is 0-179 from 0-255
- Decrease max log size, clear logs, clear apt cache
- Manual ISO sensitivity
- Minimum exposure increased to 2
- Read-only boot partition
- Mount all partitions with noatime option
- Disable all swap functionality (100 mb)
- Auto chmod 777 adminserver and visionserver from rc.local
- Smaller image
- “Convexity” changed to “Fullness”
- Exposure range set to 0-128 ms from 0-255 ms
- Support two cameras
- Fully support single-point calibration