OLED LCD Telemetry Setup help?!

This forum is dedicated to all issues and questions related to your individual setups and configurations
Post Reply
User avatar
city_kid
Posts: 64
Joined: Wed Apr 03, 2013 8:09 pm
Location: Birmingham UK

OLED LCD Telemetry Setup help?!

Post by city_kid »

Hello forum!

I have a Crius MultiWii Lite FC board, expanded with a Compass & Barometer I2C module.

It works perfectly! Can use ANGLE mode, BARO altitude holding, MAG heading hold etc etc.

Zero I2C errors reported. All working well. Running standard MultiWii v2.2. Perfect!

I have added a Crius OC-16 OLED LCD Display to show telemetry data.

My config.h contains the following:

Code: Select all

#define OLED_I2C_128x64

#define LCD_MENU_PREV 'p'             // These are not actually needed as I have no buttons?!
#define LCD_MENU_NEXT 'n'
#define LCD_VALUE_UP 'u'
#define LCD_VALUE_DOWN 'd'
#define LCD_MENU_SAVE_EXIT 's'
#define LCD_MENU_ABORT 'x'

#define LCD_CONF                           // Also probably not needed as I'm not going to use it for config?!
#define LCD_TELEMETRY                  // This is what I really want!!!
#define LCD_TELEMETRY_AUTO  "212232425262729"

Here's the problem:

1) The MultiWii boots and initializes the LCD.
2) I get a "logo" screen showing a little quad picture and splash texts.
3) After a second the display changes to "MultiWii v2.2 Quad-X"
4) Then, nothing, no change. The "MultiWii v2.2 Quad-X" text remains on-screen forever.

I really believe that this is not an electronic issue with the OLED LCD module.

Debug still shows 0 (zero) I2C errors.

All the other I2C devices (Baro, Mago etc) all work fine.

It's like the MultiWii main loop is not switching between the different telemetry pages.

Questions:

1) Is it a problem with my config.h file?
2) Does the MultiWii only loop through its telemetry pages as defined by #define LCD_TELEMETRY_AUTO "212232425262729" when the flight control is ARMED?

Please help!

Cheers!

city_kid

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: OLED LCD Telemetry Setup help?!

Post by Hamburger »

1. no, looking good. You must trigger the automatic stepping once via stick combo.
2. Or you could try this:

Code: Select all

#define LCD_CONF
#define LCD_CONF_AUX
#define SUPPRESS_LCD_CONF_AUX34

//#define LCD_TEXTSTAR
//#define LCD_VT100
#define OLED_I2C_128x64
#define SUPPRESS_OLED_I2C_128x64LOGO
#define DISPLAY_FONT_DSIZE

#define LCD_TELEMETRY
#define LCD_TELEMETRY_AUTO "1!"
#define LCD_TELEMETRY_STEP "1!5%4$2@9R" // first page gets autoloaded w/o user interaction

User avatar
city_kid
Posts: 64
Joined: Wed Apr 03, 2013 8:09 pm
Location: Birmingham UK

Re: OLED LCD Telemetry Setup help?!

Post by city_kid »

Hamburger!

Thanks for the reply!

So with the config.h DEFINES that you are showing in your reply, will the telemetry pages start changing automatically without a stick combo?

Cheers!

city_kid

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: OLED LCD Telemetry Setup help?!

Post by Hamburger »

the step sequence will automatically start with first page -and stay there;
the auto sequence must be triggered with stick input.

Read the wiki please - then come back with further questions (and enhancements to the wiki)

Maine_Guy
Posts: 27
Joined: Fri Mar 06, 2015 7:07 pm

Re: OLED LCD Telemetry Setup help?!

Post by Maine_Guy »

Why does telemetry debug have a big warning: "do NOT fly with this activated"? Does it slow the processor?

I'd like to always display telemetry - is there a reason not to?

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: OLED LCD Telemetry Setup help?!

Post by Hamburger »

It was not meant to, but I do not see why you could not if you must avoid that single stick combination after powerup.

Post Reply