Re: Beta test channel - beta v1.1-52
#betatest
Thanks, Erik for quick response. ?
Yes, I was thinking it wasn¡¯t a problem as far as the device or measurements went, but was just reporting it in case others saw the same thing and you wanted to comment on it.?
Regards,?
-Steve
|
Re: Beta test channel - beta v1.1-51
#betatest
On Mon, Dec 14, 2020 at 07:22 AM, geoff M0ORE wrote:
A bit off current topic and I don't want to distract from topic but how do you get a self test from the app. I have v1.1.4.6 installed and can't see any mention of self test or config.
Geoff, ? ?TinySA-App has a serial terminal window that can be used to send commands to the tinySA.? To send a command to perform a self test do the following: ? 1. In the main TinySA-App window select the USB icon. ? 2. The TinySA VNA Comms window will open: ? ? ? a. Change the "Paused/Un-Paused" slider button to "Pause" to pause communications. ? ? ? b. Select the "Clear" button to clear the Comms window. ? ? ? c. Type 'selftest 0' in the User command input box and <Enter> on your keyboard. ? ? ? d. Self Test should now be running on the tinySA. ? ? ??  ?3.? If you only want to run an individual self test then type 'selftest 0 n', where n is the number of the self test to run (i.e. 'selftest 0 7' to run self test 7). ?4. When you are finished sending commands you can "Un-Pause" the Comms window and close it. ? - Herb
|
Re: Beta test channel - beta v1.1-51
#betatest
OK, Ta.
On 14/12/2020 15:26, Erik Kaashoek
wrote:
toggle quoted message
Show quoted text
There is no self test in the app, only local i=on the tinySA.
The problem with the app is its constant polling interferes with
the selftest initiated and executed locally.
--
------------------------------------------
For more info on the tinySA go to
|
Re: Beta test channel - beta v1.1-51
#betatest
There is no self test in the app, only local i=on the tinySA. The problem with the app is its constant polling interferes with the selftest initiated and executed locally. --
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/
|
Re: Beta test channel - beta v1.1-52
#betatest
Steve, The stop band error (test 7) you are seeing is not critical as it is on a large offset from the passband. --
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/
|
Re: Beta test channel - beta v1.1-51
#betatest
A bit off current topic and I don't want to distract from topic
but how do you get a self test from the app. I have v1.1.4.6
installed and can't see any mention of self test or config.
Geoff
On 14/12/2020 13:35, hwalker wrote:
toggle quoted message
Show quoted text
On Mon, Dec 14, 2020 at 12:14 AM, Erik Kaashoek wrote:
....The hangup was caused by a complicated race
condition around the ADC.
Hope its solved now in beta build v1.1-52
Good morning Erik,
? 1. Connected to tinySA using TinySA-App
? 2. Uploaded v1.1-52 successfully (clearconfig, reset, restore
leveloff values and deviceid)
? 3. Ran selftest 0 from TinySA-App Comms Window
? 4. Selftest completed completed with no errors ... but, USB
communications still dropped and selftest screen battery icon
values changing wildly.
? 5. Touching tinySA screen exits selftest and resets to home
screen.
? 6. I can manually reconnect to tinySA via TinySA-App.
? After step 6 above I manually performed a selftest
(Config->Selftest) and USB communications again dropped, but no
battery icon in self-test screen:
? ? ? ? 05.592 rx: timeout vbat? lines: 0? ?data: 0/0
? ? ? ? 05.611 tx: marker
? ? ? ? 05.640 tx: sweep
? ? ? ? 05.669 tx: mode
? ? ? ? 08.565 tx: vbat
? ? ? ? 08.595 tx: marker
? ? ? ? 08.627 tx: sweep
? ? ? ? 08.657 tx: mode
? ? ? ? 10.599 rx timeout .. disconnecting
I was able to manually reconnect USB communications and capture
the self-test screen:
? ?Config->Self Test
? ? 
? Comms: selftest 0? (last two digits of battery icon values
changing wildly)
?? 
I cycled power on the tinySA and restarted TinySA-App and USB
comm's still dropped (timeout vbat lines) during manual
selftest? and selftest 0 from Comms Window.? Main improvement
over previous FW version is that I can regain USB communications
manually, but still have issue with USB disconnecting during
selftest.
Windows 10, i7, x64
- Herb
|
For me, beta test code V 1.1-40, 49, 52 break self-test #7. All other tests pass.?
No problem found when reverting back to V 1.1-32.
Not sure if this is a one-off so decided to report it.?
 
