开云体育

Hi,?
all files you are missing, you will find at ?
There are ?, dfu-util-static.exe? etc.??
Good luck, it works perfectly for me. You can also customize the BAT file according to your requirements.?

As my existing FW does not support the MENU command, so, I will have to update the FW. Previously, I reported that I was unable to update the FW via the Apps.

?

To implement Erik's recommendation of updating via DFU-UTIL, I have downloaded the file tinySA4_v1.4-177-g1687fbc.bin from . Then I renamed the file to tinySA.bin per the instruction at

?

Next, I looked for the dfu-util file per the instruction below.

?

?

I think the pink-text file in the list below is the correct one, and so, I downloaded it.

?

Extracting the zip file, the following files are shown:

?

?

According to the wiki, "For windows, open a command window and go to the folder with the downloaded files and run DFU_LOAD_BIN.bat. The tinySA should now be updating with the tinySA.bin file using dfu-util-static.exe ".

?

However, there is NO DFU_LOAD_BIN.bat. in the zipped file. Where did I go wrong?

?

73, Chin-Leong Lim, 9W2LC.

?

Hello and thank you for having me here.

?

I am using the tinySA as panorama adapter in a wideband receiver project. It gets controlled via serial commands from an ESP32. Depending on the band, the receiver uses either high injection or low injection. When I use high injection (LO above RF) the RF gets displayed mirrored (higher frequencies on the left side of the tinySA screen), so I would also need to reverse sweep direction. The sweep command does not accept a start frequency higher than the end frequency. Any ideas or workaround?

?

?

quite strange Hugen as I regularly buy electronic stuff from Aliexpress!

?

Thank you Erik, there's no hurry, don't worry, you'll look at it when you have less workload.

?

Toni

Stan Dye says: Toni, can you meanwhile get your desired behavior by just adding another trace command after the wait, before the screenshot? (or 16 traces if you want to ave16?)

?

Thanks Stan, I've tried your suggestions, but the SD_card commands are read so fast that when the command to capture the screen arrives, despite the fact that the frequencies are set, there hasn't even been time to perform any sweep and the trace hasn't been drawn. I've also tried it with the WAIT command without seconds argument and this freezes the ultra until I press the jog button. By pressing the jog it performs a full sweep and get paused, exiting the cmd script without having executed the remaining commands.

Does it happen yours differently?

?

Toni

Harm is used when lna is off, the other when the lna is on

You can change everything except there must be a first value at 30 MHz

?

--

Designer of the tinySA
For more info go to

ok, using the commandline, I found two table concerning harmonic mode - "correction harm" and "correction harm_lna".

They both contain values, one at 30MHz, and then starting at 4GHz up to 10GHz.

Which of the tables is the right to modify?

Can I just adjust some of the values above 6GHz according to my reference ?

?

Thanks,

Johann

I may have not yet added a menu for the harmonic table, should be present in command mode.

As I'm currently traveling I have no access to a tinySA

--

Designer of the tinySA
For more info go to

It is possible that Aliexpress cannot ship to your country, we will distribute to dealers in different countries after more testing of the LNA.

Hi, Erik

?

thank you for your response.

?

So, how can I access this harmonic table?

I could not find any info for that in the manual, maybe I missed it.

To correct above 6GHz would be very nice for me, because I have a signal generator available to make additional calibrations up to 12 GHz.

?

Thanks in advance,

Johann

?

There is a separate 20 point table for the harmonic mode.

Don't try to use the ultra table for the harmonic range as it will not be used

--

Designer of the tinySA
For more info go to

So, if I "steal" some calibration points to set calibration to higher frequencies, how many and which of them can I use without reducing the performance at the range up to 5.3 GHz too much?

Can you give some recommendation to that?

Regards,

Johann

Hi Erik,

Thanks for the answer. I will update the firmware later.

I don't think that is possible without knowing the antenna?

--

Designer of the tinySA
For more info go to

Hello. Is it possible to add the change of 诲叠μ痴/尘2?

Toni, can you meanwhile get your desired behavior by just adding another trace command after the wait, before the screenshot? (or 16 traces if you want to ave16?)

Hi Toni

Aha, yes, now I understand what is happening. Solving this will take some time as I'm rather busy at the moment.

--

Designer of the tinySA
For more info go to

This is what I get with two -15 dBm input signals 20 kHz apart.

?

?

?

With 20 dB of internal attenuation there is still a bit of overloading as the scan improves when I manually set 30 dB attenuation

?

?

You may be running a very old FW which is missing the later performance improvements in the automatic attenuator setting.

--

Designer of the tinySA
For more info go to

Erik, sorry, I misdefined the problem at the beginning: The WAIT command does stop the following commands from running in both the console and a . CMD. What happens is that when it is run from SD_card it also freezes the operation of the #ultra during the wait.

If we have CALC/AVER16 activated we can see better that when we send the above program from the console (I use TeraTerm V4.105), when reading the WAIT command it stops reading the commands for the wait time, meanwhile briefly informs on the screen with the sign 'Info:Waiting' and then continues to scan, perform the calculations and update the trace during the wait. Then, when the command to save the screenshot arrives, the screen is updated. This is the desired operation.

When we execute it from the SD_card, it leaves the screen frozen with the sign 'Info:Waiting', apparently without doing any other action during the wait. After waiting, when the command to save the screenshot arrives, the screen is not updated, but it is the one that was at the beginning of the wait.

?

Toni