开云体育

Hi, First let me say I'm glad this device exists so I don't have to lug my 35kg 40 year old SA around... However, having said that I have to point out a serious design flaw (and rant somewhat that it is not an open source design which would make repair so much easier). So I was pretty happy to be able to purchase my TinySA from a local reseller here in Poland after he confirmed he got it from Zeenko's. I was happily using the SA for testing the output of my ham radio amplifier when I thought. What is this "Listen" option in the menu? Can it possibly demodulate audio signals? So I took my headphones and I inserted them normally into the jack, but it felt very loose and the plug fell out when I lifted it. There was no crack felt when inserting. Minimal force was used (I've owned mini jack equipment for ages, including ones with the port on a bare pcb, I know what force to use to plug it in). So I inspected the port closer and I noticed the receptacle is not there. I opened the device and I saw the carnage and the design flaw that led to it. The receptacle is an smd part and all the support it has is in a form of very narrow cutout around the mouth. There was not even the "hot snot" type of glue around it as support. There is no back support. The part simply torn out of the pcb and damaged what I assume is a voltage regulator for the sd card behind it. This picture was taken after I very carefully placed the voltage regulator back on its pads. Is it possible I got a previously broken and returned unit from the seller? I initially thought so, but I reviewed my "parcel opening" video and there was no gaping hole where the audio port is and I doubt the receptacle would just sit there held by the case cutout. So it appears when I tried to plug it in it indeed ripped out of the pads. To add insult to injury, the design is not open source (despite being based on nanovna that is, which made me assume it too would be open hardware) ... So I have no idea what the value of now missing r32 resistor should be. When I blew up an RF switch in nanovna I simply looked up the schematic online, ordered a part from China and replaced it myself. Here it is not possible. But what about clones? Don't I understand, open hardware designs get cloned? So does current TinySA Ultra. Not being open hardware has not stopped cloners one bit, but it hinders end users in attempts to repair the device. The only reason why I could figure out the chip is a voltage regulator is because I saw such regulators before. I did manage to fix it with wires. I also lubricated the mini jack receptacle and tried to insert/retract the plug few times after the repair. It holds for now. I'll probably be applying the hot snot to stabilise it further if someone could measure that resistor and let me know it's value so I can replace it first. Maybe it is 10k?. So here you have my feedback. Why do I think it is a design flaw? Well, for one, if a smd part is used and through hole is absolutely impossible for an audio jack the case should be formed in a way that provides support behind. At the very least some sort of glue (preferably hot melt so it can be removed for repair) could also be used for purpose. I realise the "listen" feature is not that important. It's more of a gimmick as it only supports AM (my signal is SSB so I couldn't listen anyway), but in the process of messing up the jack port a very important feature (the ad card port) was damaged. I'm pleased to report the SD card works fine. I haven't tested listening yet (without the final grounding resistor), but it should work too. Regards, F

Hello! I have a problem. My tinySa ULTRA can not pass the calibration. It stops at the message - signal level incorrect, check the cable. But it always passes the self-test perfectly. I have read a lot of posts here in search of a solution to my problem. In the end I replaced the LNA. But the result is the same as it was. There is a suspicion on diode D5 on the calibration input. It rings in two directions and has a resistance of 63.5 ohms in two directions. Perhaps the reason is in it, but I can not see the labeling. What is the marking of this diode? And maybe I should replace diode D4 at once? Are they the same? I installed the latest firmware version, but the result is the same. Self-check - ok. Calibration - no. Please give advice or recommendations to solve this problem. Thanks!

New FW release Version V1.4187 Ultra only Changes: - OIP3 data now shown as dBm - Quasi peak implemented for non zero span scans. MAX HOLD DECAY may be easier to use - Function added CONFIG/TOUCH/DRAWPAD. This converts the tinySA into a drawing pad for (small) kids. Press jog button to clear. Restart to exit. -- Designer of the tinySA For more info go to https://tinysa.org/wiki

I live in a detached house on the hill in my town spaced apart from other houses and do not have much interference. After many tests I realized that the interference is caused only when the computer is on (I tried to turn on only the 2 monitors, but they do not give interference). If I turn off the computer and the 2 monitors are on, no error, all tests are passed. If I turn on the computer (ASUS TUF i9-10900x 10 Core 3.70GHz + nvidia 4090 + 64 GB RAM) the self test gives error 3. I attach the screenshot This is something to remember if measurements are to be made. Probably a $33,000 HP spectrum analyzer under the same circumstances would not give error :)) Al Il 28/11/2024 17:18, Erik Kaashoek ha scritto:

I connected the cable to the High and Low input. I attach photos of the self test 4 failure message (was not the 3) and the version screen. The box was perfect. Unopened package from amazon AURSINC. Thank you, A Il 27/11/2024 18:48, Erik Kaashoek ha scritto:

Hi, I took 2 screen dumps to demonstrate that the quasi peak measurement method does some sort of frequency domain smoothing as of the current implementation, which is clearly not what it should be doing. The 1st screenshot was made using the AVE16 calc method, the 2nd is QP. They should be nearly identical since I measured a stationary signal. The quasi peak smoothing must be done in the time domain, so each frequency bin of interest must be measured separately for a certain amount of time and the consequently taken samples need to be fed to a quasi peak detector with an attack and release time specified by CISPR. Best regards, Andras

1. When the OIP3 function is invoked thru the touchscreen, it then asks for the "left-hand" and "right-hand" frequencies. However, if the OIP3 function is invoked programmatically via "menu 8 3", the centre frequency is strangely changed to 1.5 kHz and the span to 3 kHz. Hence, I will need to send additional commands: "sweep center [Hz]" and "sweep span [Hz]" to positions the markers 1-4 on the correct frequencies. Is there a way to send "left-hand" and "right-hand" frequencies via command? 2. The measured OIP3 values are displayed on the TinySA's screen - 2nd line from the top (attached image). Is it possible to read these values programmatically? My present solution is to read the markers 1-4 individually via "marker [#]" and then calculate the OIP3, but it takes too many lines of code. ? Thanks. 73, Chin-Leong Lim, 9W2LC.

The lna is supposed to be activated to see more of the lower part of the signal, but in my case, apart from seeing more of the lower part of the signal, the upper part goes up 3 or 4 db, so I don't know what the true value is. The signals I'm measuring have values ??between -70 and -60 dbm. What am I doing wrong?