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