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
