Keyboard Shortcuts
Likes
- Tinysa
- Messages
Search
Re: Beta test channel
#betatest
Can you check if v1.1-50 also has this problem.
-- ------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/ |
Re: Beta test channel
#betatest
v1.1-49
Test #3 Stopband fails 50/50 There are visible spikes at 19 and 21 MHz. Sometimes the left spike goes beyond threshold and test fails. There are no visible spikes with stable fw, test is always Ok. |
Locked
What to do when you think you bought a tinySA clone.
Otherwise, 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 Otherwise submit a 3 photos
------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/ |
Re: Beta test channel
#betatest
Here is ok to report bugs
-- ------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/ |
Re: Video of selftest fail of bad clone
Soon will be plenty of clones and "watch and be warned" is not enough as most people will watch after having had problems with their purchase. You can do two things: 1) Do nothing else and only the most expert buyers will get a refund. The cloners will keep on selling more and more clones. 2) Be the most expert cheated buyer and give the buyers all the tools to make an efficacious request of refund at a level of copy/paste, including a compact letter in jpg format with your company name and logo where you, "the original manufactureer and owner of the tinySA name and logo" declare that devices with "the following problems..." cannot be used for their original purphose and are illegal copies using tinySa name, logo and case design illegally to deceive buyers. If you follow the second way most of the buyers will get a full refund (and buy again from you) and you probably will be able to force the copy makers to change name and logo so that buyers can recognize the difference between original and copies. ? On Fri, Dec 11, 2020 at 04:39 PM, Erik Kaashoek wrote:
|
Re: Beta test channel
#betatest
Hi Erik and everyone.
Where is the proper place to report bugs and issues for the beta fw, here or on github? Regards Andrey |
Re: New feature soon to be released; Quick menu
I love the quick menus! Nice work Erik!
73 -Jim NU0C On Fri, 11 Dec 2020 07:46:12 -0800 "Erik Kaashoek" <erik@...> wrote: Here a short video demonstrating the new Quick Menu feature available in (soon to be released) firmware release v1.1-49 or later |
Re: Beta test channel
#betatest
toggle quoted message
Show quoted text
Now the FW has become more stable I'd like to set up a beta test channel where I can announce early releases of new functionality without running the risk of upsetting new users.
|
Re: #betatest
#betatest
¿ªÔÆÌåÓýGreat story! ?Next month¡¯s meeting of the London Amateur Radio Club is all about solving interference. ?May I use your story, with proper attribution of course?!Dave On Dec 11, 2020, at 10:05, Larry Macionski via groups.io <am_fm_radio@...> wrote:
|
Re: #betatest
#betatest
To All the Beta Testers and ERIK-
Thanks for all the research, testing and feedback. You have my full support. As soon as the TinySA came out I bought one, and used it to track some RFI that we found moved up and down the band (2Meters) effecting an Amateur repeater on a fixed frequency. More below. In the upcoming weeks and month of Beta Testing and refinement, I am sure the overall product will improve, beyond my expectations. Thank you for your dedication and volunteering. One comment.. When a "stable- approved" firmware version is good enough for the average Joe- please let us know it's OK to upgrade. Perhaps that version would also match the "users" manual so that one upgrading to that firmware would be confident that it works and the "manual" can be refereed to at a high confidence level. Back to the RFI - Since the repeater duplexers and receiver band-pass limited the RFI to only look as if intermittent, we found the TinySA showed a wide signal moving up and down the band. Because it was now a visual constant signal we tracked it a few blocks... to guess what?? A BIKER BAR - with a reputation, that the local police had cleaned up a few years ago but still, not the place to take your mother for tea. even Long Island Iced Tea..? Well, alone one afternoon , I entered and spoke to the bar tender.. explained why I was there..? Once inside it was easy to find the culprit.. A neon tube beer sign about 3ft by 2ft..The bar tender told me "sometimes it flashes" and the beer distributor promised a replacement as it distracted those playing pool nearby.? Well, as soon as he saw the TinySA display and unplugging it, the signal disappeared. He said- I'll keep it off telling the distributor, you want it on, bring me a new sign.. So we had a beer and all is well since. |
Re: #betatest
#betatest
Me too, please.
toggle quoted message
Show quoted text
Martin, OK1RR Dne 10. 12. 20 v 23:19 Dennis Oszuscik napsal(a): Can you add me to the Beta test Please |
Re: Interest in tinysa without display
Simon,
toggle quoted message
Show quoted text
You could probably surgically disable the display backlight to save power (without any firmware change). --John Gord On Wed, Dec 9, 2020 at 08:29 AM, Simon Mali wrote: <!doctype html> |
Re: Interest in tinysa without display
On Wed, Dec 9, 2020 at 08:29 AM, Simon Mali wrote:
Not without modifying the SW, which you can do yourself See:?https://tinysa.org/wiki/pmwiki.php?n=Main.USBInterface The USB interface is native. There is also RS232 HW available on the PCB but currently does not fit in FW so it is commented out but you can remove unneeded parts and enable the serial interface No double peak with tinySA ? ------------------------------------------
For more info on the tinySA go to https://tinysa.org/wiki/ |