开云体育

I'm looking for some beta testers for a major FW upgrade.
The biggest change is the addition of the TRACE menu allowing much more flexibility in the usage of the 3 traces.
Also the MODIFY MARKER menu is? changed to reflect the changed way of working of the TRACE menu, markers can be placed on any trace and any marker can be a delta to any other marker.
As the change is substantial there could be some serious bugs in the FW so it is currently not recommended for mission critical use.

The important question is if the new menus are sufficiently self explanatory to not require documentation for the casual user.

In case you want to test, beta FW can be downloaded from:?





--

On Thu, Aug 5, 2021 at 09:54 AM, Erik Kaashoek wrote:

I'm looking for some beta testers for a major FW upgrade.

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-313beta.txt? 2021-08-05? 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-313-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 OFF
??????? ○ CALC OFF (or Tap on battery symbol)
???????????? o OFF (default)
???????????? o MIN HOLD
???????????? o MAX HOLD
???????????? o MAX DECAY
???????????? o AVER 4
???????????? o AVER 16
???????????? o QUASI PEAK
??? ○ ? 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
??? ? REFERENCE TRACE
??????? o REFERENCE 1
??????????? ? REFERENCE 1 (default)
??????????? ? REFERENCE 2
??????? o OFF
??????? ? 0Hz 0dBm (repeat 5 times)
??????????? FREQUENCY
??????????? LEVEL
??????????? DISABLE
??? ○ SWEEP TIME
??????? 0..600s, 0=disable
??? ?A 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
??????? 2 MHz
??????? 1 MHz

On Thu, Aug 5, 2021 at 12:54 AM, Erik Kaashoek wrote:

I'm looking for some beta testers for a major FW upgrade.
The biggest change is the addition of the TRACE menu allowing much more flexibility in the usage of the 3 traces.
Also the MODIFY MARKER menu is? changed to reflect the changed way of working of the TRACE menu, markers can be placed on any trace and any marker can be a delta to any other marker.
As the change is substantial there could be some serious bugs in the FW so it is currently not recommended for mission critical use.

The important question is if the new menus are sufficiently self explanatory to not require documentation for the casual user.

Erik,
? An additional noticeable change is in the DISPLAY menu.? Some menu options have been moved to the new TRACE Menu and others have been relocated or renamed within the DISPLAY menu.

? Users of the beta FW looking for DISPLAY->LIMITS will find that it has been renamed to DISPLAY->REFERENCE TRACE.? The name change seems meant to denote that the traces can be used for more than just creating limit lines.? "REFERENCE TRACE" seems like a name better suited for the TRACE menu.? Perhaps "REFERENCE LINE" or "DISPLAY LINE" would be more suitable for the DISPLAY menu.

?The new FW changes made to the Marker menu allow any of the 4 available markers to be assigned to any of the 3 traces.? The reference traces change values appropriately when the display units are changed as shown below.

?? ?? ?

? Besides the name changes and new functionality, what may confuse both new users and current users the most is that the three traces are shared between the DISPLAY-REFERENCE and TRACE menus.? This means that if you are using a? trace for displaying data then that same trace cannot be used as a reference trace - and vice-versa.

? Another noticeable feature that has been added is the new "trace value" console command.? It allows any of the traces to be sent to the PC for saving, using a serial console, and be restored a a later time.? It requires copy and pasting to and from the serial console, but does provide a means of saving and restoring trace data.

? Advanced users will appreciate the new Trace menu options that allow trace math operations to be performed between the 3 traces.

? ?The new menu options are well thought out and I was able to figure out their use without additional documentation.? The new FW features pretty much stay out of the way of new users, but provide additional measurement capability for those users that need it.

? When exiting out of the above screens using PRESET->LOAD STARTUP, I did notice a display artifact (solid white line at right hand bottom of the grid) was visible.



Herb

On Sat, Aug 7, 2021 at 09:42 AM, hwalker wrote:

Besides the name changes and new functionality, what may confuse both new users and current users the most is that the three traces are shared between the DISPLAY-REFERENCE and TRACE menus.? This means that if you are using a? trace for displaying data then that same trace cannot be used as a reference trace - and vice-versa.

Herb,
Valuable input.
Would it be better to have in the TRACE menu an option where you set the source of the trace to be either reference 1 or reference 2?
Under DISPLAY still can reference points?
This allows defining set of reference points independent of the traces.

Another option would be to add an option under the TRACE menu to set a trace to use REFERENCE data and you can edit the REFERENCE data from a TRACE/REFERENCE menu.
With 3 traces it is possible to give each trace an independent set of REFERENCE points.
Enabling REFERENCE for a trace should automatically disable TRACE/CALC, TRACE/SUBTRACT and enable TRACE/FREEZE

or??

--

On Sat, Aug 7, 2021 at 10:35 AM, Erik Kaashoek wrote:

Would it be better to have in the TRACE menu an option where you set the source of the trace to be either reference 1 or reference 2?
Under DISPLAY still can reference points?
This allows defining set of reference points independent of the traces.

Another option would be to add an option under the TRACE menu to set a trace to use REFERENCE data and you can edit the REFERENCE data from a TRACE/REFERENCE menu.
With 3 traces it is possible to give each trace an independent set of REFERENCE points.

Enabling REFERENCE for a trace should automatically disable TRACE/CALC, TRACE/SUBTRACT and enable TRACE/FREEZE

Erik,
? Once I understood how the DISPLAY->REFERENCE TRACE and normal TRACE menu options were mutually dependent I had no problems with navigating your current menus.? Other users may need more guidance, as you have proposed, to help them, employ the reference and measurement traces together.?

