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.


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About waxpanic1

  • Rank
    RC-Cam Visitor

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Location
    Silicon Valley, CA
  1. The next project I want to take on is connecting a PIC to the transmitter switch for one of the extra channels (Such as channel 5). The goal is to add extra buttons to the transmitter. A button press will be encoded by a PIC as a series of transmitter switch flips. A PIC on the receiver side will decode the transmitter switching. One PIC on the receiver side will be dedicated to converting the receiver pulses to pin outputs. A second PIC will carryout the commands (take picture, gear down, lights on, transmit data for example). Has anyone else tried to build a similar system? Any tho
  2. Eureka!!!! Powering the receiver off of the prototyping power supply got it up an running! The scale is a little off (low pulse = 105, neutral pulse = 143, high pulse = 180). Since the pulse error is greater on the High side, I'm guessing that this has to do with how the PIC measures the pulse. Now I need to explore this phenomenon. Great thinking on the common grounding! Now for some more information. Why does the PIC need to share a common ground / power supply with the receiver? Hey Matt...That was probably the same thunderstorm that woke me up (in California) two nights ago.
  3. You are correct on all of your assumptions except with the PCB prototyping board. I am using a DHMicrosystems protyping board. It is very similar to the MELabs prototyping boards (I have one of those as well). I've used the board before to conduct other experiments (flashing LED, A/D conversion of a Temp sensor, and the sending of serial data to my laptop computer (of course). A photo of the board is attached to my reply. the schematics for the board can be found here: http://www.dhmicro.com/PDFs/Rapid18iXL_Man.pdf The crystal is an external 4Mhz crystal (with internal capacitors).
  4. I tried connecting a servor to the receiver prior to beginning the project just to see which channel on the TX went with the RX channel. Everything seemed to work like normal. I'm guessing that the problem is with my PIC code. Quickly looking on the RC groups discussion board reveals a number of people who have successfully created this circuit. All of the examples I could find, however, were written in assembly code (something I'm not familiar with). Cheers
  5. Well, It looks like I'm at a stand still at this point. I tried to measure the duration based upon a 0 state (Low pin pulse) and I tried to connect a 5V pull up by connecting a 10K resistor to the pin and a 5V source. The result of the pull up is readings of 0 (the pull up overwhelmed the receiver signal). I don't have an oscilloscope to assess the high state voltage or the receiver output signal pattern. can timing functions be performed on every PIC port that is an I/O port or does it need to be a special port?
  6. Whoops, I hit a button and I don't know what happened. I may end up posting a response twice. I tried to add an additional Pulsin command prior to performing the serial output (in fact, I added 4 more pulsin commands for extra assurance). The Serial output remained the same...there was just more readings. The highest values were averaged around 84 (82,83,84,85,87) and the lowest readings were centered around 3 (2,3,4). Changing the transmitter input has no effect upon the measured pulse width. I even added a line to make sure all of the port B pins were output except the pulsin pin (u
  7. I am trying to use the pulsin command but, there is a lot of variability in the readings. Here is a list of the last 11 readings: Pulse Duration = 2 Pulse Duration = 3 Pulse Duration = 3 Pulse Duration = 2 Pulse Duration = 88 Pulse Duration = 88 Pulse Duration = 86 Pulse Duration = 2 Pulse Duration = 81 Pulse Duration = 82 Pulse Duration = 84 I am running the code on a PIC16F88 microchip. The RC receiver is a GWS PICO reciever. The PIC is reading off of channel 1 (Therefore, the receiver pulse should be about 1.5 msec when the transmitter stick is at the neutral "center" p
  8. Hi Gang, I am in the process of building a new PIC microchip application. I want to use the extra channels on my RC transmitter to trigger the PIC response. Therefore, the PIC will be looking at the RC receiver to determine if there has been a change in the transmitter switch (a pulse duration change from 1 msec to 2 msec). The PIC input from the receiver is similar to the input for the Aiptek CAM-Man project and the RCFS project. The timing diagram for the RCFS project is very helpful for my design (providing me with the background informaiton I need to understand the RC receiv
  • Create New...