Добро пожаловать, Гость
Логин: Пароль: Запомнить меня
In this category you can discuss how to connect a third party software (loggers, CW Skimmer etc.) or devices to ExpertSDR3.
  • Страница:
  • 1
  • 2

ТЕМА: TCI-based Skimmer for EE products

TCI-based Skimmer for EE products 17 Дек 2022 01:58 #16

  • VK6NX
  • VK6NX аватар
  • Вне сайта
  • Сообщений: 249
  • Спасибо получено: 197
Work in progress.

We are trying to have both apps for closed testing in early Jan, however ESDR3 upcoming Beta release must take a precedence.
Администратор запретил публиковать записи гостям.
Спасибо сказали: John-KC2QMA

TCI-based Skimmer for EE products 14 Янв 2023 13:53 #17

  • VK6NX
  • VK6NX аватар
  • Вне сайта
  • Сообщений: 249
  • Спасибо получено: 197
CW Skimmer dev update

- Audio Stream module *completed
- Development UI module *completed
- Detector module (validates if the signal is ligitimate CW) *completed, in intensive testing
- Decoder module (dynamic, one per valid signal) *three versions completed; enhancements are in progress
- Lingvo analysis module *work in progress
- Communication protocols module embedding *completed
- Final Horizontal UI *completed
- Final Vertical UI *work in progress

Estimations was that we will be completing initial release prior 16th of Jan, however we are clear now that we are not ready yet. Need 1-2 weeks more prior we will publish it for "closed testing". At this stage it is working in development mode within Qt framework UI.

From now we have pretty much clear vision of what would be two versions of Skimmer, what those will be sharing and what would be the difference. We do not have final names for the apps as yes, so, let me call them "Dev Skimmer" and "EE Skimmer" just for now.

Both, "Dev Skimmer" and "EE Skimmer", will share the same core. Inbound audio module, Detector module, Decoder module, CallSign recognition/validation/mapping module, Lingvo module - those all will be the same across both versions. This should mean, that basic skimmer functionality should be equal.

Major differences between two versions will be as following:
  • "Dev Skimmer" will be lightweight version, with limited basic features (inclidung TCI integration and log integration options) with three basic modes (common/dxpedition/contest) and will have max integration with ESDR3 bandscope/waterfall. This version will be usable for most "single op, single station" setups.
  • "EE Skimmer" will be full featured version. In addition to "Dev Skimmer" feature set it:
    - It is targeted to support multi-CW cluster mode, unifying miltiple skimmers (connected each to separate SunSDR transceiver) into single network.
    - It may also have extended "tuning settings" options (not yet decided).
    - It most likely will have separate switchable waterfall and capability to work simultaneously with both RX0/RX1 within one transceiver.
    - And so on ...

What is the performance and CPU usage comparing to known skimmers?

Well, we have only initial tests and we are not really ready to compare with other skimmers as yet. This part will need intensive public testing in multiple scenarios.

However we can tell not, that it is really CPU friendly. This is how "full featured" version looks like with waterfall ON in lunix-based dev machine:
photo_2023-01-15_00-44-41.jpg
Последнее редактирование: 14 Янв 2023 13:53 от VK6NX.
Администратор запретил публиковать записи гостям.
Спасибо сказали: Balaganoff, UA0SM, Rome, Is0cak, e72x, John-KC2QMA, tomas, f5ukw

TCI-based Skimmer for EE products 26 Янв 2023 14:31 #18

  • f5ukw
  • f5ukw аватар
  • Вне сайта
  • Сообщений: 5
Any update about recent progress?
Администратор запретил публиковать записи гостям.

TCI-based Skimmer for EE products 24 Фев 2023 06:16 #19

  • VK6NX
  • VK6NX аватар
  • Вне сайта
  • Сообщений: 249
  • Спасибо получено: 197
Hi All

While EE Skimmer and SkimmerLite are still in development, we are currently opening "Skimmer Feature request & Discussion" group on Github.

The logic behind is pretty much the same as "Suggestions" in ESDR3; however the difference is that "Skimmer" group (at this point of time) is invite-only and targeted to specific part of the community: 3rd party TCI developers, active contestmen and active dxpeditioners. If you are from indicated range and have the specific Skimmer-related feature requests or integration requests with DXpedition or contest soft, or if you wish to add Skimmer functionality/integration with your TCI-based product (Log, Extension, etc.), please visit github link to submit your join request.


Всем доброго дня,

