Good progress.

The message indicates an issue with the SPI communication to the SI4432.? This is most likely to be wiring again, but could also be the SI4432 module itself.? There were some posts about this in the past but that turned out to be a dodgy solder joint.? In that instance the SI4432 was receiving commands correctly but not returning values.? As that particular SI4432 is used for transmit rather than receive the unit still functioned.
Unfortunately the type FF etc message indicates no communication back from the SI4432.
The TX (local oscillator)? is the first SI4432 to be tested - if it fails then nothing else is checked.? You should get a Red Fatal error box on the display with message "LO SI4432 failed to Initialise".?

It could be the bus is running a bit too fast for your wiring/modules - in my build I run the SPI at 10MHz but the modules are only specified for 8MHz.? In si4432.h you will find a line #define BUS_SPEED? 10000000.
Try changing this to a lower value, say 4000000 and then if that works try 8000000.? I found I had to remove one of the tiny caps on one of the SI4432 modules to reduce the loading on the bus when I had the tracking generator modules as well.? It was OK with just two SI4432.? The cap is on one of the SPI lines, I forget which - clock I think.

If you have a scope then take a look at the waveforms on the bus (probe on 10x).

Getting closer!

Dave

I finally got the proper pinout completed and simpleSA boots up on screen, but errors out with "TX Si4432 Reset failed - _cs = 5", I had run across a post about this before but can not find it with any type of search now. I switched the connections between si4432's and get the same error. It seems to read the first si4432,giving "type ff, version ff, status ff, and always fails on resetting for the second. The post I read had a fix for this, does anyone have know where I can find such a post or fix?

开云体育

Dave, I am in usa, ohio, and I use an exacto knife to make my own traces on blank 2 sided pc board. A tedious and time consuming task, but I have constructed many fairly complex boards, albeit mainly one sided, but I can produce different circuit layouts that way. I can guarantee the proper pins were connected to the proper component, and I always recheck everything at least 3 times before I apply power to the circuits. I used the schematic in the pdf file I attached to my last post, which say's in bold letters across the top of it " tinysa control section v2 per m0wid's pinout", that was the only schematic I could find on the forum or anywhere else. I now see at the bottom it was VK3PE'S design, and never came across any other schematic so had to assume it was the only design existing other than the commercial tinysa version, which I didn't think would be available. I know about the gpio and pin numbering on the esp32 modules, and am always rechecking the connections constantly as I wire it up.? The attenuator I used was the prebuilt one, and I purchased parts to construct both the 200 mhz and the 350 mhz filters as per the parts bom. I am waiting for another order for pe4432's as I damaged one accidently when tracing connections.? As to the coupling capacitor between U9 and R36, 10 NF should be usable then. At this point I am undecided what steps I will be taking to finish it. My 76 year old hands are not as reliable any more, due to 2 mini-strokes and a heart attack, and soldering even 805 size components can be frustrating. I have been wanting to get myself a CNC machine but still do not have the spare funds to do so. Then maybe I can retire the exacto knife! I really appreciate your help, now knowing there was 2 designs to the board, I understand why the pinouts did not work. The compiler was compiling per your pinouts and not the pinouts of VK3PE's design,? and it was driving me crazy. I took the advise of Bodmer, on his tft_espi examples, and ran the program "user setup diagnostic" after compiling and uploading it to the TTGO module. It gave me the expected pins for the tft lcd. I changed the wiring accordingly, reloaded " simpleSA " sketch to the ttgo module and the display worked good then, but it errored out when the pe4432 could not be detected. That indicated the pinouts were still wrong, but I had followed the pinouts on the schematic completely! Again, thank you very much!




I

John - well done for wanting to make your own version and having a go.? Much more satisfaction at the end than just buying something and not understanding how it works, but also at times frustrating!

I think there is confusion over pin numbers on the modules and pin numbers on the ESP32.? Did you design your own PCB?? Also which country are you in?

The pin numbers referred to in the code are ESP32 pins.? For example if you look at VK3PE schematic, which you are using, then pin 28 of the TTGO module is GPIO13 (MOSI for the TFT) - pin 13 - on the ESP32 itself.? On the dev module it is labelled as D13 and by chance happens to be pin 13 of the module.

Another example - GPIO15 = D15 (CS for the TFT) is pin 29 on the TTGO module, pin 18 of the dev kit module.

The TTGO module will work fine, no problem, but maybe not with your PCB if you did not use the same PCB design as Glenn VK3PE.

Some other points to be aware of.? VK3PE uses the parallel interface of the attenuator - enabling use of a pre-made module with the rather tiny surface mount chip already soldered in place, while my build uses the serial interface and I had an evening of "fun" getting that soldered in properly.? Now I know what I am doing soldering these small parts it is actually no problem.? The software should handle either option, but will require different #defines in the mySA.h file from the one in the zip file posted on this site if the parallel option is chosen.? There are lots of comments in the file (thanks John!) so you should be able to work out what needs adjusting for your build.

If you decide to build as per my schematic for the RF side, there is a mistake - an additional decoupling capacitor is needed between U9 (RF switch) and R36 forming part of the 3dB pad into the mixer.? 100nF is fine, indeed a smaller value may actually be better, its not critical.

VK3PE build uses a 200Mhz low pass filter, my current version uses 350MHz.? It really depends on what you want to measure.? The layout of the LPF on my PCB is not ideal and I would look to change it if I ever order another set of PCBs, but it is a bit trial and error.? It is good enough for my use.

The VK3PE build does not have the RF switch for selecting high frequency range.

It is also worth pointing out that most pins on the ESP32 can be mapped to alternate functions.? There is some performance penalty especially for the SPI and I do not wish to spend time experimenting with it, but it may be that whatever pin mapping you have could be made to work - I really do not know for sure.

Dave M0WID

开云体育

?Thank you Dave, no, they are not same pinouts, the schematic I have is for esp32 wrover t8 1.7, the schematic you just sent is for esp32_devkit_v1_doit. I attached a copy of the one I have, so you can see. I can get the dev_kit V1 module and use it making another board for it, and order the other parts I do not have. I have an original TinySA, but wanted to build one myself that I can change/modify myself. I see the problem now, the one M0wid made is not the same and doesn't match the pinouts. I never came across the devkit v1 before, and didn't know it existed.

Hi John.

Sorry to hear you are still having trouble.? It may be my fault for not updating the pinout descriptions in the code comments - at work again so cannot easily check.

Lets start by making sure we are both working to the same schematic, and the same set up file for the display.

?

See attached files.

Note the reset connection for the display is connected to the reset (EN) of the ESP32, and the display uses the HSPI pins on the ESP32.

Dave

Sorry to post again about the esp32 t8. The compiling works flawlessly, but could only get white screen on lcd, Followed advice from Bodmer about the tft-espi examples and ran the " user setup diagnostic" example and it gave the configuration as in the attached "working" text file. when wired accordingly the display worked fine and display showed the simpleSA booting but errored out as the 4432 could not be found. I have rewired everything according to the schematic per m0wid, and no dieplay again ( after recompiling and uploading each time I rechecked everything). See attached "simpleSA text file, for some reason the program will not compile to use the configuration of the schematic connections. Using the terminal program or tinysa app, I can watch it boot and go through configuration setup, but nothing to display. What I am doing wrong I cannot find, in the? the tft espi user setup select.h has "#include <User_Setups/Setup1_ILI9341.h> " selected. In user setup "#define ILI9341_DRIVER" is selected. Is there something I need to include in the defines of the program to tell the compiler what to use?? All help is appreciated believe me!

On Sat, Jan 8, 2022 at 01:02 PM, m0wid wrote:

#include <soc/pcnt_struct.h>

Thank you, Dave, it compiled this time ok. And thanks for all the time and effort involved and the software.
John

Hi John.??

It is wet and miserable here today so I took the time to update my ESP32 core, Arduino libraries and Arduino IDE to the latest versions to see if I could replicate your problem, and I could.? Unfortunately there are some other problems to resolve as well.

To fix the PCINT issue please add the following line near the top of your encoderSA.h file, along with the other includes:
#include <soc/pcnt_struct.h>

Another issue arose in my case with the ESPAsyncWebServer library, as you would have installed the latest version from the web then you should be OK (not available in library manager - add from the ZIP file).

There were some new warning messages I have not seen before, but nothing to worry about.

