TinySA Ultra and TinySA App

Ed Wilson All Messages By This Member #8378 Colleagues, I have owned a TinySA for quite a while now and just received a new TinySA Ultra yesterday (the screen was aligned properly). The Ultra seems to be working well stand alone, but I am having some issues when using it with TinySA-App v1.1.20.1. Since I usually use the TinySA-App when making measurements, I would appreciate any suggestions for resolving an issue which I am experiencing. When I use the TinySA Ultra I seem to get a "Disconnect" after several minutes of apparently normal operation. I was originally running at the default baud rate of 115200 and reduced the baud rate to 19200 but the problem persists. As a test, I exchanged the TinySA Ultra for my original TinySA and have not experienced a disconnect for at least an hour of operation so far. I should mention that I am running Windows 10 and have ensured that the COM port is running at the same baud rate as the TinySA-App. I have also experienced this issue on two different computers, one running 32-bit Windows 10 and the other running 64-bit Windows 10. Suggestions would be appreciated! -- Ed, K0KC ? k0kc@... http://k0kc.us/
Wolfgang OE1MWW All Messages By This Member #8379 Ed, did you disable the 'power management option' of your USB port? If there is no traffic on the USB port, Windows will shut it down after certain periode of time. 73's de OE1MWW Wolfgang Google: "How to Disable Power Management for USB connected Devices"
pe1hwo All Messages By This Member #8381 It would nice to be able to enter 12GHz as a stop frequency? (for exploring the high band) in the TinySA App v1.1.20.1 max seems 9900 MHz.
Ed Wilson All Messages By This Member #8382 On Fri, Dec 9, 2022 at 09:09 AM, Wolfgang OE1MWW wrote: "How to Disable Power Management for USB connected Devices" Wolfgang, Thanks for the suggestion...I should have thought of that myself. I did disable all power management on both computers and changed the baud rate back to 115200. I am currently testing the TinySA Ultra again and will let you know if? your suggestion has fixed the problem. I am not sure why my old TinySA did not disconnect, but if this change fixes the problem, then I will not worry about it. Thanks again!!! ? -- Ed, K0KC ? k0kc@... http://k0kc.us/
Ed Wilson All Messages By This Member #8383 Well, it looks like I spoke too soon! The TinySA Ultra froze-up after about 5 minutes of operation and disconnected shortly thereafter. The only way to recover was to turn the TinySA Ultra off and on again and to close and restart the TinySA App. Still looking for suggestions...perhaps a bug??? -- Ed, K0KC ? k0kc@... http://k0kc.us/
Erik Kaashoek All Messages By This Member #8384 Here is no real flow control between the tinySA and the App. Just big buffers As the Ultra is faster there could be a buffer overflow I did not yet detect I will do some more tests And the baudrate setting does not have any impact? -- For more info on the tinySA go to https://tinysa.org/wiki/
Ed Wilson All Messages By This Member #8385 More intel...my original TinySA froze-up after about an hour of normal operation. -- Ed, K0KC ? k0kc@... http://k0kc.us/
hwalker All Messages By This Member #8386 On Fri, Dec 9, 2022 at 10:50 AM, Erik Kaashoek wrote: Here is no real flow control between the tinySA and the App. Just big buffers As the Ultra is faster there could be a buffer overflow I did not yet detect I will do some more tests And the baudrate setting does not have any impact? Erik, ? I tried to duplicate Ed's disconnect issue and could only due so after switching focus to another application.? When I switched back to tinySA-App (after a few minutes in the other application) communications had stopped, and the USB log had the following entries: rx link timeout .. disconnecting connect: serial port connecting .. connect: serial port connected 43.494? serial error connect SetCommState [31] A device attached to the system is not functioning. 43.528 tx: help 58.476 rx link timeout .. disconnecting Herb
Erik Kaashoek All Messages By This Member #8387 Can this be confirmed by other people seeing lock up? It only seems to happen when App does not have focus? -- For more info on the tinySA go to https://tinysa.org/wiki/
Ed Wilson All Messages By This Member #8388 Thanks for looking into this issue, Erik! -- Ed, K0KC ? k0kc@... http://k0kc.us/
Ed Wilson All Messages By This Member #8389 Erik, I am now running the TinySA App with the TinySA Ultra. This is the only app running and it has "focus". In this latest test it locked-up after about 5 minutes and disconnected. I set the app for 500 points per scan and a RBW of 300 KHz. The center frequency was 144.174 MHz and the span was 2 MHz. -- Ed, K0KC ? k0kc@... http://k0kc.us/
hwalker All Messages By This Member #8390 On Fri, Dec 9, 2022 at 01:04 PM, Ed Wilson wrote: Erik, I am now running the TinySA App with the TinySA Ultra. This is the only app running and it has "focus". In this latest test it locked-up after about 5 minutes and disconnected. I set the app for 500 points per scan and a RBW of 300 KHz. The center frequency was 144.174 MHz and the span was 2 MHz. -- Ed, K0KC ? k0kc@... http://k0kc.us/ Ed, ? Could you turn on the COMM dialog box (click on the USB icon next to the camera icon) and copy and paste the error message that occurs when a disconnect occurs?? It will probably be the same timeout message I received, but may provide Erik with additional info as to why your disconnection occurs so quickly. Herb
mike All Messages By This Member #8391 开云体育 ? To add to the test results ? Using TinySA App v1.1.20.1 on Windows 10 and? TinySA Ultra - TinySA4 - HW V0.4.5.1 - firmware V1.3-512 Connect via Com 4 - 100 to 137 mHz scan Stops after approx 10 minutes, App header shows 'not responding’ then after about 30 seconds status shows 'Disconnected' - still lists a com port 4 - try connect - shows connect for 10? seconds then back to disconnected - . Restart TinySa App - com port 4 shown - try connect - shows connected, then disconnected - try connect again but no response ?stays stuck with status disconnected Pull out USB cable from PC and plug back in - no com port 4 shown - windows alerts? USB device not recognised Disconnected USB – found the TinySA screen is frozen Restart TinySA - connect via USB to PC - com port 4 is now back - TinySA App connected OK – after another 10 minutes we have the same failure At the point of the failure the USB Comms show - rx link timeout .. disconnecting ? Mike Smith G8EII ? toggle quoted message Show quoted text From: [email protected] <[email protected]> On Behalf Of hwalker Sent: 09 December 2022 21:21 To: [email protected] Subject: Re: [tinysa] TinySA Ultra and TinySA App ? On Fri, Dec 9, 2022 at 01:04 PM, Ed Wilson wrote: Erik, I am now running the TinySA App with the TinySA Ultra. This is the only app running and it has "focus". In this latest test it locked-up after about 5 minutes and disconnected. I set the app for 500 points per scan and a RBW of 300 KHz. The center frequency was 144.174 MHz and the span was 2 MHz. -- Ed, K0KC ? k0kc@... Ed, ? Could you turn on the COMM dialog box (click on the USB icon next to the camera icon) and copy and paste the error message that occurs when a disconnect occurs?? It will probably be the same timeout message I received, but may provide Erik with additional info as to why your disconnection occurs so quickly. Herb
MirekD All Messages By This Member #8398 开云体育 My TinySA Ultra +TinySA App v1.1.20.1 on Windows 10? (64b)? behaves very similarly. Mirek Dne 09.12.2022 v 23:45 mike napsal(a): toggle quoted message Show quoted text To add to the test results ? Using TinySA App v1.1.20.1 on Windows 10 and? TinySA Ultra - TinySA4 - HW V0.4.5.1 - firmware V1.3-512 Connect via Com 4 - 100 to 137 mHz scan Stops after approx 10 minutes, App header shows 'not responding’ then after about 30 seconds status shows 'Disconnected' - still lists a com port 4 - try connect - shows connect for 10? seconds then back to disconnected - . Restart TinySa App - com port 4 shown - try connect - shows connected, then disconnected - try connect again but no response ?stays stuck with status disconnected Pull out USB cable from PC and plug back in - no com port 4 shown - windows alerts? USB device not recognised Disconnected USB – found the TinySA screen is frozen Restart TinySA - connect via USB to PC - com port 4 is now back - TinySA App connected OK – after another 10 minutes we have the same failure At the point of the failure the USB Comms show - rx link timeout .. disconnecting ?
Ed Wilson All Messages By This Member #8403 Herb, I let the TinySA Ultra run this morning and it disconnected after about 10 minutes of apparent normal operation. I am still running firmware 1.3-512-gd99d679 built on December 3. I updated to this version upon receipt of the TinySA Ultra yesterday. I have not updated to the version released today since Erik did not mention any fix for my problem. The log provided the following information after the disconnect: 42.222 rx: ch> 42.238 tx: sweep start 143174000 42.300 rx: sweep start 143174000 42.300 rx: ch> 42.316 tx: sweep stop 145174000 42.363 rx: sweep stop 145174000 42.379 rx: ch> 42.379 tx: scanraw 143174000 145174000 500 42.441 rx: scanraw 143174000 145174000 500 42.738 rx: 1502 bytes received 42.738 rx: ch> 42.754 tx: sweep start 143174000 42.813 rx: sweep start 143174000 42.813 rx: ch> 42.829 tx: sweep stop 145174000 42.860 rx: sweep stop 145174000 42.860 rx: ch> 42.876 tx: scanraw 143174000 145174000 500 42.907 rx: scanraw 143174000 145174000 500 43.299 rx: 1502 bytes received 43.299 rx: ch> 43.315 tx: sweep start 143174000 43.362 rx: sweep start 143174000 43.377 rx: ch> 43.393 tx: sweep stop 145174000 53.608 rx link timeout .. disconnecting I doubt if this information will assist Erik in his troubleshooting, but per your suggestion, I am sharing this anyway. Ed, K0KC ? k0kc@... http://k0kc.us/
Erik Kaashoek All Messages By This Member #8404 I can replicate the problem. Does the "Points per scan" setting have an impact on how soon it hangs? -- For more info on the tinySA go to https://tinysa.org/wiki/
Ed Wilson All Messages By This Member #8407 Erik, I know that 500 points per scan results in the problem and I think that 1000 points per scan also results in the problem. I have not tried other values. -- Ed, K0KC ? k0kc@... http://k0kc.us/
Ed Wilson All Messages By This Member #8409 Erik, I just ran it at 290 points per scan and probably got a couple of more minutes before it disconnected (about 12 minutes vs. 10 minutes). -- Ed, K0KC ? k0kc@... http://k0kc.us/
Wolfgang OE1MWW All Messages By This Member #8417 tinySA Ultra, setup: - tinySA4_v1.3-513-g92dd4b2 - HW Version:V0.4.5.1 - tinySA-App 1.1.20.1 by OneOfEleven and Erik In 'continuous scan' (118 to 136 Mhz) the tinySA Ultra is freezing after around 5 minutes, and the last serial message (in text mode, captured with 'Serial Port Monitor' software) is: ‘.虫补.虫1.虫±.虫..虫?.虫?.虫础.虫±.虫?.虫?.虫‘.虫础.虫础.虫补.虫?.虫?.虫?.虫?.虫?.虫1.虫1.虫..虫蚕.虫?.虫. x..x?.}ch> vbat vbat Last message is 'vbat', sent by the tinySA Ultra. The battery info is missing, device is frozen, has to be switched off/on again.. Remark - apparently binary values are garbled into text by the serial port monitor software, somthing like 'x‘.xA.xA.xa.x?' etc., So, it looks like, this is a HW related problem. In single scan mode of the tinySA-App, there is once a refresh for the screen on the PC only, but on the com port, every 5 seconds the following message is exchanged. Why those idle messages ? Looks, like, any command after 'ch>' is initiated by the software (?) ch> vbat vbat 4163 mV ch> marker marker 1 64 120559020 -8.01e+01 ch> sweep sweep 118000000 136000000 450 This goes on for ever, no frozen tinySA Ultra com port in this mode. 73's de OE1MWW Wolfgang
Wolfgang OE1MWW All Messages By This Member #8426 yes, “.xó.xS.x#.x#.x?.x?.x#.xc.xC.}ch> vbat last command with no reply - and frozen :-(

Previous Topic Next Topic

开云体育

TinySA Ultra and TinySA App

开云体育

开云体育