Страница 22 из 55 ПерваяПервая ... 1215161718192021222324252627282932 ... ПоследняяПоследняя
Показано с 316 по 330 из 814
Like Tree143Спасибо

Тема: LogHX: English version

  1. #316
    Координатор темы Аватар для RX4HX
    Регистрация
    03.02.2006
    Возраст
    51
    Сообщений
    17,031
    Поблагодарили
    7968
    Поблагодарил
    4163
    Цитата Сообщение от F8GHE Посмотреть сообщение
    705 will be supported for a CatHX configuration ?
    First about CatHX INI-Files:
    CatHX use INI-files from OmniRig - you can copy to /Rigs folder INI-file from OmniRig.
    Second - about IC-705: you can self create INI-file for 705, if you have documentation for CAT of 705. Or send to me documentation for 705, and I'll make INI-file.

    Цитата Сообщение от IK2XDE Посмотреть сообщение
    I thinks correct is
    Yes Andrea, You're right! I'll fix it.

  2. #317
    Low Power
    Регистрация
    02.05.2021
    Сообщений
    51
    Поблагодарили
    6
    Поблагодарил
    1
    Цитата Сообщение от RX4HX Посмотреть сообщение
    First about CatHX INI-Files:
    CatHX use INI-files from OmniRig - you can copy to /Rigs folder INI-file from OmniRig.
    Second - about IC-705: you can self create INI-file for 705, if you have documentation for CAT of 705. Or send to me documentation for 705, and I'll make INI-file.
    Alexei,

    First about CatHX INI-Files: Thanks for the advise. I did it and more than 130 files was updated and added on release 634 and my problem solved

    Second - about IC-705: The INI-file for IC-705 is included in this last Omnirig INI-file Updated 2021-04-15. It could be a good idea to update rigs in your release of your GREAT software

    Thanks very much for your help and your work
    73s Christian F8GHE

  3. #318
    Standart Power
    Регистрация
    03.01.2021
    Возраст
    52
    Сообщений
    159
    Поблагодарили
    17
    Поблагодарил
    0
    In the adif file sent to clublog, the DXCC field is missing.
    This field is not mandatory, but it is essential to avoid reporting errors in the log,
    especially for ambiguous calls for example with special calls like GB5xxx
    which have various exceptions for ENGLAND-SCOTLAND and WALES ..... just for example.

    I think it is appropriate to put this field in the file to be uploaded to Clublog, Eqsl and Lotw.

    Thanks.

    73 de IK2XDE Andrea

  4. #319
    Координатор темы Аватар для RX4HX
    Регистрация
    03.02.2006
    Возраст
    51
    Сообщений
    17,031
    Поблагодарили
    7968
    Поблагодарил
    4163
    Цитата Сообщение от IK2XDE Посмотреть сообщение
    Start log with /D=IK2XDE
    Problem with folders fixed - please check:

    https://forum.qrz.ru/355-loghx-appar...ml#post1801176

    - - - Добавлено - - -

    Цитата Сообщение от M0CGF Посмотреть сообщение
    I seem to be getting this error a lot recently in 631
    Fixed also.

  5. #320
    Standart Power
    Регистрация
    03.01.2021
    Возраст
    52
    Сообщений
    159
    Поблагодарили
    17
    Поблагодарил
    0
    Цитата Сообщение от IK2XDE Посмотреть сообщение
    I find a little problem with BANDMAP

    Вложение 297680

    Вложение 297681


    73 de IK2XDE Andrea.

    This problem persists even with the latest version 641.

    The yellow background does not follow the band, as does the bold lettering.


    The cat and the band map work correctly both
    with CATHX than with TCI without problems.

    Thanks.
    73 de IK2XDE Andrea.

    - - - Добавлено - - -

    Цитата Сообщение от IK2XDE Посмотреть сообщение

    In this regard, it would be enough to have a separate configuration for the voice.

    CW / PPT
    MMVARI / PTT
    VOICE / PTT

    73 de IK2XDE Andrea

    Surely other colleagues will appreciate this possibility

    Also ... for example.... in N1MM +,
    I can configure CW on one port and PTT on another different port.

    Thanks.
    73 de IK2XDE Andrea.

  6. #321
    Координатор темы Аватар для RX4HX
    Регистрация
    03.02.2006
    Возраст
    51
    Сообщений
    17,031
    Поблагодарили
    7968
    Поблагодарил
    4163
    Цитата Сообщение от IK2XDE Посмотреть сообщение
    This problem persists even with the latest version 641.
    I remember about this problem, but i can not catch this problem. Here is Ok!
    Is problem only for 40M band or for another bands also?

    Цитата Сообщение от IK2XDE Посмотреть сообщение
    configure CW on one port and PTT on another different port
    Ok! It's good idea. I will do it.

  7. #322
    Standart Power
    Регистрация
    03.01.2021
    Возраст
    52
    Сообщений
    159
    Поблагодарили
    17
    Поблагодарил
    0
    The problem occurs on any band, both with CATHX and IC-7600 and with TCI and SUNSDR2Dx.
    When I change bands, the yellow button stays on the initial band,
    but the bold text follows the cat correctly, the bandmap also changes bands correctly.

    The problem is only the yellow background color.

    Thanks.

  8. #323
    Координатор темы Аватар для RX4HX
    Регистрация
    03.02.2006
    Возраст
    51
    Сообщений
    17,031
    Поблагодарили
    7968
    Поблагодарил
    4163
    Цитата Сообщение от IK2XDE Посмотреть сообщение
    When I change bands, the yellow button stays on the initial band,
    but the bold text follows the cat correctly, the bandmap also changes bands correctly.
    This is an important note! I found problem - this is happening if you use "Windows style" for log.
    Ok, I'll fix this!

  9. #324
    Standart Power
    Регистрация
    03.01.2021
    Возраст
    52
    Сообщений
    159
    Поблагодарили
    17
    Поблагодарил
    0
    Цитата Сообщение от IK2XDE Посмотреть сообщение
    In the adif file sent to clublog, the DXCC field is missing.
    This field is not mandatory, but it is essential to avoid reporting errors in the log,
    especially for ambiguous calls for example with special calls like GB5xxx
    which have various exceptions for ENGLAND-SCOTLAND and WALES ..... just for example.

    I think it is appropriate to put this field in the file to be uploaded to Clublog, Eqsl and Lotw.

    Thanks.

    73 de IK2XDE Andrea
    Try also with build 644,
    of course same problem.

    Test with clublog, without DXCC field, a lot of ambiguous calls like GB5xxx
    create an error report because the country is not recognized.
    (This call was used for England-Scotland-Wales)

    Test also send adif to HRDLOG without DXCC field,
    qso added to log without flag, because country was not recognized.

    Please fix this (add DXCC field in the adif)

    Thanks.
    73 de IK2XDE Andrea

    - - - Добавлено - - -

    Цитата Сообщение от RX4HX Посмотреть сообщение
    This is an important note! I found problem - this is happening if you use "Windows style" for log.
    Ok, I'll fix this!
    ONLY FOR REPORT.

    In the build 644 yellow background now is orange,
    yes follow the band with cat, but not delete (clear) previus band.

    I think you will work again on it.

    Thanks.
    73 de IK2XDE Andrea.

  10. #325
    Координатор темы Аватар для RX4HX
    Регистрация
    03.02.2006
    Возраст
    51
    Сообщений
    17,031
    Поблагодарили
    7968
    Поблагодарил
    4163
    Цитата Сообщение от IK2XDE Посмотреть сообщение
    In the adif file sent to clublog, the DXCC field is missing
    Yes, ADIF for QSL-service created without DXCC field: DXCC field must be created by QSL-service, when station registered on QSL-service. I think it's right!
    It's right for LoTW and eQSL.

  11. #326
    Standart Power
    Регистрация
    03.01.2021
    Возраст
    52
    Сообщений
    159
    Поблагодарили
    17
    Поблагодарил
    0
    Цитата Сообщение от RX4HX Посмотреть сообщение
    Yes, ADIF for QSL-service created without DXCC field: DXCC field must be created by QSL-service, when station registered on QSL-service. I think it's right!
    It's right for LoTW and eQSL.
    Test with clublog, without DXCC field, a lot of ambiguous calls like GB5xxx
    create an error report because the country is not recognized.
    But in my log was registered correct.
    (This call was used for England-Scotland-Wales)

    Test also send adif to HRDLOG without DXCC field,
    qso added to log without flag, because country was not recognized.

    Thanks.

  12. #327
    Standart Power
    Регистрация
    03.01.2021
    Возраст
    52
    Сообщений
    159
    Поблагодарили
    17
    Поблагодарил
    0
    https://clublog.freshdesk.com/suppor...-club-log-use-

    Here is a list of the ADIF fields Club Log uses:

    QSO_DATE
    TIME_ON
    TIME_OFF (this is stored independently and used for log matching as well as ADIF exports)
    QSLRDATE
    QSLSDATE
    CALL
    OPERATOR
    MODE
    BAND
    BAND_RX
    FREQ
    QSL_RCVD
    LOTW_QSL_RCVD
    QSL_SENT
    DXCC
    PROP_MODE
    CREDIT_GRANTED
    RST_SENT
    RST_RCVD
    NOTES
    GRIDSQUARE [note that this is only set if the Club Log user sets a locator on Settings > Locators, and it is not stored per QSO]

    - - - -

    How does Club Log determine DXCC status?


    Identifying DXCC entities correctly is an important feature of Club Log, so let's take a moment to explain the philosophy.


    Club Log primarily uses details of allocated prefixes dating back to 1945 to map callsigns in uploaded logs to the corresponding DXCC entities. Maintaining the prefix data, plus a number of changes and known exceptions within defined date ranges, is a painstaking task undertaken voluntarily by Alan, 5B4AHJ.


    If you upload an ADIF log that claims a particular DXCC entity for a QSO (in the ADIF COUNTRY or DXCC field) but Club Log maps the call to a different entity, an error will be generated when the log is imported into the database. Other problems, such as unknown prefixes, also generate errors. At the end of the log import process, an error report will be emailed to you and copied to Alan.


    It is not unusual to discover from the Club Log error reports that you have worked new countries or filled additional band-slots, and most of us find it immensely satisfying to know that our logs and DXCC records are accurate. We hope that you will go through any error reports you receive, fixing busted calls and obvious country errors in your log and then re-upload your corrected log to Club Log.

  13. #328
    Координатор темы Аватар для RX4HX
    Регистрация
    03.02.2006
    Возраст
    51
    Сообщений
    17,031
    Поблагодарили
    7968
    Поблагодарил
    4163
    Цитата Сообщение от IK2XDE Посмотреть сообщение
    Here is a list of the ADIF fields Club Log uses:
    Well, I think here is not problem - I add tag DXCC to ADIF for QSL-services.

    Цитата Сообщение от IK2XDE Посмотреть сообщение
    How does Club Log determine DXCC status?
    Only user determine self DXCC status! Old call-system is broken!
    Example - USA: now KL7 or KH6 can be and Alaska, and USA, and Hawai.

  14. #329
    Standart Power
    Регистрация
    03.01.2021
    Возраст
    52
    Сообщений
    159
    Поблагодарили
    17
    Поблагодарил
    0
    I am using build 644 with satisfaction,
    surely there are still some things to improve, in my opinion, but we are getting closer .... hi ...

    My tests this week focused on the cluster.

    The cluster I use is: ik2xde.ddns.net:8000
    To check the differences I used PUTTY for the telnet connection.

    For example, I noticed that in the telnet window, many lines are cut / deleted especially
    at the beginning of the connection, all the lines sent by the cluster are not displayed.
    In my opinion this is a mistake, often in that part there are important warnings for users,
    or instructions for use, for filters, for skimmers or other.

    In my opinion all lines should be displayed.
    For example, if I send the SH/U command (to view the users connected to the cluster),
    only the first line is shown, the others are cut off.



    - The ALARMS window, once the call to be monitored has been set,
    show only the latest spots, one line only for each mode or band.

    In my opinion it would be better to see all the spots of that call,
    to have a better situation.
    Or in any case being able to choose whether to see only one line, or all.

    - Favorite Spots.
    This function is not clear to me, I did not understand what it is for, and how it can be configured.


    Thanks for your attention, I hope that my observations will help everyone to improve this software.

    73 de IK2XDE Andrea.

  15. #330
    Координатор темы Аватар для RX4HX
    Регистрация
    03.02.2006
    Возраст
    51
    Сообщений
    17,031
    Поблагодарили
    7968
    Поблагодарил
    4163
    Now you can use different port for CW and PTT:
    https://forum.qrz.ru/355-loghx-appar...ml#post1806384

    Alse add ADIF fields for export QSO to LoTW, eQSL, Clublog
    Цитата Сообщение от IK2XDE Посмотреть сообщение
    Here is a list of the ADIF fields Club Log uses:

