search

LimelightVision / limelightlib-wpijava

48 stars 16 forks source link

Bad LL 3D Data Even Though Targets Are Seen #13

Closed vyang2968 closed 1 year ago

vyang2968 commented 1 year ago

Using LimelightHelpers.getBotPose3d("") works amazingly and returns exactly what I need. However, out of curiosity, I tried LimelightHelpers.getBotPose3d_wpiBlue("") and the one for the red, and it prints Bad Limelight 3D Data on the RioLog. I am not sure why it works for one and not for the other. Also what is the difference?

bhjelstrom commented 1 year ago

It's great to hear that botpose is working well for you. Are you using the latest image (2023.2)? https://docs.limelightvision.io/en/latest/software_change_log.html#id1 2023.2 is required for wpired and wpiblue to work.

WPIRed and WPIBlue simply use different the coordinate systems that match the following: image

If you're a blue driver, wpiBlue puts the origin at the rightmost side of your driverstation wall. If you're a red driver, wpiRed puts the origin at the rightmost side of your driverstation wall.

vyang2968 commented 1 year ago

updating the limelight to the latest version worked. thanks for the help!