|
The wiki has one page on the PC SW for the tinySA
More to come
|
? ? Its good to know the tinySA will already have usable software when it is offered for sale.? Linux and Mac users will especially be happy to know that a cross-platform python derivative of Nano-Saver for the tinySA will be available.
? ? As a side note, on your PC SW wiki page, the screenshot of the Windows tinySA application shows the correct marker amplitude value for the? 25 MHz fundamental, but the 50 and 75 MHz harmonic marker amplitude values are off by 15 dB? from the display scaling (see attachment).? I was just curious about that.
- Herb
? ?
|
Hi Herb It is relative to the carrier level ? Kind regards Kurt ? ? ? ? Its good to know the tinySA will already have usable software when it is offered for sale.? Linux and Mac users will especially be happy to know that a cross-platform python derivative of Nano-Saver for the tinySA will be available.
? ? As a side note, on your PC SW wiki page, the screenshot of the Windows tinySA application shows the correct marker amplitude value for the? 25 MHz fundamental, but the 50 and 75 MHz harmonic marker amplitude values are off by 15 dB? from the display scaling (see attachment).? I was just curious about that.
- Herb
? ?
|
On Sun, May 3, 2020 at 07:16 AM, Kurt Poulsen wrote:
Hi Herb
It is relative to the carrier level ?
Kind regards
Kurt
?
Thanks Kurt. I didn't consider that.? I'm used to seeing dBc units for measurements relative to the carrier level.? Herb
|
Well...
Untill 4 days ago I did not know about dBc. Will change unit when switching to relative marker
|
On 5/3/20 6:36 AM, hwalker wrote:
the 50 and 75 MHz
harmonic marker amplitude values are off by 15 dB
It looks like the 50 and 75 MHz level might be relative to the 25
MHz level.
|
I see Kurt beat me to it.? Note to self: check to see if there are other replies before responding.
|
On Sun, May 3, 2020 at 12:21 PM, Jim Allyn - N7JA wrote:
I see Kurt beat me to it.? Note to self: check to see if there are other replies before responding.
Jim, ? ?Thanks for chiming in.? Yes, both Kurt and Erik responded.? Don't let it stop you from adding any other useful insights you have regarding the tinySA.? Its really shaping up to be another useful instrument in the same vein as the NanoVNA that hams and hobbyist didn't have in their toolbox just a couple of years ago. ? ?Attached to a computer and with additional EMC related accessories, it will be interesting to see how it shapes up as a pre-compliance measurement system below 300 MHz. - Herb
|
Hi Erik I downloaded the ? and when starting it reports MSVCP100D missing. As far I have figure out it is a file implemented in the code for debugging code created with Visual Studio 2010. How to solve ? Kind regards Kurt ? ? The wiki has one page on the PC SW for the tinySA
More to come
|
On Tue, May 5, 2020 at 07:28 AM, Kurt Poulsen wrote:
Hi Erik
I downloaded the ? and when starting it reports MSVCP100D missing. As far I have figure out it is a file implemented in the code for debugging code created with Visual Studio 2010.
? ? ? ?Kurt,
? ? ? ? ? ?You are correct, the "D" suffix indicates the executable that created the error is not a release version and not normally intended for distribution ( for software debugging?as you noted).? The release version will use the MSVCP100.dll that is already present in your Windows System32 directory.
? ? ? ?If you want to get a jump start on using the tinySA Windows application you will have to ask Erik for a release version of the application, or hunt down the?MSVCP100D and MSVR100D dll 's on the internet for use with the pre-release application.
? - Herb?
|
My mistake,
Release version uploaded.
Can you test if this runs?
When the selector bock pop's up you can select "mockup" and the SW will run with a simulated source
|
Hi Herb Thank you for the info, then I was right ? I am sure Erik will send me one when needed or put it on the group Kind regards Kurt ? ? ? On Tue, May 5, 2020 at 07:28 AM, Kurt Poulsen wrote: Hi Erik I downloaded the ? and when starting it reports MSVCP100D missing. As far I have figure out it is a file implemented in the code for debugging code created with Visual Studio 2010.
? ? ? ?Kurt,
? ? ? ? ? ?You are correct, the "D" suffix indicates the executable that created the error is not a release version and not normally intended for distribution ( for software debugging?as you noted).? The release version will use the MSVCP100.dll that is already present in your Windows System32 directory.
? ? ? ?If you want to get a jump start on using the tinySA Windows application you will have to ask Erik for a release version of the application, or hunt down the?MSVCP100D and MSVR100D dll 's on the internet for use with the pre-release application.
? - Herb?
|
Argggggg
Do not try, something wrong
|
On Tue, May 5, 2020 at 08:48 AM, Kurt Poulsen wrote:
Hi Herb
Thank you for the info, then I was right ?
I am sure Erik will send me one when needed or put it on the group
==================================================== Kurt, ? ? In case you missed Erik's reply he has already re-uploaded a release version that runs in a mock-up mode. I just tried it and it runs fine in the mock-up mode for previewing the application's features. - Herb - Herb
|
On Tue, May 5, 2020 at 08:56 AM, <erik@...> wrote:
Argggggg
Do not try, something wrong
=============================================== ? ?Too late Erik.? I tried the executable before I read your reply and it ran without dll error on my Windows 10 x64 system (see attachment).? I received a MSVCR100D and MSVCP100D dll error when trying to run your prior upload. - Herb
|
On Tue, May 5, 2020 at 09:09 AM, hwalker wrote:
On Tue, May 5, 2020 at 08:56 AM, <erik@...> wrote:
Argggggg
Do not try, something wrong
===============================================
? ?Too late Erik.? I tried the executable before I read your reply and it ran without dll error on my Windows 10 x64 system (see attachment).? I received a MSVCR100D and MSVCP100D dll error when trying to run your prior upload.
- Herb
=================================================== You're right Erik, ? ?The application loads OK in the mock-up mode, but clicking single sweep or run results in a "Input string was not in a correct format" exception. - Herb
|
Can you test if the updated version works better?
|
Hi Erik Nope, got this nice message Kind regards Kurt 
? ? Can you test if the updated version works better?
|
Hi Erik After the nice warning clicked OK it started Repeated start it gave no error message, but in the mockup it gives new meassge, but of course I have no idea what is allowed Kind regards Kurt ? 
? Can you test if the updated version works better?
|
On Tue, May 5, 2020 at 12:34 PM, Kurt Poulsen wrote:
Hi Erik
After the nice warning clicked OK it started
Repeated start it gave no error message, but in the mockup it gives new meassge, but of course I have no idea what is allowed
==============================================
Erik, ? I receive a did different exception than Kurt.? ?The new version starts up O.K. automatically in the mock-up mode, but if I hit single the single sweep or run button I get the same string format exception previously reported. 
- Herb
|
Kurt Poulsen
Jim Allyn - N7JA
