Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
5" touchscreen issues
I recently completed my build - latest version of teensy s/w installed from pjrc, using V096.7 and R8875 files from this group site and other library files installed per Jack's color coded post. The trace on the teensy has been cut. I have performed multiple screen calibrations to no apparent effect. All sdev's?below 10. I enabled the debug trace that Jack suggested and can see the touchscreen clearly registers touches, however it doesn't recognize most buttons and misrecognizes?others, eg. touch USB and RIT is selected (and confirmed this is what it saw in the trace). I suspect the calibration values aren't being stored for some reason. Any ideas from the group? 73, Joe AF4XS |
Joseph: Let me check into this. What size display are you using and what is the version of your software? Jack, W8TEE
On Wednesday, May 20, 2020, 11:28:21 AM EDT, Joseph Giallo II <jgiallo@...> wrote:
I recently completed my build - latest version of teensy s/w installed from pjrc, using V096.7 and R8875 files from this group site and other library files installed per Jack's color coded post. The trace on the teensy has been cut. I have performed multiple screen calibrations to no apparent effect. All sdev's?below 10. I enabled the debug trace that Jack suggested and can see the touchscreen clearly registers touches, however it doesn't recognize most buttons and misrecognizes?others, eg. touch USB and RIT is selected (and confirmed this is what it saw in the trace).
I suspect the calibration values aren't being stored for some reason. Any ideas from the group? 73, Joe AF4XS |
duh...didn't see the tag line! Jack, W8TEE
On Wednesday, May 20, 2020, 11:43:51 AM EDT, jjpurdum via groups.io <jjpurdum@...> wrote:
Joseph: Let me check into this. What size display are you using and what is the version of your software? Jack, W8TEE
On Wednesday, May 20, 2020, 11:28:21 AM EDT, Joseph Giallo II <jgiallo@...> wrote:
I recently completed my build - latest version of teensy s/w installed from pjrc, using V096.7 and R8875 files from this group site and other library files installed per Jack's color coded post. The trace on the teensy has been cut. I have performed multiple screen calibrations to no apparent effect. All sdev's?below 10. I enabled the debug trace that Jack suggested and can see the touchscreen clearly registers touches, however it doesn't recognize most buttons and misrecognizes?others, eg. touch USB and RIT is selected (and confirmed this is what it saw in the trace).
I suspect the calibration values aren't being stored for some reason. Any ideas from the group? 73, Joe AF4XS |
I use several Teensy boards for a lot of things.? Been playing with the new 4.1 as of late.? I use a few of the RA8875 screens.? As soon as I installed Teensyduino 1.52 final I ran into all sorts of issues with the 8875 screens.? I went back to 1.52 beta #5 and they started working again.? There is a couple of threads on PJRC forum about others with the same issue.? I am sure Paul will have it fixed soon.
|
Richard E Neese
the jackal biard and the 4.1 are not compatavle with layout and pins so they will have issues. the k\jackal board is ment for 3.6 teensy ------ Original Message ------
From: "Michael Graves" <ke4est@...>
Sent: 5/20/2020 12:27:05 PM
Subject: Re: [JackAl] 5" touchscreen issues I use several Teensy boards for a lot of things.? Been playing with the new 4.1 as of late.? I use a few of the RA8875 screens.? As soon as I installed Teensyduino 1.52 final I ran into all sorts of issues with the 8875 screens.? I went back to 1.52 beta #5 and they started working again.? There is a couple of threads on PJRC forum about others with the same issue.? I am sure Paul will have it fixed soon. |
I was just giving some back story.? I have many projects going on besides the Jackal. :)? I have not even tried the 4.1 with a RA8875 yet, I just got one the other day.
Was just letting the OP know I ran into some problems with the RA8875 using different Teensy boars once I upgraded to the latest Teensyduino 1.52. 73 Michael -- KE4EST |
Richard E Neese
as far as I know this project died no code updates . I have been looking ta the code and compairing the 2 vresions the touchscreen code did not change. Execpt a few new functions ------ Original Message ------
From: "Joseph Giallo II" <Jgiallo@...>
Sent: 5/21/2020 10:44:00 PM
Subject: Re: [JackAl] 5" touchscreen issues Unfortunately backing down to 1.52 beta 5 doesn¡¯t fix it in my case but appreciate the input nonetheless. |
Which Teensy are you using? Jack, W8TEE
On Friday, May 22, 2020, 8:27:22 AM EDT, Richard E Neese <r.neese@...> wrote:
as far as I know this project died no code updates . I have been looking ta the code and compairing the 2 vresions the touchscreen code did not change. Execpt a few new functions ------ Original Message ------
From: "Joseph Giallo II" <Jgiallo@...>
Sent: 5/21/2020 10:44:00 PM
Subject: Re: [JackAl] 5" touchscreen issues Unfortunately backing down to 1.52 beta 5 doesn¡¯t fix it in my case but appreciate the input nonetheless. |
Richard E Neese
hey jack I have been working on your code to port it to teensy4.1 we have 1 library that has to be fixed I fixed one already. the OpenAudio_ArduinoLibrary does not have the speeds and mcu support for the teensy4 /4.1 yet I have been working to fix it. and we have redone the pins for a new layout. Are you still developing or have you dropped the project as lat updates are like a year old and the website seems to not function. ?
------ Original Message ------
From: "jjpurdum via groups.io" <jjpurdum@...>
Sent: 5/22/2020 9:00:41 AM
Subject: Re: [JackAl] 5" touchscreen issues
|
Our web site was hacked and each time we fixed it, it got hacked again, so we haven't tried for some time. We have not done anything new with the JackAl, but will continue to monitor this group as best we can. Al and I have be swamped with the new Projects book, which we hope will be out in July. Al and I have both ordered T4.1's but they are not here yet. Also, with editing page proofs, I'm not sure when we will get back to the JackAl. Keep us posted, as the JackAl should fly with the new T4 series! Jack, W8TEE
On Friday, May 22, 2020, 10:18:11 AM EDT, Richard E Neese <r.neese@...> wrote:
hey jack I have been working on your code to port it to teensy4.1 we have 1 library that has to be fixed I fixed one already. the OpenAudio_ArduinoLibrary does not have the speeds and mcu support for the teensy4 /4.1 yet I have been working to fix it. and we have redone the pins for a new layout. Are you still developing or have you dropped the project as lat updates are like a year old and the website seems to not function. ?
------ Original Message ------
From: "jjpurdum via groups.io" <jjpurdum@...>
Sent: 5/22/2020 9:00:41 AM
Subject: Re: [JackAl] 5" touchscreen issues
|
James Zdunic
¿ªÔÆÌåÓýSame experience for me. ?Could never get the 7¡± touchscreen to properly recognize touch. ?Even after using cal procedure. ?And no local meetings to work as group to solve problem. ?It¡¯s been sitting in unusable condition for a year now hoping
a solution would be found.
On May 22, 2020, at 8:27 AM, Richard E Neese <r.neese@...> wrote:
|
My working hypothesis is that the touchscreen is recognizing touches since I can see them in the debug trace and that the root problem is that calibrations are not being stored. Next avenue of investigation is the EEPROM functions and related libraries. Certainly open to any suggestions the group has as it feels like a s/w issue at this point - i.e. something changed since this configuration is working for some....
73, Joe AF4XS |
John: There's a function in the EEPROM.cpp file called ShowEEPROMValues(). Try calling that function near the bottom of setup() and see if the EEPROM values make sense. Jack, W8TEE
On Friday, May 22, 2020, 2:09:47 PM EDT, Joseph Giallo II <jgiallo@...> wrote:
My working hypothesis is that the touchscreen is recognizing touches since I can see them in the debug trace and that the root problem is that calibrations are not being stored. Next avenue of investigation is the EEPROM functions and related libraries. Certainly open to any suggestions the group has as it feels like a s/w issue at this point - i.e. something changed since this configuration is working for some.... 73, Joe AF4XS |
Yup, they make sense and are in fact being stored. Now trying to see if the issue is in the RA8875 library. Curiously using the sumotoy 8875 library referenced in some JackAl literature produces a compile error: "class RA8875 has no member named touch". Interesting since the problem is not recognizing touches. The RA8875 library off of the groups.io JackAl site does compile without the error but exhibits the original problem I described. Seems like the issue is somewhere in the RA8875, URTouch, or UTFT libraries....investigative suggestions welcome.
Joe |
Al and I talked about this yesterday, and we (vaguely--we're old) remember the coordinate system was "reversed" on the 7" system. If you can, put in some Serial.print() statements in the calibration routine and see if they look that way. Meanwhile, we're trying to dig out a 7" display on this end. Jack, W8TEE
On Saturday, May 23, 2020, 12:07:00 AM EDT, Joseph Giallo II <jgiallo@...> wrote:
Yup, they make sense and are in fact being stored. Now trying to see if the issue is in the RA8875 library. Curiously using the sumotoy 8875 library referenced in some JackAl literature produces a compile error: "class RA8875 has no member named touch". Interesting since the problem is not recognizing touches. The RA8875 library off of the groups.io JackAl site does compile without the error but exhibits the original problem I described. Seems like the issue is somewhere in the RA8875, URTouch, or UTFT libraries....investigative suggestions welcome. Joe |
OK - will do. Note that I'm using a 5" display but latest behavior definitely indicates what is recognized is shifted from what is actually touched so some sort of coordinate reversing is a possibility. I have gone back to using the time, timerone libraries referenced in your "libraries" document to see this latest behavior. It does seem like the some of the latest teensy libraries are somehow different from those I understand other users have previously shown to work. Also, after a few touches the screen stops reacting, almost as if there is some sort of buffer overflow occuring where new touches aren't recognized on the screen and the debug trace doesn't register them either....
Joe AF4XS |
James Zdunic
¿ªÔÆÌåÓýJack,
I¡¯m local and have a 7¡± display that I¡¯d be willing to let you guys use for revisiting this. ?Let me know if you¡¯re interested.
On May 23, 2020, at 9:07 AM, jjpurdum via groups.io <jjpurdum@...> wrote:
|
to navigate to use esc to dismiss