开云体育

Is there anyway to change the colors of the traces?. I want to have the active t(fast) race, while using the delayed decay to be Yellow (not Red), In other words, the reverse as it is now. Thanks Don

Thanks Igor!

That looks to have resolved the issue. All self tests now pass.

This is the result of the tests requested by Erik:

After battery reset.?

A friend reported something similar (image attached). Then the command clearconfig was executed (initially it seems to have no effect).
Finally after disconnecting from the battery and reconnecting, tinySA alive again.?

Igor

I have also noticed a constant 1MHz saw tooth signal on the high port that starts right after turning the unit on.
No signal seen on the low port. Both checked using an oscilloscope.?

Doesn't look like there was any change.

Can you connect high and low with a good SMA cable and do after switching the device on:

• PRESET/STORE/FACTORY DEFAULTS

than switch the device off and on again and do:

• MODE/CALL OUTPUT/30MHz/return to LOW

and post a picture of the screen showing the 30MHZ calibration signal

DO NOT calibrate the tinySA or make any other adjustment.
Just what I describe above.
--

I received a new TinySA yesterday. After ensuring it was running the most recent fw it now fails all self tests.
It is able to perform the level calibration successfully but the signal generator fails to produce output and all self tests except number 11 fail.

Is there anything I can do to correct this or is this unit hosed?

Its a clone.
Too bad Mirfield is selling a clone again.
WIll remove them from the "where to buy" list
--

Hi all,

Just received a tinySA from Mirfield in the UK, an official supplier. Has ver 1.2-67 firmware on it, hardware revision 0.3.? Unfortunately it fails tests 7 and 10. I tried the following steps to recalibrate it.

1. Used supplied SMA between low-high, run level cal reset, level cal, self test. Still fails on tests 7, 10.
2. Used different SMA cable between low-high (known good), run level cal reset, level cal, self test. Still fails on tests 7, 10.
3. Connected it to PC and read config off it. leveloffset low was 5.6. I set that to 0.0. Self tests then pass.

Included photos below of the test failures.

Have I got a duff or marginal one or am I doing something wrong here or is there anything I can do?

Test 10 failure - stopband critical. Which looks like it's actually literally on the pass gate.



Test 7 failure - stopband fail. Appears slightly over the pass gate.



It looks like it made a passable effort but is slightly out somewhere. Is this safe to ignore?

Any help appreciated.

Best regards,

Chris

On Mon, Aug 9, 2021 at 11:25 PM, Erik Kaashoek wrote:

On Mon, Aug 9, 2021 at 09:22 AM, hwalker wrote:

One issue I noted while using the TABLE menu is that the table values under trace 3 (red trace) have a couple of presets that don't appear to be intentional (see below).? When I tried to disable the [0Hz 108zdBm] button a "FATAL ERROR" message appeared on the display screen and required me to power cycle the tinySA.?

new beta FW release that should solve this bug.
The table is now limited to 6 entries. The 8 in previous FW was incorrect causing memory corruption. Increasing to 8 entries may be possible in the future

Erik,
? ?Yes, the updated beta FW release solved the bug.? Users that need more than 6 entries for a limit line or conversion/correction factors can use an PC side text editor to construct a table and send values to the tinySA using the "trace value" command.

? The following issue occurred when turning off either trace 2 or 3 using the "trace # view off" console command.? The trace would turn off but then seconds later re-enable on its own. This does not happen with trace 1.

? Do you plan on adding a "trace # display" console command that allows the user to programmatically set the values of the TABLE entries?

Herb

On Wed, Jul 14, 2021 at 07:05 PM, Reginald Beardsley wrote:

A tracking generator

You can use a second tinySA as a generator for the first.

On Mon, Aug 9, 2021 at 09:22 AM, hwalker wrote:

One issue I noted while using the TABLE menu is that the table values under trace 3 (red trace) have a couple of presets that don't appear to be intentional (see below).? When I tried to disable the [0Hz 108zdBm] button a "FATAL ERROR" message appeared on the display screen and required me to power cycle the tinySA.?

