@felmue said in M5-TOUGH / unable to change display brightness:

M5.Axp.SetLDOVoltage(3,3000);

Hi Felmue!

That one works, thanks a lot!

Really confusing that there is a PWM backlight LED mentioned in the library which does not work. And that the usage of SetLcdVoltage is inconsistent between the Core2 and TOUGH.

On Core2 the LcdVoltage changes DCDC3 (@param number 0=DCDC1 / 1=DCDC2 / 2=DCDC3 ) which is connected to LCD_BL. For the TOUGH on the other hand DCDC3 is unused and they used the LDO3.

So maybe they should simply change the line SetDCVoltage(2, voltage); to M5.Axp.SetLDOVoltage(3,voltage); or maybe even better introduce a new function SetLCDBacklightVoltage(...) in their library.

Thanks to all for your hints.

Well, yeah... but nothing works with the M5-TOUGH which should support it via the Axp.

Hi.

No Luck with M5.Axp.SetLcdVoltage(...);
The value has to be from 0-255 anyway.

At the backside they mentioned the backlight:
"BL: ACP_LDO3"

So this seems to the same as in Core2.

Hi.

I'm using the latest library via Platformio (lib_deps = https://github.com/m5stack/M5Tough) and am unable to change the display brightness.

My code is as simple as this:

M5.Axp.SetLcdVoltage(2500);

This does not change anything on the display.

It works with the M5-Core2 module though.

Can anybody confirm the SetLcdVoltage works for the M5-TOUGH?

Thanks and have a great week.

@forairaaaaa you can find my code here:
https://github.com/erazor83/nb_dtu_reset_issue/

Update for anybody who's reading this.

My previous assumption that the reset-button kills the modem seems incorrect.

I've had another two devices and carefully did not use the reset-button at all but these modules also stopped working.

@felmue thanks for your hints and your time!

@felmue there is nothing. I also removed and replaced Q3 with Q5. My idea was, that maybe Atom-RX line became output and killed Q3 but that's not the case.

Removing the Q5 completely changed nothing.

I ordered another two modules to check the signals but I start to think the issue is in the modem.

Maybe I come to a point where I should ask the M5 team for help. This is kinda annoying, I really like the design of the DTU.

Well, yes.... "AT\r" should be enough and this was even mentioned in the datasheets.

Anyway, mostly people use tinyGSM and "AT\r\n" should work anyway.

I tried "AT\r" - no difference, the modem remains silent. I also tried a USB-USART connection with 3.3V levels and tried different baudrates, spamming the modem with any combination of "AT\r\n" - no success.

Normally it has autobaud, if not it should start with "RDY" - I'm not getting anything with powerup. The modems LEDs blink but thats all.

I saw that they're translating the logic-levels from 3.3V to 1.8V. I'm not sure but these are looking completely strange to me.

There shouldn't be any 3.3V peaks, right? The image shows my TX line, somewhere at transistor Q3. NB_RX and U1_RX are looking quite similar, so maybe the transistor is broken?

Hi, I was playing with the DTU-NB some days ago until suddenly the modem stopped responding to any AT command.

So I bought two new devices, and now none respond anymore.

For testing I started to use "TinyGsmAutoBaud" (I also modified the code to use the correct PINs). With my first broken DTU - no response to any Baudrate.

Since I seemed to broke the second module already and the TinyGsmAutoBaud also does not respond I simply put the Atom into my third unused DTU - which worked and got a response with 115200 - so the TinyGsmAutoBaud and Firmware seems to work.

I tried the same Atom on my second (broken) DTU with no success. So I resumed playing with the third DTU, and pressed the rest button - and finally this one also does not respond.

Is this a hardware issue? Any way to get the broken devices running again?

Thanks for your time.