Making a phototransistor cable for Canon S110
I want to make a phototransistor cable for my S110 to attach infront of its red eye LED light and connecting it to pixhawk in order to imporve the geotagging process. But I am fairly new with electronic, wiring and soldering stuff.Thus I need help and guidance on how to properly make one. I want to know is this the right connection for me to make the cable.Any help is really appreciated. Thank you.
Read more…
Comments
@Martin,
What good is being able to purchase a new Pixhawk1 going to do you, unless you are replacing an existing PH1, as you cannot purchase the DF13 connector cables for a new installation anymore?
Also, if 3DR chooses to sell an improved PH1 that has a different connector configuration than you are presently using, what are you going to do?
I am in the same boat as you, however I stockpiled quite a few 4 and 6 pin Hirose connector cables to act as replacements for damaged cables, but not for new builds. I believe that the new style connectors (Molex?) found on the PH2 are the wave of the future.
I believe that the white connectors you have mentioned are JST connectors and as you have found, do not fit the 3DR PH1 Hirose mating connectors.
Regards,
TCIII AVD
Thanks, Chris, for setting that straight (regarding the Pixhawk) NOT being discontinued. I have been a loyal 3DR customer (as my order history would reflect this). My concern.....and what started this thread.....is the availability, or lack of, 3DR OEM cables (with light brown connectors) for the Pixhawk, as the non OEM (clone) versions, at least all the ones I've tried ordering, identified by the white connectors, are not "correct". The locking tabs are not in the correct location and the pin (female) "receivers" are the wrong shape. Yes, they can be "forced" on, but that's not a good connection. So if I understand correctly....3DR Pixhawk available but not the cables (for peripherals)?? I can't find them in the 3DR "store".
For those of you who feel that the new, improved Pixhawk, that Chris Anderson promoted in his response to Martin Lachance's Group Message, will not meet your demanding flight controller requirements, you might want to become a member of the Pixhawk 2 User Group.
Regards,
TCIII AVD
This was purchased from an authorized 3DR dealer in Singapore. If it is busted, I hope we can get a r placement as this is the first install. Whereas mine has been in several craft, a tricopter,and two planes.
Has anyone come across the same problem? Is this the dreaded " bad accel error" I have read about?
Thanks Rodney Johnson for your suggestion. It worked. Going to Tokoroa Friday for the Maiden flight.
Hi guys and gals, Im having issues with my pixhawk for some reason it is not recording data flash logs i did a mapping mission but when i plug it in via USB and try to download there is nothing there.
I tries setting LOG_BITMASK to the default pixhawk settings and i also tried just camera in log_bitmask and still nothing does anyone know a solution? THANK YOU !
The Pixhawk in the Sky Hunter surely is a weird beast. Initially I couldn't complete an ACCEL calibration as it would freeze up after each step of laying it on its side, front, back etc. At the time I was getting constant pre arm warnings of AHRS, Inconsistent compass etc etc. I installed copter and calibrated everything and had noticeable fewer issues. Re installed plane and found that I could now calibrate ACCEL although still getting a lot of AHRS warnings. Been raining here for the last couple of days so have been unable to place it outside to obtain a good gps lock. I will let you know how I get on when I do.
I recommend you start over! Install plane so it clears out copter, and then reinstall copter, and complete all the mandatory hardware installs.
Rodney
Thanks for replying. I will do as you suggest and get back to you.
Try loading a copter program onto pixhawks. Do a mock setup and take the pixhawk outside during calibration.
If everything works without error then you know that is not the pixhawk or its hardware it's a issue with Arduplane V3.5.0 code.
Or load with an older version of Arduplane and see if you get the same issue.