So, when you have the program's baud rate at 115200 and the Serial monitor at 9600, you get the proper output on the Serial monitor?

Jack, W8TEE

On Saturday, May 11, 2019, 4:02:26 PM EDT, Ronald Pfeiffer <w2ctx@...> wrote:

I was addressing the serial monitor only.

Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------

From: "jjpurdum via Groups.Io" <jjpurdum@...>

Date: 5/11/19 3:36 PM (GMT-05:00)

To: [email protected]

Subject: Re: [JackAl] touch screen

If the Teensy always uses 12mbs, but the USB port is set to some other speed, are you saying that the Teensy automatically adjusts to the USB baud rate? Also, there's a difference between communicating with the Arduino IDE using a Teensy baord and the PC at the same baud rate and the Teensy running standalone and using one of its ports. That I can agree with, but I do not think that's true when working with the IDE. All of Dave's questions are relative to compilation processes.

Jack, W8TEE

??? On Saturday, May 11, 2019, 2:34:56 PM EDT, Ronald Pfeiffer <w2ctx@...> wrote:

From Teensy pages:
"Unlike a standard Arduino, the Teensy Serial object always communicates at 12 Mbit/sec USB speed. "

So it doesn't seem to matter what you set the baud rate in the program or what is set in
the Serial Monitor!? The Teensy serial ports understand each other....


> On May 11, 2019 at 2:07 PM k7da <k7da@...> wrote:
>
>
> ok i'll except that.
>
> but puzzle this.? i set the baud rate at the setup to 9600 and forgot to
> reset the monitor baud rate and the thing works now when it show 115200.
>
> explain
>
> but i done show the eeprom dump on the monitor?
>
>
> dave
>
> On 5/11/2019 11:03 AM, jjpurdum via Groups.Io wrote:
> > Aw, come on...first mistake since the late 60's, and a fat-finger one
> > at that.
> >
> > Jack, W8TEE
> >
> > On Saturday, May 11, 2019, 1:46:23 PM EDT, k7da <k7da@...> wrote:
> >
> >
> > could it by chance be 115200.
> >
> > copied from the jackal.h
> >
> >
> > #ifndef BEENHERE
> > #define BEENHERE
> >
> > #define DEBUG??????????????? // Comment out when not debugging
> >
> > //#define JACK???????????????? // Jack's 5" display stuff
> > #define AL????????????????? // Al's 5" display stuff
> > //#define JACK7?????????????? // Jack's 7" stuff
> > //#define AL7???????????????? // Al's 7" stuff
> >
> > #include <Arduino.h>????????? // Standard with IDE
> > #include <EEPROM.h>?????????? // EEPROM distributed with Teensy libraries
> > #include <math.h>???????????? // Standard with IDE
> > #include <Wire.h>???????????? // Standard with IDE
> > #include <SPI.h>????????????? // Standard with IDE
> > #include <stdio.h>??????????? // Standard with IDE
> >
> > On 5/11/2019 6:07 AM, jjpurdum via Groups.Io wrote:
> > Ports 0 and 1 are normally the Serial monitor ports for COM when the
> > board is running your code, but the programming port is something
> > else. The only thing I can think of is that the DEBUG flag isn't set
> > at the top of the JackAl.h header file, or there's a mismatch between
> > your monitor's baud rate and JackAl, which is set to 155200.
> >
> > Jack, W8TEE
> >
> > On Saturday, May 11, 2019, 12:26:05 AM EDT, k7da <k7da@...>
> > <mailto:k7da@...> wrote:
> >
> >
> > for some reason i am having trouble with the serial monitor.? when i
> > load the program it shows it is using port 1.? but if i watch when
> > connecting the usb cable it shows that i am using port 5.? but in
> > either case i get nothing on the serial monitor.
> >
> > i thought that maybe something was wrong with something in the
> > computer so i tried using things to load a program into a nano card
> > and thing worked fine. it was using port 6
> >
> > anyone have an idea what is happening?
> >
> > dave k7da
> >
> >
> >
>
>
>

On May 11, 2019 at 4:31 PM "jjpurdum via Groups.Io" <jjpurdum@...> wrote:


So, when you have the program's baud rate at 115200 and the Serial monitor at 9600, you get the proper output on the Serial monitor?
Jack, W8TEE

On Saturday, May 11, 2019, 4:02:26 PM EDT, Ronald Pfeiffer <w2ctx@...> wrote:

