Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
On Tue, Oct 6, 2020 at 02:45 AM, Jim Shorney wrote:
I played a bit with trace smoothing again tonight. First image, is there a signal there? Second image, ye! I already knew it was there but this was testing with a weaker signal tonight. It is a digital subcarrier on a local FM broadcaster. Of course it is not a very accurate representation of the signal but it does show that there is something.
Many thanks to Erik and Cathy for this wonderful software!
73
-Jim
NU0C
What I can see in your 1st image is the scanraw floating point to 16-bit (2-byte) integer compression showing itself (limited dB resolution). The only way to improve that would be to go to a 24-bit (3-byte) scanraw integer value.
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
Thanks for the comments. I haven't quite figured out the time averaging yet, but that will come. These Naoo* devices are lots of fun! :) 73 -Jim NU0C On Mon, 05 Oct 2020 20:32:12 -0700 "OneOfEleven" <cmoss296@...> wrote: The time averaging is very useful too, it's the same as the tinysa's own averaging per point (sample repeat ?) ..
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
On Tue, Oct 6, 2020 at 02:45 AM, Jim Shorney wrote:
I played a bit with trace smoothing again tonight. First image, is there a signal there? Second image, ye! I already knew it was there but this was testing with a weaker signal tonight. It is a digital subcarrier on a local FM broadcaster. Of course it is not a very accurate representation of the signal but it does show that there is something.
Yes it certainly can help. The time averaging is very useful too, it's the same as the tinysa's own averaging per point (sample repeat ?) ..  
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
I played a bit with trace smoothing again tonight. First image, is there a signal there? Second image, ye! I already knew it was there but this was testing with a weaker signal tonight. It is a digital subcarrier on a local FM broadcaster. Of course it is not a very accurate representation of the signal but it does show that there is something. Many thanks to Erik and Cathy for this wonderful software! 73 -Jim NU0C On Mon, 05 Oct 2020 09:53:51 -0700 "Erik Kaashoek" <erik@...> wrote: The tinySA supports averaging per point (reading the same frequency multiple times) so I guess it is better to change the flattening to set the amount of averaging per point? inside the tinySA
|
Re: TinySA In stock at R&L Electronics
R&L back in stock as of 3:58 PM central time on 10-5-2020.? I ordered one...
73,
Steve_WB8GRS
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
On Mon, Oct 5, 2020 at 09:58 AM, OneOfEleven wrote:
Erik will need to use the updated code to solve the problem in his TinySA-App program
Will do
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
On Mon, Oct 5, 2020 at 03:20 PM, EB4APL wrote:
I have played with the Windows localization settings and found that the
use of the comma as de decimal separator in Windows, not in the program
settings for csv files)? is the cause for the "Range check error", and
it happens when the program tries to write the tinySA-App.ini and the
live.csv files, as there are decimal separators involved.
I've fixed the settings ini file problem. Erik will need to use the updated code to solve the problem in his TinySA-App program.
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
The tinySA supports averaging per point (reading the same frequency multiple times) so I guess it is better to change the flattening to set the amount of averaging per point? inside the tinySA
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
The trace smoothing as is isn't really that useful on a spectrum analyser due to it flattening out wanted peaks, it's use will remove/corrupt useful data. As was suggested a 'threshold' setting would help to alter the way the frequency domain smoothing works.
The time averaging is different though, that maintains frequency detail, it smooths/averages in the time domain rather than in the frequency domain.
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
On Mon, Oct 5, 2020 at 07:16 AM, Erik Kaashoek wrote:
Made a new release based on the latest code from OneOfEleven, lots of changes.....
Hope it works better now
Erik, ? ?Yes! All major functions related to changing high and low input modes and related sweep settings appear to be working as expected.? Only minor UI related artifacts noted: ? S11 label below? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?TDR window should be RBW? ? ? ? ? ? ? Label5? ??  ? ? ? ? ? ? ?  ? ? ? ? ? ? ? ? ? ? ? ??  The new release adds some new scaling options such as using the mouse wheel or dragging the axis to change values.? Looks like things are definitely getting there. - Herb
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
Hi Erik,
I have played with the Windows localization settings and found that the use of the comma as de decimal separator in Windows, not in the program settings for csv files)? is the cause for the "Range check error", and it happens when the program tries to write the tinySA-App.ini and the live.csv files, as there are decimal separators involved.
Even the tinySA-App.ini file written with other separator settings throws the same error when invoking the program, but it is not important, it is supposed that a user keeps this regional settings steady.
While testing this I found that in the .ini file there are some inherited parameters that contribute to the problem and could be deleted, for example:
inline_s21_attenuator_db 0.000000
edelay 0.000000
vswr_gamma 2.500000
velocity_factor 0.660000
A possible solution is to use the same approach as in the frequency settings, that are all in Hz so they are all integers. This could be applied to the graph scale table (if needed), disregarding the decimal part since it looks to me that they are not used, or multiplying all decimal values by a suitable number and keep them integers.
Kind regards,
Ignacio EB4APL
toggle quoted message
Show quoted text
El 05/10/2020 a las 15:23, EB4APL via groups.io escribió: Hi Erik,
I found another minor nuisance: When changing mode from Low to High the default frequencies also changes, which is nice, but the CW frequency not, which is ok being CW mode not allowed in High mode, which is grayed out, but it gives an exclamation mark alarm (error:? invalid CW frequency), which I must clear entering a "in range" value such as 500 in order to allow the scan. When changing back to Low mode, the value persist and I got the same alarm.? I think that the range check in the CW field should be disabled when in High mode.
I'm quite good finding software bugs, as a friend used to say "I have a sexual finger: anything that I touch, I screw it".
Regards,
Ignacio EB4APL
El 05/10/2020 a las 13:44, EB4APL via groups.io escribió:
Hi Erik,
Everything you mention works, but if I try to close the program once I made a scan, I got the message "Range check error" and the comms disconnects. In order to be able to quit I have to connect again and close the program without doing any sweep this time.
I saw a nice feature: the frequency settings are got by the tinySA and effective when the App scan is finished
Kind regards,
Ignacio EB4APL
--
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
Made a new release based on the latest code from OneOfEleven, lots of changes.....
Hope it works better now
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
Hi Erik,
I found another minor nuisance: When changing mode from Low to High the default frequencies also changes, which is nice, but the CW frequency not, which is ok being CW mode not allowed in High mode, which is grayed out, but it gives an exclamation mark alarm (error:? invalid CW frequency), which I must clear entering a "in range" value such as 500 in order to allow the scan. When changing back to Low mode, the value persist and I got the same alarm.? I think that the range check in the CW field should be disabled when in High mode.
I'm quite good finding software bugs, as a friend used to say "I have a sexual finger: anything that I touch, I screw it".
Regards,
Ignacio EB4APL
toggle quoted message
Show quoted text
El 05/10/2020 a las 13:44, EB4APL via groups.io escribió: Hi Erik,
Everything you mention works, but if I try to close the program once I made a scan, I got the message "Range check error" and the comms disconnects. In order to be able to quit I have to connect again and close the program without doing any sweep this time.
I saw a nice feature: the frequency settings are got by the tinySA and effective when the App scan is finished
Kind regards,
Ignacio EB4APL
--
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
On Mon, Oct 5, 2020 at 12:32 AM, Erik Kaashoek wrote:
I'm still finding my way in the rather large amount of code OneOfEleven wrote.
Hope this time its better, at least its more teste
Release tinySA App 1.0.203.2
Changes:
- Version number increased
- start/stop no longer reset
- mode switch directly reflected on tinySA
Erik, ? ?I'm sure before OneOfEleven refactored her code navigating through the code base would have been even tougher.? It looks like you are getting more familiar though.? The only new feature I am still finding an issue with is as follows: ? 1. Low Input | 0-350MHz | 30MHz Cal Out-ON | Single Scan ? 2. All O.K. ? 3. Mode High| Single Scan ? 4. tinySA changes to high mode, 240-960MHz but no scan occurs.? The battery voltage just seems to randomly change values. ? 5. Returning to the low mode restores normal program operation. ?BTW, any chance of returning the external attenuation/gain setting (s21 attenuation)?? Its not absolutely necessary because tinySA provides an "Externa Amp" setting but it would be an added convenience. - Herb
|
UI Minor Comment/Observation/Suggestion
Hi Erik,
I have a comment/observation/suggestion on one small aspect of the TinySA.
That being when you are in a menu, if you use the jog switch left to go to the top of menu and then one more left of the jog wheel, you exit the menu. ?If you then press the jog switch again, you re-enter the same menu. ?I personally think it would be better to return to the top level menu when exiting a menu in this way. ?Do you agree?
73,
Robert, WA2T?
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
Hi Erik,
The same "Range check error" is thrown when trying to save a CSV file without previous errors. I will check if this can be caused by something related to the localization of my Window installation.
Ignacio EB4APL
toggle quoted message
Show quoted text
El 05/10/2020 a las 13:44, EB4APL escribió: Hi Erik,
Everything you mention works, but if I try to close the program once I made a scan, I got the message "Range check error" and the comms disconnects. In order to be able to quit I have to connect again and close the program without doing any sweep this time.
I saw a nice feature: the frequency settings are got by the tinySA and effective when the App scan is finished
Kind regards,
Ignacio EB4APL
El 05/10/2020 a las 9:32, Erik Kaashoek escribió:
I'm still finding my way in the rather large amount of code OneOfEleven wrote.
Hope this time its better, at least its more teste
Release tinySA App 1.0.203.2
Changes:
- Version number increased
- start/stop no longer reset
- mode switch directly reflected on tinySA
--
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
|
Erik.
Do you find it interesting?
When selecting "FREQUENCY" => "CENTER":
If the frequency is below 350Mhz, TinySA selects "LOW in";
If the frequency is above 350Mhz, TinySA selects "HIGH in" automatically.
If that has already been answered, sorry :)
Using research in another language is sometimes a little more difficult.
Thank you for your work.
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
Hi Erik,
Everything you mention works, but if I try to close the program once I made a scan, I got the message "Range check error" and the comms disconnects. In order to be able to quit I have to connect again and close the program without doing any sweep this time.
I saw a nice feature: the frequency settings are got by the tinySA and effective when the App scan is finished
Kind regards,
Ignacio EB4APL
toggle quoted message
Show quoted text
El 05/10/2020 a las 9:32, Erik Kaashoek escribió: I'm still finding my way in the rather large amount of code OneOfEleven wrote.
Hope this time its better, at least its more teste
Release tinySA App 1.0.203.2
Changes:
- Version number increased
- start/stop no longer reset
- mode switch directly reflected on tinySA
--
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
Will integrate as the serial interface is a nice option to avoid the USB communication disturbances
|
Re: New tinySA-App.exe: Added mode, rbw and attenuation buttons
On Sun, Oct 4, 2020 at 03:18 PM, hwalker wrote:
David,
? ?The software should run on any Windows PC or laptop with a USB2 or USB3 interface.? In tinySA-App, select the comport that the tinySA is connected to from the dropdown box (i.e. COM5) and you should be good to go.? The speed setting is meaningless for USB and Erik will probably disable it to avoid confusion.? The NanoVNA version of the program used it for setting up DiSlord's wireless module modification.
I port Serial connection code to tinySA (see branch?) so it can be used to connect over COM port vs Serial to TTL convertor om MAX232 for example.
|
Jim Shorney
Igor - PY3IG