@billybob Note, Voxl J12 is a 5V bus. FCv1 J1 is also a 5V bus. However, FCv2 J1 port is a 3.3V bus to be in-line with Dronecode, but it is 5V Tolerant due to buffers on J1. All other FCv2 ports are NOT 5V compliant since they are direct to the MCU which has an ABS max of 4.0V on all signal pins. There are a few noted exceptions as shown in the diagram above. Most of the Recieve UART pins are 5V tolerant, but the receive buffers on the other side loose a lot of noise margin. It gets complicated really fast parsing through the MCU datasheet and running PX4 on-top. Always reach out if you need more info.
Latest posts made by billybob
-
RE: Fumble fingers problem on FC
-
RE: Fumble fingers problem on FC
@Bulldog357
That's great, I keep reading about your 5v-3.3v level shift solution. I decided to go the route of updating to ver2 control board thinking it would be better because it's newer and because I have a desire to complicate things when I can. I have a question on your level-shift and the 5v supply. The tech info says the ver2 is 5v tollerant but there could be lost data. Is your solution easy as far as building and implementing, maybe alivating this data loss issue. My ver1 board is working fine with a MRO Sik reciecver so still useable but I wouldn't use a damaged board for a flying machine and I am also documenting my voxl drone build so it needs to be as straight forward as possible. This Voxl-Cam has been a serous learing brain drain. I wanted to understand the inside metrics of the drone build and have gotten more than I could have hoped for. At least now I have converted several of my Win computers to Linux -
RE: Fumble fingers problem on FC
@Bulldog357
I just had the same thing. I don't think your to blame. My receiver just fell off and took the pads with it. No way to put down new pads although I tried. I have been working trying to get this voxl-cam transmitting for a week to find the connector flopping against the fiber board. I would believe the connection and connector were the wrong choice and placement also. My thoughts was to connect a telemetry modem for the mavlink data and try to configure the 4gmodem for the voxl. Will be looking to see if you get a solution, I just purchased the v2 flight core because I am not expert enough and need to work on learning and not fixing