I have spent quite a bit of time trying to get this to work, and I suspect some kind of configuration problem. I’m hoping that if I list everything, someone might be able to see what’s wrong.
frc_camera_s, using compiled .hex that was in the download
CMUcam2 connected via TTL port to RC
2006 RC tethered to 2006 OI
tilt/pan servos connected to RC pwm1,2
RC pwm to CMUcam2 power
jumpers on pan reverse, oscillator connect, internal power to servos
DB-9 serial from RC program port to laptop via USB to Serial converter
12 volt and 7.2 volt batteries fully charged
The camera shows a green light, and all of RC lights are green like normal. The camera holds its default position, and does not respond to any light. Nothing comes up over the terminal, although I expected to see “Scanning…”. With the camera configured stand-alone (DB-9 to USB to laptop, servos plugged directly in to camera, power still supplied by RC) I was able to use LabView and the CMUcam2 demo program to calibrate the camera well. It tracked as I believe it was supposed to without any problems.
Any assistance would be appreciated. Thanks.
Dublin Robotics, Team 1014 (with the Bad Robot t-shirts)
I was working with another team today that was also having a similar problem. Here’s the thread. Unless you’re using the code build that was messed up, I can only conclude that your TTL serial port is malfunctioning. Just as I had the other team do, turn-on debugging messages in camera.h and report back with the output (if any) from your terminal screen. In the meantime, I’ll whip-up a piece of software that you can use to test the serial port.
I had already verified that I was not using the code with the serail port setting bug. I will run the two tests you asked for as soon as I get the RC and camera, which are locked in the school until Tuesday morning. I can’t get the link to the other forum you mentioned to work. Thank you, and I’ll post my results when I have them.
I ran the serial port diagnostic tests. In loopback mode, terminal input was not echoed. When connected to the camera, there was no responce. I am confident that I configured everything per the ReadMe file.
When I ran debug, the following was printed to the terminal:
Camera: Initialized abnormally with code 131
Camera: Initialization state = 1
Camera: Initialization state = 2
Camera: Initialization state = 3
I hope to test the TTL to RS232 board soon using the ifi instructions.
Thank you for your help.
One thing you didn’t list is whether or not you still have anything plugged into the DB-9 on the CMUcam board. If the computer is still connected there, it’ll interfere with the RC-to-camera communication.
This indicates that your TTL-RS232 converter board, cable, or the TTL serial port port itself is messed-up. To discount the TTL serial port as the source of your problem, remove the converter board from the TTL serial port and short the RX and TX pins with a piece of wire, jumper block etc. See the attached file to identify the RX and TX pins. Once you’ve done that, reload the serial port diagnostics and perform test one, the loopback test. If you get characters echoed back to the terminal, your problem is either the converter board or your cable. Remove the jumper and plug the converter board back in and short the two upper pins that connect to the red and white wires. Perform the loopback test again. Do you get the characters echoed? If not, your converter board is toast. If you do get echo, your PWM cable is bad.
Of course, the DB-9 serial was not connected from the camera to computer. I feel like whacking myself in the head; the problem was the pwm cable. We didn’t think to check it because it was brand new and unabused. We also found that I had misplaced the oscillate jumper to accidentally short user i/o 5v+ and ground when I was working on it this morning, which caused a lot of trouble as we tried to figure out how the camera didn’t have enough power. Finally we noticed that the servos were only powered when the camera was off, which gave away the problem. Thanks again for the help and the great code.
1014 Controls Team
We are having the same issue (failing in State 3) - something probably amiss with our camera to RC communication. The readme file for the diagnostic files says it’s only for the full sized controller. We are still messing with the EDU until we get our full system running. Any tweaks I can do to get the diagnositcs to work with the EDU?
Grab a copy of the edu_serial_ports.zip file from my website and modify the EDU Process_Data_From_Master_uP() function to look like the same function in the diagnostics package. I think that’s all you’ll need to do.
I got the diagnostics to run on the EDU, thanks. We pass the loop back test so we know the RS232 converter and cable are good. We don’t pass the second diagnostic test. Your notes say we either have our camera misconfigured or it’s a bad camera. The baud is set to 115200 (no jumpers). Are there other config items we need to check?
I even went into the EDU version of serial_ports.c and changed the SPBRG2 = BAUD_115200; and XSTA2bits.BRGH = 1; thinking that might be the anwer but it did not help.
You must be swamped! Thanks for your efforts Kevin!
Yes, it worked fine with LabView using the DB9. I have all the calibration numbers for tracking an orange traffic cone to get us started (our green light is not assembled yet!). I guess that would narrow it down to the camera’s 3 pin RS232 port? That does not seem very likely. I’ll keep playing…
You’re using a 2006 controller? If so, the code is getting corrupted somehow and you should contact IFI for help diagnosing the problem. If you’re using an earlier controller, you need to re-compile the code using the included instructions. Come back here if the above doesn’t help out.
Thanks, but I just ave one question. Where are the recompile instructions? I am using last year’s bot as a test platform. Are they in the work or another of the .pdf’s from FIRST? I did a scan through the workbook, but I may have missed it. Thanks alot, you guys are very helpful. Good luck with your bots this year.