new beta FW release that should solve this bug.
The table is now limited to 6 entries. The 8 in previous FW was incorrect causing memory corruption. Increasing to 8 entries may be possible in the future
?
--

On Mon, Aug 9, 2021 at 06:32 PM, Rudi wrote:

Flash tinySA when in DFU mode.
$ dfu-util -a 0 -D tinySA_v1.3-314-g86fc401.dfu

Sorry, wrong file name, correction:
$ dfu-util -a 0 -D tinySA_v1.3-314-g341000f.dfu

73, Rudi DL5FA

On Mon, Aug 9, 2021 at 05:18 PM, Erik Kaashoek wrote:

New beta release:
The REFERENCE trace no longer exists.

Hello Erik,
I have adopted my tinySA menu map.
As a text file for easier editing.
73, Rudi DL5FA

File: ReadMe_tinySA_menu_V1.3-314beta.txt? 2021-08-09? DL5FA

Home of tinySA firmware files:
??? http://athome.kaashoek.com/tinySA/DFU/beta/
Flash tinySA when in DFU mode.
$ dfu-util -a 0 -D tinySA_v1.3-314-g86fc401.dfu


Menu tree:
Legend: ? select ON/OFF
??????? ?A Select: Auto/ON/OFF

● PRESET
??? ○ LOAD STARTUP
??? ○ EMPTY 1 (or frequency span)
??? ○ EMPTY 2
??? ○ EMPTY 3
??? ○ EMPTY 4
??? ○ STORE
??????? STORE AS STARTUP
??????? STORE 1
??????? STORE 2
??????? STORE 3
??????? STORE 4
??????? FACTORY DEFAULTS

● FREQUENCY
??? ○ START
??? ○ STOP
??? ○ CENTER
??? ○ SPAN
??? ○ ZERO SPAN
??? ○ JOG STEP AUTO
??? ○ RBW? # if the RBW is reduced the span must be reduced.
??????? Auto (default)
??????? 3kHz
??????? 10kHz
??????? 30kHz
??????? 100kHz
??????? 300kHz
??????? 600kHz
??? ○ SHIFT FREQ

● LEVEL
??? ○ REF LEVEL
??????? AUTO (default)
??????? MANUAL
??? ○ SCALE/DIV
??? ○ ATTENUATE
??????? Auto (default)
??????? Manual
??? ○ UNIT
??????? dBm
??????? dBmV
??????? dBm?V
??????? Volt
??????? Watt
??? ○ EXTERNAL GAIN
??? ○ TRIGGER
??????? AUTO
??????? NORMAL (default)
??????? SINGLE
??????? TRIGGER LEVEL
??????? UP EDGE (default)
??????? DOWN EDGE
??????? MID TRIGGER
??? ? LISTEN

● TRACE
??? ○ TRACE 1,2,3 (yellow,green,red)
??? ○ ? ENABLE (default ON)
??? ○ ? FREEZE
??? ○ ? CALC TABLE (default ON)
???????? (or Tap on battery symbol)
???????? o OFF
???????? o MIN HOLD
???????? o MAX HOLD
???????? o MAX DECAY
???????? o AVER 4
???????? o AVER 16
???????? o QUASI PEAK
???????? o TABLE->TRACE (default ON)
???????????? ? 0Hz 0dBm (repeat 7 times)
??? ○ ? NORMALIZE
??? ○ ? SUBTRACT OFF
??????? o SUBTRACT OFF (default)
??????? o SUBTRACT TRACE 1
??????? o SUBTRACT TRACE 2
??????? o SUBTRACT TRACE 3
??? ○ ? COPY-?TRACE
??????? o ->TRACE 1
??????? o ->TRACE 2
??????? o ->TRACE 3

