¿ªÔÆÌåÓý

Date

Re: New FW release: various errors in FM modulation corrected

 

Thanks. Haven't received the unit yet.

MIke N2MS

On 10/02/2020 3:00 PM Erik Kaashoek <erik@...> wrote:


Please go to the website indicated on the label inside the nice box that protected the tinySA


Re: TinySA-app display question

 

On Fri, Oct 2, 2020 at 01:53 PM, charlie carroll wrote:
Herb:
You said "
I forgot to mention in my previous reply that if the user wants the tinySA display to match the start stop settings entered in tinySA-App, they can select the button with 4 right arrows before performing a single or continuous scan."

That's not the way that mine works.? If I select the 4 right arrows, the values (for example 1,31) are changed to the values from the TinySA (.001, 350).
Charlie,
? You're right.? I got that backwards as far as making the sweep settings match.? As you said you have to set-up the range on the tinySA first and then make tinySA-App match it by selecting the 4 right arrow heads.? Maybe Erik can add a second button with 4 left arrow heads that send the tinySA-App sweep setting to the tinySA?

? Currently, if you can't access the touchscreen and want to remotely change the sweep range you have to send a user command like: 'sweep 1M 31M'
??

??
Thanks for correcting my error.

- Herb


Re: Hardware versions ...

 

¿ªÔÆÌåÓý

Thanks for the info folks

Dave


On 02/10/2020 13:51, hwalker wrote:

On Thu, Oct 1, 2020 at 10:23 PM, David Slipper wrote:
Hi, a very interesting device - and I'm sorely tempted, but on a
restricted budget so looking for a used unit.

Is there any documentation on the various hardware revisions and the
differences between them ? Just in
case there are any problematic versions.

I have also seen mention of an -H version - what is that ??

I have seen a UTube video describing it used with an external mixer to
produce a tracking generator
to look at filter performance.? I already have a small selection of SMA
mixers and that would be a very
useful tool.

TIA
Dave
Dave,
? Erik and hugen targeted the tinySA for those on a restricted budget like students and electronics enthusiasts.? R&L is selling the unit for $49.99 USD including accessories.? Since the tinySA has only been marketed recently it may be hit or miss finding a used unit and you may not find one for less than $50.00 since it is being sold by some venders on eBay for more than that.? I've also got a few mixers, some of which retail for more than the tinySA.

? I agree with Erik that if you already own a NanoVNA device that its S21 through function is better for measuring filter performance.

?Erik has packed a lot of spectrum analyzer features into the tinySA and on top of it has included some pretty nifty signal generator capabilities.? If your interests primarily lie below 350MHz then I highly recommend the tinySA.? The 240-960MHz band has stated limitations, so you have to evaluate those limitations with your own requirements before considering purchasing.

? - Herb


Re: TinySA-app display question

 

¿ªÔÆÌåÓý

Herb:
You said "
I forgot to mention in my previous reply that if the user wants the tinySA display to match the start stop settings entered in tinySA-App, they can select the button with 4 right arrows before performing a single or continuous scan."

That's not the way that mine works.? If I select the 4 right arrows, the values (for example 1,31) are changed to the values from the TinySA (.001, 350).

charlie



On 10/2/2020 4:37 PM, hwalker wrote:

On Fri, Oct 2, 2020 at 12:43 PM, Erik Kaashoek wrote:
Correct
The scanning mechanism used by TinySA-app is different from normal scanning so it can scan with many more points.
If this is confusing I can consider to update the scan information on the tinySA to at least reflect the range
Erik,
? I forgot to mention in my previous reply that if the user wants the tinySA display to match the start stop settings entered in tinySA-App, they can select the button with 4 right arrows before performing a single or continuous scan.

??


- Herb


Re: TinySA-app display question

 

On Fri, Oct 2, 2020 at 12:43 PM, Erik Kaashoek wrote:
Correct
The scanning mechanism used by TinySA-app is different from normal scanning so it can scan with many more points.
If this is confusing I can consider to update the scan information on the tinySA to at least reflect the range
Erik,
? I forgot to mention in my previous reply that if the user wants the tinySA display to match the start stop settings entered in tinySA-App, they can select the button with 4 right arrows before performing a single or continuous scan.

