开云体育

Yes, this is normal. Any electronics device will emit some radiation.?
Try other devices. You will be suprised by the emissions from a phone, computer, keyboard, mouse, monitor, etc...
Even the radio you are using to listen to the tinySA will radiate.
--

SA Ultra shows signal at 192.100MHz. Tuned that on a radio and heard steady beeps that seem to come from the SA. when I move the radio away, they are inaudible and when I move the marker with the jog wheel they match my movements. And if I hold the jog wheel, the beeps stop while the screen is frozen.?

is this normal, and how many other signals are being produced by the device itself?

Good day to all! Blind grandfather is in touch with you again.
Please tell me the pins of the display cable so that I can connect a larger screen.
Thank you!

Is there any pinout for monitor? How is it connected in general?

TNX!!!

Try this...
/g/tinysa/message/16336

Roger

Thanks to everyone for their replies. I finally was able to find the Zip file and installed it without a problem. I big thanks to Ian for all the work that has gone into this program!

Let me check. This could be a bug
--

Thank you, Erik, for the document.
It describes nicely the calibration procedure, which I also applied before.

I see, that on page 19 it is stated that for DIRECT and DIRECT LNA can't be
changed by the user for whatever reason (although it works for the last 18/17 frequencies).?

But surprisingly also for IN HARM and IN HARM LNA the last 8 (IN HARM) / 9 (IN HARM LNA)
correction values (index 12..19 and 4..19 for IN HARM and IN HARM LNA, respectively) cannot
be changed via the GUI on the device. They can be changed only via USB commands.

Is this the expected behavior?

Best regards,
Michael

Thanks Erik for the explanation.
I see, the observed behavior is expected and not a bug.
:-)

On Sun, Jun 9, 2024 at 04:47 AM, <f.w.ten.wolde@...> wrote:

I just turned on my TinySA Ultra and noticed the touch screen is unresponsive. It does not respond to any touch input on the screen.

Also, the jog-wheel/switch (next to the power switch on the top) is unresponsive.

Frank,
? ?If your tinySA Ultra is less than 30 days old and was sold by a reputable seller, then I would contact the seller about exchanging the unit.? If you have owned the unit for more than 30 days and it only recently has stopped working properly then I would try the following troubleshooting steps.

1. Loosen the 4 screws on the back of the case and see if touch operation is restored.? The case on some version 4.5.1 units fit too tightly and if the screen mounting became slightly misaligned during use, the touchscreen would not work properly.? This same issue could also interfere with USB communications.? The tight case issue should have been solved on your version 4.5.1.1 unit unless you are just unlucky.

2. Completely remove the case and disconnect the battery for a few minutes.? Reconnect the battery and see if normal touch screen operation has returned with the case still removed.? Take normal ESD precautions while doing the above.

3. Check if the flexible cable connecting the display panel to the main board is properly seated.

? If the above trouble shooting steps don't solve your problem, then more extensive repairs are indicated and Erik or hugen may be able to give you additional suggestions.

Herb

Further analysis on my TinySA Ultra:

• This is an official (no clone) TinySA Ultra, HW version V0.4.5.1.1
• Device powers up, screen works.
• Can connect to serial port and enter 'version'.
• Can do 'clearconfig <passcode>' and 'reset'.
• On most other commands, the serial interface freezes, and I have to power cycle the device.
• The TinySA windows program connects to the serial port, but after the vbat command it times out:

connect: serial port connecting ..
connect: serial port connected
43.888 tx: help
43.926 rx: help
43.926 rx: commands: freq time dac nf saveconfig clearconfig zero sweep pause resume wait repeat status caloutput save recall trace trigger marker line usart_cfg vbat_offset color if if1 lna2 agc actual_freq freq_corr attenuate level sweeptime leveloffset levelchange modulation rbw mode spur lna direct ultra load ext_gain output deviceid correction calc menu text remark
43.926 rx: Other commands: version reset data frequencies scan hop scanraw abort test touchcal touchtest usart capture refresh touch release vbat help info selftest sd_list sd_read sd_delete threads
43.926 rx: ch>?
43.926 tx: version
43.957 rx: version
43.957 rx: tinySA4_v1.4-169-ged1dfed
43.957 rx: HW Version:V0.4.5.1.1
43.957 rx: ch>?
43.957 tx: info
44.004 rx: info
44.004 rx: tinySA ULTRA
44.010 rx: 2019-2024 Copyright @Erik Kaashoek
44.010 rx: 2016-2020 Copyright @edy555
44.010 rx: SW licensed under GPL. See: https://github.com/erikkaashoek/tinySA
44.010 rx: Version: tinySA4_v1.4-169-ged1dfed
44.026 rx: Build Time: May 30 2024 - 13:32:12
44.026 rx: Kernel: 4.0.0
44.026 rx: Compiler: GCC 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
44.041 rx: Architecture: ARMv7E-M Core Variant: Cortex-M4F
44.041 rx: Port Info: Advanced kernel mode
44.041 rx: Platform: STM32F303xC Analog & DSP
44.057 rx: ch>?
44.126 tx: vbat_offset
44.157 rx: vbat_offset
44.157 rx: 300
44.157 rx: ch>?
44.173 tx: vbat
44.204 rx: vbat
59.210 rx link timeout .. disconnecting

• Serial commands like 'touchtest', 'touchcal', etc also seems to hang.
• I have succesfully installed the latest firmware using the ST32CubeProgrammer
• When I poweron the device while holding the 'rockwheel' to the left, it seems to change the frequency.
• When I poweron and then very quickly (within 0.5 seconds or so) press and hold the rockwheel , the menu displays, but after that the device seems to freeze up. The menu remains on the screen, but I cannot use the rockwheel to change anything and also the touchscreen is unresponsive.

Are schematics of the TinySA Ultra available, so I can troubleshoot myself?

-Frank

The executables are stand-alone programmes and do not need an installed version of python.

For Linux, extract the two files inside QtTinySA.tar.gz into a folder, open a terminal in that folder and execute the programme by typing ./QtTinySA
There are other ways but this way is straightforward.
??
For Windows extract the two files inside QtTinySA.zip into a folder and run QtTinySA.exe by double-clicking it, or you can run it from the CMD window set to your folder.
The Windows executable works in Win-10 and Win-11 but not earlier versions.? It was built on Win-11.

There is a Wiki on GitHub: https://github.com/g4ixt/QtTinySA/wiki

Ian

On Sun, Jun 9, 2024 at 11:02 AM, Erik Kaashoek wrote:

You first need to install python and possibly some required libraries
There could be a rather large single file for use in windows that includes python

In the "Release" section of his GitHub repository, Ian has a zip file (??) containing a stand-alone compiled executable. The executable usually bundles the Python interpreter, required modules and program into a single file so that a separate installation of python is not required.

I already have python 3.8 installed on all my computers, so I cannot personally verify Ian's executable does not require an already installed version of python.

Herb?

Thanks. gives me something to work with and thanks for all the work you have put into this.

You first need to install python and possibly some required libraries
There could be a rather large single file for use in windows that includes python
--

On Sun, Jun 9, 2024 at 08:08 AM, daniel grafflin wrote:

Some confusion. I downloaded v0.10.6, have all the files in a folder. so, how do I apply this update to Tiny SA app?

QtTinySA and tinySA-App are two entirely different software applications for the tinySA. If you downloaded and unachieved the? QtTinySA zip file, then running the QtTinySA.exe should get you up and running in Windows.??

I've never used Linux so if you are using that operating system and having issues then perhaps someone else can assist you.

Herb

On Sun, Jun 9, 2024 at 07:18 AM, Ian Jefferson wrote:

I have updated to v0.10.6 which adds some new features and fixes various bugs

Ian,
? Excellent contribution to the tinySA user community.? QtTinySA already exceeds a lot of the feature set of tinySA-App.? You should be aware that the VID/PID (0x0483/0x5740) is not unique to the tinySA and is shared also by the nanoVNA, tinyPFA and possibly other devices developed and manufactured by Erik/hugen.

? Also, if there is more than one tinySA in the user's system, for instance one as a signal generator and the other as a specan, then automatic identification of the specan unit may fail using the VID/PID.? If more than one device is detected with a VID/PID of 0x0483/0x5740, then the user should be given the option of choosing which one to use.? You could consider adding a menu option that allows the user to manually select or change the serial port.

? The time, effort and skill to develop and maintain a project like QtTinySA? is well beyond trivial.? Your efforts are greatly appreciated.

Herb

On Sun, Jun 9, 2024 at 08:18 AM, Ian Jefferson wrote:

v0.10.6

Some confusion. I downloaded v0.10.6, have all the files in a folder. so, how do I apply this update to Tiny SA app?