Keyboard Shortcuts
Likes
- Tinysa
- Messages
Search
|
Locked
Re: Windows 11 does not properly load tinySA in DFU mode.
USB 3.0 I have a 2.0 hub on the way. Thanks for the help all!
|
|
Locked
Re: Windows 11 does not properly load tinySA in DFU mode.
¿ªÔÆÌåÓýAre you using USB3.0 ports??? I bought a cheap amazon USB 2.0 four port and my problem was solved.? I am not sure if this applies to you.?? Just a note, I do not need the USB2.0 port for the Ultra Rich On 10/20/2023 16:21 PM, Pirok-W4UNX
wrote:
|
|
Locked
Re: Windows 11 does not properly load tinySA in DFU mode.
The software does not like the USB 3 interface. If you can't find a computer with the prior interface, try finding on older USB hub. Connect the hub to your co.puter and try again. This has been documented numerous times on this group. Good luck. On Fri, Oct 20, 2023, 4:21 PM Pirok-W4UNX <jason.pirok@...> wrote:
|
|
Locked
Re: Windows 11 does not properly load tinySA in DFU mode.
Make sure using a USB2 port. Things havent worked on USB3 ports a lot of times.?
toggle quoted message
Show quoted text
Don? ?K5ZRQ?
|
|
Locked
Windows 11 does not properly load tinySA in DFU mode.
I feel like I'm in the same boat as Larry in the?/g/tinysa/message/10492?topic, but I don't have an old windows computer laying around. Are there detailed instructions for flashing the tinySA on linux? Are there newer instructions for Windows 11? I have 4 windows 11 laptops in my house and 7 other linux devices and that's it. I have tried using the tinysa-app and the stcubeprogrammer with no success. tinySA v0.3 2019-2020 Copyright @Erik Kaashoek 2016-2020 Copyright @edy555 SW licensed under GPL. See: https://github.com/erikkaashoek/tinySA Version: tinySA_v1.3-347-g31eb02e Build Time: Mar 21 2022 - 14:57:08 Kernel: 4.0.0 Compiler: GCC 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204] Architecture: ARMv6-M Core Variant: Cortex-M0 Port Info: Preemption through NMI Platform: STM32F072xB Entry Level Medium Density devices ? ESD protected ? ? |
|
Re: Detecting low power motion sensors
On Sat, Oct 14, 2023 at 04:50 PM, ANDREAS Decker wrote:
frequency span 100 MHz, Min Hold, RBW 300 KHz, LNA=ON.Use a narrower sweep bandwidth, wider RBW and Max hold. <6GHz the LNA is fine, it gradually gets worse as you go higher in frequency, but you should still be able to see older 10GHz CW doppler radars without too much difficulty, although they are not that stable. Regards, Martin |
|
Re: #TinySA-App @Toni
#TinySA-App
This is useful if the goal is to operate the ultra completely remotely, viewing the results and taking remote screenshots from a computer, but with the limitation of 450 measurement points.?
Although it has no effect on the large screen of the app, it does have effect on the 480*320 screen on which you are trading and which is being shown to you on the computer.? Many remote system administrators, sometimes hundreds of miles away, show you the device as it really is so you can operate it as if you were there. |
|
Re: Detecting low power motion sensors
On Mon, Oct 16, 2023 at 03:05 AM, mike wrote:
I have uW sensors in wall since similar time, I know they are 5.6gig operating frequency (model = Zinc ZN29188 ) and my TinySA cannot see them either...According to what your device manual says here , this should be operating at 5.8 GHz and not 5.6 GHz. Could you try to detect it again ? On Mon, Oct 16, 2023 at 09:53 AM, John Cunliffe W7ZQ wrote: kindly remember that above ~6ghz the lna becomes essentially an attenuator. It is better to have it off. Most motion detectors I have dealt with have a steady output signal between 0 and 15 dbm ...Thank you for the information. At what frequency were working the sensors that you detected with TinySA Ultra ? ?
?
? ? |
|
Re: #TinySA-App @Toni
#TinySA-App
Haven't tried this, but if it's the same as doing it on the physical screen then i have done that already and while it works on the physical screen, it has not effect on the app screen.
|
|
Re: #TinySA-App
#TinySA-App
Tried this already.
The scale on the device was corrected, but not in the app. |
|
Re: #TinySA-App
#TinySA-App
You can also click on the app's camera icon, select Auto Refresh (Yes) and act with the mouse on this computer screen, accessing the menus as if you were doing it directly on the physical screen of the #ultra
Toni |
|
Re: #TinySA-App
#TinySA-App
I don't know if the App will pick this up but there is a checkbox for gain on the device. Just enter -59 and the scale is automatically corrected.
Sam |
|
Re: #TinySA-App
#TinySA-App
Easy to target and measure harmonics.? Just set the center frequency step to the harmonic frequency.? Then every requested center step will increase the center frequency by the harmonics of the fundamental.? Dave - W?LEV On Tue, Oct 17, 2023 at 4:44?PM <virtual81@...> wrote: Any way to set EXT GAIN in TinySA-App? -- Dave - W?LEV |
|
#TinySA-App
#TinySA-App
Any way to set EXT GAIN in TinySA-App?
I have 59db worth of external attenuation hooked up and can't see a way to set this in the app. Also side question, the 'Measure > Harmonics' feature in the device, is that somehow able to be replicated in app? |
|
Re: 6-18ghz analysis with tinySA & a downconverter?
Many products I've tested pretty much cease emissions above 1 or 2 GHz.? The silicon "runs out of gas" at some undetermined frequency and no longer produces energy above that frequency.? Well, it might, but generally insignificant energy to amount to much.? If you don't detect emissions above something less than 6 GHz, I wouldn't worry about it for a prescan. Actually the FCC requires testing and documenting to the fifth harmonic of the highest frequency used or generated (clock frequencies) and,......., if you generate it (greater than the fifth harmonic) you use it.? However, a caveat:? These days FCC doesn't give a rip about the small fish in the ponds (evidence all the Chinese wall warts).? Further, we EMC/RFI engineers are now tasked with conducting what FCC was originally tasked to do.? In addition, when it comes to the solar power industry, our very own ARRL is doing their job, grattis (well, not quite as your and my dues to ARRL pay for a very well outfitted lab and staff). Won't pursue that further as I could write a book on the subject. ?? Dave - W?LEV? On Tue, Oct 17, 2023 at 5:12?AM <mykle-tinysa@...> wrote:
-- Dave - W?LEV |
|
Re: how to save the calibration data for 6G-12G for SA and SG in the high freq for Ultra
Hi Terry,
Its is a bit more complex When sending a 5.34GHz signal into the tinySA Ultra you can calibrate the "harmonic step" e.g. the change in sensitivity when the mixer goes to hamonic mode. With this calibration done the level calibration should be good (within the constraints as specified in the wiki) up to 6GHz. Above 6GHz there is currently NO level calibration present. However, if you have a signal source above 6GHz with a known level you can create yourself a correction table that goes up to whatever frequency by "stealing" some of the 20 correction points in the regular ultra correction table and moving these points to higher frequencies. Do keep the frequencies in the correction table in sorted order otherwise the internal calculations will fail. -- For more info on the tinySA go to https://tinysa.org/wiki/ |
|
Re: how to save the calibration data for 6G-12G for SA and SG in the high freq for Ultra
hi, Erik:
after I check the?TinySA4_Menu_Tree.pdf, in this?document it said "However this single predefined leveloffset are pretty close to the ideal value so only if accurate SA measurements above 5.34GHz is required, this above 5.34GHz calibration is needed."? Is this means, if I use a SG to send out the 5.34Ghz sigal to Ultra SA, then Ultra SA will automatically calibrate the signal level from 5.34G-12G? and then I will have a right reading value in the X-band? And also checking "the 6 input correction tables with 20 frequency level corrections entries" seems UltraSA only support to maximum 6Ghz, not 12Ghz, how can I add 6G-12G calibration data to these correction tables? thanks a lot. |
|
Re: Detecting low power motion sensors
The data sheet for one of these devices says that the power output is <0.2mW CW at 5.8GHz. <-7dBm.
toggle quoted message
Show quoted text
Regards Jeff -----Original Message-----
From: [email protected] <[email protected]> On Behalf Of John Cunliffe W7ZQ Sent: 16 October 2023 17:53 To: [email protected] Subject: Re: [tinysa] Detecting low power motion sensors kindly remember that above ~6ghz the lna becomes essentially an attenuator. It is better to have it off. Most motion detectors I have dealt with have a steady output signal between 0 and 15 dbm. Given that it is plastered over I don't think the resulting signal will be very strong. Add to that the vastly reduced sensitivity of the TinySA ultra in the 10Ghz and above region you would have to be very close to the actual unit to detect anything unless you use an antenna with some gain and / or a preamp for those frequencies. |
|
6-18ghz analysis with tinySA & a downconverter?
Hello, Thanks, |
|
Re: Detecting low power motion sensors
¿ªÔÆÌåÓýThese 'sensor' radars are CW, not pulsed. I have a 10.3GHz radar head and my tinySA Ultra see it with no problem. Mike C. Sand Mtn GA On 10/16/2023 12:53 PM, John Cunliffe
W7ZQ wrote:
kindly remember that above ~6ghz the lna becomes essentially an attenuator. It is better to have it off. Most motion detectors I have dealt with have a steady output signal between 0 and 15 dbm. Given that it is plastered over I don't think the resulting signal will be very strong. Add to that the vastly reduced sensitivity of the TinySA ultra in the 10Ghz and above region you would have to be very close to the actual unit to detect anything unless you use an antenna with some gain and / or a preamp for those frequencies. |
Sam Reaves
Mike C.