I was addressing the serial monitor only.


Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: "jjpurdum via Groups.Io" <jjpurdum@...> Date: 5/11/19 3:36 PM (GMT-05:00) To: [email protected] Subject: Re: [JackAl] touch screen
If the Teensy always uses 12mbs, but the USB port is set to some other speed, are you saying that the Teensy automatically adjusts to the USB baud rate? Also, there's a difference between communicating with the Arduino IDE using a Teensy baord and the PC at the same baud rate and the Teensy running standalone and using one of its ports. That I can agree with, but I do not think that's true when working with the IDE. All of Dave's questions are relative to compilation processes.

Jack, W8TEE

??? On Saturday, May 11, 2019, 2:34:56 PM EDT, Ronald Pfeiffer <w2ctx@...> wrote:

From Teensy pages:
"Unlike a standard Arduino, the Teensy Serial object always communicates at 12 Mbit/sec USB speed. "

So it doesn't seem to matter what you set the baud rate in the program or what is set in
the Serial Monitor!? The Teensy serial ports understand each other....

On May 11, 2019 at 2:07 PM k7da <k7da@...> wrote:


ok i'll except that.

but puzzle this.? i set the baud rate at the setup to 9600 and forgot to
reset the monitor baud rate and the thing works now when it show 115200.

explain

but i done show the eeprom dump on the monitor?


dave

On 5/11/2019 11:03 AM, jjpurdum via Groups.Io wrote:

Aw, come on...first mistake since the late 60's, and a fat-finger one
at that.

Jack, W8TEE

On Saturday, May 11, 2019, 1:46:23 PM EDT, k7da <k7da@...> wrote:


could it by chance be 115200.

copied from the jackal.h


#ifndef BEENHERE
#define BEENHERE

#define DEBUG??????????????? // Comment out when not debugging

//#define JACK???????????????? // Jack's 5" display stuff
#define AL????????????????? // Al's 5" display stuff
//#define JACK7?????????????? // Jack's 7" stuff
//#define AL7???????????????? // Al's 7" stuff

#include <Arduino.h>????????? // Standard with IDE
#include <EEPROM.h>?????????? // EEPROM distributed with Teensy libraries
#include <math.h>???????????? // Standard with IDE
#include <Wire.h>???????????? // Standard with IDE
#include <SPI.h>????????????? // Standard with IDE
#include <stdio.h>??????????? // Standard with IDE

On 5/11/2019 6:07 AM, jjpurdum via Groups.Io wrote:
Ports 0 and 1 are normally the Serial monitor ports for COM when the
board is running your code, but the programming port is something
else. The only thing I can think of is that the DEBUG flag isn't set
at the top of the JackAl.h header file, or there's a mismatch between
your monitor's baud rate and JackAl, which is set to 155200.

Jack, W8TEE

On Saturday, May 11, 2019, 12:26:05 AM EDT, k7da <k7da@...>
<mailto:k7da@...> wrote:


for some reason i am having trouble with the serial monitor.? when i
load the program it shows it is using port 1.? but if i watch when
connecting the usb cable it shows that i am using port 5.? but in
either case i get nothing on the serial monitor.

i thought that maybe something was wrong with something in the
computer so i tried using things to load a program into a nano card
and thing worked fine. it was using port 6

anyone have an idea what is happening?

dave k7da

On May 11, 2019 at 4:31 PM "jjpurdum via Groups.Io" <jjpurdum@...> wrote:


So, when you have the program's baud rate at 115200 and the Serial monitor at 9600, you get the proper output on the Serial monitor?
Jack, W8TEE

On Saturday, May 11, 2019, 4:02:26 PM EDT, Ronald Pfeiffer <w2ctx@...> wrote:

I was addressing the serial monitor only.


Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: "jjpurdum via Groups.Io" <jjpurdum@...> Date: 5/11/19 3:36 PM (GMT-05:00) To: [email protected] Subject: Re: [JackAl] touch screen
If the Teensy always uses 12mbs, but the USB port is set to some other speed, are you saying that the Teensy automatically adjusts to the USB baud rate? Also, there's a difference between communicating with the Arduino IDE using a Teensy baord and the PC at the same baud rate and the Teensy running standalone and using one of its ports. That I can agree with, but I do not think that's true when working with the IDE. All of Dave's questions are relative to compilation processes.

Jack, W8TEE

??? On Saturday, May 11, 2019, 2:34:56 PM EDT, Ronald Pfeiffer <w2ctx@...> wrote:

From Teensy pages:
"Unlike a standard Arduino, the Teensy Serial object always communicates at 12 Mbit/sec USB speed. "

So it doesn't seem to matter what you set the baud rate in the program or what is set in
the Serial Monitor!? The Teensy serial ports understand each other....

On May 11, 2019 at 2:07 PM k7da <k7da@...> wrote:


ok i'll except that.

but puzzle this.? i set the baud rate at the setup to 9600 and forgot to
reset the monitor baud rate and the thing works now when it show 115200.

explain

