"progress bar", no gps, etc

1

hello everybody.
just got my unit today, connected a lcd display, and installed the latest fw
is a rev 0.7 board apparently.
i have a couple questions.
1- on the display there is a progress bar continuously running, and as it runs the screen brightness increases. pushing the control button the screen changes but the progress bar keeps running.
2- i keep getting a “nogps” message on the display. left the unit outside for a long time but seems GPS cant get a fix. there is a ceramic antenna, tried different orientations but doesnt seem to change anything.
3) - on the meshtastic application on the settings tab i keep getting a “you must turn on location etc etc”
location services are on…im on android 10
4) - havent found any place on the android app where to upgrade the fw on the unit. but maybe it only appears if there is a fw upg available…

if you need logs or extra info let me know.

thanks and regards from switzerland

1 Like
2

What hardware are you using?

3

is a LILYGO® TTGO T-Beam V0.7 868/915Mhz

4

I’ve seen a similar problem with one of my V1.1 boards, where it says it can’t find the AXP power chip and it can’t connect to the GPS. The constant screen brightness trigger sounds like a problem with setting the pull-up for the user button input, but I don’t know if that’s a version-specific problem or not :\

5

“sounds like a problem with setting the pull-up for the user button input”
yeah looks like. maybe something to do with 1.0/1.1 version having 2 buttons

i am truly amazed at the complexity and cheapness of these boards but i really wish they would invest couple hours writing at least some documentation.

6

The 1.0/1.1 boards still only have one user button, the other two are power and reset! It’s kinda annoying how opaque they can be. I can’t figure out what’s wrong with the one board I have, nothing looks broken or poorly-soldered, it just doesn’t find GPS or the power chip, for no apparent reason.

7

got around to connect a serial monitor. here the log

I2C device found at address 0x3c
ssd1306 display found
done
Meshtastic swver=0.7.10, hwver=1.0-EU865
Setting random seed 1238329936
Total heap: 265260
Free heap: 215952
Total PSRAM: 4194252
Free PSRAM: 4194252
AXP192 not found
Turning on screen
Read RTC time as 1 (cur millis 1511) valid=0
ERROR: No UBLOX GPS found, hoping that NEMA might work
RadioConfig reset!
Installing AES128 key!
Initial packet id 51093632, numPacketId 4294967295
Loading saved preferences
Loaded saved preferences version 10
Installing AES128 key!
NODENUM=0xabddd000, dbsize=1
JOINING WIFI: ssid=geeksville
Starting meshradio init…
Set radio: name=Default, config=3, ch=0, power=23
LORA init result 0
Battery -3mV 0%
Screen got status update 1
Screen: Started…
sending owner !2462abddd000/Gian/G
Update DB node 0xabddd000, rx_time=0
Node status update: 1 online, 1 total
Screen got status update 3
showing standard frames
old user !2462abddd000/Gian/G
updating changed=0 user !2462abddd000/Gian/G
Adding packet record (id=0x030ba083 Fr0x00 To0xff, WantAck0, HopLim3 Payload:Use r)
enqueuing for send (id=0x030ba083 Fr0x00 To0xff, WantAck0, HopLim3 encrypted)
txGood=0,rxGood=0,rxBad=0
showing standard frames
Starting low level send (id=0x030ba083 Fr0x00 To0xff, WantAck0, HopLim3 encrypted)
Transition powerFSM transition=boot timeout, from=BOOT to=ON
Setting bluetooth enable=1
Pre BT: 201504 heap size
Starting bluetooth
*** Mesh service:
Completed sending (id=0x030ba083 Fr0x00 To0xff, WantAck0, HopLim3 encrypted)
authenticated and connected to phone
showing standard frames
getFromRadio, !available
Trigger powerFSM 9
Client wants config, nonce=25
Reset nodeinfo read pointer
getFromRadio, state=2
encoding toPhone packet to phone variant=3, 52 bytes
getFromRadio, state=3
encoding toPhone packet to phone variant=6, 81 bytes
getFromRadio, state=4
Sending nodeinfo: num=0xabddd000, lastseen=0, id=!2462abddd000, name=Gian
encoding toPhone packet to phone variant=4, 42 bytes
getFromRadio, state=4
Done sending nodeinfos
getFromRadio, state=5
encoding toPhone packet to phone variant=8, 2 bytes
getFromRadio, !available
Trigger powerFSM 1
Transition powerFSM transition=Press, from=ON to=ON
Setting fast framerate
Setting idle framerate

ERROR: No UBLOX GPS found, hoping that NEMA might work

so not finding the GPS…
guess at least i have the answer to one question
good luck to me getting a replacement board from china :smiley:

AXP192 not found

uhm

1 Like
8

Yep, exact same issue I have :frowning:

9

In relation to the screen I don’t know if this is relevant but the connections are different to that of the screens for the T-beam V1, then terminals are marked VCC, GND, SCL, SDA, could this be the reason for the progress bar?

10

no i have of course vcc and gnd pins crossed through the wires. else display would not work

1 Like
11

There is a separate I/O pin that can trigger the button code, since someone wanted a way to wire up an external switch. It’s pin #13 on the v1.1 board, so if that’s being held low somehow it would also cause the screen brightness bar problem

12

tried pulling up the #13 but no change

#13 is already high anyway

maybe i should scope the ublox serial data, but not sure i want to spend this time…

13

Yeah it was a long shot, just included it for the sake of completeness. Hopefully replacement hardware comes soon! I’m told banggood has some UK stock, but I’m still waiting for mine…
If I magically find some way to fix my broken one, I’ll pass the info on

14

thanks.
i also got mine from banggood. but to be honest, never been a big fan. i usually shop for electronics on ebay and had very few issues.

15

0.7 TBEAM boards are not supported (and haven’t ever been - other than a brief two week experiment) with the current release.

But good news is by coincidence @slavino submitted the changes needed to make the 0.7 tbeams work and they will be included in next weeks build.

16

The progress bar is showing because the button GPIO tbeam 0.7 puts the button on a different GPIO. So if you run a 1.0 TBEAM load on it thinks the button is always pressed.

17

“0.7 TBEAM boards are not supported”
oh ok, good to know.
here it says they are, though :slight_smile:


“tbeam 0.7 puts the button on a different GPIO.”
also good to know
thanks.
18

Heh. I think slavino added that line when he added the support. :slightly_smiling_face:. But I haven’t put a build out with it yet. Probably later today.

19

no worries and no hurry.

20

progress report.
with FW 0.7.11 everything seems to work fine. gps has gotten a fix.

only funny thing i see a 254% battery status. i guess 256% would be fully charged :slight_smile:

2 Likes