Re: serial USB not recognized - a clone ? - "to be, or not to be, that is the question"
When I connect the tinySA to the USB port, it appears in device
manager on the Ports(COM & LPT) as "USB serial device (
COM6)".
As soon as I enter DFU mode via config, the device disappears
from the Ports list. On the tinySA app it appears on the upload
firmware as Port_#0003.hub_#0004 followed by a string of code.
Upload works OK. It also works on STMicroelectronics? Dfuse Demo.
Again, no indication on the device manager but it works.
On 10/02/2021 18:42, Wolfgang OE1MWW
wrote:
toggle quoted message
Show quoted text
On Wed, Feb 10, 2021 at 09:26 AM, Gyula Molnar wrote:
/g/tinysa/message/3040
interresting link, thanks for that. But all this can and will not
help in my setup, because
my tinySA (clone) is not shown as a com port device with a missing
driver. Therefore
DfuSeDemo? does not recognize my tinySA clone in DFU mode. The
STM32 Boot-
loader does not help.
The only indication I see is in Windows Device Manager on 'USB
Controller' as an
'Unknown Device' (see picture). My default com ports showing no
changes or new
entries if I plug in/power on the tinySA clone. Deinstalling the
'Unknown Device'
will bring it up after the next off/on cycle.
USBVIEW.exe (Microsoft) and USBDeview.exe (Nirsoft) showing all
kind of connected,
or even disconnected devices, but never ever any info/change by
the tinySA clone.
I guess, since the one message (see my previous post) says 'Error
29' Windows does
not know what type of? USB device has been connected - audio,
keyboard, com port,
or whatever. Looks like a garbled USB interface routine in the
firmware.
At the end, it's a lesson learned about crippled USB devices ;-)
73's de OE1MWW
Wolfgang
 