but i done show the eeprom dump on the monitor?


dave

On 5/11/2019 11:03 AM, jjpurdum via Groups.Io wrote:

Aw, come on...first mistake since the late 60's, and a fat-finger one
at that.

Jack, W8TEE

On Saturday, May 11, 2019, 1:46:23 PM EDT, k7da <k7da@...> wrote:


could it by chance be 115200.

copied from the jackal.h


#ifndef BEENHERE
#define BEENHERE

#define DEBUG??????????????? // Comment out when not debugging

//#define JACK???????????????? // Jack's 5" display stuff
#define AL????????????????? // Al's 5" display stuff
//#define JACK7?????????????? // Jack's 7" stuff
//#define AL7???????????????? // Al's 7" stuff

#include <Arduino.h>????????? // Standard with IDE
#include <EEPROM.h>?????????? // EEPROM distributed with Teensy libraries
#include <math.h>???????????? // Standard with IDE
#include <Wire.h>???????????? // Standard with IDE
#include <SPI.h>????????????? // Standard with IDE
#include <stdio.h>??????????? // Standard with IDE

On 5/11/2019 6:07 AM, jjpurdum via Groups.Io wrote:
Ports 0 and 1 are normally the Serial monitor ports for COM when the
board is running your code, but the programming port is something
else. The only thing I can think of is that the DEBUG flag isn't set
at the top of the JackAl.h header file, or there's a mismatch between
your monitor's baud rate and JackAl, which is set to 155200.

Jack, W8TEE

On Saturday, May 11, 2019, 12:26:05 AM EDT, k7da <k7da@...>
<mailto:k7da@...> wrote:


for some reason i am having trouble with the serial monitor.? when i
load the program it shows it is using port 1.? but if i watch when
connecting the usb cable it shows that i am using port 5.? but in
either case i get nothing on the serial monitor.

i thought that maybe something was wrong with something in the
computer so i tried using things to load a program into a nano card
and thing worked fine. it was using port 6

anyone have an idea what is happening?

dave k7da

If you look around line 952 in JackAl.ino, you'll see:

#ifdef DEBUG
? Serial.begin(115200);
#endif

so there's no need for you to be messing with the baud rate in setup(). If you set your baud rate to something different, it's like your program is speaking Mandarin and the Serial monitor is speaking English. If you don't have the DEBUG flag set, the Serial monitor isn't even turned on.

"but i done show the eeprom dump on the monitor?"

I don't even know what that means.

Jack, W8TEE

On Saturday, May 11, 2019, 2:07:57 PM EDT, k7da <k7da@...> wrote:

ok i'll except that.

but puzzle this.? i set the baud rate at the setup to 9600 and forgot to reset the monitor baud rate and the thing works now when it show 115200.

explain

but i done show the eeprom dump on the monitor?

dave

On 5/11/2019 11:03 AM, jjpurdum via Groups.Io wrote:

On May 11, 2019 at 2:07 PM k7da <k7da@...> wrote:


ok i'll except that.

but puzzle this.? i set the baud rate at the setup to 9600 and forgot to
reset the monitor baud rate and the thing works now when it show 115200.

explain

but i done show the eeprom dump on the monitor?


dave

On 5/11/2019 11:03 AM, jjpurdum via Groups.Io wrote:

Aw, come on...first mistake since the late 60's, and a fat-finger one
at that.

Jack, W8TEE

On Saturday, May 11, 2019, 1:46:23 PM EDT, k7da <k7da@...> wrote:


could it by chance be 115200.

copied from the jackal.h


#ifndef BEENHERE
#define BEENHERE

#define DEBUG??????????????? // Comment out when not debugging

//#define JACK???????????????? // Jack's 5" display stuff
#define AL????????????????? // Al's 5" display stuff
//#define JACK7?????????????? // Jack's 7" stuff
//#define AL7???????????????? // Al's 7" stuff

#include <Arduino.h>????????? // Standard with IDE
#include <EEPROM.h>?????????? // EEPROM distributed with Teensy libraries
#include <math.h>???????????? // Standard with IDE
#include <Wire.h>???????????? // Standard with IDE
#include <SPI.h>????????????? // Standard with IDE
#include <stdio.h>??????????? // Standard with IDE

On 5/11/2019 6:07 AM, jjpurdum via Groups.Io wrote:
Ports 0 and 1 are normally the Serial monitor ports for COM when the
board is running your code, but the programming port is something
else. The only thing I can think of is that the DEBUG flag isn't set
at the top of the JackAl.h header file, or there's a mismatch between
your monitor's baud rate and JackAl, which is set to 155200.

Jack, W8TEE

On Saturday, May 11, 2019, 12:26:05 AM EDT, k7da <k7da@...>
<mailto:k7da@...> wrote:


