¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: New tinySA.exe uploaded

 

Hard to get a true "Maple Mini" now:??
I assume the blue pill clone would do.??

A $2 CH340 Nano ATMega328P clone should work fine as a 3.3v processor.
Remove the SD101CWS diode so it doesn't get 5v from the USB connector.
Then apply 3.3v from an external supply to both the "5V" and "3V3" header pins.
No connection to the "VIN" pin.? Exceeds spec at 16mhz for an ATMega328P with 3.3v,
but reports are it works fine.? (The CH340 chip also works down to 3.3v on VCC.)
? ??

The "teensy" line from PJRC is nice if you want to spend $20.

But I'm still going for the $5 RPi-Zero running Raspbian linux.?
Almost as small as any of the above, orders of magnitude more memory,
easy to use the SPI IO pins, can show plots on an HDMI display if you wish.

Jerry, KE7ER


On Wed, Jan 29, 2020 at 11:07 AM, <erik@...> wrote:
I'm using a protoneer arduino nano footprint compatible STM32F1xx. Overkill for the tinySA
Suggest to use a maple mini


Re: New tinySA.exe uploaded

 

I'm using a protoneer arduino nano footprint compatible STM32F1xx. Overkill for the tinySA
Suggest to use a maple mini

--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK


Re: New tinySA.exe problem

 

On Wed, Jan 29, 2020 at 08:38 AM, wb6ogd wrote:
Next question is about the automatic markers..
Sometimes they don't pick the strongest signal, sometimes they miss the "fundamental" big sig...
In the newest tinySA.exe there are some settings on the settings panel related to the peak search algorithm
?
--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK


Re: New tinySA.exe problem

 

Agree, maple mini!
--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK


Re: New tinySA.exe problem

 

I would search for Maple Mini. Lower cost and better performance, plus more I/O pins.

Ion
VA3NOI


--
Ion
VA3NOI


Re: New tinySA.exe problem

Dan Reynolds
 

Speaking of which - are the Arduino Zero "clones" OK Erik? I was looking at one on eBay called the ...
--
Dan Reynolds - KB9JLO


Re: New tinySA.exe uploaded

 

Jerry,
I first raised the question of shared TX/RX back in post #720.
Erik's code is very portable, you just re-assign pins (mostly) as you would like.

I am having really good results now with my cheap 5V Nano clone ($3.50).
I don't have a display or encoder yet but enabling the compile options shows even Erik's latest with big
touch display will fit (at 97% program memory, 72% dynamic memory).
73,
Gary
WB6OGD


Re: New tinySA.exe problem

 

OOPS.. sorry Erik.
Somehow MIN had got set as my default, even when I changed it, next time it kept coming back.
I thought yeah, ok Minimum averaging, why not..? doh..

Next question is about the automatic markers..
Sometimes they don't pick the strongest signal, sometimes they miss the "fundamental" big sig...

Now Nano(CH340G) is working fine..? BUFFERSIZE 32, Speed (in Settings) set to 0.

73,
Gary
WB6OGD


Re: New tinySA.exe uploaded

 

It's probably in some forum post somewhere, but nothing in
either tinySA.ino or in the BuildInstructions states what Arduino you are using.
Only says it is 3.3v

Arduino compatible stuff is all over the map.
Once you get beyond blinky lights, the exact module should be specified
for repeatable results.

Jerry, KE7ER


On Tue, Jan 28, 2020 at 11:42 PM, <erik@...> wrote:
On Tue, Jan 28, 2020 at 01:00 PM, Jerry Gaffke wrote:
The Arduino board you are using might be significantly different from a Nano.
I am using a STM32F1 on a nano compatible board so yes, substantially different!!

Question 1:
Why have an extra RAM buffer for outgoing Serial data to make it go out as larger packets?
I"m not using Serial but SerialUSB (see #define at the top of the code). SerialUSB send every print or printnl as a separate USB transfer which incurs substantial overhead

Question 2:
With Nano pin D0 defined as SI_nSEL[0] and Nano pin D1 defined as SI_SCLK,
doesn't that conflict with the use of those pins as TX and RX for UART traffic to the CH340? USB bridge chip?
Again, I'm NOT using a nano so no problem for me


Re: New tinySA.exe uploaded

 

I use the web interface exclusively, and often read by topic.
This topic has 28 messages, (now 29).

With no history at the bottom of your posts
it's occasionally tough to tell what you are responding to.

Jerry, KE7ER


On Tue, Jan 28, 2020 at 11:45 PM, <erik@...> wrote:
On Tue, Jan 28, 2020 at 12:34 PM, Jerry Gaffke wrote:
And no clue what post you are responding to.
Jerry,
If you go to?/g/HBTE/topics?you can see the posts grouped in threads so they make sense
?
--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK


Re: New tinySA.exe uploaded

 

On Tue, Jan 28, 2020 at 12:34 PM, Jerry Gaffke wrote:
And no clue what post you are responding to.
Jerry,
If you go to?/g/HBTE/topics?you can see the posts grouped in threads so they make sense
?
--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK


Re: New tinySA.exe uploaded

 

On Tue, Jan 28, 2020 at 01:00 PM, Jerry Gaffke wrote:
The Arduino board you are using might be significantly different from a Nano.
I am using a STM32F1 on a nano compatible board so yes, substantially different!!

Question 1:
Why have an extra RAM buffer for outgoing Serial data to make it go out as larger packets?
I"m not using Serial but SerialUSB (see #define at the top of the code). SerialUSB send every print or printnl as a separate USB transfer which incurs substantial overhead

Question 2:
With Nano pin D0 defined as SI_nSEL[0] and Nano pin D1 defined as SI_SCLK,
doesn't that conflict with the use of those pins as TX and RX for UART traffic to the CH340? USB bridge chip?
Again, I'm NOT using a nano so no problem for me

?
--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK


Re: New tinySA.exe problem

 

ATTENTION!!!!!!

The setting "min" in Average means "minimum hold" !!!!!!!!!!!!!!!!!

Never use this unless you know what you are doing.
Always start with Averaging off

The "minimum hold" is automatically reset when you change anything in the scan parameters but NOT if you change only the input signal

--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK


Re: New tinySA.exe problem

 

Erik,
Hopefully the attachment is visible.. first time I tried this on this group...
I am doing Single sweeps, Avg set to Min so I do a few.
I start with a 10MHz signal, sweep it, then change it to 11MHz, sweep it several
times, 11MHz doesn't show up.
Then I change the attenuator setting and do sweeps.. Now 11MHz shows up.
Wierd.
I think I may need to get a Zero and start over...
73,
Gary
WB6OGD


Re: New tinySA.exe uploaded

 

Jerry,
I changed a number of pin assignments for the Nano, to make the code work:

//DB2OO, 18.1.20----------------------------------------------------------
/***
* PIN Connections Arduino Nano:
* Encoder:
* int R_pinEncA=D3;
* int R_pinEncB=D2;
* NANO: const int buttonPin = 8--> 11; // the number of the pushbutton pin
* NANO const int backButtonPin = 9 --> 12;
* NANO: const int buttonPin = D0; // the number of the pushbutton pin
* NANO const int backButtonPin = SD3;
* Display:
* NANO: A4, A5 for SDA, SCL for I2C
* ESP8266: D1, D2 for I2C
*
* SI4432:
* nSEL for TX=D5, RX=D7, ??=11, ??=12
* const int SI_nSEL[2] = { 7,8, 11, 12 };
* const int SI_SCLK = 6 ;
* NANO: const int SI_SDI = 2 --> 9?
* NANO: const int SI_SDO = 3 --> 10;?
* ESP8266: const int SI_SDI = SD1 ; --> WILL NEED A CHANGE
* ESP8266: const int SI_SDO = SD2; --> will need a change
*
* Attenuator:
* #ifdef PE4302_serial
* Clock and data pints are shared with SI4432
* Serial mode LE pin
* #define PE4302_en 10
* #else
* Parallel mode bit 0 pin number, according below line the PE4302 is connected to lines A0,A1,A2,A3,A4,A5
* #define PE4302_pinbase A0
* #endif
*
* LED, that blinks during data transfer
* #if defined(ARDUINO_ARCH_SAMD)
* #define tinySA_led 13
* #else
* #define tinySA_led LED_BUILTIN
* #endif
/
BTW: I have no PE4302 connected and have put those code sections into #ifdef's. On the Nano D2 and D3 should be kept available for the encoder, as they support interrupts. Moreover I did not yet test on an ESP8266, which unfortunately does not have enough IOs, to support display and encoder.
--
Joerg, ex-DB2OO


Re: New tinySA.exe uploaded

 

Erik,?

If you were referring to one of my posts, the primary questions I have
are in regard to running the Jan 17 version of tinySA.ino on the Nano.
The Arduino board you are using might be significantly different from a Nano.

Question 1:
Why have an extra RAM buffer for outgoing Serial data to make it go out as larger packets?
The Serial library already has a significant RAM buffer (perhaps 64 bytes?).
If the Serial library falls behind, then the bytes will accumulate in that RAM buffer
and go out as a larger burst anyway.? The USB interface is likely much faster than
the 115.2kbaud UART link from ATMega328P to the CH340 bridge chip anyway.

Question 2:
With Nano pin D0 defined as SI_nSEL[0] and Nano pin D1 defined as SI_SCLK,
doesn't that conflict with the use of those pins as TX and RX for UART traffic to the CH340? USB bridge chip?

Jerry, KE7ER





On Tue, Jan 28, 2020 at 12:34 PM, Jerry Gaffke wrote:
And no clue what post you are responding to.


Hide quoted text

?

On Tue, Jan 28, 2020 at 12:03 PM, <erik@...> wrote:
No clue what you are asking?
--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK


Re: New tinySA.exe uploaded

 

A few notes on Nano IO pins as coded up in tinySA.ino as posted on Jan 17, 2020


The SPI CLK pin is defined to be at D1 in tinySA.ino:
? ??const int SI_SCLK = 1 ;
But on the Nano at least, D1 also gets used as the UART TX pin to transfer serial data
from the ATMega328P over to the CH340 USB chip.

I find it hard to believe that the Nano works at all with the code of tinySA.ino.
Am I missing something?
Perhaps the UART receiver in the CH340 manages to mostly ignore all that toggling
because it is not at the correct baud rate?
Note that Erik is not using the Nano.

Likewise, SI_nSEL[0] is at pin D0, which conflicts the UART RX pin, used to receive
UART data coming back from the CH340 into the ATMega328P.
How does this work at all?

I would think that for the Nano we should move the three dedicated SPI pins in tinySA.ino
<? ?const int SI_SCLK = 1 ;
<? ?const int SI_SDI = 2 ;
<? ?const int SI_SDO = 3 ;
over to the hardware SPI pins at D11,D12,D13
>? ?const int SI_SCLK = 13 ;? ? ? // SCLK
>? ?const int SI_SDI = 12 ;? ? ? ? ?// MISO
>? ?const int SI_SDO = 11 ;? ? ? ?// MOSI
That way we can use the much faster SPI hardware of the Nano, instead of bit-banging IO pins.

The nSEL pins can be any digital output except D0,D1.
I'd probably go with D9 and D10, keep all the SPI pins together.

The names SI_SDI and SI_SDO might be a bit confusing to some.
SI_SDI is configured as an output, goes to the Si4432 input pin, a better name might be SPI_MOSI (master-out-slave in).
SI_SDO is configured as an input, goes to the Si4432 output pin, a better name might be SPI_MISO (master in slave out).




Here's the current pin assignments in tinySA.ino as of the Jan 17 file:

########################
int R_pinEncA=7;
int R_pinEncB=6;
const int SI_nSEL[4] = { 0,5, 11, 12 }; // #4 is dummy!!!!!!
const int SI_SCLK = 1 ;
const int SI_SDI = 2 ;
const int SI_SDO = 3 ;
const int SI_GPIO = 4 ;
const int buttonPin = 8;? ? // the number of the pushbutton pin
const int backButtonPin = 9;
#define PE4302_en 10
pinMode(13, OUTPUT);
#define ATTBASE A0
? for (int i=0; i<6; i++) pinMode(i+ATTBASE, OUTPUT);? ? ? ? ? // Setup attenuator at D6 - D11
##########################

And a few notes:

Only SI_nSEL[0] and SI_nSEL[1]? at D0 and D5 get used, the other two entries in the SI_nSEL[] array are ignored.
As stated previously, the SI_nSEL[0] at D0 conflicts with the RX UART pin, at least on the Nano.

Most of us are not using the Button or Enc pins.

With ATTBASE=A0, the parallel attenuator pins are at pins A0-5,? not at D6-11 as per the comment
Most of us are not using these parallel attenuator pins.
The SPI interface into the PE4302 attenuator uses only one additional pin, PE4302_EN at D10, and so might be a better choice.
The A0-5 pins can be used as digital IO or as analog input pins, but A6,A7 can only be used as analog input pins on the Nano's ATMega328P chip.

The code initializes the SI_GPIO pin at D4 with:
? ? pinMode(SI_GPIO, INPUT_PULLUP);
but this pin is not otherwise used.

The code initializes D13 as an output:
? ??pinMode(13, OUTPUT);
but this pin is not otherwise used.

There are other references in the code to GPIO pins, but these are on the Si4432 chips
and controlled through SPI registers.? ?These are not pins on the Nano:

// GPIO automatic antenna switching
? SI4432_Write_Byte(0x0B, 0x12) ;
? SI4432_Write_Byte(0x0C, 0x15) ;
}

?SI4432_Write_Byte(0x0D, 0x1F) ; // Set GPIO2 output to ground


Jerry, KE7ER


Re: New tinySA.exe uploaded

 

And no clue what post you are responding to.


On Tue, Jan 28, 2020 at 12:03 PM, <erik@...> wrote:
No clue what you are asking?
--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK


Re: ADE25MH Mixer - warning #tinysa

 

I tested with 6dB attenuators at LO and RF gates, did not see any difference
--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK


Re: New tinySA.exe uploaded

 

No clue what you are asking?
--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK