开云体育

Or an Si5351, $1 on Mouser, cheaper than a mixer. Assuming 250mhz or so max is sufficient. The Sig-Gen mode of the tinySA is interesting in that it might be able to emit a sine wave capable of going

Speaking about shielding: Did anyone find a source for shields on ebay, aliexpress etc? Whatever search quires that I use I get 0 results. Can't find any on LCSC either.

You can output the LO and send it to a completely separate fully shielded tracking generator box with a mixer, SI4432 and any micro to setup the SI4432. LO from tinySA to RF port of mixer, internal

Thanks Erik..? I was assuming good shielding..? Do you have a recommendation? Two more Si4432s?? That's only $3 and two more nSel pins, minor Arduino code. Or just a noise generator I already

I tried and the 433MHz did deafen the RX SI4432 You can test by disconnecting the RF input from the RX SI4432 from observe if there is still a zero Hz peak. Only with VERY good shielding will a

Ah, you're right.? One additional Si4432, not two.

Jerry, Yes, Si5351 is an excellent part, I have several. Another Si4322 programmed to TX at the IF (434MHz) feeding a mixer... and the LO feeding the 2 mixers will make a great tracking oscillator.

The Si5351 is a $1 part. common, very small, does 4khz to 250mhz, lots of DIY projects are already using it with Arduino boards. Not clear to me how two additional Si4432's and a mixer are better.

Erik already demonstrated using a Si4432. He just said to use another mixer and use the LO to do the sweep. I think it would need a peak hold or something on the display though? 73, Gary WB6OGD

I assume that tracking generator need only do up to 250 mhz. An Si5351 should be fine, spec'd for 225mhz, but does up to 290mhz. The tinySA will ignore any harmonics from the square wave. Jerry

Ok, its been a month or so, how are those tinySAs coming? I am ready to build my next version.. the first is quick and dirty, see attached photo. It works beyond expectations for the quick and dirty

Jerry, The scanning loop for the local display is different from the scanning loop for PC data, I was referring to the local display scanning loop -- HBTE Files section: /g/HBTE/files

Correction: So the RSSI read occurs delaytime*100*2/3 microseconds after the frequency is set. And perhaps the 2/3 factor is due to the processor specific execution time of this loop: while (micros()

Perhaps I misunderstand, but this doesn't seem quite right: In the tinySA.ino code of Jan 17, I see the following under the 'M' command: ################### ... for(int i = 0; i < steps; i++ )? ?{

The RSSI is read on request as there is no guaranteed good latched value (no way to automatically capture a defined time after a PLL change). The is no delay in the tinySA code between setting the

Thanks.? Will give it a try this evening.? I think I need to fit the matching parts to the 434MHz filters to flatten out the response and try and get a consistent peak reading as the IF changes.

Best is to take as offset twice the RBW, as long as 6*offset is less then IF BW -- HBTE Files section: /g/HBTE/files Erik, PD0EK

I am porting tinySA.ino to the Raspberry Pi. Code as it is now can be found at /g/HBTE/files/KE7ER/tinySArpi00.c Need to shut this down for a couple weeks, have other urgent projects

That almost works, see attached. At each point in the sweep I take readings at the nominal IF, then with the IF at an offset each side, and take the lowest value of the three readings. Need to see how

These so call "bad"? modules are mostly 250MHz or 333MHz modules used ad 433MHz. Make sure your supplier understands the different between the frequencies and only buy from a supplier (click on the