Похожие темы

  1. LogHX: Актуальные релизы и история изменений.
    от RX4HX в разделе LogHX: Аппаратный журнал любительской радиостанции
    Ответов: 875
    Последнее сообщение: 20.03.2024, 22:34
  2. DIY UW3DI (for English OPs)
    от UU2JET в разделе КВ: UW3DI
    Ответов: 3
    Последнее сообщение: 18.01.2013, 12:04
  3. KENWOOD TS-2000 (Black Version)
    от UA3IRS в разделе TS-2000
    Ответов: 4
    Последнее сообщение: 16.11.2009, 20:16
  4. Navitel 2.0 Pocket PC Version
    от RX3AOE в разделе APRS
    Ответов: 1
    Последнее сообщение: 26.09.2006, 03:39
  5. windows 64 bit version не ставится
    от UR4LZW в разделе Программное обеспечение
    Ответов: 5
    Последнее сообщение: 12.09.2005, 23:58

Социальные закладки

Социальные закладки

Ваши права

  • Вы не можете создавать новые темы
  • Вы не можете отвечать в темах
  • Вы не можете прикреплять вложения
  • Вы не можете редактировать свои сообщения
  •  
Похоже, что вы используете блокировщик рекламы :(
Форум QRZ.RU существует только за счет рекламы, поэтому мы были бы Вам благодарны если Вы внесете сайт в список исключений!
как отключить
×
Рейтинг@Mail.ru
eXTReMe Tracker


Похоже, что вы используете блокировщик рекламы :(
Форум QRZ.RU существует только за счет рекламы, поэтому мы были бы Вам благодарны если Вы внесете сайт в список исключений!
как отключить
×