? Hopefully, other users will provide feedback regarding which of your suggested changes would help them more easily use the DISPLAY->REFERENCE TRACE and normal TRACE menu options.

Herb

How about adding under TRACE/CALC a TABLE option. Once CALC/TABLE is selected it is possible to edit the trace table (which effectively is what used to be called the REFERENCE table)
Each trace can be set to CALC/TABLE and it will take its values from the table.
This eliminates the concept of REFERENCE TRACE and replaces it with something that is hopefully more intuitive.

On Sun, Aug 8, 2021 at 02:27 AM, Erik Kaashoek wrote:

How about adding under TRACE/CALC a TABLE option. Once CALC/TABLE is selected it is possible to edit the trace table (which effectively is what used to be called the REFERENCE table)
Each trace can be set to CALC/TABLE and it will take its values from the table.
This eliminates the concept of REFERENCE TRACE and replaces it with something that is hopefully more intuitive.

?

Erik,
? My opinions:

? Since the table values are applied to one of the 3 measurement traces then I think moving the TABLE (REFERENCE TRACE) menu option to the TRACE menu makes good sense and would be more intuitive to the user.? Looking at the functions of the other menu options under the CALC menu, I question whether a TABLE menu option would be a logical fit there.? A better location would be directly under the TRACE menu but there is not a spare location there.

?Under the DISPLAY menu, if a DISPLAY LINE option could replace the REFERENCE TRACE option that? would be welcome.? This would be a line, like the trigger level line produced by your TRIGGER menu option, that is not associated with any of the measurement traces.? It would have ON|OFF|VALUE parameters.? Its value would be in the same units as the current display setting.? A DISPLAY LINE menu option should only be considered if you have sufficient FW space and the display line is disassociated from the TRACE menu - other than possibly as an additional option under the SUBTRACT menu (i.e. SUBTRACT DISPLAY LINE).

?Herb

Herb. Each trace should have its own table avoiding the complication of linking tables with traces.

On Sun, Aug 8, 2021 at 05:58 PM, Erik Kaashoek wrote:

Herb. Each trace should have its own table avoiding the complication of linking tables with traces.

Technically it is the only option use the traces for display lines. Otherwise the code will not fit.
--

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

For more info on the tinySA go to https://tinysa.org/wiki/

On Sun, Aug 8, 2021 at 05:58 PM, Erik Kaashoek wrote:

Herb. Each trace should have its own table avoiding the complication of linking tables with traces.

Technically it is the only option use the traces for display lines. Otherwise the code will not fit.
--

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

For more info on the tinySA go to https://tinysa.org/wiki/

?On Sun, Aug 8, 2021 at 05:58 PM, Erik Kaashoek wrote:

Herb. Each trace should have its own table avoiding the complication of linking tables with traces.

Technically it is the only option use the traces for display lines. Otherwise the code will not fit.
--

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

For more info on the tinySA go to https://tinysa.org/wiki/

Dear All,

As a long retired (medical) doctor, may I make a request on behalf of those who are not current or past professional electronic engineers, that the use of TinySa does not go down the road that Hewlett Packard did in the late 70’s / early 80’s.

To be brief, HP made a world leading bedside monitor for women in labour in the early 1970’s. It transformed medical practice on the labour ward. It had only two knobs to adjust and spewed out a long paper chart of uterine pressure and foetal heart rate at beat-to-beat resolution, so that the midwife/anaesthetist/ obstetric registrar/ consultant could look at current, past short term and long-term trends. Decisions during labour were suddenly backed up by hard data. For example, loss of beat-to-beat foetal heart rate (ie jitter) or serious heart rate dips after the end of a uterine contraction suggested the need for prompt Caesarian Section to save the baby.

BUT, their next version got polluted by their oscilloscope syndrome and was far too complex for your average stressed doctor or midwife to use, as Its front panel had dozens of knobs and buttons, just like their oscillocopes. Their Intensive Care monitoring kit was the same and their useless medical hardware resulted in shutting down the medical arm by the late 80’s and possibly contributed to their overall demise.

The TinySa is in danger of getting too complex. The new novice user might stare at the screen like a rabbit in headlights, if it gets tooooo complex to use. Maybe it is time to have a separate basic firmware and a “pro” firmware. Yes, you all reply, then do not update firmware, but fundamental improvements might be lost too, to the relative novice. I only switch my device on once every few weeks and have to “relearn” the menu structure every time.

Steve L ( retired Consultant anaesthetist, but with an Electrical Sciences degree, just for fun.)

On Sun, Aug 8, 2021 at 11:30 AM, Stephen Laurence wrote:

... then do not update firmware, but fundamental improvements might be lost too, to the relative novice. I only switch my device on once every few weeks and have to “relearn” the menu structure every time.

Steve,
? I'm sure you exaggerate about relearning the menu structure "every" time.? The addition of the Trace menu would be the first major restructuring of the tinySA menu in quite a while by Erik and it is pretty much to add the fundamental improvements that you fear loosing by not upgrading.

? I'm a long time user of the tinySA and Erik's goal has always been to make the UI as easily assessable to novices as to seasoned users of spectrum analyzers.? His product is aimed at the amatuer as well as students studying electrical sciences that include spectrum analysis in their course of study.? The proposed beta trace features will definitely benefit the latter class of users and are something that will definitely enhance my students learning.

? More importantly, the beta process is where user's can try out any new improvements and let Erik know if they need to be placed in a sub-menu that obscures them from novices because they make the UI too complex.?

?Almost every time Erik seems to make the right UI choice based on his own experience and user feedback.? I do still have my suspicions about the quasi-peak menu option :)

Herb??

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

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 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 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 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 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