search

cyoung / stratux

Aviation weather and traffic receiver based on RTL-SDR.
BSD 3-Clause "New" or "Revised" License
1.06k stars 365 forks source link

RY835AI AHRS stopped working - troubleshooting help? #330

Closed JohnOCFII closed 8 years ago

JohnOCFII commented 8 years ago
  1. Stratux version: v0.8r1 (also tried images for .6 and .7)

  2. Stratux config:

    SDR [ ] single [ X] dual

    GPS [ X] yes [ ] no type:

    AHRS [ X] yes [ ] no

    power source: wall wart and Anker (same behavior each)

    usb cable: thick mono price cable stratux.log.zip

  3. EFB app and version: (WebUI)

    EFB platform: (iOS 9.2.1)

    EFB hardware: (iPad Air 2)

  4. Description of your issue:

As I prepared to put my components in a 3D printed case, I've tested as I've made changes. After coating the rear side of the RY835AI in liquid electrical tape, I re-connected the wires to the Raspberry Pi, and the AHRS is no longer working.

This was working just before I applied the coating. I did not coat the sensors on the front side of the board. GPS is working fine. I re-confirmed continuity for all connections, and confirmed that there was no short between the SCL1/SDA1 wires.

I re-tried the last three images (which had worked successfully for me). I am assuming this is a hardware issue on my end, but wanted to see if there were any ideas on what to try next.

Thanks,

John

If possible, enable "Replay Logs", reproduce the problem, and provide a copy of the logs in http://192.168.10.1/logs/stratux/ and http://192.168.10.1/logs/stratux.log. (Logs attached)

Nokomis449 commented 8 years ago

I had similar green check/red X blinking behavior once after disassembly/reassembly. Thought I had fried the RY, but my 4th check of the wiring finally revealed that I had transposed two of them, possibly the send/recv. Your eyes will see what your brain tells it to see.

JohnOCFII commented 8 years ago

I had similar green check/red X blinking behavior once after disassembly/reassembly. Thought I had fried the RY, but my 4th check of the wiring finally revealed that I had transposed two of them, possibly the send/recv. Your eyes will see what your brain tells it to see.

Certainly possible. On the RY, there are only two wires involved (as power and ground are good from the GPS side. I have swapped them around, and the behavior does not change. I'm hoping a developer can tell me if the above-mentioned log message [ readBMP180(): input/output error ] provides any additional clues.

Thanks,

John

ghost commented 8 years ago

First, make sure the modules are being detected with i2cdetect. As su:

apt-get update
apt-get install i2ctools
i2cdetect -y 1

The gyro has hardware address 0x68, and the pressure sensor is 0x77. If both are connected and talking to the bus, i2cdetect will show this:

      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 
 70: -- -- -- -- -- -- -- 77
bjax commented 8 years ago

Looks like that should be

apt-get install i2c-tools

JohnOCFII commented 8 years ago

The gyro has hardware address 0x68, and the pressure sensor is 0x77. If both are connected and talking to the bus, i2cdetect will show this:

Thanks - I'll check it out this weekend when I'm back in town.

JohnOCFII commented 8 years ago

I get nothing. I can pull the wires and re-solder, in case there is something I can't see and the multi-meter can't detect. Of course, that just doesn't make sense, as I tested it after I soldered everything in place. The only change between that test, and the failure situation was covering the back side of the RY board with liquid electrical tape.

pi@raspberrypi ~ $ sudo i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --
pi@raspberrypi ~ $

skypuppy commented 8 years ago

Your Pi is definitely not seeing the AHRS unit at all, with i2cdetect output like that. Has to be 1) electrical, or 2) i2c comms not enabled in the kernel.

On 03/18/2016 09:28 PM, JohnOCFII wrote:

I get nothing. I can pull the wires and re-solder, in case there is something I can't see and the multi-meter can't detect. Of course, that just doesn't make sense, as I tested it after I soldered everything in place. The only change between that test, and the failure situation was covering the back side of the RY board with liquid electrical tape.

pi@raspberrypi ~ $ sudo i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --

pi@raspberrypi ~ $

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/cyoung/stratux/issues/330#issuecomment-198618348

JohnOCFII commented 8 years ago

Your Pi is definitely not seeing the AHRS unit at all, with i2cdetect output like that. Has to be 1) electrical, or 2) i2c comms not enabled in the kernel.

It was electrical. I pulled off the liquid electrical tape, and there was a whisker of a wire shorting on the SCL1/SDA1 wires. Not sure why the continuity check didn't catch it.

cyoung commented 8 years ago

Glad you got it!