开云体育

Arv:

An if (DEBUG statement block will not cause scaffolding code to be excluded from a compile. I think what you mean is something like:

#define DEBUG????????????????????????// Place near the start of the code...

// ...a bunch of program code...

#ifdef DEBUG

Serial.print("val = ");

Serial.println(val);

#endif

// ...more program code...

Now, when you comment out the #define preprocessor directive, that scaffolding code block no longer appears in the compiled code. Uncomment the directive and it returns back into the compiled code. This makes for a great way to "toggle" debugging code into and out of a program with a single edit line, saving a lot of retyping.

Jack, W8TEE

On Sunday, May 16, 2021, 11:33:09 AM EDT, Arv Evans <arvid.evans@...> wrote:

Jerry

I strongly agree with you.? Code organization and functions that contain blocking

code are important and a PITA.? At present I am working on code for some test equipment (Arduino based) which involves a main loop that has some serious timing

constraints.? Slow operation in my initial code was fixed when I converted blocking routines to non-blocking and then spaced the slower sections equally around the

loop, taking care to duplicate critical routines so that they appear multiple times in

a single pass around the loop.

When I added timing discovery points it revealed what was slowing things down

and indicated just where things needed to be moved, deleted, or changed.? In the

process of timing discovery I almost made a real-time version of my code, but

not quite.? John helped me with scaffolding which allowed my DEBUG routines

to become "if DEBUG" so that a compile could include or not include the DEBUG

parts.? Thanks John.? That was a big help.

Some of the C++ based library calls in the Arduino IDE appear to be poorly

constructed for my particular needs.? This caused me to rewrite a few of these

calls.? I think the lesson here is that the Arduino libraries in the IDE should not

be taken as the sacred last word in how to do things.? If you need a special

function call, do not be afraid to write it yourself.? These type things can then

be included in your code and do not need to be formalized and stored as

a library.

Arv

_._

On Sun, May 16, 2021 at 8:23 AM Jerry Gaffke via <jgaffke=[email protected]> wrote:

I had that wrong.??
PARIS is 50 "dot elements", the spaces between the dots count as separate dot elements.
So 20wpm is a rising or falling edge every 1/16.66 = 60 milliseconds, not 30.

With properly organized code, a Nano should have no trouble keeping up.
However, reliably catching that first dot when the processor might be busy doing other stuff
probably does require an interrupt driven digital pin for the key.

Jerry, KE7ER


On Sun, May 16, 2021 at 06:25 AM, Jerry Gaffke wrote:

So 20wpm is 20*50/60 = 16.66 dots/sec, a rising or falling edge every 1/(2*16.66) = 30 milliseconds.

--
Jack, W8TEE

Jerry

I strongly agree with you.? Code organization and functions that contain blocking

code are important and a PITA.? At present I am working on code for some test equipment (Arduino based) which involves a main loop that has some serious timing

constraints.? Slow operation in my initial code was fixed when I converted blocking routines to non-blocking and then spaced the slower sections equally around the

loop, taking care to duplicate critical routines so that they appear multiple times in

a single pass around the loop.

When I added timing discovery points it revealed what was slowing things down

and indicated just where things needed to be moved, deleted, or changed.? In the

process of timing discovery I almost made a real-time version of my code, but

not quite.? John helped me with scaffolding which allowed my DEBUG routines

to become "if DEBUG" so that a compile could include or not include the DEBUG

parts.? Thanks John.? That was a big help.

Some of the C++ based library calls in the Arduino IDE appear to be poorly

constructed for my particular needs.? This caused me to rewrite a few of these

calls.? I think the lesson here is that the Arduino libraries in the IDE should not

be taken as the sacred last word in how to do things.? If you need a special

function call, do not be afraid to write it yourself.? These type things can then

be included in your code and do not need to be formalized and stored as

a library.

Arv

_._

On Sun, May 16, 2021 at 8:23 AM Jerry Gaffke via <jgaffke=[email protected]> wrote:

I had that wrong.??
PARIS is 50 "dot elements", the spaces between the dots count as separate dot elements.
So 20wpm is a rising or falling edge every 1/16.66 = 60 milliseconds, not 30.

With properly organized code, a Nano should have no trouble keeping up.
However, reliably catching that first dot when the processor might be busy doing other stuff
probably does require an interrupt driven digital pin for the key.

Jerry, KE7ER


On Sun, May 16, 2021 at 06:25 AM, Jerry Gaffke wrote:

So 20wpm is 20*50/60 = 16.66 dots/sec, a rising or falling edge every 1/(2*16.66) = 30 milliseconds.

Arv,
Here is a link to a company that produces the hardware and software to replace the v6 Raduino with one that is designed for the Teensy 4.1.?

They sold an adapter board for the pre v6 Raduino, however that has been discontinued. ??

The cost seems reasonable, considering it is not in high demand and the low volume of boards sold (assumed).? A good choice for someone who wants to experiment with things like DSP or other SW based additions to the uBITX.? The supplied code is open source and can be worked with the Arduino IDE.

73
Evan
AC9TU

If we were all the same, would it not be a VERY?dull world??

I had that wrong.??
PARIS is 50 "dot elements", the spaces between the dots count as separate dot elements.
So 20wpm is a rising or falling edge every 1/16.66 = 60 milliseconds, not 30.

With properly organized code, a Nano should have no trouble keeping up.
However, reliably catching that first dot when the processor might be busy doing other stuff
probably does require an interrupt driven digital pin for the key.

Jerry, KE7ER


On Sun, May 16, 2021 at 06:25 AM, Jerry Gaffke wrote:

So 20wpm is 20*50/60 = 16.66 dots/sec, a rising or falling edge every 1/(2*16.66) = 30 milliseconds.

Yes, using various voltage levels into an ADC was done
because of no remaining pins on the Nano.

Best to choose a processor with enough pins for the job
such as the RPi-Pico that Farhan has been looking at.

I believe the ATMega328P can sample the ADC at around 10khz.
Arv's suggestion of reading twice might solve the immediate problem for CW ops.

Could program the two UART pins RX and TX for use as digital inputs
to inspect the dot and dash paddle switches.? Going into CW mode would be handled
by a menu option, and would disallow CAT communications with a USB host.?
The analog pin could still be used for hand keys.?

Or go to an i2c LCD display, that frees up plenty of pins.

Jerry, KE7ER


On Sat, May 15, 2021 at 04:23 PM, Arv Evans wrote:

I am not a "CW Op"...barely able to walk and talk sometimes.? 8-)

?

I must admit that using voltage based switching via an ADC would

not be my first choice for generating CW.? The ADC in an AVR328

has "settling time" in its operation.? For my own use I usually read-

twice to ensure that the voltage reported is closer to reality.

?

The idea that the ADC may be reading CW state during transition

times sounds like a good one.? Possibly just making a slight change

to the threshold voltages between dit and dah could tame the

problem?

?

My guess is that in the initial software there was a shortage of digital

pins that could have been used to initiate a Dit or Dah.? Farhan may

be able to clarify that guess.?

?

There are several ways to "multiplex" functionality of digital pins on

the Arduino, so this could be something to look into if rewriting parts

of the Raduino software.? Back when the uBITX software was being

designed we did not have enough AVR328 experience to reuse

digital inputs for multiple purposes.?

?

Arv? K7HKL