for some reason i am having trouble with the serial monitor.? when i
load the program it shows it is using port 1.? but if i watch when
connecting the usb cable it shows that i am using port 5.? but in
either case i get nothing on the serial monitor.

i thought that maybe something was wrong with something in the
computer so i tried using things to load a program into a nano card
and thing worked fine. it was using port 6

anyone have an idea what is happening?

dave k7da

Aw, come on...first mistake since the late 60's, and a fat-finger one at that.

Jack, W8TEE

On Saturday, May 11, 2019, 1:46:23 PM EDT, k7da <k7da@...> wrote:

could it by chance be 115200.

copied from the jackal.h

#ifndef BEENHERE
#define BEENHERE

#define DEBUG??????????????? // Comment out when not debugging

//#define JACK???????????????? // Jack's 5" display stuff
#define AL????????????????? // Al's 5" display stuff
//#define JACK7?????????????? // Jack's 7" stuff
//#define AL7???????????????? // Al's 7" stuff

#include <Arduino.h>????????? // Standard with IDE
#include <EEPROM.h>?????????? // EEPROM distributed with Teensy libraries
#include <math.h>???????????? // Standard with IDE
#include <Wire.h>???????????? // Standard with IDE
#include <SPI.h>????????????? // Standard with IDE
#include <stdio.h>??????????? // Standard with IDE

On 5/11/2019 6:07 AM, jjpurdum via Groups.Io wrote:

Ports 0 and 1 are normally the Serial monitor ports for COM when the board is running your code, but the programming port is something else. The only thing I can think of is that the DEBUG flag isn't set at the top of the JackAl.h header file, or there's a mismatch between your monitor's baud rate and JackAl, which is set to 155200.

Jack, W8TEE

On Saturday, May 11, 2019, 12:26:05 AM EDT, k7da <k7da@...> wrote:

for some reason i am having trouble with the serial monitor.? when i load the program it shows it is using port 1.? but if i watch when connecting the usb cable it shows that i am using port 5.? but in either case i get nothing on the serial monitor.

i thought that maybe something was wrong with something in the computer so i tried using things to load a program into a nano card and thing worked fine. it was using port 6

anyone have an idea what is happening?

dave k7da

Ports 0 and 1 are normally the Serial monitor ports for COM when the board is running your code, but the programming port is something else. The only thing I can think of is that the DEBUG flag isn't set at the top of the JackAl.h header file, or there's a mismatch between your monitor's baud rate and JackAl, which is set to 155200.

Jack, W8TEE

On Saturday, May 11, 2019, 12:26:05 AM EDT, k7da <k7da@...> wrote:

for some reason i am having trouble with the serial monitor.? when i load the program it shows it is using port 1.? but if i watch when connecting the usb cable it shows that i am using port 5.? but in either case i get nothing on the serial monitor.

i thought that maybe something was wrong with something in the computer so i tried using things to load a program into a nano card and thing worked fine. it was using port 6

anyone have an idea what is happening?

dave k7da

For some reason, it's beginning to sound like the EEPROM is not getting written to. See what the EEPROM debug functions return which I mention in another post.

Jack, W8TEE

On Thursday, May 9, 2019, 5:20:00 PM EDT, k7da <k7da@...> wrote:

attached is a screen shot of the radio in calibration mode.? 4 times around. ? checking again it appears that the touch part is compressed from both sides.? if i fiddle with it i can make most of the buttons work with some difficulty.

dave

On 5/9/2019 1:03 PM, jjpurdum via Groups.Io wrote:

The new calibration routine requires you to press firmly on each dot and will not let you move to the next one until it gets a good reading. You should do at least 3 "complete cycles around the screen" before you exit the calibration routine. After that's done the key values are stored in EEPROM and used on the next reboot.

Jack, W8TEE

On Thursday, May 9, 2019, 12:59:19 PM PDT, k7da <k7da@...> wrote:

should the calibration have taken that long or longer also with each step?

dave

On 5/9/2019 12:41 PM, jjpurdum via Groups.Io wrote:

No, it should respond in less than a second and all of those button should be active, so something's still amiss. What version of the software are you running?

Jack, W8TEE

On Thursday, May 9, 2019, 3:01:45 PM EDT, k7da <k7da@...> wrote:

jack or others that might have the answers

i got the touch screen to work( miswired) and ran the calibration

routine but now it appears that the calibration is not right. have run

the calibration several times with the same results.

the buttons do not respond as i thought they should.? if i press the

1800 key i get the 1500 instead.? the top line of red buttons do not

work at all.? the other side on the display seems to work though.

should the response time be 2-3 sec

thanks dave k7da