Thanks!
-Steve
|
Re: Beta test channel - beta v1.1-51
#betatest
On Mon, Dec 14, 2020 at 05:49 AM, Erik Kaashoek wrote:
Do you also loose USB comms when connected with a terminal program or only when connected with tinySA-App?
tinySA-App continuously issues commands in the background task and these interfere with the selftest.?
In particular the reading of the battery level is problematic as it uses the same ADC as the touch decoder
Erik, ? ?1. No USB disconnection when running self test from PuTTY. ? ?2. Using stable v1.1-32, TinySA-App also drops USB connection when running self test.? I didn't recall this previously?occurring when capturing a self test screen, so it appears the current behavior is normal. ? ?3.? Based on your feedback I also ran a selftest from the Comms window with the "Pause" button selected, and there was no USB disconnection.? So a work around for the USB disconnection issue when running a self test is to "Pause" the Comms windows until the self test is complete. ? TinySA-App VNA Comms "Paused" before selftest 0.? No comport disconnection. ??  ? Now that I understand how to avoid the dropped USB connection this is no longer an issue for me, and with your changes, v1.1-52 behaves better than v1.1-32. ?- Herb
|
Re: Beta test channel - beta v1.1-51
#betatest
Do you also loose USB comms when connected with a terminal program or only when connected with tinySA-App? tinySA-App continuously issues commands in the background task and these interfere with the selftest.? In particular the reading of the battery level is problematic as it uses the same ADC as the touch decoder --
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/
|
Open the case temporarily connect Boot0 and Vdd on PCB edge close to the battery switch on the tinySA, you should get a black screen. no longer needed to connect Boot0 and VDD connect USB Now it should be possible to update the FW, preferably to stable version (not a beta version)
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/
|
Re: Beta test channel - beta v1.1-51
#betatest
On Mon, Dec 14, 2020 at 12:14 AM, Erik Kaashoek wrote:
....The hangup was caused by a complicated race condition around the ADC.
Hope its solved now in beta build v1.1-52
Good morning Erik, ? 1. Connected to tinySA using TinySA-App ? 2. Uploaded v1.1-52 successfully (clearconfig, reset, restore leveloff values and deviceid) ? 3. Ran selftest 0 from TinySA-App Comms Window ? 4. Selftest completed completed with no errors ... but, USB communications still dropped and selftest screen battery icon values changing wildly. ? 5. Touching tinySA screen exits selftest and resets to home screen. ? 6. I can manually reconnect to tinySA via TinySA-App. ? After step 6 above I manually performed a selftest (Config->Selftest) and USB communications again dropped, but no battery icon in self-test screen:
? ? ? ? 05.592 rx: timeout vbat? lines: 0? ?data: 0/0
? ? ? ? 05.611 tx: marker
? ? ? ? 05.640 tx: sweep
? ? ? ? 05.669 tx: mode
? ? ? ? 08.565 tx: vbat
? ? ? ? 08.595 tx: marker
? ? ? ? 08.627 tx: sweep
? ? ? ? 08.657 tx: mode
? ? ? ? 10.599 rx timeout .. disconnecting I was able to manually reconnect USB communications and capture the self-test screen: ? ?Config->Self Test ? ?  ? Comms: selftest 0? (last two digits of battery icon values changing wildly) ??  I cycled power on the tinySA and restarted TinySA-App and USB comm's still dropped (timeout vbat lines) during manual selftest? and selftest 0 from Comms Window.? Main improvement over previous FW version is that I can regain USB communications manually, but still have issue with USB disconnecting during selftest.
Windows 10, i7, x64
- Herb
|
After playing with the settings a white screen,not possible to update the firmware.Not possible to set the tinysa in dfu mode.After booting the sa isn't visible anymore.
Please help,
Victor
|
Re: Beta test channel - beta v1.1-51
#betatest
On Sun, Dec 13, 2020 at 06:34 AM, hwalker wrote:
I'm having the following issue after loading beta v1.1-51:
Hi Herb, The hangup was caused by a complicated race condition around the ADC. Hope its solved now in beta build v1.1-52 ? --
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/
|
Locked
Re: What to do when you think you bought a tinySA clone.
I always purchase through the "official" store and email Maggie.
No problem then either in getting original equipment or paying with Paypal.
Thanks again Erik for your commitment and patience.
Garry M0MGP
|
Locked
Re: What to do when you think you bought a tinySA clone.
That is true, harsh but true, some folks just have to learn the hard way...
John VE7KKQ
On Sun, Dec 13, 2020 at 6:47 PM §¡§ß§Õ§â§Ö§Û §¥§Ö§ß§Ú§ã§ð§Ü < lilo.chita@...> wrote: On Mon, Dec 14, 2020 at 09:31 AM, John wrote:
the source store for each is listed in the heading of the respective Groups.io page
Exactly.
But if someone choose to save couple of $ and purchase from suspicious source... Not a problem. Miser pays twice.?
|
Locked
Re: What to do when you think you bought a tinySA clone.
On Mon, Dec 14, 2020 at 09:31 AM, John wrote:
the source store for each is listed in the heading of the respective Groups.io page
Exactly. But if someone choose to save couple of $ and purchase from suspicious source... Not a problem. Miser pays twice.?
|
Locked
Re: What to do when you think you bought a tinySA clone.
To obtain either the nanovna or the Tinysa, the source store for each is listed in the heading of the respective Groups.io page, if you buy it from some other source, very good chance you got a clone, IMHO.
John VE7KKQ
On Sun, Dec 13, 2020 at 3:47 PM Brian Donaldson < brianb253@...> wrote: I believe the one I ordered is legit. But we will find out once I get it. If it is suspect I can take photos and post them. But blacklisting a seller is rather hard. I know when I got my NanoVNA it was questionable if it was legit or a clone.
We'll cross that bridge when we get to it. Thanks for the heads up. Brian D KF6BL
On Sat, Dec 12, 2020 at 11:27 PM Erik Kaashoek < erik@...> wrote: Open the tinySA case by removing the 4 screws
If the PCB is green, there are no shields on the PCB and the print on the PCB says "tinySA v0.4" you have a clone
Print you purchase details and put the tinySA PCB showing the "tinySA v0.4" text on the printout so the purchase details are still visible.
Make a photo of the purchase details printout with the PCB and a photo of the box with all the accessories of the tinySA and send these photos in a private reply to this message.
We will formally confirm in reply the product you bought is a clone and it is violating our trademark? so you can go back to your supplier and request a refund.
We will? contact the supplier using your purchase as evidence and request them to stop selling products that violate our trademark.
--
------------------------------------------
For more info on the tinySA go to
|
Locked
Re: What to do when you think you bought a tinySA clone.
I believe the one I ordered is legit. But we will find out once I get it. If it is suspect I can take photos and post them. But blacklisting a seller is rather hard. I know when I got my NanoVNA it was questionable if it was legit or a clone.
We'll cross that bridge when we get to it. Thanks for the heads up. Brian D KF6BL
On Sat, Dec 12, 2020 at 11:27 PM Erik Kaashoek < erik@...> wrote: Open the tinySA case by removing the 4 screws
If the PCB is green, there are no shields on the PCB and the print on the PCB says "tinySA v0.4" you have a clone
Print you purchase details and put the tinySA PCB showing the "tinySA v0.4" text on the printout so the purchase details are still visible.
Make a photo of the purchase details printout with the PCB and a photo of the box with all the accessories of the tinySA and send these photos in a private reply to this message.
We will formally confirm in reply the product you bought is a clone and it is violating our trademark? so you can go back to your supplier and request a refund.
We will? contact the supplier using your purchase as evidence and request them to stop selling products that violate our trademark.
--
------------------------------------------
For more info on the tinySA go to
|
Locked
Re: What to do when you think you bought a tinySA clone.
Agree with the "getting old quickly", I fear objecting to the payment medium would also be fruitless. Business in China is very different from the western world. Although the Chinese Government is trying to enforce patents and copyrights, I don't think it is done with much enthusiasm. The only way to put these clone masters out of business is not to buy their offerings. When things like the TinySA and the Nanovna are offered for sale by those who have done the development work and the prices are twenty to thirty dollars different, I will go for the originator of the device, that way I get not only the genuine article but support as well. Buy a clone, take yer chances, caveat emptor, no point in cheaping yourself into frustration and disappointment.
John VE7KKQ
I believe it is wishful thinking to believe a clone maker will stop their source of income if a few customers complain. I think you¡¯ll be lucky to receive a refund, and the maker will just make up the loss on a bunch of other customers who aren¡¯t as informed.
I¡¯d recommend hitting the maker where it hurts, their relationship with their payment processor. Dispute the charge with your payment provider ¡ª Paypal, credit card, whatever you used as payment. If Erik is willing to document the unit is a clone, so much the better for your dispute, but that might get old for Erik pretty quickly.
|
Locked
Re: What to do when you think you bought a tinySA clone.
I believe it is wishful thinking to believe a clone maker will stop their source of income if a few customers complain. I think you¡¯ll be lucky to receive a refund, and the maker will just make up the loss on a bunch of other customers who aren¡¯t as informed.
I¡¯d recommend hitting the maker where it hurts, their relationship with their payment processor. Dispute the charge with your payment provider ¡ª Paypal, credit card, whatever you used as payment. If Erik is willing to document the unit is a clone, so much the better for your dispute, but that might get old for Erik pretty quickly.
|
Garry Champion