Jump to content

Attention: RC-CAM.com will be closing down August 2021.

The RC-Cam.com forum was the very first online community dedicated to the advancement of wireless video cameras on radio controlled (R/C) models. This is now called "FPV" (First Person View). We are proud of the contributions that our members have made to the FPV hobby.

We've seen significant changes over the last twenty years. Initially there were a lot of eager R/C hobbyist that built their own video systems. Allowing these creative individuals to share their work was the purpose of this site. Now the FPV market is flooded with low cost systems; Sadly DiY FPV video projects are now rarely discussed.

RC-CAM.com (main site and forum) will be closing down August 2021. This is being announced now (March 2021) so that everyone has time to download any information that is important to them. After the site is shutdown the information will no longer be available here.

We appreciate every member's involvement with advancing the FPV hobby. It is indeed sad to say goodbye to all our online friends. Be safe and stay healthy.


Trusted Member
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bluegill

  • Rank

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Location
  1. I was wondering when somebody would do this. Why did you find it desireable to sense two of the leads, instead of only one? --bluegill
  2. I get no video, like when the transmitter is off. At home, where I can have the transmitter and receiver only 15 feet apart, I get a snowy picture. At much greater distances the receiver's squelch operates and I don't get anything. When I bought the video system I mounted the camera and tx on a rc car and my 9 year-old friend and I had a blast driving it in and around the house, so I am familiar with the deadspots in the house due to large metal objects like stoves, refrigerators, and furnaces. I now get not much of anything at all, not like I had up until a couple of weeks ago. There ha
  3. Hi Kilrah, thank you for posting the frequencies -- it'a a big help! I recently have run into a problem where I lose video after about 5 minutes, and I haven't been able to figure out if it is the transmitter, the receiver, or what. Having only one of each makes it hard to troubleshoot! So I am planning on buying another tx/rx pair from BW, because that is what I already have, and your frequency list shows there are no alternatives if I want to be able to mix and match. The frustrating thing is that this problem has cropped up but I haven't made any changes to the system. I did take the
  4. You just think it's a joke! I'm already looking at the connector for the external switch and LED with the idea of watching those flashes in my telemetry stream. Just think of the heartthrob it would make if it were connected to the roll indicator of the MAHI... --bluegill
  5. Being the cheapskate that I am, does anyone discount the price of the FMAdirect FS5 receiver? --bluegill
  6. Sometimes I think I'm slow, real slow. I was going to whine yet again that this technology is wonderful, but there is no immediate feedback to the pilot. After reading FMAdirect's manual for how to use this receiver with a copilot I finally understood -- just set the failsafe of a high channel that you don't use for flying the plane to indicate a problem! Duhhh! So in my case I could set the receiver's failsafe for channel 5 go to +100, while for normal flying it would be 0. Connect that channel to the MAHI pitch indicator and I can immediately see when the receiver goes into failsafe mo
  7. Yes, I noticed that. I also noticed that he claimed he was averaging the current pulse (if it seemed OK) with the previous good one, but what he is actually doing is exponentially filtering each pulse. Nothing inherently wrong with that as long as everyone understands what is going on. Still, it looks like a solid design to start from, and will allow me to get my toes wet in PIC assembler with a useful starting point. I've done a lot of assembler code in years past, but this will be the first time for the PIC, which looks like a *very* different beast than what I'm familiar with. --bl
  8. Actually, the mating connector can be simpler than that, because the card needs to get the power and ground pins only once, not for each servo connection on the receiver. So one needs only 7 connections for a 5-channel receiver (power, ground, and the 5 channels). A story in frustration, though -- I designed such a board to make it easier for me to move my Hitec 555 receivers among several planes. It worked fine -- BUT One of my 555 receivers suddenly decided it was intermittantly dead. I looked at having Hitec repair it, but that was nearly the same cost as getting a Hitec Electron
  9. Oh yes, I quite agree! That is why I am especially appreciative of the link you gave to Bruce Abbot's project at http://homepages.paradise.net.nz/bhabbott/decoder.html His 6-channel design looks like a good starting point. --bluegill
  10. I didn't mean to imply that the RCFS-V2 is ineffective. In fact, based on your other designs as well as comments about how it works, I would be very surprised if it was not effective. My line of thought isn't about the effectiveness of its glitch-busting, but about informing the pilot that he is getting into dangerous territory and needs to get out. I can tell from your comments about RSSI that your environment is quite different and much quieter than mine. I can easily show areas where RSSI of my receiver shows a strong signal, and that's without my transmitter being turned on! We have a m
  11. Yes, I had seen that thread but I thought you had decided not to add it to your list of current projects -- in other words, the preprogrammed PIC chips are no longer available. I certainly do agree with you that I had not seen Bruce Abbot's thread, and appreciate the link you provided. --bluegill
  12. Mr.RC-Cam, you know I like your work and products, but... I think that the whole receiver glitch issue needs to be looked at from a systems point of view, not from the servo's point of view. The RC Servo Failsafe with Glitch Filtering is a great little device, but it doesn't share its conclusions with anyone or anything beyond the servo it is connected to. The only indication one gets (while flying) that reception is spotty is that the plane no longer responds to the controls. I often am not doing anything at the controls for many seconds, so the fact that I am flying into an area with i
  13. I hope my experience and solution will help someone else who encounters RFI/EMI problems. --bluegill
  14. yb2normal, my understanding is that the error is slowly varying with distance and time, so the plane won't be dancing up and down. However, I wanted people's real-world experiences with WAAS, not the FAA's glowing poopsheet, which is the reason I posted the question in the first place. I guess I'll have to just try it and find out! BTW, I've been considering using a pressure sensor anyway in order to determine airspeed, so I can account for wind. I would really like to know BEFORE I get into trouble that I'm flying downwind in a gale and won't have enough energy left to get back home if
  • Create New...