I have compiled with the mod above and downloaded to my version and it appears to work as before, except for the websockets - the basic page is shown on the browser, so the webserver is working, but the websockets fail to connect :(.?
I will have to do some more investigation into this and post a fix when I have one.

Good luck and thanks for making me update everything!

73

Dave M0WID

Dave, I have a dell laptop with


Dave, I have a laptop with I5 processor, 4 gbyte memory, 1 tbyte? hd, running windows 10 pro, I just installed arduino 1.8.9 for the first time and went through boards manager to configure it, installed esp32 with it. Then downloaded the simpleSa 0.15 version, extracted it to documents/arduino/, selected simpleSA.ino and to open it with arduino. It also errored with the pcnt error not declared in this scope. The same error on both machines, I have rechecked everything I can think of, and insured all libraries were in correct places and no duplicates, and am stopped because of the error. I am not a programmer and have no idea of how to correct it. Attached is the last copy of it, please let me know what you think is causing it when you get the chance to do so








i5

开云体育

Dave, I always install all boards through boards manager, in fact the url has changed to? ( ). I just uninstalled arduino 1.8.19, made sure all was gone from programs x86 folder, then went to user/john/appdata/local/arduino15 and deleted the folder. Only thing left over was the sketch folder in documents, deleted the simplesa folder too from documents. Then installed arduino version 1.8.9, opened the ide and went to boards manager and installed the boards available. Then went to preferences, entered the url for esp32, closed the ide then reopened it, proceeded to boards manager and installed esp32 from there. Closed the ide, unzipped the file for simplesa 0.15 and copied it to documents/ arduino folder, then right clicked on simplesa.ino file selected to open it with arduino ide. Attached is the error file created from compiling, at least no more multiple files detected anyway. Only thing left is to take all sketches and files except sinplesa from documents/arduino, except simplesa and try to compile it again.

Did you install the ESP32 boards using the boards manager or some other way?? Certainly your PC is more modern and capable than my ancient i5, so nothing to do with the hardware.? I do use windows 10 though (PC too old to run Win11), never tried Windows 8.? I doubt that changing to an older version of Arduino would help.? Uninstalling the ESP32 boards and re-installing may be the best approach, but maybe you have tried that already.? Computers sometimes seem to have an obstructive personality!

Good luck

Dave

开云体育

David, I had quite a few errors which I had to correct and they all were caused by the ide not finding the file in the place expected. It took me a while to read back through the error report to find out where the file was supposed to be and place it there. As far as the multiple libraries found, yes, I saw that and haven't had time to track them all down. I did have version 1.8.9 but upgraded to the current version 1.8.19. Think I will go back to 1.8.9 and see. I am running on win 8.1 pro with all updates, it has been running very well for me and any problems were caused by my blunders so far.? intel I7 4820 cpu @3.70 ghz,? 32 gigbytes system memory and total of 14 terabytes disk space (4 hd's). So my system has been very reliable to me. I can't explain why the compiler/linker is using the standard wifi class, something I will have to track down. Thank you for your response and help, I really appreciate it.

Interesting.? Again I am at work, but took a quick look through your error log.? It seems like your compiler/linker is using the standard arduino wifi class rather then the specific one for ESP32.

I think this specific library is installed when the ESP32 core is installed, so I am not sure why your instance is not finding the correct wifi library.

When I compile (I use the old Arduino environment version 1.8.9 - are you using PlatformIO, the beta Arduino IDE or something else?) I get a message like this:

David, I downloaded the last version you posted "0.15", and after correcting several not found files, making sure they were in the library where expected, I recompiled and now get this error "pcnt was not declared in this scope". I am attaching the error message in a text file so you can see it. At least I now longer get the error I was getting before.And thank you for replying to my post.

Hi John.

I am at work at the moment, and will not have time to look tonight, maybe tomorrow.

I have a vague recollection that the touch library is only loaded if TOUCH_CS and/or SPI_TOUCH_FREQUENCY are defined in your setup file for the TFT_eSPI library (found in your arduino/libraries/TFT_eSPI folder).

Dave M0WID

I posted this on tinysa group and was advised to post here. I compiled the example of wifi scan and uploaded it to the esp32 wrover t8 1.7 without any errors, and it ran with no problems. So the arduino ide and software are working correctly. I think it is a problem with tft_sSPI libraries, but am not a programmer so not sure. Does anybody have any idea of how to correct this problem? Any help would be greatly appreciated.

I have built the analyzer per dave M0WID design, tried to compile the arduino sketch for it version 1.4 , have corrected all errors so far (esp32 libraries were not loaded correctly by boards manager), but am stopped by one error.? "'class TFT_eSPI' has no member named 'getTouchRawZ', How do I create a member name for this, not a programmer myself? Am trying to learn about programming, especially arduino, understand a little but don't understand how to fix this error. Using arduino 1.8.13 ide, Any help would be appreciated a lot.
John

Hello,

All file reading problems are fixed.
you needed a version 6 of Kicad
This is what they call build of night(?)
At least it works
https://forum.kicad.info/t/pb-version-kicad/32266/3

thank you

Just re-read your post and noted the wish for an offset for the TG.? I will add that to the list of things to look at - it may happen over the xmas break - it may not.? Good idea.

73

Dave M0WID