Пока EE Skimmer и SkimmerLite все еще находятся в процессе разработки/тестирования, мы сделали специальный проект для пожеланий и запросов нового функционала Скиммера (воспользовавшись опытом раздела "Предложения" ESDR3). В настоящий момент прием в группу ограничен следующими категориями: разработчики собственного софта с применением TCI (Логов, дополнений), активные CW контестмены (имеющие специальные запросы на функционал скиммера для соревнований), активные операторы DXпедиций (со специальными запросами по расширению функционала для DXпедиций и интеграций с DXпедиционным софтом). Если вы относитесь к одной из перечисленных категорий и/или интересуетесь вопросами интеграции Скиммера с вашим софтом, пожалуйста перейдите по ссылке на гитхаб и разместите вашу заявку на присоединение к группе.
Администратор запретил публиковать записи гостям.
Спасибо сказали: Balaganoff, Rome, tomas, f5ukw

TCI-based Skimmer for EE products 05 Авг 2023 11:15 #20

  • n3qq@na-234.com
  • n3qq@na-234.com аватар
  • Вне сайта
  • Сообщений: 6
  • Спасибо получено: 1
Hello Pavel,

Any updates on ETA?
Thank you
Администратор запретил публиковать записи гостям.

TCI-based Skimmer for EE products 06 Авг 2023 22:53 #21

  • VK6NX
  • VK6NX аватар
  • Вне сайта
  • Сообщений: 249
  • Спасибо получено: 197
Hi Yuri

We are targeting to line up with ESDR3 release.

We have basic app working and reached CW Skimmer (VE3NEA) decoding level; and now working on improve it. We stand by for what was announced at the start - there is no need nor for another CW skimmer, unless it has better functionality. And we do not think that +few % to decoding is, really, what we can call "better". We are focusing on extended functionality for areas, where skimmer is most needed: dxpeditions/pileups (we have not heard much feedback from contestman).

FYI, to my knowledge EE will be anouncing soon some updates in regards to spot clusters support.
Администратор запретил публиковать записи гостям.
Спасибо сказали: f5ukw, PE1PUX

TCI-based Skimmer for EE products 07 Авг 2023 12:59 #22

  • n3qq@na-234.com
  • n3qq@na-234.com аватар
  • Вне сайта
  • Сообщений: 6
  • Спасибо получено: 1
Thank you, Pavel!

Sounds good.
My main interest is for dxpeditions use. The current setup involves AutoHotKey script with 3 mouse clicks for complete QSO.
Only need TX freq +20KHz max.
The problem is when N1MM+ version is updated need to update the script.
Ideally same functionality without AHK.

Thank you and 73,

Yuri N3QQ
Администратор запретил публиковать записи гостям.

TCI-based Skimmer for EE products 07 Авг 2023 23:20 #23

  • VK6NX
  • VK6NX аватар
  • Вне сайта
  • Сообщений: 249
  • Спасибо получено: 197
For "dxpedition mode" (note, there are three modes we are building-in: "dxpedition", "contest" and "common") there are currently three "decoding windows" preset sizes: 5KHz, 10KHz and 25KHz.

Each "window" size corresponds with Sample Rate resolution: 5KHz uses 39KHz, 10 and 25 use 78KHz. Using lower resolution allows to fit quicker decoding rate with the same FFT (fast Fourier transform) parameters: each FFT sequence, obviously, performs full scan of 39KHz quickier (seeking for the ligitimate CW signal), than 78KHz.

In settings there is an option to apply "decoding window" to the start frequency, i.e. (assuming 53000 is "listen on" and "yellow" represents 10KHz "decoding window"):
w1-1.png

working in UP1... UP5, decoding only UP

w1-2.png

working in UP1, decoding DOWN and UP

Note: in above examples yellow = "decoding window", the algorithm is decoding within this window only and ignoring anything outside of its boundaries. This approach allows to implement min "from detect - to decode" period, whie keeping CPU usage to its minimum (assuming dxpedition PC not always top spec).

There is "quick switch" (one click) to change between 5/10/25 KHz window. At later phase we may implement variable "decoding window" size, if this will be needed.

In regards to operatios: sure, we are implementing "minimal click" approach. Once initial setup completed, Skimmer will use ESDR3 Panorama to display the decoded callsigns; and single left-mouse click on callsign will offer all parameters (associated with this callsign) to the log: callsign, freq (both RX and TX freq if working in TX1/TX2 mode), UTC, mode, etc.

Where most time currently consumed: there are few versions of FFT we are testing, alongside with few algorithms within each FFT versions. We have started with 500+ versions, now reduced to 16. At the end we will select 1-2 most promicing FFT version and will test them against "dxpedition", "contest" and "common" mode, defining most effective for each.
Вложения:
Последнее редактирование: 07 Авг 2023 23:26 от VK6NX.
Администратор запретил публиковать записи гостям.
Спасибо сказали: n3qq@na-234.com, Rome

TCI-based Skimmer for EE products 12 Нояб 2023 08:34 #24

  • Iu4jnr
  • Iu4jnr аватар
  • Вне сайта
  • Сообщений: 8
  • Спасибо получено: 1
Hi,
Any update?
Max IU4JNR
Администратор запретил публиковать записи гостям.
  • Страница:
  • 1
  • 2
Время создания страницы: 0.130 секунд