??


- Herb


Re: TinySA-app display question

 

On Fri, Oct 2, 2020 at 12:40 PM, charlie carroll wrote:
In the upper left corner of the display you can set Start, Stop frequencies.? Is the TinySA supposed to be set to these frequencies?? The app's display changes according to the settings.? But, the TinySA itself does not change.

thanks
Charlie,
? ?tinySA-App uses the very efficient 'scanraw' command for data transfers. This is a binary format that has the advantage of not being limited to the 290 point display limit of the tinySA.?

? In your example, if the display of the tinySA is set to, for instance, 100k-350MHz and in tinySA-App you enter start and end frequencies of 1 and 31 MHz with 500 scan points the 'scanraw' command will acquire 500 points of data between 1 and 31MHz and display the data in a graph without disturbing the tinySA's display.??

?If you actually want to remotely control the tinySA sweep settings you bring up the tinySA-App Comms window and enter 'sweep' commands from there.

??

- Herb


Re: TinySA-app display question

 

Correct
The scanning mechanism used by TinySA-app is different from normal scanning so it can scan with many more points.
If this is confusing I can consider to update the scan information on the tinySA to at least reflect the range


Re: File /tinySA-app/tinySA-App.exe uploaded #file-notice

 

Herb, thanks for maintaining the todo list.


TinySA-app display question

 

¿ªÔÆÌåÓý

In the upper left corner of the display you can set Start, Stop frequencies.? Is the TinySA supposed to be set to these frequencies?? The app's display changes according to the settings.? But, the TinySA itself does not change.

thanks

charlie



Re: File /tinySA-app/tinySA-App.exe uploaded #file-notice

 

On Fri, Oct 2, 2020 at 09:59 AM, hwalker wrote:

? I downloaded v1.0.203 and had the following observations:

? 1.? Looks like you did manage to sneak a new icon in before release.
? 2.? The only confusing references I could still find to the NanoVNA were:
? ? ? ?a. Settings->VNA Settings:? Change to 'tinySA' Settings
? ? ? ?b. Settings -> Threshold: Remove or disable
? ? ? ?c. S1P and S2P buttons: For the tinySA one of these buttons is probably redundant.? Both recall the same waveform when using the M1-M3 buttons.

3? The 'mode' command does not return the current input mode, so there is no way to let the user know if the frequency range is inappropriate for the current input mode.
4.? If the entered frequency range changes from low to high, then there should be a warning alerting the user? to change ports at the applicable cross-over point.
5. Can the S11 | S21 notations in the following screen capture be changed to tinySA specific equivalents?



I haven't heard much from Cathy lately, but I suspect this version of tinySA-App would be more towards her liking.

===============================================

Erik,
? Hopefully you already read this in my earlier post but in-case not....

?? The 3 middle buttons pertain to built-in NanoVNA firmware and need to be disabled and eventually removed.



- Herb


Re: FW upgrade problems

 

Another option for updating the firmware is to use the new tinySA-App software.? One-Of-Eleven incorporated that function in the original master software and it works very well.? I've found myself using it as my first choice because you can also use it as a console command application also.? The steps for updating using tinySA-App are:

1. Turn on tinySA and enter DFU mode (CONFIG->DFU->ENTER DFU).
2. Run the tinySA-APP (located at?/g/tinysa/files/tinySA-app/tinySA-App.exe?).
3. Select the button with the two up arrows in the following screen shot.
? ??

?4.? The following screen should appear. Select 'Upload Firmware' and a file-open dialogue window should appear to allow you to select the new .dfu file.? After selecting the DFU file upgrading will immediately commence.??
??

? One caution, that I need to pass on to Erik, is the 3 middle buttons pertain to built-in NanoVNA firmware and need to be disable and eventually removed.

- Herb


Re: FW upgrade problems

 

¿ªÔÆÌåÓý

