Navio2 and mission planner are not connected

Hello
I bought four to experiment with Navio2, but two are working normally, but the other two are not working.
I attach a picture.
I wonder why it’s not working and how it can work.


Hi @osung1598,

From the pictures you attached, I see that you’re trying to run sudo emlidtool when ArduCopter is already enabled. However, it won’t let you do this until you disable ArduCopter first. This is how it works, it’s not an issue.

So, can you tell me how to shut down the arducopter?

@osung1598,

You can disable it by selecting the Stop option in the Emlidtool window, as it’s shown in your first screenshot.

We re-installed the Raspbian SW provided by emrid and reset it to Navio2 docs, but it is still not connected to the mission planner.
I have also modified the contents of the section “Specifying Launching options” in Navio2 docs.
Finally, ms5611: Faild occurs as shown in the picture below.
I don’t know if it’s a HW defect or if I set it up incorrectly, but out of the 4 products purchased, the same phenomenon occurs in 2 products.
All four settings were the same.

If the hardware is broken, should I just throw it away?
Or is AS available?
Installing and updating a new SW all day long will not solve this problem.
Please check.

Hi @osung1598,

Is there anything connected to the I2C port on these Navio2 boards when the test fails?

no. I opened navio2 for the first time and connected and tested as per navio2 documentation.

@osung1598,

Please check that Navio2 is fixed properly to the Raspberry Pi with screws. Then, please run one of the Barometer examples and post the output here.

Hello
I wrote back late because I had work to do. I’m sorry.
The output you mentioned is as follows.

  1. navio2
    Failed to write reg: Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Temperature©: 20.000023 Pressure(millibar): -0.019955
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Temperature©: 20.000023 Pressure(millibar): -0.019955
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Temperature©: 20.000023 Pressure(millibar): -0.019955
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Temperature©: 20.000023 Pressure(millibar): -0.019955

  2. navio2
    Failed to write reg: Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Temperature©: 20.000065 Pressure(millibar): -0.019869
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Temperature©: 20.000065 Pressure(millibar): -0.019869
    qFailed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Temperature©: 20.000065 Pressure(millibar): -0.019869
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Temperature©: 20.000065 Pressure(millibar): -0.019869
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Failed to write device(-1): Remote I/O error
    Failed to write reg: Remote I/O error
    Temperature©: 20.000065 Pressure(millibar): -0.019869

The output of two failed Navio2 is posted.
Please check.

Hi @osung1598,

Thanks for the details.

Could you please post a screenshot of the i2cdetect -y 1 command output?

Please also take a photo of the screwed Navio2 and share it with me here. I need to check that it’s connected properly. It might be the issue you get can be solved by a tighter connection.

Thank you so much for your care.
First of all, the contents and photos you mentioned are as follows.
Please check it.

  1. navio2
    pi@navio:~ $ 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@navio:~ $ 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: – -- – -- – -- – --


    image

  2. navio2
    pi@navio:~ $ 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@navio:~ $ 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: – -- – -- – -- – --


    image

Hi @osung1598,

Could you please check those Navio2 with another pins extender? Might be it cause loose contact with Navio2.

Thank you for your confirmation.
I checked using a different pin extender, but there is nothing different from the above.
Also, there is no problem with connecting a product that works normally using the same pin extender.
Is it really broken?

Please check the above information.
I’m telling you again because there was no reply.

Hi @osung1598,

Please check your PM. I’ve written to you there as we need some details that might include sensitive information.