I loaded the SnakeEyes version of Photonvision on my Raspberry Pi. It seemed to work fine except it didn’t seem to save settings. I connected the Raspberry Pi to the robot through the laptop. I got a mismatch error because the Photonvision on the Raspberry Pi was different than the laptop. I updated the Raspberry Pi with the latest jar from Photovision. Now my pi camera does not work. Any assistance would be greatly appreciated. Would it make more sense for me to just get a Limelight? Thank you.
I went to the Discord for help, but all I got was people telling me i did not follow directions. What did i miss?
Hey JLS, I gave an answer a week back and have just been watching here, seeing if others have answers.
But, since you asked specifically:
The reality: Not a single person knows at this point. All anyone has to go off of is the 89 words you’ve shared above. And of those words, the only thing that seems meaningful is “I installed photonvision (on something), and my camera (unspecified) doesn’t work”.
Contrast that with the tens of thousands of words in the photonvision documentation explaining how it works from the user facing side, which only describe it when it is fully working. There’s no way to have a concrete answer at this point.
What we have so far is a random collection of facts that you deemed important enough to say, but no information about what’s in-between.
The challenge ahead of you is actually to learn to describe enough of your situation to get answers which will move you forward.
This is a very hard challenge - and it’s going to be frustrating. The reality is that, currently, you don’t know what you don’t know. It’s going to feel like we’re asking stupid questions, or asking you to repeat steps. That’s intentional.
The reason is that we didn’t see what happened the first time you went through the steps, and (as you indicated) you don’t yet know what’s important to look for at each step to say with certain the step was successful.
There’s about 10 reasonable ways to get photonvision up and running, and about ten million ways to get it not running. For that reason, we’re going to ask you to start from scratch again. We need to be sure you’re working on one of the 10 good ways, and not one of the much-more-common incorrect ways.
So here’s the plan:
Prove a Compatible Hardware Set
First, read through this documentation page in detail. Describe what hardware you’re using, being very specific to show where it’s listed on the supported/recommended hardware page. If it’s not there, we’ll need the most precise info you can provide on exactly what pieces of hardware you’re working with, and how you have them wired together. Pictures are great, as are links to exactly where you purchased the hardware (or where I could purchase an equivalent device).
Of note, as mentioned a few weeks back - please get yourself out of the midest of “using SnakeEyes”. Historically, there was specific support needed so that PhotonVision could control the LED’s. That is no longer required, so there is no special steps for that part of your hardware equation. You are installing photonvision on a raspberry pi. Forget SnakeEyes.
Install from Scratch
Assuming your hardware is indeed a supported Raspberry Pi, Follow these instructions, step by step, start to finish. Do not skip steps. At each step, document what you did. Re-write the step in your own words, and write an explanation of why you think it succeeded or did not succeed. Take screenshots, circling things that led you to your conclusions.
At the first step where you believe something did not work, stop. Document what you expected to see, and what you actually saw. Ask about this specifically. State your assumptions, and let folks here help correct you.
Respond to Feedback
Once you give this more detailed output, you’ll get some questions. People may ask you to fill in the gaps, take another screenshot, send a log, etc. All these are attempts to narrow the scope of the issue. Since each observation can correspond to many root causes, the follow-up questions are mini experiments used to prove or disprove certain root causes being the issue.
Be Relentless
Again - this process will seem long and drawn out. The issue is that we aren’t in the room with you, and at the same time as we’re trying to help you debug, we’re also teaching you what you need to be looking for to report issues successfully. 99% of the information and questions asked won’t actually point to root cause - rather, they help throw out things that are not root cause. This will feel frustrating because after each answer, the other people will still have to say “we don’t know”. The key is - we don’t yet know what the issue is - each question is a step in the process to get us closer to it though.
Also - I’d recommend - pick one forum to focus the debug until we have the first root cause found. I think we’re up to two CD threads and a discord post - anything will work, but keep the focus in one spot.
1 Like
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.