Settings Screen Doesn't Allow/Provide Return to Main Screen

[daveclifford]

I finished assembling the T3 Throttle and went through a test functions/throttle famiiarization phase.

When I selected the Settings Screen (Loco UI/Screen Rotation), I can't go back to the Main Screen, unless I turn the Throttle off snd then back on.

Is this the correct behavior or did I miss something ?

Dave

[alex-code]

Hi Dave,

Touching the menu icon on the top right will always take you back to the menu.
With settings this is what also triggers the save to remember the settings so if you powered off any settings you selected would change back to the previous ones.

[daveclifford]

I found a US distributor - Mouser and shipping is only $7.99

[daveclifford]

I hate to have to do this, but it looks like I will have to disassemble the throttle to determine the cause of the touch screen failure.

It might be a case that the screen opening is too tight and impinged on the screen edge. Only a guess!

I am making another throttle, so I have a new un-used touchscreen to try out.

Stay tuned

Dave

[alex-code]

You could try adding a Serial.println("touch"); on line https://github.com/DCC-EX/EX-T3-WiFi/blob/master/src/main.cpp#L442 to see if a touch is being detected.

[daveclifford]

Alex,

Took your advice and added Serial.println("touch"); to main.cpp, then compiled, uploaded and then monitored.

When I touch the upper right icon on the Screen Rotation screen, the monitor shows "touch
177168".

Each touch on the screen anywhere displays a monitor "touch nnnnnn" character string.

Also, when I turn the throttle off/then on, the screen inverts.

NOTE: I am NOT connected to the DCC CS.

Dave

[alex-code]

The number is the free ram available, I used it to help debug mem leaks.

Settings won't be saved unless you can exit back to the main menu (without power cycling).

On line https://github.com/DCC-EX/EX-T3-WiFi/blob/master/src/main.cpp#L445 you could try adding

Serial.print("X: ");
Serial.print(points[0].x);
Serial.print(" - Y: ");
Serial.println(points[0].y);

So we can see what coordinates it's detecting.

[daveclifford]

lines 443-449 now are:

if (touches) {
// Remember the original touch points so we can use later calls to check for swipes
// Serial.println("touch");
Serial.print("X: ");
Serial.print(points[0].x);
Serial.print(" - Y: ");
Serial.println(points[0].y);

-------------PIO log below ---------------------------------------------------

Building in release mode
Compiling .pio/build/firebeetle2/src/main.cpp.o
src/main.cpp:23:21: warning: extra tokens at end of #include directive
#include <WiFiUI.h> Serial.println("touch");
^~~~~~
src/main.cpp: In function 'void loop()':
src/main.cpp:447:19: error: 'points' was not declared in this scope
Serial.print(points[0].x);
^~~~~~
src/main.cpp:447:19: note: suggested alternative: 'printf'
Serial.print(points[0].x);
^~~~~~
printf
*** [.pio/build/firebeetle2/src/main.cpp.o] Error 1
======================= [FAILED] Took 7.29 seconds =

Alex,
I don't know your code well enough to fix the error.

Can I assume the touchscreen hw is working due to the free ram value returned when pushing the return to main screen icon in upper left ? - or is it too soon to tell???

Dave

[daveclifford]

Wait for it, wait for it ....... the number is ........... 320 (is that the number you were thinking of?)

I have an accelerometer attached and noticed that it doesn't flip the screen.

Dave

[alex-code]

320 is what should be expected.

The problem is if you can't exit from settings back to the menu without power cycling, the settings (like screen rotation) won't be saved.

Leaving in the Serial outputs for x & y what x do you get if you touch anywhere on the right side of the display.

[daveclifford]

X: 282 - Y: 408
156548

[daveclifford]

weird - original in spanish

[alex-code]

I'm lost on this one, no idea why x won't go above 282.
Might have to make a debug app, something I've seen before where it draws as you touch the screen so we can see if the coords relate to the x & y of the display.

[daveclifford]

I plan to take the throttle partially apart to get to the touchscreen cable - reseat it - and then reassemble

I also think the accelerometer connections (4 solid wires ) may not be making contact with th FireBeetle2.
I can't see the screen flip when turning the throttle clockwise /counterclockwise.

For me, it's worth a try in disassembling my pride and joy.

A quick question - I assume these debug lines only reduce memory for real code, but won't affect the operation, since the user only sees the result in monitor mode, If so, why don't you put some instructions into the code for this purpose? You can take them out if program memory becomes tight.

I will do the disassembly/reassembly tomorrow Wednesday 4/5.

Dave

[alex-code]

A few Serial prints won't affect much.
They're only really needed for this kind of debugging but I've not encountered this issue so not needed them.

When you're on the settings could you invert the display then touch the same top right corner and see what x & y that shows.

[daveclifford]

inverted
push lower left
X: 302 - Y: 0
X: 289 - Y: 21
X: 294 - Y: 12
X: 296 - Y: 6

now push upper right *still inverted)
X: 43 - Y: 447
155948

X: 300 - Y: 9
push lower left

X: 42 - Y: 449
155956

Dave