|
Re: Metal case for TinySA
I have had both my NanoVNA and my TinySA in the metal case for about a year. The cases has cut the RF noise by about 90%.
I attached a photo of them.
I also use a cut down pice of plastic phone screen protector over the displays.
Clyde Lambert KC7BJE?
|
Re: serial USB not recognized - a clone ? - "to be, or not to be, that is the question"
On Wed, Feb 10, 2021 at 09:26 AM, Gyula Molnar wrote:
/g/tinysa/message/3040
interresting link, thanks for that. But all this can and will not help in my setup, because my tinySA (clone) is not shown as a com port device with a missing driver. Therefore
DfuSeDemo? does not recognize my tinySA clone in DFU mode. The STM32 Boot-
loader does not help.The only indication I see is in Windows Device Manager on 'USB Controller' as an 'Unknown Device' (see picture). My default com ports showing no changes or new entries if I plug in/power on the tinySA clone. Deinstalling the 'Unknown Device' will bring it up after the next off/on cycle. USBVIEW.exe (Microsoft) and USBDeview.exe (Nirsoft) showing all kind of connected, or even disconnected devices, but never ever any info/change by the tinySA clone. I guess, since the one message (see my previous post) says 'Error 29' Windows does not know what type of? USB device has been connected - audio, keyboard, com port, or whatever. Looks like a garbled USB interface routine in the firmware. At the end, it's a lesson learned about crippled USB devices ;-) 73's de OE1MWW Wolfgang  
|
Re: serial USB not recognized - a clone ? - "to be, or not to be, that is the question"
|
I had the same issue. I let Windows 10 searching for the driver but it did not find one. Then I googled for 'STM32 Bootloader' and download the driver from?.
Now Windows was able to update and after putting the TinySA in DFU mode?DfuSeDemo sees it as 'STM Device in DFU Mode' . Thereafter I was able to download the latest firmware.
Regards, Rudi
|
Re: serial USB not recognized - a clone ? - "to be, or not to be, that is the question"
Gentlemen,
thanks for all your tips. Whatever port I plug in, or cable I am using, the tinySA never
shows up in com ports, just in the section of the 'USB Controller' section as an 'unknown device'
Right click and remove / deinstall and power cycling the tinySA results in the same info.
Windows 10/x64 Laptop:
Info: Unknown USB device (error requesting a device description)
in properties: This device stopped because it caused errors. (Code 43) An error occurred while solving the USB device descriptor.
Windows 7 Pro/x64
Info: Unknown device
in properties: This device does not work properly because the device firmware does not provide the necessary resources. (Code 29)
Windows 7Pro/x64
Today this PC did not even recognized the connected device, different cables, different ports, plug-in/plug-out cycling
Have no idea why.
Remark: I am using Windows 7 pro and Windows 10 in German language, the shown messages had been translated.
So, it looks like, the USB section in this clone has a fault and does not report it's device type to Windows.
FYI: I am a developer for Ham Radio software, 'CW via CAT' etc. , so I am pretty firm with all this com port stuff.
Never mind, a hopefully 'real tinySA' was ordered at Aliexpress Zeenko Store yesterday.
|
Re: serial USB not recognized - a clone ? - "to be, or not to be, that is the question"
Or even simpler: Goto device manager app Right click on faulty driver Click remove or uninstall drive unplug tinySA plug back in The driver may now install correctly If not, try again but when asked "remove driver from computer" or similar? say "Yes" ? --
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/
|
Re: serial USB not recognized - a clone ? - "to be, or not to be, that is the question"
Hi Wolfgang,
Hugen said a tip: USB-CDC
How to do it: download that pdf file and find the cdc download link and its installation in the description.
I hope this helps in the solution.
Link: http://ha3hz.hu/images/download/Preparing_to_run_NanoVNAPartner_on_Windows_XP_HU.pdf
--
73, Gyula HA3HZ
|
Re: Metal case for TinySA
I got two of the metal cases a few months ago; I think I made a post about it.
I only put my Tinysa in it a few weeks ago. I did it for physical protection, rather than for screening but it is good to know that the screening is effective. I managed it ok without any extra screws. I have not tried peeling the sticky label off the plastic case though.
I have bought a second Tinysa (mainly as a spare) so that will go in the other one. Fortunately it was not a clone and I sourced it in the UK so delivery was speedy.
I agree it is well worth it for a nanovna or Tinysa.
Steve L
|
Re: What to do when a selftest fails
Brad, KN4ODM, Vidas, N8AUM
I received the same CLONE - why do I know it's a clone?
Look at the picture, it says "HICH" and not "HIGH"
on the front panel. This is not a bad print, no, it's simply a typo. ?
73s
Wolfgang
OE1MWW
|
Locked
Re: What to do when you think you bought a tinySA clone.
Yeah, I did both, just to see what happens, for interests sake.
Things With IN connected to OUT, all's good, as expected. :)
|
Locked
Re: What to do when you think you bought a tinySA clone.
I suppose I can.? Since the thing works, I have always dislike "upgrading for the sake of upgrading", unless there are some supremely marvelous added features/enhancements.
1.0_91_g0f9078f is my current.
1.1_85-gb7ee0047.dfu is the latest?? What would it give over my current?? Asking, as he best listing I have found only goes up to 1.1_31.
Any known "nasties" in the '85 that have popped up?
Will get the flash program from ST & try it over the next few days.
Thanks!
As I mentioned, of you or the mods want to dump the pictures to keep the security for "genuine", feel free!
Joe? VE3IUW
|
If you own one of the original NanoVNA or the TinySA with the 2.8 inch screen there is one small problem, it either has no case or a plastic case. For the TinySA this becomes a problem when you live next to strong transmitters. Right up the hill from me is a strong pager transmitter and even with the inputs terminated with 50 ohm loads I see the signal when it comes on. I did some research and found this seller on e-bay that sells metal shells for the nanoVNA. Since the TinySA has the same footprint I bought a case to see if it will fix the problem. I had to scrape the paint of the mounting studs and the case screws to ensure a good ground connection, and since it is designed to take the place of the front panel for the NanoVNA it uses those screws ...so they will be missing when the case is used for the TinySA but lucky I have ample of M2.5x5 screws so I had no problem. Does it solve the issue? Yes it does, it even solves the ingress from my 900Mhz beacon I run at the house. Well worth the money. All that is needed now is to get a few white rub on letters to label the inputs and I will be ready to go. If they are out of stock, just wait a couple of days the seller replenishes the stock regularly. It took about a week to arrive.
John
|
Re: serial USB not recognized - a clone ? - "to be, or not to be, that is the question"
Erik, all kind of different cables and ports was the very first thing I tried - without success ?
|
Locked
Re: What to do when you think you bought a tinySA clone.
Sorry didn't care about the good test with cable . All look to be ok .
Le?mar. 9 f¨¦vr. 2021 ¨¤?21:39, F1RVC via <f1rvc.patrice= [email protected]> a ¨¦crit?: Hello, the result looks? like the self test has been done WITHOUT the cable between High and Low sockets.
Joe ,? did you connect the cable during the test or you missed it ?
Regards.
Le?mar. 9 f¨¦vr. 2021 ¨¤?20:22, Erik Kaashoek < erik@...> a ¨¦crit?: On Tue, Feb 9, 2021 at 11:21 AM, <josephk.p02@...> wrote:
Would you please check?
Looks good
Can you upgrade FW and run selftest? ? --
------------------------------------------
For more info on the tinySA go to
|
Locked
Re: What to do when you think you bought a tinySA clone.
Hello, the result looks? like the self test has been done WITHOUT the cable between High and Low sockets.
Joe ,? did you connect the cable during the test or you missed it ?
Regards.
Le?mar. 9 f¨¦vr. 2021 ¨¤?20:22, Erik Kaashoek < erik@...> a ¨¦crit?: On Tue, Feb 9, 2021 at 11:21 AM, <josephk.p02@...> wrote:
Would you please check?
Looks good
Can you upgrade FW and run selftest? ? --
------------------------------------------
For more info on the tinySA go to
|
Re: serial USB not recognized - a clone ? - "to be, or not to be, that is the question"
Try a USB 2.0 port
Try a different USB cable --
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/
|
Re: serial USB not recognized - a clone ? - "to be, or not to be, that is the question"
On Tue, Feb 9, 2021 at 10:01 AM, Hugen wrote:
... unless their USB port is installed incorrectly
Thanks Hugen for the info, I guess so. If I connect, I just see in 'USB-Controller' an 'Unknown Device' and in this device property: This device does not work properly because the device firmware does not provide the necessary resources. (Code 29) Installed the drivers out of en.stsw-stm32080.zip with no sucess for the tinySA.
Looks like, there is no info from this 'tinySA' to tell Windows what kind of USB device it is, therefore no driver is selected to activate a com port. This has been tried on two different Win 7 Pro PC and on my Win 10 Laptop. Otherwise this thingy shows on inputs & touch display what it should do. But no com port...? :-(
|
Locked
Re: What to do when you think you bought a tinySA clone.
On Tue, Feb 9, 2021 at 11:21 AM, <josephk.p02@...> wrote:
Would you please check?
Looks good
Can you upgrade FW and run selftest? ? --
------------------------------------------
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.
Greetings, Eric: Going through the thread, I would like to think my purchase via Amazon.ca is a genuine article. Would you please check? Also trying to figure out the firmware details. The presentation case appears legit, as per a previous poster's photo. I am enclosing pictures.? If you wish, please delete images, so you can keep the security intact.? The board colour isn't quite as described, so that raised a flag. Thank you! Joe VE3IUW     
|
Clyde Lambert
Gyula Molnar
John Cunliffe W7ZQ