.dfu worked this time.? display showing 1.1-5-

thanks

charlie

On 10/2/2020 2:21 PM, Erik Kaashoek wrote:

Try download the .dfu file again and upgrade again as the version number displayed should at least be v1.1-4


Re: New FW release: various errors in FM modulation corrected

 

Arghhh. You are still waiting. http://tinysa.org


Re: New FW release: various errors in FM modulation corrected

 

Please go to the website indicated on the label inside the nice box that protected the tinySA


Re: New FW release: various errors in FM modulation corrected

 

Erik,

Eagerly awaiting delivery of my TinySA. Where can I find the firmware?

Mike N2MS

On 10/02/2020 9:25 AM Erik Kaashoek <erik@...> wrote:


New FW release
Version v1.1-5

Changes:
- Solved a crash in the frequency menu
- Corrected various errors in FM modulation. (shifting, wrong deviation)

FM modulation should now work correctly for both low and high mode over the entire frequency range.
Be aware: In low mode around 46MHz and in high mode around 480MHz the fm modulation way deviate a bit due to complex PLL switching.
_._,_._,_


Re: File /tinySA-app/tinySA-App.exe uploaded #file-notice

 

¿ªÔÆÌåÓý

Thank you Erik, I was looking for it in the second site but it I think it was not updated yet. Now I got it.

Ignacio EB4APL


El 02/10/2020 a las 16:20, Erik Kaashoek escribi¨®:
On Fri, Oct 2, 2020 at 07:05 AM, EB4APL wrote:
Where is this last version?
Both here:?/g/tinysa/files/tinySA-app
and here:?
_


Libre de virus.


Re: FW upgrade problems

 

Try download the .dfu file again and upgrade again as the version number displayed should at least be v1.1-4


Re: FW upgrade problems

 

I have forgotten (again) to clear the project before building and this messes up the version number displayed. V1.0-85 display V1.0-84. Need to improve my build environment.
This is what Erik has said before. It¡¯s likely that the same thing happened.


FW upgrade problems

 

¿ªÔÆÌåÓý

I am not able to upgrade the firmware.

Several days ago, I managed to upgrade to ver. 1.0-99.? As I recall, I was only able to get 1 of the 2 methods (dfu vs. bin) to work, but I don't remember which one.? I do realize that I don't need to use both methods.

Today I tried to upgrade to 1.1-5.? When using the DFUDemo app, it seemed to work correctly, upgrade & verify.? However, the TinySA still shows ver. 99 after a restart.? If I try with the .bin file method, I get an error that says "Cannot open DFU device 0483:df11."? This was probably the method that did not previously work.

Is there some other firmware update document other than the page at tinysa.org?? Anyone have any other ideas?

thanks

charlie


Re: File /tinySA-app/tinySA-App.exe uploaded #file-notice

 

On Fri, Oct 2, 2020 at 06:36 AM, Erik Kaashoek wrote:
I uploaded tinySA-app.exe, can someone test?
The new version does not work anymore with nanoVNA
The app ICON is not yet updated, need to spend some time to make a nice icon.
Erik,
? I downloaded v1.0.203 and had the following observations:

? 1.? Looks like you did manage to sneak a new icon in before release.
? 2.? The only confusing references I could still find to the NanoVNA were:
? ? ? ?a. Settings->VNA Settings:? Change to 'tinySA' Settings
? ? ? ?b. Settings -> Threshold: Remove or disable
? ? ? ?c. S1P and S2P buttons: For the tinySA one of these buttons is probably redundant.? Both recall the same waveform when using the M1-M3 buttons.

3? The 'mode' command does not return the current input mode, so there is no way to let the user know if the frequency range is inappropriate for the current input mode.
4.? If the entered frequency range changes from low to high, then there should be a warning alerting the user? to change ports at the applicable cross-over point.
5. Can the S11 | S21 notations in the following screen capture be changed to tinySA specific equivalents?




I haven't heard much from Cathy lately, but I suspect this version of tinySA-App would be more towards her liking.

- Herb