● DISPLAY
??? ? PAUSE SWEEP
??? ? WATER FALL
??? ○ SWEEP TIME
??????? 0..600s, 0=disable
??? ? SWEEP POINTS
?????????? ? 51 point
?????????? ? 101 point
?????????? ? 145 point
?????????? ? 290 point (default)
??? ○ SWEEP ACCURACY
??????? NORMAL (default)
??????? PRECISE
??????? FAST
??????? ?A FAST SPEEDUP
??????????? 2..29, 0=disable

● MARKER
??? ○ MODIFY MARKERS
??????? ■ MARKER 1
??????????? ? DELTA 1
??????????? ? NOISE
??????????? ? TRACKING (default)
??????????? TRACE 1
??????????????? o TRACE 1
??????????????? o TRACE 2
??????????????? o TRACE 3
??????????? ? TRACE AVERAGE
??????????? ■ SEARCH
??????????????? PEEK SEARCH
??????????????? MIN < LEFT
??????????????? MIN > RIGHT
??????????????? MAX < LEFT
??????????????? MAX > RIGHT
??????????????? ENTER FREQUENCY
??????????????? ? TRACKING (default)
??????????? DELETE
??????? ■ MARKER 2 same as above
??????? ■ MARKER 3 same as above
??????? ■ MARKER 4 same as above
??? ○ MARKER OPS
??????? START
??????? STOP
??????? CENTER
??????? SPAN
??????? REF LEVEL
??? ○ SEARCH MARKER
??????? PEAK SEARCH
??????? MIN < LEFT
??????? MIN > RIGHT
??????? MAX < LEFT
??????? MAX > RIGHT
??????? ENTER FREQUENCY
??????? ? TRACKING
??? RESET MARKERS

● MEASURE
??? ? OFF (default)
??? ? HARMONIC
??? ? OIP3
??? ? PHASE NOISE
??? ? SNR
??? ? -3dB WIDTH
??? ○ MORE
??????? ? AM
??????? ? FM
??????? ? THD
??????? ? CHANNEL POWER
??????? ? LINEAR

● CONFIG
??? TOUCH
??? SELF TEST? # OK
??? LEVEL CAL
??? VERSION
??? ? SPUR REMOVAL
??? ○ EXPERT CONFIG
??????? ? LOW OUTPUT
??????? LEVEL CORRECTION
??????? ?A IF FREQ
??????? ■ SCAN SPEED
??????????? ? SAMPLE DELAY
??????????? ? OFFSET DELAY
??????? SAMPLE REPEAT
??????? ■ MIXER DRIVE
??????????? +16dBm
??????????? +12dBm
??????????? +9dBm
??????????? +6dBm
??????? ■ MORE
??????????? ?A AGC
??????????? ?A LNA
??????????? ? BPF
??????????? ?A BELOW IF
??????????? DECAY
??????????? ATTACK
??????????? ○ MORE
??????????????? CORRECT FREQUENCY
??????????????? MINIMUM GRIDLINES
??????????????? CLEAR CONFIG password 1234
??????????????? ? PULSE HIGH (for external trigger)
??????????????? ■ CONNECTION
??????????????????? USB (default)
??????????????????? SERIAL
??????????????????? ■ SERIAL SPEED
??????????????????????? 19200
??????????????????????? 38400
??????????????????????? 57600
??????????????????????? 115200 (Default)
??????????????????????? 230400
??????????????????????? 460800
??????????????????????? 921600
??????????????????????? 1843200
??????????????????????? 2000000
??????????????????????? 3000000
??? DFU (for flashing firmware)

● MODE
??? Return to LOW in
??? Switch to HIGH in
??? Switch to LOW out
??? Switch to HIGH out
??? Cal.output: OFF
??????? 30 MHz
??????? 15 MHz
??????? 10 MHz
??????? 4 MHz
??????? 3 MHz
??????? 2 MHz
??????? 1 MHz

--------------

On Mon, Aug 9, 2021 at 08:18 AM, Erik Kaashoek wrote:

New beta release:
The REFERENCE trace no longer exists.
Now you can go to TRACE/CALC and select TABLE->TRACE and edit the table used for the trace.

Traces taking their data from a table can be used to normalize (e.g. using an antenna response table) or these can be used to draw lines on the display acting as visual limits

Erik,
? The "look and feel" of the TABLE menu under the TRACE menu is more intuitive.? One issue I noted while using the TABLE menu is that the table values under trace 3 (red trace) have a couple of presets that don't appear to be intentional (see below).? When I tried to disable the [0Hz 108zdBm] button a "FATAL ERROR" message appeared on the display screen and required me to power cycle the tinySA.? I performed a clearconfig and reset before using the new FW.? Traces 1 and 2 do not have this issue.



? ? ?"Traces taking their data from a table can be used to normalize (e.g. using an antenna response table) or these can be used to draw lines on the display acting as visual limits"

? ?I can see the TABLE menu being used in conjunction with the subtract menu to correct the measurement trace when using correction and conversion factors.? For example, conversion factors for a current probe or antenna could be entered into the table for trace 2 TABLE and subtracted from trace 1 so that the displayed units are effectively converted from dBUV to dBuA and dBuV to dBuV/m, respectively.
??
Herb

On Mon, Aug 9, 2021 at 03:31 AM, <tardivat@...> wrote:

Ability? to select EMC bandwidths like 9khz and 120khz with Quasi peak detector would be nice

Quasi peak detector is available and I hope someone will test it in zero span mode
And 10kHz seems close enough to 9kHz (given the more rectangular shape) and 100kHz RBW is actually 112kHz.

New beta release:
The REFERENCE trace no longer exists.
Now you can go to TRACE/CALC and select TABLE->TRACE and edit the table used for the trace.

Traces taking their data from a table can be used to normalize (e.g. using an antenna response table) or these can be used to draw lines on the display acting as visual limits

This approach saved some code space, which is in itself a positive, and it eliminated 2 menu's and eliminated the complex linking between reference tables and traces as now each trace has its own table.

Hope the midwives are still happy

The QRM guru? loop design is essentially "deaf" It will only work on very strong? interference sources.

Accurate signal levels can only be done with an antenna with a calibrated? antenna? factor chart for accuracy. In ham radio work there is very little need for such accuracy. The other problem is that you are not using a defined filter bandwidth and shape like the CISPR 9khz HF filter width so you will have to perform numerous calculations to come up with accurate results. Even if you did have access to an EMC receiver or spectrum analyzer you will need to use a Quasi peak detector with its associated dwell times can be very time-consuming. I am really struggling to understand why you would want to go through all this trouble when the test results relative a rough scan will be just as meaningless. Its a complex business measuring HF radio noise.

You will probably be better off? using a standard loop of wire? and a 1:1 braid break common choke to feeding a low noise preamp. The antenna factor is? easily predictable.? However detecting noise? below ITU rural quiet levels will always be a technical challenge with any broadband loop. Even the EMC fails to acknowledge that the antennas that they are using are too? much noise and are very poor antennas.? And you using a QRM.guru loop that is deaf to do a survey will produce?? an incorrect result.

Most EMC loops that costs thousands of dollars have very poor dynamic range when you use them outside the anechoic chamber. I have access to a Teseq, R&S, Emco and a couple of other professional EMC antennas and they are lousy performance in the real RF world. They suffer very badly from IMD and overload. Their main virtue is a? documented antenna factor. You would be far better investing in a Wellbrook or LZ1AQ? loop for a survey antenna.? Tuned loops produce the best results despite their narrow band issues.

A easy-to-use antenna like the Active rod with a 1 meter whip can easily be calibrated and produce good accurate results. You can look up the ENAMS project n Germany to give you some ideas. A 1 meter whip is technically not the correct antenna? to use in? all the EMC regulations for HF level monitoring. Like any active vertical antenna the ground plane plays a big rile and the feedline becomes part of the antenna unless you deal with this issue in a technical manner.
--
Henry