Blogs

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • Distributor
    Martint BuildYourOwnDrone.co.uk January 23, 2011 at 1:14pm

    Hello Sandro,

     

    Would this help or this at all with Johann's camera?, It would appear that the information in the links points at the codes needed to make it work?

     

    Martin

  • Developer
    Sandro Benigno January 23, 2011 at 12:57pm

    Hello Johan, this cam isn't listed as compatible with actual Canon SDK. And it have "NO" CHDK firmware.

    PTP (on that cam and other newer Canon models) usually is about just printing from the camera or send the SD recorded pictures to your PC. Remote controlling by PTP is another PTP resource. I have two ways to go:

    1 - Oficial Canon SDK, that is already working.

    2 - By CHDK firmware with a PTP patch (still is a work in progress)

     

    SDK cams with PTP remote controll listed here: http://code.google.com/p/arducam-osd/wiki/PTP_compatibility

    CHDK cams with firmware ported here: http://mighty-hoernsche.de/

     

    Regards

  • Developer
    Sandro Benigno January 19, 2011 at 12:03pm

    Hey Daniel,

    I finished the schematic two weeks ago.  It will mix all in one: 328p at 16Mhz + Max7456 (OSD) and Max3421 (USB). The OSD library is 100% OK. I'm working on the APM integration and we have some finished OSD panels (battery, distance from home, number of satellites, GPS lock info, latitude, longitude and a animated compass. You will see a new post very soon. I'm working in a new PTP base too, which will work on newest Powershots (without PTP by factory).

     

    About EOS ones, Oleg have a nice library here. It should be easy to implement in a special edition of ArduCam OSD.

     

    Best regards!

  • Developer
    Sandro Benigno January 19, 2011 at 11:50am

    Hi Oleg,

    Great news! I just take a look at the code. For sure I will read all carefully soon.

    You have quite helpfully sketches there too. Many thanks for share it with us. ;)

    Best regards!

     

     

  • Daniel Gru January 19, 2011 at 11:40am

    Hey Sandro, how are you getting along.
    Very interested in this project, I think a big interest group for you could be people doing pole photography...

    Any sucess on getting the EOS-Productline to work together with your code? I have a XSi (450D) I'd love to use with it...


    Daniel

  • Oleg Mazurov January 19, 2011 at 11:32am

    Hi all,

    This is my PowerShot code for USB Host Shield:

     

    Announcement -> http://www.circuitsathome.com/mcu/controlling-canon-powershot-camer...

    Description -> http://www.circuitsathome.com/using-ptp-library-with-canon-powersho...

    Code -> https://github.com/felis/Arduino_Camera_Control

     

    Enjoy,

    Oleg.

  • Russkel December 5, 2010 at 2:58am
    Oh my, this is much nicer (albeit more expensive) than hacking open a camera and modifying the shutter switch/relay circuit (I am not too well versed on what is required).

    Very interested in the development of this.
  • Developer
    Sandro Benigno November 29, 2010 at 4:24am
    Note: Just correcting myself: UART isn't the right term. The correct is USART ports (Universal Synchronous/Asynchronous Receiver/Transmitter).
  • Developer
    Sandro Benigno November 29, 2010 at 4:17am
    @BillI - Very interesting the box. Recently, I bought a 3.5" display from a car parking monitor system. I'm designing a small one to attach on TX. :)

    Do you tried to test the MiniPro without change the VBus to 5V?

    Serial 2 isn't talking SPI to the shield's ADC chip". SPI don't uses UART line. SPI uses miso, mosi, sck, ss and sometimes other pins to do the chip selection of more slaves.

    I will use "telem port" from IMU board to communicate with the camera control when using just TX to control shot, focus and zoom.

    If you wanna use XBee on IMU telem-port and talk to CameraControl at same time, you can solder a male header at the side of IMU to expose the first UART port, like I did here:


    Let's talking about. I need to concentrate at the OSD part for now. This is why I bought the 3.5" display. I will use it instead a TV. Hehehe :)
  • Bill Noyce November 28, 2010 at 6:59pm
    I have managed to get the following communication all working

    hardware GCS <-> xbee ----------- xbee <-> APM <-> USB Host Arduino -> Canon G9

    Here are a few notes which other people might find useful and which might save others from making the silly mistakes which i did!

    The USB Host Mini shield must be run at 3.3v because the MAX3421e USB Host chip requires it. By default the USB port Vbus is hard wired to the arduino pro mini board and shield's Vcc, so by default Vbus is 3.3v which was too low to trigger my Canon G9 into realising it was connected via USB. So as documented over at http://www.circuitsathome.com/category/camera-control I cut the trace and fed Vbus with 5v

    I then blindly went ahead and wired the USB host into the APM Serial2 pins only to find that the pins are in use talking SPI to the shield's ADC chip! [note to self: read schematics...] So the only Serial port available once in the air is Serial0 which is wired into the FTDI chip. The only consideration here is that the USB host arduino does need to be disconnected from the Serial0 pins when uploading APM code.

    I have slowed down the baud rate to 9600 on the link between the APM and the USB Host Arduino. I was having problems at 115200 getting the Arduino Pro Mini to read a APM_BinComm message reliablely.

    The APM is simply pushing all serial bytes it receives on the xbee port ( Serial3 ) through to the camera host port ( Serial ) in due course it will only pass messages with IDs associated with camera control. Incoming BinComm data with MessageIDs setup for the Camera USB Host board are ignored by the APM and it is left upto the Camera USB Host to acknowledge these messages.

    The next plan is to move the comms across to the MAVLink protocol.
This reply was deleted.