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
On Mar 15, 2019, at 4:37 PM, jjpurdum via Groups.Io < jjpurdum@...> wrote:
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
I¡¯m running version 95 and did go through the setup/calibration routine contained in that version.
Jim KM4TXR
On Mar 15, 2019, at 2:10 PM, jjpurdum via Groups.Io < jjpurdum@...> wrote:
Have you run the new software calibration routine?
Jack, W8TEE
On ?Friday?, ?March? ?15?, ?2019? ?02?:?05?:?52? ?PM? ?EDT, James Zdunic < james_zdunic@...> wrote:
Hello Vince,
I¡¯d be curious to how the touch response performance is on your 7¡± display after doing the calibration? ?Reason being my 7¡± screen touch response is inaccurate with adjacent buttons as well as distant buttons being activated at random times. ?Also having
issues with the touch response stopping completely requiring a reboot of the system to make it respond again. ?I¡¯m trying to determine if my screen has issues or if it could be something else going on.
Jim KM4TXR
On Mar 15, 2019, at 12:54 PM, Vince Loschiavo < vince320@...> wrote:
mine came up perfect first time..(once i got it to come up....)
vince
n2aie
|
jjpurdum