Keyboard Shortcuts
Likes
- Tinysa
- Messages
Search
Re: tinySA-H4
Interesting.?
toggle quoted message
Show quoted text
Are you saying that it may be possible to piggyback a SI4432 module to the H4 so we can play more with the FW?
|
Re: ISSUE REPORT: New release: improved screen capture and better trigger status
¿ªÔÆÌåÓýHi Erik Quite understandable. Anyway it work now with various small flaws. There is no vertical lines for log sweep. On one computer the markers is not shown on another they are. And do not change anything for storing when sweeping as stop sweep and do what you like to do such as subtract then sweep again, els crash . Kind regards Kurt ? Fra: [email protected] <[email protected]> P? vegne af Erik Kaashoek ? I haven't spent enough time in tinySA.exe lately with the various changes in the tinySA itself. |
tinySA-H4
I transfer tinySA firmware to NanoVNA-H4 platform
Now possible use H4 platform (STM32F303 CPU + 4` display module) for next tinySA generation You can flash it to H4 and see how it work (yes no any tinySA hardware on H4, and you not see spectre, but all menus work, sweep times and e.t.c) H4 allow SD card, so in next tinySA possible save something to it PS STM32F303 have hardware FPU, and in it SI4432 run on hardware SPI mode, so it allow moew fast work, minimum Zero Span time = 700us, also values convert (if use Volt for example) less slowdown. |
Re: ISSUE REPORT: New release: improved screen capture and better trigger status
¿ªÔÆÌåÓýHi Erik The change of dB/Level to 32 got it to work Kind regards Kurt ? Fra: [email protected] <[email protected]> P? vegne af Erik Kaashoek ? I haven't spent enough time in tinySA.exe lately with the various changes in the tinySA itself. |
Re: ISSUE REPORT: New release: improved screen capture and better trigger status
¿ªÔÆÌåÓýHi Erik Is seem to be able to run the sweep as stop the TinySA sweep when pressing single. If pressing Run the Tiny SA screen continuous stopped which I suppose it as it should be, but I see no trace. If setting the sweep on the TinySA it does not send frequency information to the TinySA. The Com port crashes quite often Kind regards Kurt ? Fra: [email protected] <[email protected]> P? vegne af Erik Kaashoek ? I REALLY HATE the windows serial port implementation in VC |
Re: External modulation function
The low output signal is created by mixing a fixed 433.9MHz signal with an LO at 433.9MHz + the required output frequency.?
The external modulation option disables the build-in LO and connects the mixer LO input to the high port. So a better name should have been "external LO" In this configuration you can use two tinySA's to create a tracking generator option with a possible offset (within +/- 500kHz) by connecting the high input of the tinySA in external modulation mode to the LO output of another tinySA. This is exactly how the tracking generator of the early HP spectrum analyzers worked. See this post:?/g/tinysa/message/10 Disadvantage of the direct coupling as shown in above post is the reduced dynamic range (max 70dB) due to reverse leakage through the mixers of the two tinySA. This can be solved by putting an isolation amplifier in between. |
External modulation function
Hello,
I was reading through the documentation and was curious about the external modulation function. Does this allow one to input through the high input either modulated audio or a modulated tone that is of a different frequency from the built in 800hz tone? Thank you, - Mike |
Re: ISSUE REPORT: New release: improved screen capture and better trigger status
On Sat, Jul 25, 2020 at 08:17 AM, Erik Kaashoek wrote:
Some suggestions:Erik, ? ?The level/dB setting was set to a default value of '2' which is why no sweep data was displayed. Once I changed it to '32' the sweep data displayed properly.? The sweep data was displayed 3dB too low because of the Zero level(dB) setting of -125, this needs to be -128.? Are those to values initialized in the tinySA.cfg file included in the?? directory?? The cfg file in that directory is over a month old. level/dB changed from '2' to '32', Zero Level(dB) should be -128? ? ? ? ? ? ? ? ? ? ? ? ? ? ?After level/dB changed from '2' to '32' sweep data is visible. After the above changes, the Mockup device is still the only device shown in the SerialPortSelector but all else is working correctly.? This is probably only a issue if more than one tinySA is connected, or a tinySA and a NanoVNA are connected since they use the same VID:PID. Note: I just connected a NanoVNA to another port on my computer and, after File->Connect only displayed the Mockup device. Returning to the Spectrum screen locked up the application when a sweep was attempted. - Herb |
Re: ISSUE REPORT: New release: improved screen capture and better trigger status
Some suggestions:
- Try again to connect, sometimes it will a second time. - Set level/dB in the settings screen to 32 as the internal data format has changed - Set the RBW to Auto. setting to 3kHz will be extremely slow as tinySA.exe can not yet scan in fast mode |
Re: ISSUE REPORT: New release: improved screen capture and better trigger status
On Sat, Jul 25, 2020 at 07:55 AM, Erik Kaashoek wrote:
I REALLY HATE the windows serial port implementation in VCErik, ? I tried unplugging the port and cycling power on the tinySA.? The Mockup device is still the only selection that shows up in the Connect dropdown list.? The primary problem is that even though the tinySA serial port is not showing up in the tinySA.exe dropdown list it is successfully receiving commands from the application. The tinySA.exe screen is not plotting whatever data is being received back and it is not properly registering the tinySA serial port in the drop down list. ?I also noticed that 'Zero Level (dB)' value under the settings tab is still defaulting to -125. - Herb |
Re: ISSUE REPORT: New release: improved screen capture and better trigger status
On Sat, Jul 25, 2020 at 07:34 AM, hwalker wrote:
On Sat, Jul 25, 2020 at 05:40 AM, Erik Kaashoek wrote:Further investigation, after seeing that the screenshot tab works, shows that pause and resume commands are being sent to the tinySA when a single trigger is performed although no sweep data appears on the tinySA.exe screen.? Again, only the Mockup device is displayed when File->Connect is selected. - Herb |
ISSUE REPORT: New release: improved screen capture and better trigger status
On Sat, Jul 25, 2020 at 05:40 AM, Erik Kaashoek wrote:
New FW released: v1.0-39Erik, ? ? I experienced the following issue with the new tinySA.exe release: 1. tinySA serial port not showing in drop-down list and tinySA can't connect. Tried to load tinySA.cfg file? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Tried to connect to tinySA serial port. 2. Strangely, even though the main interface won't run and no serial port shows as selected, the screenshot function works. By chance I tried to capture a screenshot and it worked, even though the main screen shows no device connected. 3.? I tried deleting the 'Kaashoek\SpectrumAnalyzer' directory and letting tinySA create a fresh installation without any change. - Herb |