OK, I been looking around online posts for days and havent found anything so I will start this new thread.
I have a generic APM 2.6 /w the 3.2.1 firmware and the bluetooth module. Actually all the hardware is straight from the 3DR store. The tablet is a galaxy tab s nearly straight out of the box. I followed the direction in mission planner re: unchecking the box "disconnect on usb whatever" and paired the BT to the tablet(flawless)
I install and open androidplanner 3 and hit the connect button. The program says connected. I can arm, disarm from the program and it reads the battery voltage correctly. It even flashes failsafe when I plug a 3S battery so it is reading something from the APM. It also shows the MAVlink version in settings (3.0) but does not show firmware of the APM
BUT... it doesn't read any telemetry info, (heading, orientation) has no GPS fix, will not read parameters and wont load or read waypoints. It also shows the MAVlink version in settings (3.0) but does not show firmware of the APM
if I plug the tablet directly into the APM with a USB cable I have no problems.
I'm aware that I could probably just go to the radio telemetry gear, but I was hoping to save the weight space for the FPV system.
Any thoughts would be much appreciated.
Replies
Ended up fixing this one myself. Turns out the APM adapter sent with the BT module was pinned incorrectly (VCC,Tx,open,Rx,GND), which is why it would arm but not actually receive anything from the GS. After moving the Rx pin to the correct location everything works perfectly.
Sorry to hear that! So we can investigate, can you please send a picture of the corrected connector and which wires you needed to switch?
No worries. I actually think this sort of thing happens quite a bit and is mostly the reason for a lot of "isn't working" posts. I recently found a well known camera gimal that didn't work properly because one leg of one motor header hadn't been soldered.
I found the current problem when I started to build a device to passively record the stream for debugging, looked at the eagle file and noticed pin 3 wasn't supposed to be open. anyway I digress, here is the picture.
apm-bt-adpt.pdf