Hi,
I keep having issues with the telemetry when I try to connect it to my my pixhawk.
I managed to establish a connection between the air module and the ground module when i connect both of them to my laptop(I connected the air module to the laptop using a ftdi adapter), and using mission planner i was able to link it and get solid green light in both. But when i connect the air module to the pixhawk it just shows a faint red light while the ground module keep flashing green which i believe means its searching for transmitter signal. I dont understand what seems to be the issue here. I even tried changing the baudrate and it didnt solve the issue. What could be the problem?
What Pixhawk exactly?
What telemetry module?
How did you connect them?
Are you really on Copter 4.3? if yes, then update to Copter 4.5.2 or 4.5.3-beta.
“faint red” sounds like a power issue.
Overall that sounds to me like a case of RTFM…
2 Likes
A Universally recognized troubleshooting technique 
1 Like
Sorry I’m actually on copter 4.5.3
I’m using pixhawk 2.4.8
Initially the two modules wouldn’t connect to each other. Both modules would always be blinking green. I used a FTDI USB to UART converter to connect the air module to my computer after which I uploaded firmware to the air module as well and then both the air and ground module was solid green(this is when connected to the computer). But after I did this and I connected the air module to the pixhawk it just started blinking a faint red. I don’t know what this means and I can’t find any solution to it online. I don’t know if it’s something I did wrong .
Also before all this when connecting the air module to the pixhawk it used to be blinking green it was only after I did this that this change occured
I’m going to agree with @Janno , faint red is a power issues. Use a multi-meter to check that you are supplying the air radio with 5v. You may need to have the flight controller connected to a battery as some ports aren’t powered off USB alone.
I thought that too but it doesn’t work with a battery either… Could it be some fault with my pixhawk?
Without knowing more about your system it is really hard to tell.
So again, which telemetry module exactly are you using?
Where on the pixhawk did you connect it to?
Did you just try it with a battery or did you also measure the supply voltage like Allister suggested? If yes, what was the result? If no, then do it.
Sure, everything is possible. Or more precise: nothing is certain. However experience has shown that user error is more likely to be the problem than faulty hardware and without proper testing I’d be hesitant to write the FC off.
1 Like
As I said before, use a multi-meter to see if the radio is getting 5v. Check the pins on the FC and if that’s good, check the cable. Start with the cheap stuff, often these are just wiring issues.
1 Like
Can you please elaborate it in more details please? Do you mean disassemble pixhawk and check the circuit on this port under the power?
I have checked it by checking voltage on power and grounds wires of JST-GH cable from telem2 port (red probe on 1st pin, black probe on 6th pin) and it is near the zero.
I have similar issue discussed here.:
Well then it’s damaged if you don’t see 5V.
Ok! But Cube Orange itself is working, at least it and part of the curcuit related to it is doing well.
I searched the web for a last half hour and found two or three simialr cases. Based on your experience is it likely a possible flaw in design\implementation of the curcuit or just not correct setup on my side?
This is almost certainly the root cause. There’s no need to search for a flaw in the design. There is also no need to post the same issue across multiple topics.