I've come across an issue lately where my minimosd stopped working after a firmware upgrade, and i'm beginning to think that the root cause of the issue is that my telemetry rx and tx pins on the oilpan are broken. There's no voltage if I measure between either the rx and tx pins and ground (on the telemetry header), but I do get 4.5v on the 5v pin. I think that maybe the connection between the pin socket and the trace on the board has become unstuck or broken somehow.
What I want to know is, is there another point on the board that I can solder a couple of pins to, to access the telemetry rx and tx pins?
YESSS! Found the eagle files for the oilpan and connected my tx and rx pins to the pins above and beside the telemetry port and my minimOSD is back in business. Phew.
hi there, i have a broken LED on my APM2. can someone guide what are the specs of the red boot LED on purple APM2 board. looks only the LED has damaged because of an screwdriver and rest all is fine.i have the eagle files but on which software do they open.
I found a pdf version of the eagle files which showed me what I needed. Maybe see if you can find the pdf of them for APM2.
Are you sure that it isn't just the upgrade to using MAVlink 1.0? ArduCopter 2.6 and ArduPlane 2.4 now use MAVLink 1.0 rather than 0.9, and MinimOSD needs to be updated to match or it will sit and wait for telemetry data forever because it does not recognize the new format.
Yes definitely sure. That was the first thing I tried (over and over). I got the minimOSD to work by connecting to the neighbouring pins on the oilpan, but now I am getting weird yaw behaviour with the oilpan.. arggh
Hi Mike, I figure it's probably best to keep this discussion in here rather than the 2.6 thread.
I am thinking that there is a short or something inside the oilpan's PCB near the telemetry port. What originally happened was that one of the telemetry port pads must have become separated from the trace when I unplugged the cable that connected to the minimOSD. I tried to add solder to this pin to reconnect this connection, but I think it may have overheated the trace and damaged it. This is why I started to use the two next upstream pins from the original telemetry pins for telemetry (which worked fine).
Since then, I have been having an issue where the yaw will run out of control by itself, but the magnetometer would continue to test correctly and indicate correct headings in the CLI. I tried disabling the compass in MP, and the yaw still behaved eratically.
I pulled the oilpan off, and removed the original telemetry tx/rx pins as I thought they may be causing a short (and I suspect something is still shorting in there) and then when I reconnected the oilpan, my yaw held and behaved correctly, but my compass started to report initialisation errors when I started the CLI, and came back with unhealthy in the test menu.
I took the oilpan off again, and reflowed the solder joints between the compass and oilpan, and now the compass tests and behaves OK again, but now my yaw is all over the place as it initially was.
Is it possible that there is some voltage leaking onto the i2c bus? Is there anything else I can possibly do or try, or is my oilpan most likely toast? I'm trying to avoid replacing hardware if I can, since i've just shelled out for a replacement minimOSD which it turns out I don't need, and I won't be able to get a replacement APM for some time.