no baro and mag detected on SPREVO on eeaa20a

[bk79]

this is the status and bootlog

status

System Uptime: 32 seconds, Voltage: 0 * 0.1V (1S battery - NOT PRESENT), System load: 0.01 CPU Clock=72MHz, GYRO=MPU6500, ACC=MPU6500 Sensor status: GYRO=OK, ACC=OK, MAG=NONE, BARO=NONE, SONAR=NONE, GPS=NONE Stack size: 2048, Stack address: 0x10002000 Cycle Time: 2010, I2C Errors: 0, config size: 2032

bootlog

Time Evt Description Parameters 0: 0 CONFIG_LOADED 0: 1 SYSTEM_INIT_DONE 501: 19 TIMER_CHANNEL_MAPPED (0, 0, 0, 0) 501: 19 TIMER_CHANNEL_MAPPED (1, 1, 0, 2) 501: 19 TIMER_CHANNEL_MAPPED (2, 2, 0, 2) 501: 19 TIMER_CHANNEL_MAPPED (3, 3, 0, 2) 501: 19 TIMER_CHANNEL_MAPPED (4, 4, 0, 2) 501: 19 TIMER_CHANNEL_MAPPED (5, 5, 0, 2) 501: 19 TIMER_CHANNEL_MAPPED (6, 6, 0, 2) 501: 19 TIMER_CHANNEL_MAPPED (7, 7, 0, 2) 501: 19 TIMER_CHANNEL_MAPPED (8, 8, 0, 2) 501: 19 TIMER_CHANNEL_MAPPED (9, 9, 0, 2) 501: 19 TIMER_CHANNEL_MAPPED (10, 10, 0, 2) 501: 2 PWM_INIT_DONE 511: 3 EXTRA_BOOT_DELAY 1047: 9 GYRO_DETECTION (7, 0, 0, 0) 1639: 10 ACC_DETECTION (8, 0, 0, 0) 1639: 11 BARO_DETECTION (0, 0, 0, 0) 1639: 12 MAG_DETECTION (0, 0, 0, 0) 1639: 13 RANGEFINDER_DETECTION (0, 0, 0, 0) 1639: 4 SENSOR_INIT_DONE 2340: 7 TELEMETRY_INIT_DONE 3342: 8 SYSTEM_READY

[stronnag]

Expected behaviour. For 1.5 you need to explicitly set the hardware. Thusly:

# version
# INAV/SPRACINGF3EVO 1.5.0 Dec 14 2016 / 16:59:14 (eeaa20af)
# status
System Uptime: 44 seconds, Voltage: 0 * 0.1V (1S battery - NOT PRESENT), System load: 0.10
CPU Clock=72MHz, GYRO=MPU6500, ACC=MPU6500, BARO=BMP280, MAG=HMC5883
Sensor status: GYRO=OK, ACC=OK, MAG=OK, BARO=OK, SONAR=NONE, GPS=OK
Stack size: 2048, Stack address: 0x10002000
Cycle Time: 1005, I2C Errors: 0, config size: 2032

baro_hardware = BMP280
                      Allowed values: NONE, BMP085, MS5611, BMP280, FAKE

mag_hardware = HMC5883
                      Allowed values: NONE, HMC5883, AK8975, MAG_GPS, MAG_MAG3110, MAG_AK8963, FAKE

[bk79]

Not exactly user friendly...i don't think less expert people to mess with cli to find the correct hw

Il 14/dic/2016 21:56, "stronnag" notifications@github.com ha scritto:

Expected behaviour. For 1.5 you need to explicitly set the hardware.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/931#issuecomment-267154188, or mute the thread https://github.com/notifications/unsubscribe-auth/ALSWigwwyDPajiPq7oZ1z_vvo-JB3pCRks5rIFgPgaJpZM4LNZt6 .

[stronnag]

They can find it from the wiki and enter the values in the updated configurator. Maybe even that can get automated from the FC identification. Given the myriad of problems with auto-detection, this will at least be reliable. Care to close this non-issue?

[bk79]

Close it

Il 14/dic/2016 22:14, "stronnag" notifications@github.com ha scritto:

They can find it from the wiki and enter the values in the updated configurator. Maybe even that can get automated from the FC identification. Given the myriad of problems with auto-detection, this will at least be reliable. Care to close this non-issue?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/931#issuecomment-267158591, or mute the thread https://github.com/notifications/unsubscribe-auth/ALSWin1D90nuyvl5KYsB5EjocF2F__yqks5rIFxLgaJpZM4LNZt6 .

[digitalentity]

Autodetection caused all kinds of issues, it even may misdetect MS5611 for BMP085 (or vice versa I can't remember). It may also cause problems if more than one chip is available on the bus - i.e. it may result in onboard compass being used instead of external one.

While new solution is a bit less user-friendly it's considerably more robust.

[bk79]

It would be nice to have the possibility to configure it from the configurator l

Il 15/dic/2016 06:38, "Konstantin Sharlaimov" notifications@github.com ha scritto:

Autodetection caused all kinds of issues, it even may misdetect MS5611 for BMP085 (or vice versa I can't remember). It may also cause problems if more than one chip is available on the bus - i.e. it may result in onboard compass being used instead of external one.

While new solution is a bit less user-friendly it's considerably more robust.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/931#issuecomment-267243656, or mute the thread https://github.com/notifications/unsubscribe-auth/ALSWihGVOlCqK17aHP4VrBtWX25eX04gks5rINJrgaJpZM4LNZt6 .

[digitalentity]

That's the idea!

[DzikuVx]

@bk79 Configurator will follow shortly