Jump to content

Mr.RC-Cam

Admin
  • Content count

    5,340
  • Joined

  • Last visited

Community Reputation

121 Excellent

2 Followers

About Mr.RC-Cam

  • Rank
    RC-Cam Mentor

Contact Methods

  • Website URL
    http://www.rc-cam.com
  • ICQ
    0

Profile Information

  • Location
    USA
  • Interests
    R/C, FPV, Embedded Programming, Electronic Design.

Recent Profile Visitors

6,757 profile views
  1. Analog HD FPV Video. Why Not?

    I came across a discussion on the Caddx Turbo Micro F1 camera that talks about its menu selected HD mode. Most likely AHD 720P given its low price. Caddx claims it has removed this feature because setting it to HD mode effectively bricks it (because you'll need a compatible HD system to restore NTSC/PAL mode). Too bad, it would have been a good candidate for AHD video on a small FPV model. Here's the discussion: https://www.rcgroups.com/forums/showpost.php?p=39074392&postcount=1 Please note the warning: Please NOT change the setting "TRANSFER MODE" on OSD menu or you will get into HD mode which FPV monitors cannot display. Only the first batches have this setting on the OSD menu. If you already did that, please PM Caddx
  2. The History of FPV.

    I came across an online article that summarizes the history of the FPV hobby. The story includes some details about multicopter (drone) development too. Online article: http://www.currykitten.co.uk/the-history-of-fpv/ Original PDF version: http://www.currykitten.co.uk/wp-content/uploads/2017/10/HistoryOfFPV_RCFCA11.pdf
  3. Analog HD FPV Video. Why Not?

    Thanks for reporting the details on the C800T. Learning about what works for us is exactly how the FPV hobby got to where it is today. So contributions of information, like this tidbit on the C800T, is appreciated. The possibility of a firmware change after your Nov 2017 purchase is what's at stake here. But my experience is that the Chinese vendors rarely fix their design problems. So I might purchase a C800T and check it out. But I'd rather have others join in on testing/development and help push this technology.
  4. Analog HD FPV Video. Why Not?

    I searched for any details to a C800T firmware update; I can't find any discussion about it. But plenty of users have shared their experience with this camera. The reviews on the C800T are mixed. Two notable things are that it isn't CCD as advertised (it has a CMOS sensor) and is very heavy due to the metal case. But despite those things, the version that supported AHD1.0 may have been a better choice than the AHD security camera that I used in last year's tests.
  5. Analog HD FPV Video. Why Not?

    If the currently sold C800T still has AHD mode then I'll order one to try out with the redesigned 5.8GHz Airwave modules. But before I waste my time, can anyone confirm that they didn't remove the AHD function?
  6. Analog HD FPV Video. Why Not?

    Status Update: Despite receiving some privately messaged teasers a few months ago, a commercialized AHD 720p FPV product seems to be going nowhere. Such a shame since this technology offers a lot of promise for micro FPV. New News: I mentioned last year that my Airwave AHD module evaluation revealed it had serious performance problems. I recently found out that Airwave has redesigned their AHD modules and made some improvements. I expect to re-evaluate the new modules when they become available. Not sure if I will post about my new findings, but I would like to know for myself how it performs. Parting Words: I'm too stubborn to totally give up on AHD; As mentioned before, I strongly believe that it's a nice stop gap solution until zero-latency digital HD FPV is dirt-cheap and fits on a micro sized drone. Most likely that's several years away, so for now I think AHD 720p has its place in FPV. But I'm short on resources and have done all I can to promote AHD - - it's time for the brilliant engineers at a far east FPV manufacturer to get on board and make it happen.
  7. Analog HD FPV Video. Why Not?

    That banggood video system is MIMO/OFDM technology. It will be several years before the airborne vTx will be low cost & small enough for a micro-sized race drone. For now I think that AHD 720p is a more promising choice since the vTx would be very tiny (and very low cost) using available technology. For example, micro race drones would need something small/lightweight like this, which is possible with AHD technology:
  8. Analog HD FPV Video. Why Not?

    If you mean you want to use it for FPV then I'd suggest you keep looking. Everything about that system reinforces why our hobby needs a low cost AHD based FPV system.
  9. You are welcome! Thanks for reporting it is working well for you.
  10. Thank you for the kind words. Your technical assistance was extremely helpful in identifying the LCD Keyboard problem, so it was a joint effort.
  11. I suppose that is the best we can do for now. Given the random nature of the Chinese boards I expect the LCD-Keyboard shield compatibility issue will pop up again. To be proactive about this I have released a new version of the firmware (V2.3). It is posted here: https://www.rc-cam.com/forum/index.php?/topic/4139-diy-rf-power-vswr-meter-low-cost/&do=findComment&comment=29002 There's now a keyboard debug function. It will display the key-press code value when each menu button is pressed. The feature is enabled via the config.h file using DEBUG_KYBD found under the Troubleshooting section. What does it do? For those that need help solving keyboard compatibility problems: Enable DEBUG_KYBD in config.h, re-flash the firmware and then report the five keypress code values shown on the LCD. When posting for help be sure to include the two A0 voltage values mentioned earlier. Also, the config.h file now supports an alternate LCD/Keyboard shield. Currently there's two choices, my DFRobot branded board (LCD_SHIELD_DFR) and the clone used by HF_ATL (LCD_SHIELD_ALT1). The shield choice is made by enabling LCD_SHIELD_DFR or LCD_SHIELD_ALT1 found under the LCD/Keyboard Shield Type section.
  12. You are welcome. Thanks for letting me know the keypad is working now. I should add a note to the docs about the changes for your LCD/Keypad shield. Is there a Chinese manufacturer's name or unique ID printed on your DFRobot clone shield so it can be identified by other project builders? That's a sane/reasonable value with nothing connected to the SMA. It should be fine for VSWR only measurements. But a calibration will be required for accurate RF power measurements .
  13. The 2K ohm (1.99K) resistor is a good A0 choice for your LCD shield. Now the various key press codes will need to be re-mapped. In the RF_Power_Meter.ino file, go to the ReadLCD_Buttons function (starts at line 435). Replace the adc_key_in code section (from lines 486 to 506) with this revised snippet: if (adc_key_in > 1000) { kybd = btnNONE; } else if (adc_key_in < 50) { kybd = btnRIGHT; } else if (adc_key_in < 265) { kybd = btnUP; } else if (adc_key_in < 525) { kybd = btnDOWN; } else if (adc_key_in < 690) { kybd = btnLEFT; } else if (adc_key_in < 865) { kybd = btnSELECT; } else { kybd = btnNONE; } Upload code then check all the button functions. Hopefully you are rewarded with button press happiness. EDIT: Beginning with firmware V2.3 this alternate key press code can be selected in the config.h file. Choose LCD_SHIELD_ALT1 to enable it.
  14. The voltages and key press values are now a bit too low. Increase the resistor value a small amount (try ~1.8K). Ideally the A0 voltage with no button pressed will be 2.45V - 2.50V with a "None" key press value between 1015 and 1023. With the Select button pressed you should see about 2.0V. Get as close to these voltages as practical then report all the key press debug values. Important: Never power the meter without the A0 resistor installed.
  15. Almost there. Try a 1.5K and report the debug values. With the 1.5K installed, please measure the A0 voltage when no buttons are pressed and also when the select button is pressed.
×