Marty, email me and I'll send the zip files for the libraries.?
--
John P.
WA2FZW

John / Dave,

Thanks very much for the latest V1.3 file. Trying to compile the sketch and finding that I need to add several header files to make the compile work (I've tried adding them and then get into 'missing class' issues next). I've also had to add libraries that I think may not have been the correct ones (especially for WiFi).?

I guess the simpler question is: How is your project (and libraries) set up to make the compile clean such that I can load my ESP32??

Anything you can add to help me along on this will be greatly appreciated. I've had past compiles with the Protoneer go great once I got everything set up, but now with the ESP32 (WROOM) I have it's becoming a real Rubik's cube to set up. Again, anything so I can get to the same setup within the Arduino IDE will be greatly appreciated.?

73 de Marty, KN0CK

开云体育

Sorry Erik, this is time per point, not the whole sweep.? Apologies for not being accurate.? So for the 290 points (if Auto RBW and wide bandwidth) around? 210mS for the full sweep.

Dave

What is meant with "Sweep time"?
Total time for one full sweep?
Time for one point?
?
--
HBTE Files section:?/g/HBTE/files
Erik, PD0EK

On Wed, Apr 1, 2020 at 05:56 AM, "[email protected] Notification" <[email protected]> wrote:

including revised attenuator object to enable parallel versions to be used (requires additional IO expander hardware).

Actually, you can use the parallel attenuator without the PCF8574 GPIO expander but you'll need to?repurpose some of the GPIO pins we've reserved for future enhancements. They are listed in the post before this one.

You need a total of?6 pins for the attenuator. There are currently two un-assigned, so for example, you could use the?three?reserved for an encoder and the one reserved for the SD card chip select.

Glenn's PCB used the PCF8574.

?
--
John P.
WA2FZW

Hi Glenn.? Well done!

Interested to see your sweep time is much slower than the 720uS or so I see with no WiFi clients, around 780uS with a WiFi client.? Are you running the display at 40MHz?

73

Dave M0WID (should be working from home but easily distracted)

Hello,

This email message is a notification to let you know that the following files have been uploaded to the Files area of the [email protected] group.

• /Tiny Spectrum Analyzer/ESP32/tinySA_V1.3.zip

Uploaded By: m0wid <david.wilde@...>

Description:
Latest version of TinySA for ESP32. Includes basic operation and control via WiFi, faster sweep times, comments and tidy up by John WA2FZW, including revised attenuator object to enable parallel versions to be used (requires additional IO expander hardware). To use the WiFi you will need to modify the SSID and Password in TinySA.h to suit your router. Later this will be changed so it can be set easier. No doubt some bugs, and the layout of the web page needs some work. Please provide feedback. Good luck, 73, Dave M0WID

Cheers,
The Groups.io Team

Got mine up and running after dinner tonight. Using the PCB shown in another thread.

Using Sketch by Dave and John at moment on ESP32 Wrover.

Early days to see just well it performs.

Glenn
vk3pe

Marty et al, here are the pin assignments for the ESP-32:

?GPIO-0???????????????? SD_CS????????????? Reserved for SD card chip select
?GPIO-2???????????????? TFT_RST????????? TFT Reset; Could be set to -1 if using processor reset
?GPIO-2???????????????? tinySA_led???????? The on-board LED flashes on data transfer
?GPIO-4??????????????? ?SI_RX_CS???????? RX Si4432 Transceiver chip select
?GPIO-5???????????????? SI_TX__CS?????? TX Si4432 Transceiver chip select
?GPIO-12/MISO2?? TFT_MISO??????? Display data input (to processor)
?GPIO-13/MOSI2?? TFT_MOSI??????? Display data output (from processor)
?GPIO-14/CLK2????? TFT_SCLK?????? Display SPI clock
?GPIO-15??????????????? TFT_CS??????????? Display chip select
?GPIO-18/CLK?????? ?SI_SCLK???????? ?Transceiver & Attenuator SPI clock
?GPIO-19/MISO????? SI_SDO??????????? Transceiver & Attenuator SPI data in (to processor)
?GPIO-21/SDA??????? SDA???????????????? ?PCF8575 Data line (VK3PE Implementation only)
?GPIO-21/ATT_CS? ATT_CS?????????? Chip Select for the serial type attenuator
?GPIO-22/SCL???????? SCL????????????????? PCF8575 Clock line (VK3PE Implementation only)
?GPIO-23/MOSI?????? SI_SDI?????????????Transceiver & Attenuator SPI data out (from processor)
?GPIO-25???????????????? TFT_LED?????????Display backlight intensity (PWM)
?GPIO-26???????????????? TOUCH_CS???? Touch screen chip select (in TFT_eSPI library setup)
?GPIO-27?????????????? ? TFT_DC?????????? Display data/command select line
?GPIO-32??????????????? ?ENC_PB?????????? Reserved for encoder pushbutton switch
?GPIO-33????????????????????????????????????????? *** Available (was BACK_PB) ***
?GPIO-34??????????????? ?ENC_B???????????? Reserved for encoder pin "B" (input only pin)
?GPIO-35??????????????? ?ENC_A???????????? Reserved for encoder pin "A" (input only pin)
?RX0?????????????????????????????????????????????? ? USB Receive
?TX0???????????????????????????????????????????????? USB Transmit


The SD card and the encoder are not yet implemented. GPIO-21 has different assignments based on whether you are using the serial type attenuator or Glenn's implementation using a PCF8574 with the parallel type attenuator. To use the parallel type attenuator without the PCF8574, you'll have to re-assign some GPIO pins; you're on your own!

--
John P.
WA2FZW

Dave / John,

First off, as we're in these unprecedented times with this viscous flu (I refuse to give it credit of a name being the scourge on mankind that it is) I hope and pray that you're healthy and keeping the social distance between yourself and this project to less than 6 feet...anyone/anything else, 12 feet...I know I am. Please keep happy, healthy, and productive in the days ahead...Geeks like me have no problem with that.

I've scoured the '05 project and come up with the connections (I think) to the ESP32 I have from the code and here's what I'm finding (again, mine's a WROOM 32 with nothing fancy on it):

For the ILI9341 Display:
Function? ? ESP32 Pin
-------------------------------
TFT_DC = Pin 27
TFT_CS = Pin 15
TFT_MOSI = Pin 13
TFT_MISO = Pin 12
TFT_SCLK = Pin 14
TFT_RST = Pin 2
TFT_LED = Pin 25
TFT_CS = Pin 26

SI4432 Transceivers:
Function? ? ?ESP32 Pin
------------------------------
SI nSEL Tx = 4, 11
Si nSEL Rx = 5, 12
SI_CLK = Pin 18
SI_SDI = Pin 23
SI_SDO = Pin 19

...Eventually I'll add the attenuator, but that's for 'phase 2'.?

...So the question becomes...Did I get that right?? I'm trying to compare functions to what I have now on my breadboard that has the Protoneer on it and want to confirm all this before the 'BIG SWAP' happens. I plan to remove the working Protoneer from my setup because it's getting plugged into my PWB I designed and received from JLPCB (<AHEM> China) that I plan to uncork from its hermetically sealed package with <practically a space suit on> my own red-neck PPE and A LOT of sterile wipes handy. Please let me know if the above will work with my WROOM ESP32 with nothing fancy on it.

Again, many thanks again for your confirmation on the above - My 'phase 2' will be the above device instead of the Protoneer. I'm interested in the other's work - maybe I'll buckle and go that route, but for now I have the will to see my own PWB design since I have a fair amount of time in-between working from remote for the company.

Be safe, be happy, be healthy, and above all stay strong against the 'the storm'.

73 de Marty, KN0CK
??

On Mon, Mar 30, 2020 at 04:39 AM, m0wid wrote:

a new release is just one bug fix away

David's next release will include support for the VK3PE Version 1 PCB set which uses a PCF8574 GPIO expander between the processor and the attenuator (saves a few GPIO pins for future enhancements).

I don't know if anyone has ordered?Glenn's PCB (actually, I'm not sure he's even published the Gerbers for it), but we have found a couple of errors on the board. Simplest to fix is that he flip-flopped the CS pins for the RX and TX Si4432 modules; just flip-flop them in the code to fix that.

The other issue is that it needs 4K7 pull-up resistors on the data lines between the PCF8574 and the attenuator. This can be done by?using 4K7 axial lead 1/8W resistors standing vertically in the holes?used to connect the attenuator to the PCB and tying the top ends to 3V3.

Glenn is nearly finished a Version 2 PCB set which will add the pull-ups, but probably not change the CS pin numbers.

Jim (G3ZQC) has the SA pretty much running on Glenn's PCBs which uses the TTGO T8 V1.7 (WROVER) ESP32.

One other note on the software. For whatever reason (probably the rat's nest on my breadboard) I can only get the display to work?with the SPI bus speed set to 27MHz. The display works fine in my VFO at 40MHz however. That can be changed if necessary by changing the comments on the following lines in the "M0WID_Setup_ILI9341_TinySA.h" file as shown here:

??????? #define SPI_FREQUENCY? 27000000
????? //#define SPI_FREQUENCY? 40000000

The fix for the flip-flopped CS pin numbers is to change the line:

??????? const int SI_nSEL[2] = { 4, 5 };??// Transceiver chip select pins RX - TX
to:??? const int SI_nSEL[2] = {?5, 4?};??// Transceiver chip select pins RX - TX

Right at the top of the ".ino" file

--
John P.
WA2FZW

Hi Marty,

I hope you and everyone else reading this group are safe and well.

I am also working remotely, and so far is working out OK.

The Version 5 release was a bit flakey on the touch sensing, and a new release is just one bug fix away, but you should be able to use either the 02 or 05 versions to test your hardware out.


John WA2FZW has done some extensive work on tidying up the code and added thousands of comments, and this will be in the next release.? Thanks John.
Other enhancements to come in the next version are significantly faster sweep times (now around 3/second when doing a 0-100Mhz sweep with Auto RBW), better touch response, some minor changes to the UI and a webserver so you can control, and view from a browser using the WiFi.? I have the page updating every second without affecting the standalone sweep times and the WiFi activity seems to have no effect on the SA trace.

At the moment the web page has only the same number of data points as the local display, but I think (not yet tested) it should be possible to increase this quite a bit.

To answer your questions though:
1.? I am not clear what board you have.? It does need to be an ESP32, and any version board that doesn't have its own display or LORA module should be OK.
2.? Use version 02 to get it going otherwise you will be frustrated by the poor touch handling in version 5.? Both versions have the same pinouts.
3.? The software doesn't know or care if the attenuator is there or not - it just sends out the instructions and hopes it gets there.? I don't have an attenuator connected yet either and it works just fine
4.? There was a hope that there was an easier method of configuring the ILI9341 library hardware definitions, but it didn't work out.? When you have the TFT_eSPI library installed in your Arduino environment replace the existing User_Setup_select.h in the TFT_eSPI library folder with the one in the zip file, and add the M0WID_Setup_ILI9341_TinySA.h in the User_Setups subfolder. You should probably make a backup copy of the original User_Setup_Select.h

Good luck, don't hesitate to ask if you need any help, and let me know how you get on.

73

Dave M0WID

Dave,

Apologies if this message is requesting repeat info but I've been working from remote for the past two weeks (and for the foreseeable future until this COVID-19 threat is behind us) and I'm JUST now coming up for air. I see that you have (what looks like) a version 5 of the TinySA load. I picked up the following ESP32 devices and loaded your version TinySA02 onto it successfully:



...But I'm looking at your code and the User_Setup_Select.h file and wondered if what I have is compatible (ESP8266 to WROOM-32) for your version TinySA05, or should I just stick with your version TinySA02? Also, I see where the connections are defined, but need to correlate them to what I have (SI4432x2, ILI9341, for now - I don't have the attenuator yet, still working on that).

This message is more to refresh my head from being away from the project for a couple of weeks and to try my ESP32 to my setup that is driven off the Protoneer (like Erik has now). It's just a matter of removing the Protoneer and installing the ESP32 and just wiring up to it. The connections in the User_Setup_Select.h look familiar, but a few of the signals look different and just trying to correlate them to the signal scheme that Erik started out with.

Let me know at your soonest - I'm going to spend today getting this ESP32 working with the setup next - - Thanks in advance for your help with that, Dave,

73 de Marty, KN0CK?


?

On Mon, Mar 23, 2020 at 06:59 PM, jafinch78 . wrote:
?For this application there should be no problem because of the insertion loss in the attenuator module. I checked insertion loss lineaity across the frequency range I am interested in and different attenuation levels, and it is very consistant.
http://kv4qb.blogspot.com/2019/10/checking-step-attenuator-with-nanovna.html?
So just setting a calibration level for the S.A. to a known value should be adequate.
--
DuWayne,? KV4QB

On Mon, Mar 23, 2020 at 03:27 PM, DuWayne Schmidlkofer wrote:

I am planning on using the simple parallel versiono of the attenuator board.?

While somewhat on the topic... any issues with your latest mod for adjusting to a relative value??http://kv4qb.blogspot.com/2020/01/small-update-t-step-attenuator.html

I am planning on using the simple parallel versiono of the attenuator board.? I have used these in a 63 dB. varfiable attnuator project?
?and have found them to work well.? On ething I did find is that some of them came with pulldown resistors installed, and others did not, so I provided for adding resistors on my circuit board..? For this application I only plan on using 4 control lines to give me 2dB steps.? ?For most cases the attenuation values will be 1.10,20,30 dB. so 2 dB steps will be adequate.
--
DuWayne,? KV4QB

On Fri, Mar 20, 2020 at 08:47 PM, K9HZ wrote:

True… but in this day and age… with parts getting smaller and smaller, you gotta work to get over that

Yeah! Glenn is making me bite the bullet and learn how to handle things I can't even see! I have the magnifying glasses, one of those digital microscopes tons of tweezers and dental picks.

My dentist told me about a woman who worked in the lab that made crowns for him. In her spare time, she would take ones that didn't come out right and make teeny-tiny sculptures out of them! God bless her!
?
--
John P.
WA2FZW

开云体育

Another reason for using the parallel board is the perceived difficulty by some, in soldering small smd IC's.? Yes for some its a challenge, no doubt.

My board for example,? is mostly smd parts as it is, but mainly discrete parts, do-able if one sets your mind to it.

Glenn
vk3pe