|
Re: 7 inch Screen Calibration
Vince Loschiavo
Jack,
Thanks for the response. 1.? Did removed the jumper between the pads so all is ok now with ability to pgm teensy in-situ with supply connected. 2.? I did expect that based on page 25 of the manual, that i would see the yellow circles to initiate the cal (not sure if this was intended with the previous software release (v094) but currently using v095. i didn't have the display hooked up at first powerup of the teensy (doing voltage checks) so never saw the yellow circles.? so down to the manual initiate of the screen cal as stated on pg 25. display comes up with your splash screen and with some values in the display does recognize touch, but way off...have to hunt around to find a spot, that reacts (love the other screens ie. wpm..and encoder works. You can see the images.? so that's all good. If possible if you have some rough numbers for the 7 inch I would like to try those and see what i'm not doing correctly that would be appreciated. I've spent about 3 hours figuring out i don't know what I'm missing.. Is it possible to bring up the 'yellow circles? or do i do the top left bottom right using the serial monitor, and then where do those values go?? in here? float xFinal = ;
float yFinal = ; thanks for your help.. Vince n2aie |
|
Re: 7 inch Screen Calibration -- Opps, pressed wrong button
On Saturday, March 16, 2019, 10:06:31 PM EDT, Jack Purdum <jjpurdum@...> wrote:
The problem is that the code goes out and checks the first byte of EEPROM (EEPROMNew.cpp): void ReadUserSettings() { ? int val; ? EEPROM.get(0, val);????? // Read first byte of EEPROM memory //val = 0;???????????????? // Uncomment this line forces a rewrite of EEPROM. Comment out line 23 to display ?????????????????????????? // is not changed. Serial.print("Val = "); Serial.println(val);?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ? ? if (val != EEPROMINITVALUE) {???????????????????????????? // Already set or not? ??? GlobalDefaultEEPROMValues();??????????????????????????? // No, so set some common values ??? WriteEEPROMSettings(EEPROMDEFAULTOFFSET);?????????????? // Write default values to default block ??? WriteEEPROMSettings(EEPROMUSEROFFSET);????????????????? // Also assume defaults for user first time through If that first byte (e.g., EEPROM address 0) read into val is not equal to EEPROMINITVALUE, the program automatically goes into the initialization routines. Raw EEPROM on a new Teensy is initialized to 0xFF, which is not what EEPROMINITVALUE. This will cause the code to write default values into EEPROM. No doubt, that's what happened to your system. Exactly what is the problem after you init the screen? Is it that the buttons don't respond to presses at all, or that the presses are way off target? I did find some early tests we did with the 7" display (it died!) and the values we were using were: // ------------------------? Al's 7" Calibration ------------? 8-14-18 ? calty = map(yFinal, 838, 174, 50, 430);?????? // Al ? range = map(int(calty), 0, 479, 1, 4); ? switch (range) { ??? case 1: ????? caltx = map(xFinal, 684, 321, 50, 750); // Map from ADC values to Screen??? // Al ????? break; ??? case 2: ????? caltx = map(xFinal, 684, 321, 50, 750); // Map from ADC values to Screen??? // Al ????? break; ??? case 3: ????? caltx = map(xFinal, 684, 321, 50, 750); // Map from ADC values to Screen??? // Al ????? break; ??? case 4: ????? caltx = map(xFinal, 684, 321, 50, 750); // Map from ADC values to Screen??? // Al ????? break; ? } #endif which is near line 158 in the DisplayCalibration.cpp file. You'll notice this code was only toggled in when we were testing Al's 7" display (e.g., #define AL7) much like I explained with the DEBUG symbolic constant. I don't know if this will help, as we don't have a working 7" display right now. It might be a starting point... Jack, W8TEE
On Saturday, March 16, 2019, 11:37:36 AM EDT, Vince Loschiavo <vince320@...> wrote:
Jack, maybe I didn't ask the correct question. I missed the initial cal routine at first powerup...probably because i didn't have the display installed?? anyway. to get to run the cal routine, i should set VAL = 0? ?? then what is the next step?? Vince n2aie |
|
Re: 7 inch Screen Calibration
The problem is that the code goes out and checks the first byte of EEPROM (EEPROMNew.cpp): void ReadUserSettings() { ? int val; ? EEPROM.get(0, val);????? // Read first byte of EEPROM memory //val = 0;???????????????? // Uncomment this line forces a rewrite of EEPROM. Comment out line 23 to display ?????????????????????????? // is not changed. Serial.print("Val = "); Serial.println(val);?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ? ? if (val != EEPROMINITVALUE) {???????????????????????????? // Already set or not? ??? GlobalDefaultEEPROMValues();??????????????????????????? // No, so set some common values ??? WriteEEPROMSettings(EEPROMDEFAULTOFFSET);?????????????? // Write default values to default block ??? WriteEEPROMSettings(EEPROMUSEROFFSET);????????????????? // Also assume defaults for user first time through If that first byte (e.g., EEPROM address 0) read into val is not equal to EEPROMINITVALUE, the program automatically goes into the initialization routines. Raw EEPROM on a new Teensy is initialized to 0xFF, which is not what EEPROMINITVALUE. This will cause the code to write default values into EEPROM. No doubt, that's what happened to your system. Exactly what is the problem after you init the screen? Is it that the buttons don't respond to presses at all, or that the presses are way off target? I did find some early tests we did with the 7" display (it died!) and the values we were using were:
On Saturday, March 16, 2019, 11:37:36 AM EDT, Vince Loschiavo <vince320@...> wrote:
Jack, maybe I didn't ask the correct question. I missed the initial cal routine at first powerup...probably because i didn't have the display installed?? anyway. to get to run the cal routine, i should set VAL = 0? ?? then what is the next step?? Vince n2aie |
|
Re: 7 inch Screen Calibration
If you plan on using the JackAl system with both USB power and the 3.3V supply, you should but the trace between the VUSB pads on the underside of the board: This will prevent a conflict between power from the USB port and the 3.3V supply. If you later find you don't need the USB connection to the PC, you can jumper the traces again. I don't think this is your problem, however, but it is a safer way to keep the USB connection between the UCB port and the Teensy. Jack, W8TEE
On Saturday, March 16, 2019, 12:12:05 PM EDT, Vince Loschiavo <vince320@...> wrote:
just looking at the code and the serial.print values, I'm assuming i should be monitoring the serial monitor to get the values and not on the display. so that requires the teensy to be connected to the computer and the board fired up with the display. so when i connect the teensy to the computer with the board powered up, doesn't get recognized, but if i disconnect board from the supply it connects. does this relate to the 2 pads under the teensy that are connected? and should be separated? Thanks still a bit confused.. Vince n2aie |
|
Re: 7" Display Drawing
I was reading my overnight emails, which I do from top to bottom, so I didn't see this before I wrote my last email to you. Actually, these values don't look too far out of what I would expect. Let Al and I experiment with it a little. Honestly, it probably won't be until Monday or so before we can get to it. Sorry... Jack, W8TEE
On Friday, March 15, 2019, 11:11:41 PM EDT, James Zdunic <james_zdunic@...> wrote:
Jack,
I could only get around the screen 7 times before the point ignored became unrelenting and I can¡¯t get past the point you see in the photo below...
Jim KM4TXR
|
|
Re: 7" Display Drawing
The expected calibration values for the display are "guessed" near the top of the DisplayCalibration.cpp file (line 55): float xMapLowRange1 = 671; float xMapLowRange2 = 689; float xMapLowRange3 = 689; float xMapLowRange4 = 716; These values are seen as approximations for the 5" display. Your values are close, but look a little wonky. Just for grins, place this code: #ifdef DEBUG xMapLowRange1 = 671; xMapLowRange2 = 689; xMapLowRange3 = 689; xMapLowRange4 = 716; #endif in the bottom of the setup() routine, after the EEPROM is read. ? EraseMessageLine();??????????????????????????????????????????????? // This is around line 1070 in the INO file #ifdef DEBUG ? ShowEEPROMValues(); #endif #ifdef DEBUG???????????????????????????????????????????????????????????? // test values xMapLowRange1 = 671; xMapLowRange2 = 689; xMapLowRange3 = 689; xMapLowRange4 = 716; #endif That will force these values and you can judge their impact on the behavior of your display. If it does, we need to figure out why your calibration routine isn't working right. Remind me again of the display size you are using. Jack, W8TEE
On Friday, March 15, 2019, 11:20:38 PM EDT, James Zdunic <james_zdunic@...> wrote:
Jack,
The following are the initial debug values after boot up...
Val = 150
displayWidth = 800
displayHeight = 480
defaultTextSize = 3
activeVFO = 1
currentFrequencyA = 14285000
currentFrequencyB = 14250000
currentXmitMode = 0
ssbIndex = 1
bandArrayIndex = 1
wordsPerMinute = 15
cwSidetone = 700
ssbCenterFrequency = 1500
currentRIT = 0
speechCompression = 0
cwSwitchIndex[0] = 1
cwSwitchIndex[1] = 2
cwSwitchIndex[2] = 3
AGCState = 0
meterChoice = 0
freqScalarPosition = 4
cwCenterFrequency = 700
cwCustomFilterWidth = 400
ssbCustomFilterEdgeLo = 200
ssbCustomFilterEdgeHi = 2500
lastBandFreqUsedSSB[0] = 3985000
lastBandFreqUsedSSB[1] = 7277000
lastBandFreqUsedSSB[2] = 14285000
lastBandFreqUsedSSB[3] = 21385000
lastBandFreqUsedSSB[4] = 28385000
xMapLowAve1 = 600.96
xMapLowAve2 = 609.51
xMapLowAve3 = 644.70
xMapLowAve4 = 700.04
sidetoneVolume = 0.10
rxEqualizer[0] = 0
rxEqualizer[1] = 290
rxEqualizer[2] = 290
rxEqualizer[3] = 235
rxEqualizer[4] = 215
rxEqualizer[5] = 295
rxEqualizer[6] = 320
rxEqualizer[7] = 340
txEqualizer[0] = 260
txEqualizer[1] = 260
txEqualizer[2] = 260
txEqualizer[3] = 260
txEqualizer[4] = 260
txEqualizer[5] = 260
txEqualizer[6] = 260
txEqualizer[7] = 260
cwFilterDefaultIndex = 3
keyType = 0
ssbDefaultFilterIndex = 3
calSi5351CrystalFreq = 25007172
usbCarrier = 11996000
decoderToggle = 0
filterSkirts[8][0] = 500
filterSkirts[8][1] = 900
filterSkirts[9][0] = 100
filterSkirts[9][1] = 2200
yMapLowAve = 861.33
xMapHighAve = 299.86
yMapHighAve = 155.05
0:00:02 1 1 1970
displayWidth = 800
displayHeight = 480
defaultTextSize = 3
activeVFO = 1
currentFrequencyA = 14285000
currentFrequencyB = 14250000
currentXmitMode = 0
ssbIndex = 1
bandArrayIndex = 1
wordsPerMinute = 15
cwSidetone = 700
ssbCenterFrequency = 1500
currentRIT = 0
speechCompression = 0
cwSwitchIndex[0] = 1
cwSwitchIndex[1] = 2
cwSwitchIndex[2] = 3
AGCState = 0
meterChoice = 0
freqScalarPosition = 4
cwCenterFrequency = 700
cwCustomFilterWidth = 400
ssbCustomFilterEdgeLo = 200
ssbCustomFilterEdgeHi = 2500
lastBandFreqUsedSSB[0] = 3985000
lastBandFreqUsedSSB[1] = 7277000
lastBandFreqUsedSSB[2] = 14285000
lastBandFreqUsedSSB[3] = 21385000
lastBandFreqUsedSSB[4] = 28385000
xMapLowAve1 = 600.96
xMapLowAve2 = 609.51
xMapLowAve3 = 644.70
xMapLowAve4 = 700.04
sidetoneVolume = 0.10
rxEqualizer[0] = 0
rxEqualizer[1] = 290
rxEqualizer[2] = 290
rxEqualizer[3] = 235
rxEqualizer[4] = 215
rxEqualizer[5] = 295
rxEqualizer[6] = 320
rxEqualizer[7] = 340
txEqualizer[0] = 260
txEqualizer[1] = 260
txEqualizer[2] = 260
txEqualizer[3] = 260
txEqualizer[4] = 260
txEqualizer[5] = 260
txEqualizer[6] = 260
txEqualizer[7] = 260
cwFilterDefaultIndex = 3
keyType = 0
ssbDefaultFilterIndex = 3
calSi5351CrystalFreq = 25007172
usbCarrier = 11996000
decoderToggle = 0
filterSkirts[8][0] = 500
filterSkirts[8][1] = 900
filterSkirts[9][0] = 100
filterSkirts[9][1] = 2200
yMapLowAve = 861.33
xMapHighAve = 299.86
yMapHighAve = 155.05
Jim KM4TXR
From: [email protected] <[email protected]> on behalf of jjpurdum via Groups.Io <jjpurdum@...>
Sent: Friday, March 15, 2019 9:49 PM To: [email protected] Subject: Re: [JackAl] 7" Display Drawing ?
Also record the values.
Jack, W8TEE
On Friday, March 15, 2019, 4:54:31 PM EDT, Rick Price <rickprice48@...> wrote:
Not in debug guess I could try that. The magic number was supposed to be at least 10 times around.? I gone as many as 15 and as
little as 6 or 7.? The average?numbers on the calibration screen are always under 5 with a few in the 2's and occasionally 1+.? Only one of the average?calibration numbers seems to be in the 4 or 5 region and never seems to get lower.? I'll go and do it again
and report back as to which number stays higher than the rest. In the words of someone more knowledgeable than me .......I have slept since the last time I did it.
?
Rick KN4AIE
From: [email protected] [mailto:[email protected]] On Behalf Of jjpurdum via Groups.Io Sent: Friday, March 15, 2019 4:37 PM To: [email protected] Subject: Re: [JackAl] 7" Display Drawing How many data points (trips around the display) do you make? If you're in the DEBUG mode, you should see the EEPROM values that are read back when the program starts. The call is around line 955 in
setup(). Are you seeing reasonable values for all of the values shown there, including the display offsets.
Jack, W8TEE
On Friday, March 15, 2019, 4:00:28 PM EDT, Rick Price <rickprice48@...> wrote:
Jack,
I have the same problems on a 5" screen.? Very sluggish at times to over responsive at others.? I have
calibrated using the setup option numerous times always the same results.? Frequency digit selection arrow buttons are only responsive at the left hand edge and sometimes will cause the cursor to jump 2 or 3 places.? Moving right is always harder then trying
to move the cursor?left.?When I do the selection the audio changes to a quieter tone for the time I am pushing on the button.? I did calibrate one time using an imaginary point to the right of the calibration points on the?left hand side of the screen(1st
two points)?and that did seem to help center the action better. Band selection is especially troublesome when I select 20.? 9 out of 10 times it will change to 15 and then I have to reselect 20. I am using a fiber stylus spudger tool ?to do the selections
and have tried the end retracted end of a ball point pen and a nylon tuning wand with the same results. Just more info FWIW.
?
Rick KN4AIE
From: [email protected] [mailto:[email protected]] On Behalf Of James Zdunic Sent: Friday, March 15, 2019 2:12 PM To: [email protected] Subject: Re: [JackAl] 7" Display Drawing I¡¯m running version 95 and did go through the setup/calibration routine contained in that version.
Jim KM4TXR
|
|
Re: 7" Display Drawing
James Zdunic
¿ªÔÆÌåÓýJack,
I could only get around the screen 7 times before the point ignored became unrelenting and I can¡¯t get past the point you see in the photo below...
Jim KM4TXR
|
|
Re: 7" Display Drawing
Also record the values. Jack, W8TEE
On Friday, March 15, 2019, 4:54:31 PM EDT, Rick Price <rickprice48@...> wrote:
Not in debug guess I could try that. The magic number was
supposed to be at least 10 times around.? I gone as many as 15 and as
little as 6 or 7.? The average?numbers on the calibration screen are
always under 5 with a few in the 2's and occasionally 1+.? Only one of the
average?calibration numbers seems to be in the 4 or 5 region and never
seems to get lower.? I'll go and do it again and report back as to which
number stays higher than the rest. In the words of someone more knowledgeable
than me .......I have slept since the last time I did it.
?
Rick KN4AIE From: [email protected] [mailto:[email protected]] On Behalf Of jjpurdum via Groups.Io Sent: Friday, March 15, 2019 4:37 PM To: [email protected] Subject: Re: [JackAl] 7" Display Drawing How many data points (trips around the display) do you make? If you're in
the DEBUG mode, you should see the EEPROM values that are read back when the
program starts. The call is around line 955 in setup(). Are you seeing
reasonable values for all of the values shown there, including the display
offsets.
Jack, W8TEE
On Friday, March 15, 2019, 4:00:28 PM EDT, Rick Price
<rickprice48@...> wrote:
Jack,
I have the same problems on a 5" screen.? Very sluggish at times
to over responsive at others.? I have calibrated using the setup option
numerous times always the same results.? Frequency digit selection arrow
buttons are only responsive at the left hand edge and sometimes will cause the
cursor to jump 2 or 3 places.? Moving right is always harder then trying to
move the cursor?left.?When I do the selection the audio changes to a
quieter tone for the time I am pushing on the button.? I did calibrate one
time using an imaginary point to the right of the calibration points on
the?left hand side of the screen(1st two points)?and that did seem to
help center the action better. Band selection is especially troublesome when I
select 20.? 9 out of 10 times it will change to 15 and then I have to
reselect 20. I am using a fiber stylus spudger tool ?to do the selections
and have tried the end retracted end of a ball point pen and a nylon tuning wand
with the same results. Just more info FWIW.
?
Rick KN4AIE From: [email protected] [mailto:[email protected]] On Behalf Of James Zdunic Sent: Friday, March 15, 2019 2:12 PM To: [email protected] Subject: Re: [JackAl] 7" Display Drawing I¡¯m running version 95 and did go through the setup/calibration routine
contained in that version.
Jim KM4TXR
|
|
Re: J3 display connector
¿ªÔÆÌåÓýthat must be the 7" display as it is different then my 5" dave
On 3/15/2019 10:02 AM, Vince Loschiavo
wrote:
Correct pin 9 is not used. |
|
Pressed the wrong button!
No. Look at line #4 in the JackAl.h header file: #define DEBUG??????????????? // Comment out when not debugging If you want to debug stuff, leave as it is above. When you're done debugging, change it to: // #define DEBUG??????????????? // Comment out when not debugging Placing the two comment lines at the front removes the DEBUG symbolic constant from the program once you recompile the code. So what? Look at line 927 at the top of setup(): #ifdef DEBUG ? Serial.begin(115200); #endif and line 955: #ifdef DEBUG ? ShowEEPROMValues(); #endif Now think about what these say: If the symbolic constant named DEBUG is defined in the program (in the JackAl.h header file), the code at line 927 in setup() says to instantiate the Serial monitor, which is your primary tool for debugging a program in the Arduino IDE. About thirty lines later, if you're in the DEBUG mode, you will see the ShowEEPROMValues() call displays all of the data that is stored in EEPROM. There are a number of other "hidden" debug calls throughout the program. Likewise, if DEBUG is NOT defined, no Serial object is instantiated and all of the debug function calls are NOT compiled into the program. This technique is called "scaffolding". It allows you to keep debugging stuff in the program, but without bloating the code when you're not debugging. Jack, W8TEE
On Friday, March 15, 2019, 4:47:56 PM EDT, James Zdunic <james_zdunic@...> wrote:
Jack,
Sorry Arduino newby here...
When you say debug mode do you mean running the IDE while the CPU is connected to the PC? ?And if so is it the serial monitor where you would see these values reported, or is there a separate debug function...?
Jim KM4TXR
|
jjpurdum