Thanks for the responses guys! I was not aware that USB-C connectors differ from Micro-USB connectors. From what I can determine, the TinySA does utilize a USB-C connector but many of my other devices (including my NanoVNA SAA-2) use a Micro-USB connector. I guess that I am a little bit smarter than I was yesterday. I will order a longer USB-C cable for my TinySA.
Ed, K0KC
?
k0kc@...
http://k0kc.us/
|
As it didn't seem anyone understood what I wrote last, I started work on a tutorial to explain only to realized it already existed:
if you have data which matches either the time or the frequency display, you are doing the transform in the time domain. To get rid of the side lobes pick a time domain window function that suits you. There is no justification other than lack of memory for not offering all of them plus user defined. You just need room for the tables.
BTW On a log scale sinc**2 doesn't look as attractive as it does on a linear scale. Sorry about that. I'm not as habituated to the log domain as are EEs.
Have Fun!
Reg
|
USB-C is not keyed, doesn't matter which way they go, if the plug will not go into the socket, then either you have the wrong plug for the socket or you need to invert the plug, if that works, it is not USB-C.
John
On Sat, Aug 28, 2021 at 10:10 AM Niel Nielsen < Nieldk@...> wrote: Did you know. For some of these cables (USB C) it matters which is up and down. On the Chinese cables, you might wanna turn them.
On Sat, Aug 28, 2021, 18:41 John Cunliffe W7ZQ < n2nep@...> wrote: News to me,
Both original TinySA's I have feature standard USB-C connectors.
I never had any problems using a standard USB- C cable of any length. Just make sure you don't buy one of the Chinese charging only cables and you should be fine.
John
|
Did you know. For some of these cables (USB C) it matters which is up and down. On the Chinese cables, you might wanna turn them.
On Sat, Aug 28, 2021, 18:41 John Cunliffe W7ZQ < n2nep@...> wrote: News to me,
Both original TinySA's I have feature standard USB-C connectors.
I never had any problems using a standard USB- C cable of any length. Just make sure you don't buy one of the Chinese charging only cables and you should be fine.
John
|
News to me,
Both original TinySA's I have feature standard USB-C connectors.
I never had any problems using a standard USB- C cable of any length. Just make sure you don't buy one of the Chinese charging only cables and you should be fine.
John
|
Re: TinySA battery no longer charging
Looks like I had forgotten to use the "clearconfig 1234" command. Once this was done, the battery voltage is now working as expected on firmware v1.3-317.
After re-loading the firmware, I did a self test (all passed), and Level calibration. All appears to be working good now.
|
Re: tinySA with a larger screen
Agreed. Patience is important.
They seem to have no poll for wanted features for the larger (e.g. 4.3 inch) version. For example, I would like to see it have buttons, to replace the poor quality jogwheel.? For example, for the NanoVNA-F, they released both a wheel version and a newer button version (I use the latter).
|
As most of you already know, the supplied USB cable for the TinySA does not terminate in a standard USB-C connector at the TinySA end. I am interested in ordering a longer spare cable and was wondering what cable type to look for. Any? help would be appreciated! Thanks! --
Ed, K0KC
?
k0kc@...
http://k0kc.us/
|
Re: TinySA battery no longer charging
Hi Rudi, I will try the clearconfig command and report back...
|
Re: TinySA battery no longer charging
On Fri, Aug 27, 2021 at 01:34 AM, Lane Wilson wrote:
There appears to be a problem with the latest firmware release v1.3-317 !
Hello Lane, I am using firmware v1.3-317 and the battery voltage shows 4.27 V, see tinySA_v1.3-317_Batter-4.27V.jpg. Question: Did you "CLEAR CONFIG" after the firmware update? Menu->CONFIG->EXPERT CONFIG->MORE->MORE->CLEAR CONFIG, enter 1234 73, Rudi DL5FA
|
Re: Can't update firmware
I've been around computers long enough that I just know to try right-click when trying out software. As a former IBM OS/2 user right-click and I were good friends since long before Microsoft realized there was a right button.... 73 -Jim NU0C On Fri, 27 Aug 2021 08:41:52 -0700 "Terry Perdue" <K8tp@...> wrote: Oh, cool! How would anyone know to right-click the grid? Is there a Help
file somewhere?
On 8/26/2021 10:24 PM, Ted Chesley wrote:
Hi Terry, THX for the reply on the drivers, I remember I had to do that once. That info might help out someone with the same problem.
As to the TinySA interface with the TinySA-app, when connected, clicking on the four arrows next to the freq setting will set the application to agree with the TinySA, the start/stop freq , data points etc, but not the grid. You have to right click on the grid and enter the desired MIN/MAX settings with the manual set. The auto set can be used when there is a waveform in the screen.
Happy Hunting¡.Ted (KD7AQO)
On Aug 26, 2021, at 8:46 PM, Terry Perdue <K8tp@...> wrote:
?That¡¯s precisely what I found out the hard way today.
On Aug 26, 2021, at 8:11 PM, Jim Shorney <jshorney@...> wrote:
?
The thing that seems to bite a lot of people is that the Tiny/Nano gadgets are different device when in DFU mode and need a different driver. When connected to the computer in DFU mode you should see a "STM Device in DFU Mode" device appear in your USB tree under Device Manager. This driver is part of the DfuSe_Demo package but is not installed automatically. You have to hunt it down in the DfuSe folders and install it manually if it is not showing up. I've been told that it is needed for the app to upload firmware but I can't say because I already had it installed before the app came around.
73
-Jim
NU0C
On Wed, 25 Aug 2021 20:45:07 -0700
"Terry Perdue" <K8tp@...> wrote:
I'm not sure I understand that, but I should mention that I see that
when using the tinySA app, it /automatically /puts the device in DFU
mode. That works. But as you can see, it appears to be unable to 'open'
the device to write the file to it. I've tried many times.
On 8/25/2021 8:04 PM, Ted Chesley wrote:
Hey Terry, also forgot to add: you must be connected to the TinySA app
before you can use the upgrade. I think that's the case but I haven't
tried it before connection.
-----------------------------------------
From: "Terry Perdue"
To: [email protected]
Cc:
Sent: Wednesday August 25 2021 7:05:52PM
Subject: Re: [tinysa] Can't update firmware
? I don¡¯t see anything in the upgrade document about renaming any
file. Can you elaborate?
On Aug 25, 2021, at 5:08 PM, Larry Acklin <acklin@...> wrote: ?
I had the same issues. I used dfu-util, a bit of a PITA but
figured it out. You need to follow the how to and also rename the
file to what the batch file expects. It¡¯s a DOS based process but
mine is running latest and works- passes self test and Cal.
And Windows 10 needed to recognize the tinySA as a usb device-
running zadig helped get it recognized.
Good Luck
Larry
KB3CUF
On Wed, Aug 25, 2021 at 7:25 PM <K8tp@...> wrote: I've downloaded dfusedemo, version 3.0.6. With it running, I
connect the TinySA and put it in DFU mode, but the application
doesn't find it. If it's any help, when I enter DFU mode I get
the 'USB disconnect' sound.
I've viewed a couple of YouTube videos, and can't figure out
what I could be doing wrong. Also, if I click CHOOSE and
select the new .DFU file, the application reports that the
file doesn't have the correct format. Seems I have two
different issues.
|
Re: Can't update firmware
Thanks, Ted. I think the nanoVNA is next on my list, and it's good
to know the proper driver is ready for it. You sure can carry a lot
of decent test gear in your pocket now!
On 8/27/2021 9:08 AM, Ted Chesley
wrote:
toggle quoted message
Show quoted text
Terry, Yeah that's a problem with a lot of the software for these
devices, you basically have to muddle through the program to gain
familiarization with it. The TinySA app is a derivative from the
parent application: NanoVNA-app, which has a lot more functions to
support the VNA's. Also is the issue of the frequent firmware
updates which generally don't have detailed explanations of the
changes except as described in the rollout announcement messages
from the group sites, and message queries from users? However,
once relatively familiar with the programs use, it becomes second
nature. It is useful to go through the wiki info and docs on the
group sites, but much of the info is dated, and as the device FW
is frequently updated, it's a chore to keep up.?
By the way, I noticed this morning a post on the NanoVNA site
where a user had the same driver issue you did with DFU on his
NanoVNA and found the same solution (bootloader vs ST Micro in
DFU Mode) which fixed it with the correct selection. The driver
interface is the same for either the TinySA or the NanoVNA.
....Ted (KD7AQO)
-----------------------------------------
From: "Terry Perdue"
To: [email protected]
Cc:
Sent: Friday August 27 2021 8:41:56AM
Subject: Re: [tinysa] Can't update firmware
Oh, cool! How would anyone know to right-click the grid? Is
there a
Help
file somewhere?
On 8/26/2021 10:24 PM, Ted Chesley wrote:
> Hi Terry, THX for the reply on the drivers, I remember I
had
to do that once. That info might help out someone with the
same
problem.
>
> As to the TinySA interface with the TinySA-app, when
connected, clicking on the four arrows next to the freq
setting
will set the application to agree with the TinySA, the
start/stop
freq , data points etc, but not the grid. You have to right
click
on the grid and enter the desired MIN/MAX settings with the
manual
set. The auto set can be used when there is a waveform in the
screen.
>
> Happy Hunting¡.Ted (KD7AQO)
>> On Aug 26, 2021, at 8:46 PM, Terry Perdue
<K8tp@...> wrote:
>>
>> ?That¡¯s precisely what I found out the hard way
today.
>>> On Aug 26, 2021, at 8:11 PM, Jim Shorney
<jshorney@...> wrote:
>>>
>>> ?
>>> The thing that seems to bite a lot of people is
that
the Tiny/Nano gadgets are different device when in DFU mode
and
need a different driver. When connected to the computer in DFU
mode
you should see a "STM Device in DFU Mode" device appear in
your USB
tree under Device Manager. This driver is part of the
DfuSe_Demo
package but is not installed automatically. You have to hunt
it
down in the DfuSe folders and install it manually if it is not
showing up. I've been told that it is needed for the app to
upload
firmware but I can't say because I already had it installed
before
the app came around.
>>>
>>> 73
>>>
>>> -Jim
>>> NU0C
>>>
>>>> On Wed, 25 Aug 2021 20:45:07 -0700
>>>> "Terry Perdue" <K8tp@...>
wrote:
>>>>
>>>> I'm not sure I understand that, but I should
mention that I see that
>>>> when using the tinySA app, it /automatically
/puts
the device in DFU
>>>> mode. That works. But as you can see, it
appears
to be unable to 'open'
>>>> the device to write the file to it. I've
tried
many times.
>>>>
>>>>> On 8/25/2021 8:04 PM, Ted Chesley wrote:
>>>>> Hey Terry, also forgot to add: you must
be
connected to the TinySA app
>>>>> before you can use the upgrade. I think
that's
the case but I haven't
>>>>> tried it before connection.
>>>>>
>>>>> -----------------------------------------
>>>>>
>>>>> From: "Terry Perdue"
>>>>> To: [email protected]
>>>>> Cc:
>>>>> Sent: Wednesday August 25 2021 7:05:52PM
>>>>> Subject: Re: [tinysa] Can't update
firmware
>>>>>
>>>>> ? I don¡¯t see anything in the upgrade
document
about renaming any
>>>>> file. Can you elaborate?
>>>>>
>>>>>
>>>>>
>>>>>> On Aug 25, 2021, at 5:08 PM, Larry
Acklin
<acklin@...> wrote:
>>>>> ?
>>>>> I had the same issues. I used dfu-util, a
bit
of a PITA but
>>>>> figured it out. You need to follow the
how to
and also rename the
>>>>> file to what the batch file expects. It¡¯s
a
DOS based process but
>>>>> mine is running latest and works- passes
self
test and Cal.
>>>>>
>>>>> And Windows 10 needed to recognize the
tinySA
as a usb device-
>>>>> running zadig helped get it recognized.
>>>>>
>>>>>
>>>>> Good Luck
>>>>> Larry
>>>>> KB3CUF
>>>>>
>>>>>>> On Wed, Aug 25, 2021 at 7:25 PM
<K8tp@...> wrote:
>>>>>> I've downloaded dfusedemo, version
3.0.6.
With it running, I
>>>>>> connect the TinySA and put it in DFU
mode,
but the application
>>>>>> doesn't find it. If it's any help,
when I
enter DFU mode I get
>>>>>> the 'USB disconnect' sound.
>>>>>>
>>>>>> I've viewed a couple of YouTube
videos,
and can't figure out
>>>>>> what I could be doing wrong. Also, if
I
click CHOOSE and
>>>>>> select the new .DFU file, the
application
reports that the
>>>>>> file doesn't have the correct format.
Seems I have two
>>>>>> different issues.
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
>
>
|
Re: Can't update firmware
Terry, Yeah that's a problem with a lot of the software for these devices, you basically have to muddle through the program to gain familiarization with it. The TinySA app is a derivative from the parent application: NanoVNA-app, which has a lot more functions to support the VNA's. Also is the issue of the frequent firmware updates which generally don't have detailed explanations of the changes except as described in the rollout announcement messages from the group sites, and message queries from users? However, once relatively familiar with the programs use, it becomes second nature. It is useful to go through the wiki info and docs on the group sites, but much of the info is dated, and as the device FW is frequently updated, it's a chore to keep up.?
By the way, I noticed this morning a post on the NanoVNA site where a user had the same driver issue you did with DFU on his NanoVNA and found the same solution (bootloader vs ST Micro in DFU Mode) which fixed it with the correct selection. The driver interface is the same for either the TinySA or the NanoVNA.
....Ted (KD7AQO) ----------------------------------------- From: "Terry Perdue" To: [email protected]Cc: Sent: Friday August 27 2021 8:41:56AM Subject: Re: [tinysa] Can't update firmware
Oh, cool! How would anyone know to right-click the grid? Is there a
Help
file somewhere?
On 8/26/2021 10:24 PM, Ted Chesley wrote:
> Hi Terry, THX for the reply on the drivers, I remember I had
to do that once. That info might help out someone with the same
problem.
>
> As to the TinySA interface with the TinySA-app, when
connected, clicking on the four arrows next to the freq setting
will set the application to agree with the TinySA, the start/stop
freq , data points etc, but not the grid. You have to right click
on the grid and enter the desired MIN/MAX settings with the manual
set. The auto set can be used when there is a waveform in the
screen.
>
> Happy Hunting¡.Ted (KD7AQO)
>> On Aug 26, 2021, at 8:46 PM, Terry Perdue
<K8tp@...> wrote:
>>
>> ?That¡¯s precisely what I found out the hard way today.
>>> On Aug 26, 2021, at 8:11 PM, Jim Shorney
<jshorney@...> wrote:
>>>
>>> ?
>>> The thing that seems to bite a lot of people is that
the Tiny/Nano gadgets are different device when in DFU mode and
need a different driver. When connected to the computer in DFU mode
you should see a "STM Device in DFU Mode" device appear in your USB
tree under Device Manager. This driver is part of the DfuSe_Demo
package but is not installed automatically. You have to hunt it
down in the DfuSe folders and install it manually if it is not
showing up. I've been told that it is needed for the app to upload
firmware but I can't say because I already had it installed before
the app came around.
>>>
>>> 73
>>>
>>> -Jim
>>> NU0C
>>>
>>>> On Wed, 25 Aug 2021 20:45:07 -0700
>>>> "Terry Perdue" <K8tp@...> wrote:
>>>>
>>>> I'm not sure I understand that, but I should
mention that I see that
>>>> when using the tinySA app, it /automatically /puts
the device in DFU
>>>> mode. That works. But as you can see, it appears
to be unable to 'open'
>>>> the device to write the file to it. I've tried
many times.
>>>>
>>>>> On 8/25/2021 8:04 PM, Ted Chesley wrote:
>>>>> Hey Terry, also forgot to add: you must be
connected to the TinySA app
>>>>> before you can use the upgrade. I think that's
the case but I haven't
>>>>> tried it before connection.
>>>>>
>>>>> -----------------------------------------
>>>>>
>>>>> From: "Terry Perdue"
>>>>> To: [email protected]
>>>>> Cc:
>>>>> Sent: Wednesday August 25 2021 7:05:52PM
>>>>> Subject: Re: [tinysa] Can't update
firmware
>>>>>
>>>>> ? I don¡¯t see anything in the upgrade document
about renaming any
>>>>> file. Can you elaborate?
>>>>>
>>>>>
>>>>>
>>>>>> On Aug 25, 2021, at 5:08 PM, Larry Acklin
<acklin@...> wrote:
>>>>> ?
>>>>> I had the same issues. I used dfu-util, a bit
of a PITA but
>>>>> figured it out. You need to follow the how to
and also rename the
>>>>> file to what the batch file expects. It¡¯s a
DOS based process but
>>>>> mine is running latest and works- passes self
test and Cal.
>>>>>
>>>>> And Windows 10 needed to recognize the tinySA
as a usb device-
>>>>> running zadig helped get it recognized.
>>>>>
>>>>>
>>>>> Good Luck
>>>>> Larry
>>>>> KB3CUF
>>>>>
>>>>>>> On Wed, Aug 25, 2021 at 7:25 PM
<K8tp@...> wrote:
>>>>>> I've downloaded dfusedemo, version 3.0.6.
With it running, I
>>>>>> connect the TinySA and put it in DFU mode,
but the application
>>>>>> doesn't find it. If it's any help, when I
enter DFU mode I get
>>>>>> the 'USB disconnect' sound.
>>>>>>
>>>>>> I've viewed a couple of YouTube videos,
and can't figure out
>>>>>> what I could be doing wrong. Also, if I
click CHOOSE and
>>>>>> select the new .DFU file, the application
reports that the
>>>>>> file doesn't have the correct format.
Seems I have two
>>>>>> different issues.
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
>
>
|
Re: Can't update firmware
Oh, cool! How would anyone know to right-click the grid? Is there a Help file somewhere?
toggle quoted message
Show quoted text
On 8/26/2021 10:24 PM, Ted Chesley wrote: Hi Terry, THX for the reply on the drivers, I remember I had to do that once. That info might help out someone with the same problem.
As to the TinySA interface with the TinySA-app, when connected, clicking on the four arrows next to the freq setting will set the application to agree with the TinySA, the start/stop freq , data points etc, but not the grid. You have to right click on the grid and enter the desired MIN/MAX settings with the manual set. The auto set can be used when there is a waveform in the screen.
Happy Hunting¡.Ted (KD7AQO)
On Aug 26, 2021, at 8:46 PM, Terry Perdue <K8tp@...> wrote:
?That¡¯s precisely what I found out the hard way today.
On Aug 26, 2021, at 8:11 PM, Jim Shorney <jshorney@...> wrote:
?
The thing that seems to bite a lot of people is that the Tiny/Nano gadgets are different device when in DFU mode and need a different driver. When connected to the computer in DFU mode you should see a "STM Device in DFU Mode" device appear in your USB tree under Device Manager. This driver is part of the DfuSe_Demo package but is not installed automatically. You have to hunt it down in the DfuSe folders and install it manually if it is not showing up. I've been told that it is needed for the app to upload firmware but I can't say because I already had it installed before the app came around.
73
-Jim
NU0C
On Wed, 25 Aug 2021 20:45:07 -0700
"Terry Perdue" <K8tp@...> wrote:
I'm not sure I understand that, but I should mention that I see that
when using the tinySA app, it /automatically /puts the device in DFU
mode. That works. But as you can see, it appears to be unable to 'open'
the device to write the file to it. I've tried many times.
On 8/25/2021 8:04 PM, Ted Chesley wrote:
Hey Terry, also forgot to add: you must be connected to the TinySA app
before you can use the upgrade. I think that's the case but I haven't
tried it before connection.
-----------------------------------------
From: "Terry Perdue"
To: [email protected]
Cc:
Sent: Wednesday August 25 2021 7:05:52PM
Subject: Re: [tinysa] Can't update firmware
? I don¡¯t see anything in the upgrade document about renaming any
file. Can you elaborate?
On Aug 25, 2021, at 5:08 PM, Larry Acklin <acklin@...> wrote: ?
I had the same issues. I used dfu-util, a bit of a PITA but
figured it out. You need to follow the how to and also rename the
file to what the batch file expects. It¡¯s a DOS based process but
mine is running latest and works- passes self test and Cal.
And Windows 10 needed to recognize the tinySA as a usb device-
running zadig helped get it recognized.
Good Luck
Larry
KB3CUF
On Wed, Aug 25, 2021 at 7:25 PM <K8tp@...> wrote: I've downloaded dfusedemo, version 3.0.6. With it running, I
connect the TinySA and put it in DFU mode, but the application
doesn't find it. If it's any help, when I enter DFU mode I get
the 'USB disconnect' sound.
I've viewed a couple of YouTube videos, and can't figure out
what I could be doing wrong. Also, if I click CHOOSE and
select the new .DFU file, the application reports that the
file doesn't have the correct format. Seems I have two
different issues.
|
Re: Can't update firmware
Jim, NU0C has a picture for your message -- 73, Gyula HA3HZ 
|
Re: Can't update firmware
Hi Terry, THX for the reply on the drivers, I remember I had to do that once. That info might help out someone with the same problem.
As to the TinySA interface with the TinySA-app, when connected, clicking on the four arrows next to the freq setting will set the application to agree with the TinySA, the start/stop freq , data points etc, but not the grid. You have to right click on the grid and enter the desired MIN/MAX settings with the manual set. The auto set can be used when there is a waveform in the screen.
Happy Hunting¡.Ted (KD7AQO)
toggle quoted message
Show quoted text
On Aug 26, 2021, at 8:46 PM, Terry Perdue <K8tp@...> wrote:
?That¡¯s precisely what I found out the hard way today.
On Aug 26, 2021, at 8:11 PM, Jim Shorney <jshorney@...> wrote:
?
The thing that seems to bite a lot of people is that the Tiny/Nano gadgets are different device when in DFU mode and need a different driver. When connected to the computer in DFU mode you should see a "STM Device in DFU Mode" device appear in your USB tree under Device Manager. This driver is part of the DfuSe_Demo package but is not installed automatically. You have to hunt it down in the DfuSe folders and install it manually if it is not showing up. I've been told that it is needed for the app to upload firmware but I can't say because I already had it installed before the app came around.
73
-Jim
NU0C
On Wed, 25 Aug 2021 20:45:07 -0700
"Terry Perdue" <K8tp@...> wrote:
I'm not sure I understand that, but I should mention that I see that
when using the tinySA app, it /automatically /puts the device in DFU
mode. That works. But as you can see, it appears to be unable to 'open'
the device to write the file to it. I've tried many times.
On 8/25/2021 8:04 PM, Ted Chesley wrote:
Hey Terry, also forgot to add: you must be connected to the TinySA app
before you can use the upgrade. I think that's the case but I haven't
tried it before connection.
-----------------------------------------
From: "Terry Perdue"
To: [email protected]
Cc:
Sent: Wednesday August 25 2021 7:05:52PM
Subject: Re: [tinysa] Can't update firmware
? I don¡¯t see anything in the upgrade document about renaming any
file. Can you elaborate?
On Aug 25, 2021, at 5:08 PM, Larry Acklin <acklin@...> wrote: ?
I had the same issues. I used dfu-util, a bit of a PITA but
figured it out. You need to follow the how to and also rename the
file to what the batch file expects. It¡¯s a DOS based process but
mine is running latest and works- passes self test and Cal.
And Windows 10 needed to recognize the tinySA as a usb device-
running zadig helped get it recognized.
Good Luck
Larry
KB3CUF
On Wed, Aug 25, 2021 at 7:25 PM <K8tp@...> wrote: I've downloaded dfusedemo, version 3.0.6. With it running, I
connect the TinySA and put it in DFU mode, but the application
doesn't find it. If it's any help, when I enter DFU mode I get
the 'USB disconnect' sound.
I've viewed a couple of YouTube videos, and can't figure out
what I could be doing wrong. Also, if I click CHOOSE and
select the new .DFU file, the application reports that the
file doesn't have the correct format. Seems I have two
different issues.
|
Re: TinySA battery no longer charging
Somewhat of a mystery then. Could i have a setting wrong?
|
Re: tinySA app display doesn't match device display
Right-click on the graph area and you will find some handy options. 73 -Jim NU0C On Thu, 26 Aug 2021 21:15:55 -0700 "Terry Perdue" <K8tp@...> wrote: This is what I was referring to in my earlier post. Why is the app's
amplitude scaled differently than the device? (-90 to +10 vs. -100 to 0)
The noise floor isn't even visible.
On 8/26/2021 5:15 PM, Terry Perdue wrote:
Just curious - my tinySA display's default amplitude range is -100dBm
(bottom line) to 0dBm, but the app is displaying -90dBm to +10dBm. The
~-90dBm noise floor shows up on the device, but is mostly off-scale on
the app. Shouldn't the app mimic what's displayed on the device?
|
Re: TinySA battery no longer charging
I'm on firmware 313 and my SA sez 4.21V. 73 -Jim NU0C On Thu, 26 Aug 2021 16:34:22 -0700 "Lane Wilson" <lane.wilson.5811@...> wrote: Update: This appears to be a firmware problem. I opened the case and measured the battery voltage it was at 4.1v!
I had recently updated the firmware to v1.3-317-g9d82970.dfu from Erik's web site. That is when the battery voltage was being displayed as low.
I re-loaded firmware v1.3-265-ga0c410f.dfu and the battery voltage is now displayed in green and at 4.23V
There appears to be a problem with the latest firmware release v1.3-317 !
Lane
|
Re: tinySA app display doesn't match device display
This is what I was referring to in my earlier post. Why is the app's
amplitude scaled differently than the device? (-90 to +10 vs. -100
to 0) The noise floor isn't even visible.
On 8/26/2021 5:15 PM, Terry Perdue
wrote:
toggle quoted message
Show quoted text
Just
curious - my tinySA display's default amplitude range is -100dBm
(bottom line) to 0dBm, but the app is displaying -90dBm to +10dBm.
The ~-90dBm noise floor shows up on the device, but is mostly
off-scale on the app. Shouldn't the app mimic what's displayed on
the device?
|
John Cunliffe W7ZQ
Jim Shorney
Gyula Molnar