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.

Arthur P.

Trusted Member
  • Content Count

  • Joined

  • Last visited

Everything posted by Arthur P.

  1. Not my project but might be of interest to the Graupner MX12 / JR .... 6 channel radio users: adding two channels to this TX using an ATtiny processor and some code: http://forum.mikrokopter.de/topic-4405.html
  2. Hi Vic, Sorry about that. Haven't looked in that forum for a long time. I thought they did have a bit of an international section. There is currently a new UAVP parameters thread in www.RCGroups.com under Aerial Photography. If you post your question there, I expect you will get confirmation quickly.
  3. You could also do a search for DX6 and AR6000 in the forum on http://www.uavp.de/ . It is one of the frustrating forums where you have to register before being allowed in. But it does supply a lot of info on the UAVP system, and will get you a lot of support if you post quesions there. I don't believe they're too strict on the use of German.
  4. Hi Victor, I didn't check completely, but I think you're pointing to the same set as the US shop is offering. I expect you'll have it quicker and with less hassle with e.g. customs when you order there. And it will get you English language support from them.
  5. -AT-Victor, Assuming your located in the USA: http://www.quadroufo.com/ Look under Flight Controler for the populated board. I would suggest that you check with them whether you an use the AR6x00 and/or AR7x00. I believe the UAVP had problems with the latter due to the unusual sequence of the channels. Also check whether the ESCs you want to use will work if you want to use PWM control. You can of course use Holgers, YGExxi-s, or converted TowerPro 18A, 25A, or 30A ESCs over I2C/TWI. Note that there are two threads here on UAVP and/or Mikrokopter under Floobydust. E.g. http://www.rc-cam.com
  6. And a closeup.. Of note, I would really urge anybody who has TowerPro type 2 like ESCs (with the BEC on a little satelite PCB, as used in the type 2 and 3) to check the FETs. If they are those used in the type 2, as I call it, either replace the FETs or the ESCs as soon as possible. In any case ensure you use type 2's at loads of 10A or more, ensure forced cooling, and avoid accidental blocking of the prop. BECs 7805's stacked up on main pcb = type 1, no overheating problems. BEC on breakout board and hot TC8114/TC8111 FETs = type 2, can seriously overheat. BEC on breakout board but diff
  7. That toy is the standard X-UFO with a mechanical gyro. Not very stable for more than a minute or so. It has taken quite some time, but I have two of my four APMk's (Aerial Photography Multi-kopters; but also derived from my initials ) flying since last week. First outdoor testflights ocurred with winds gusting to 45kmh, no problem. APMk nr 1 has Turnigy 2213/20 motors and EPP1045 props, RTF weight about 1350g, will fly a bit over 6 minutes on a 2150mAh 11.1V lipo. APMk nr 2 has Turnigy 2217/20 motors and currently still EPP1045 props, RTF weight about 1550g, will fly a bit over 11 minut
  8. For some reason they don't want to guarantee shipping outside of the US and Canada. So here I am with my high Euro/low Dollar and I can't even buy US stuff (even accepting excessive customs taxes in the bargain)..... Guess I-ll have to wait until united have them back in stock ;=))
  9. -AT-Labmaster, That replacement receiver is really impressive !! Certainly deserves a separate thread ! Btw, where do you order your satelite receivers from?
  10. Very ingenous and very impressive Richard and Mr Cam-Man !! Actually, I believe the 2 second delay is in part due to the FC settings. At least in v0.68d the default delay in the MKTool is 20x 0.1 seconds I converted 8 new TowerPro 25A/2's on Sunday afternoon, am back to just quickly soldering the programming wires to the right legs and then removing them. Those are actually so easy, that it takes about as long as the multiple attempts needed to position the clay programming adapter. Overall time for conversions is down to about 45 minutes per ESC from starting to put on the battery connne
  11. Actually I have the FC ready and the parts all lined up for APMk nr 4. Got stuck with an additional one on a group order. I-m going to use that one as "experimental", i.e. for testing different frame improvements, new firmware, etc. Motors for that one initially will be Turnigy 2830 - 1050kV, so it will be a "lightweight", but may get 4 more and go for an octocopter on that testbed ;=)) The ESC on motor 1 of the heavy APMk nr 3 has me stumped. All connections are intact. The motor arms correctly with the nice Quax tones. But it isn't responding to I2C/TWI throttle commands at all. I-m consi
  12. Well today was "the" big day, the first outdoor testflights. Conditions were "near perfect": 8 degrees Centigrade, heavy overcast, and winds gusting to 45km/h (about 30 mph) But in view of the good stability the machines had shown during some indoor handheld testing, I decided to just go ahead. Of course all did not go completely as planned. APMk (Aerial Photography Multikopter, but also a jab at my initials APM) nr 1 had a wrong and incompletely charged battery, so only several short hops, but still it managed the wind quite well, immediately hanging into it as soon as it got light on its f
  13. Little update from my side: as those following the thread in 'RCGroups.com / Aerial Photography / Multikopter build thread' know, I-ve had a few setbacks along the way which resulted eventually in having 4 flightready Mikrokopter flightcontrollers, multiple sets of converted TowerPro ESCs, and Richard's v.2 of the PWM2PPM converter to be able to interface the Spektrum AR7000 to the flightcontroler. I still have to finalize wiring up the PWM2PPM converters today, but I should have 3 APMk's (Aerial Photography MultiKopters, or in a pun at my initials Arthur P M's kopters) ready for test-flights
  14. Sorry about that Richard. It was indeed late, and it indeed concerns your v.2. PCB. I-ve corrected it in my post above (but can't correct the quotes which still call you Jim).
  15. -AT-Mr Cam-Man, Very nice little PCB. And interesting solution to the failsafe issue. I-ve been thinking about the latter as well. I think I would rather see that solved in the FC firmware as almost all MK's have an airpressure sensor, all have gyro's and accelerometers, and then some have compass and GPS. The changes needed to the firmware, from a logical perspective, would probably have to do the following: on first throttle up over x% get airpressure value as zero altitude value (could be a handstart, but we can correct for that) and set flightflag if no ppm signal (receiver without fai
  16. There are actually one or two people who have done that. The satelite receivers are industry standard and have all the firmware to control their connection. They output a simple serial data stream. That can be read with a microprocessor. At least one person has used two such satelite receivers to create his own "Spektrum" receiver but output a single PPM stream. See: http://www.rc-cam.com/forum/index.php?show...0&start=140 The Mikrokoper FC is actually very flexible in channel sequence. It essentilly just accepts the channels in whatever sequence they come in. The user then defines whi
  17. Well after some experimenting I managed to create a programming adapter for less than 1 USD in material costs Material used: plastic clay (that coloured stuff that children clay with) which gets hard when baked for 30 min at 125C in the kitchen oven, and a few strands of wire-wrap wire. Only tools needed: very thin drill-bit (a fraction thicker than the wire-wrap wire with insulation), a sharp knife, the kitchen oven, and finally the trusted soldering iron to connect the adapter to thicker wires and your favourite programming plug. I-ve posted more details and pics here: http://www.rcg
  18. Hi Walter, So you were the first ! And one good and one excellent solution. Would be really great if you could provide more details on your current solution for the DX7, e.g. diagram and firmware / source code. In principle with your solution I could image that you could even modify the DX7 so that you can put multiple switches onto one channel and then use additional outputs on your "receiver" to split them out again. That would e.g. allow activation of different flight mode, airpressure sensor, compass, different GPS modes, return to home, over a single channel with several switching r
  19. You're right. Reread the section. The Spektrum manual is far from clear on a number of things. The use two terms: "smartsafe" and "failsafe" and if I understand the text correctly now the "smartsafe" refers to the startup "stick position" programmed, while failsafe indeed retains last control surface positions and the failsafe throttle setting. I'd hardly dare call this "smart"-safe.
  20. From the Spektrum DX7 manual: Note: Fail-safe positions are stored via the stick and switch positions on the transmitter during binding. According to this it stores all stick and switch positions, but most people leave the roll, nick, and yaw positions neutral so it would seem only the throttle is stored.
  21. I believe the normal FC setup is to go to slow descent with neutral roll, tilt and yaw on loss of signal. I.e. the FC software has a failsafe build in. If you have GPS integrated, you might be able to go one step further and program in a return to origin (hoping that there are no high trees or buildings in between ;=)) but I-m not sure how far that development is. I wonder whether you couldn't simply modify one or two lines of source code in the FC programming. You need it to identify either no signal (current program) or a particular preset of controls which should not normally occur durin
  22. Isn't this an adapter for not yet mounted ATMega8's? What I-m proposing is an adapter that can be used for chips which are already soldered in place, e.g. for reprogramming ESCs.
  23. -AT-Brashley, Just had another look at your PCBs. Any chance of you etching and selling me a couple (4-6) of those PCBs ? And any test-results of actually flying with this design? Regarding hooking it up to the Rx, I used single strands only connecting to the Rx signal pins, instead of the full three pin connectors. I-ve been thinking about epoxying the row to a thin strip of plywood to create a single long PWM connector which would ensure a fixed (correct) sequence with the 7th channel connector on the right pin. Might not save a lot of weight but does reduce the bulk of wires between Rx a
  24. You would activate it my mixing two channels for e.g. flaperon control. That could move the two channels next to each other.
  • Create New...