2018年8月13日月曜日

FT8Call version 0.4.2 がリリースされる。

Verison 0.3.Xか0.4.2にアップデートされる。
Version 0.4.2はWSJT-X, JTDX, MSHVのFT8はデコードできません、1パケットに情報量を増やしてのでFT8Callは独自仕様となり、FT8Call V0.4.2以降間でしか通信できない、その分チャットQSOに特化する。

The FT8 crc12 using XOR 42 so we do not interfere with standard FT8 station
これい以外にも変更がありスタンダードFT8から変わる。


絵はUbutusとWin10間でオーディオで通信テスト。
Ubuntu
Win10


バンド:

  • ●  160m: 1.838 MHz // 2 kHz below FT8
  • ●  80m: 3.580 MHz // 7 kHz above FT8
  • ●  40m: 7.080 MHz // 6 kHz above FT8
  • ●  30m: 10.130 MHz // 6 kHz below FT8
  • ●  20m: 14.080 MHz // 6 kHz above FT8
  • ●  17m: 18.104 MHz // 4 kHz above FT8u
  • ●  15m: 21.080 MHz // 6 kHz above FT8
  • ●  12m: 24.920 MHz // 5 kHz above FT8
  • ●  10m: 28.080 MHz // 6 kHz above FT8
  • ●  6m: 50.300 MHz // 13 kHz below FT8 

注1:絵のバンドは適当です。
注2:Version 0.3XX以下はWSJT-X, JTDX, MSHVのFT8をデコードできる。
ドキュメントここから:



Ubuntu FT8Call v0.4.2

以下大きな変更した情報です。

Here are the most important changes:
  • FT8Call v0.4 is not backwards compatible with v0.3
  • New frequencies! Make sure you go into the settings, click the Frequencies tab, right click the table, and click Reset to get the new recommended frequencies built into the app.
  • You'll also see a new feature on that Frequencies tab. Automatic band hopping on a schedule, allowing you to set up your station to use something like 20m during the day and 40m during the night!
  • Version 0.4 uses much more efficient message packing. With this, FT8Call no longer supports standard FT8 messages (neither transmit nor decode). We now have our own BEACON and CQ format that enables more information to be sent (like arbitrary prefixes/suffixes up to 4 characters long). For example, the following transmissions all can be sent in one 15-second cycle.
    • KN4CRD: BEACON EM73
    • KN4CRD: CQCQCQ EM73
    • KN4CRD/QRP: CQCQCQ EM73
    • VE3/KN4CRD: BEACON EM73
  • With the new message format most freetext messages will be sent in 10% fewer bits (or better). Here are some examples of phrases that could be sent in one 15 second transmit cycle:
    • EEEEEEEEEEEEEEEEEEEEEEE (23 characters) 
    • I HAVE EATEN A SHOE (19 characters)
    • WHICH WAY TO OHIO (17 characters)
    • NEVER HAVE I EVER (17 characters)
    • TU UR 599 INTO (14 characters)
    • etc
  • With this new message packing, we have proper compound callsign support! Compounds can be supplemented with a 4-character prefix/suffix. You'll have to transmit an extra 15-second cycle for most commands, but there should be no issues with the application recognizing compound calls.
  • Beacons and auto-replies are now placed in a transmit queue for better scheduling of outgoing mesages.
  • There's a new message format called a "hashed" message. It includes a longer checksum and will only display if the recipient receives it in its entirety. It also automatically ACKs back to the sender when properly received.
  • A couple nice direct responses of QSL? and QSL (query and confirmation).
  • An API for external apps to interface with FT8Call.
  • And a BUNCH of general improvements:
    • Upgraded to WSJT-X 1.10 base for various bugfixes
    • Removed other modes. FT8CALL is THE mode
    • Starting compound call refactoring
    • Varicode packing without a 5-bit pad integer
    • Restructured building frames and decoding for better support of compound callsigns
    • Added some comments about trigrams and quadgrams
    • Varicode packing of trigram and quadgrams
    • Reorder a few of the special escapes
    • Reordered varicode escapes for better efficiency
    • Continued refactoring of command processing
    • Added a prioritized TX queue for beacons (low priority) and automatic replies (normal priority) and eventually outgoing messages (high priority)
    • Added some better alignment of low priority beacons with other messages
    • Refactor display of recent and directed messages
    • Cache in recent when we process rx activity
    • Write unpacked entries to the ALL.txt file
    • Properly handle compound call parsing for CQs and DEs
    • Parse callsigns from BCN command
    • Added remove activity to band activity right context menu
    • Removed BCN command... it's parsed separately
    • Refactored callsign packing to use 21 bits instead of 22, reducing our dependence on Prefix/Suffix flags added to our frame type enum
    • Refactoring for better compound message display
    • Restructuring beacons to be more like standard allcalls
    • Split beacon packing from compound packing
    • Added large checksum message processing
    • Added hashed message with ack
    • Stop displaying general activity in the directed text area (for now)
    • Refactor compound call structure for directed messaging by using a new frame type FrameCompoundDirected. This allows us to send only two frames when each station has a compound callsign. No aliasing, full calls are sent with each transmission.
    • Escape key stops transmission
    • Cleanup compound call display
    • Added QSL commands
    • Fixed issue with compound directed calls with numerical values
    • Added ability to add newline into the text edit panel with Shift+Enter
    • Send compound frames for stations heard to be more efficient in delivery. Added FT8CallFirst to flush the buffers of incomplete transmissions.
    • Modified the FT8 crc12 using XOR 42 so we do not interfere with standard FT8 stations
    • Updated comment about FrameReserved
    • Fixed issue with rebase and FoxQSO definition
    • Bump Version to 0.4.0
    • Added wider offset for band activity +/- 10Hz. Update dirty display 2x per transmission period
    • Experimenting with full packing of 72-bit messages using an intermediate base64 alphabet (12 x 6-bit characters)
    • Added 72-bit packing
    • Updated varicode to support 72 bit message lengths
    • Updated decoded to use new alphabet. Updated frame packing to use new 72 bit messages
    • Updated directed frames to take advantage of the extra numerical bits so we don't have to delineate between positive and negative frame types
    • Remove old style FT8 beacon
    • Fixed bug in new decoder alphabet
    • Message buffer should ack
    • Require i3bits to be set to avoid most weird false decodes
    • Better beacon scheduling. Should prevent future issues with beacons going missed
    • Initial stab at frequency suggestions
    • FT8CALL the mode is all uppercase
    • Fixing some remnants related to modes logging
    • Updated to ft8call_log.adif for logbook
    • Get rid of the advanced tab in configuration
    • Escape key clears message queue too
    • Fixed bug in beacon that prevented it from kicking off if AUTO was disabled
    • Updated display of command and rx activity
    • Directed cache good for 5 minutes
    • Long checksums for hash buffered messages. Display a newline if we reach the last frame and the frame is not buffered
    • Added frequency offset spinbox into the widegraph
    • FT8 does not permid CW id
    • Write to ft8call.log too
    • Fix bug in widegraph not actually setting offset value
    • Our callsign is not a selected callsign
    • Fix CQ highlighting
    • Bump expiration date
    • Initial stab at band switching...broken
    • Switched to time range instead of a fixed point for easier comparisons
    • Updated editing experience for frequency schedule. Fixed some bugs with the data storage
    • Added some better scheduling logic around station band switching
    • Fixed bug in saving of band hopping information
    • Cleanup some compiler warnings
    • Updated frequency list with new locations for 40m and 80m
    • Do not reset frequency on saving of configuration
    • Restructuring message client for external api with a python example
    • Removed most message client networkmessage serialization
    • Simplified textual network command structure
    • Initial commands supported, get and set grid locator, with example app udp.py
    • Working through some common api commands
    • Updated API to be better organized and scoped functions
    • Updated band hopping to not hop bands when on the frequency
    • Use new dialFrequency function for grabbing the current rig frequency
    • Fixed bug in frequency list
    • Fixed bug in auto band switching checkbox
    • Restored ft8apset
    • Fixed bugginess when displaying rx activity that are buffered commands
    • Added window menu for showing/hiding band activity, call activity, and waterfall...as well as reset all of those sizes to their defaults
    • Added selected callsign to log window. Fixed bug in window panel size restoration when new
    • Redraw overlay for more consistent look and feel
    • Fixed bug with 200Hz minimum RX frequency
    • Fixed issue with legacy Qt and toSecsSinceEpoch
    • Make sure MessageClient has QDataStream ref
    • Fixed bug in configuring band hopping
    • Fixed bug causing compound calls not to send when a grid locator larger than 4 characters was set in the configuration
    • Fixed issue with grid length. Fixed back-to-back CQs
    • Fixed alignment of red waterfall indicator
    • Fixed isFreqOffsetFree when responding to directed query
    • Fixed issue with changing frequency in response to directed allcalls
    • Fixed issues with double printing of messages and skipping printing some frames
    • Fixed printing of grid in compound call messages
    • Allow changes to station message from external programs
    • Fixed compound callsigns not displaying in the heard list
    • Fixed display of messages that drift more than a few Hz during transmission
    • Fixed configuration of band hopping to reset cached band position after configuration save. Fixed issue with band hopping not working across a date transition
    • Bump to v0.4.2



2018年8月12日日曜日

MSHV version 1.83 FT8の設定、ロギング、マルチスレッド


1)設定
 通常の自動シーケンス設定は2つCQing,とCQ局を呼ぶ時
 CQing マルチ アンサー自動シーケンス設定(CQing)
2)ロギング
 N1MM, CQRLOG, MSHV log file, ADIF
3)マルチスレッド
   MSHVを複数走らせる。無線機2台を同一PCないでMSHVを2つ動かす。

Win10,Ubuntuで動作確認済み。

1)設定
MSHV version 1.83  FT8の自動設定は3つの設定があります。
1.1)基本設定
1.2)CQing 通常の自動シーケンス設定(CQing)
  CQing in normal mode
1.3)通常のアンサー自動シーケンス設定(CQ局を呼ぶ時)
  Answering in normal mode
1.4)CQing マルチ アンサー自動シーケンス設定(CQing)
  CQing in "Multi Answering Auto Seq Protocol"
  最大5局と同時QSO可能。

1.1)基本設定:Program config
1. Options Use two decode lists. 
2. Options Double click on call sets auto is on.
3. Options Prompt me to to log qso. 
4. Palette to 6 palette.
5. Mode to FT8
6. Decode to Deep.
7. Decode to Enable AP.

1.2)CQing 通常の自動シーケンス設定(CQ)
IF CQing in normal mode
1. ASeq Label to red color.  添付絵参照
2. RESET QSO (make to radio is clear).
3. Press TX6.
4. Auto Is OFF to ON

1.3)通常のアンサー自動シーケンス設定(CQ局を呼ぶ時)
IF Answering in normal mode
1. Check LTR (Lock TX RX). 添付絵参照
2. ASeq Label to red color. 添付絵参照
3. Double click to CQing station in to list 1 (Messages).

1.4)CQing マルチ アンサー自動シーケンス設定(CQ)
IF CQing in "Multi Answering Auto Seq Protocol"
1. Options "Multi Answering Auto Seq Protocol" or CTRL+`
2. Uncheck LTR (Lock TX RX). 添付絵参照
3. Auto Is OFF to ON.
TX Slot1の時はQSO開始ごCQを出します。TX Slotは最大5Slotで
最大5局と同時または1、2シケーンス遅れQSOできます。

Config

 

 

CQing

_._,_._,_


2)ロギング
*MSHVのLogはMSHVフォルダーにある。
   MSHV/log/mshvlog.edm
   mshvlog.edmファイルフォーマットは多分独自仕様。ADIFではない?
*MSHVはUDP ADIF QSO logを送ることができる。。
(127.0.0.1:2237 / 192.168.0.255:2237)
*MSHVはUDPリクエストを受け付けないようです。またデコードしても
UDPは出さない。WSJT-X、JTDX、FT8CallはデコードでUDPを出す。

*Log4OMはWSJTX.adiを参照しUPDの両方を見ている、MSHVはWSJTX.adiに
書き込まない。 それでNG.
*N1MMはWSJTX.adiを参照しない、UDPを受け取るだけなので問題なく動く。
*CQRLOGもWSJTX.adiを参照しない、UDPを受け取るだけなので問題なく動く。
*RumLogNGはLog4OMを同じで動きません。
*GridTrakerはMSHVがデコードでUDPを出さないでのアイドル状態。
*Logger32,DXkeeperは動くようです、Web検索から。

MSHV+JTAlertは試していません  、JTALertを捨てました。捨てた理由はDBが大きくなりPCのパワーを使うから。
多分MSHVがデコードでUDP出さないのでQSO logだけ表示かも??

いまのところ うちの環境ではMSHVのLogをADIFに変換して、Log4OM,
RumlogNGにインポートしかないです。
今日のメーリングリストからUDPのフルサポートしてくれと ありました。そのうちよくなる。

MSHV log

N1MM log

 



3)マルチスレッド
MSHVマルチスレッド(MSHV複数RUN) テストです。
メトロスキャター VHFで無線機2台同時に使いたい(6m、2m)、これがベースにあるのかも?。

FT8でマルチスレッドで試して見る。
環境:
*FT817+TS590の組み合わせ。
  FT-817  Signaling USB CAT 9600 8b np s2
      TS-590G DigMaster Pro3 CAT 38400 8b np s1
*SDRplay2 CAT無し+TS590Gの組み合わせ。

結果:問題なくCAT 2つもUSB codecも2つ認識して動く。
注意点1:USB codecはSignaling USBとDigMaster Pro3の2つなります。
      USB codecは USBポートを分けること。ハブなどで共有しないこと。
      ハブなどで共有すると1つしか認識しない。
注意点2:MSHVを2つ動かすときは:
1)始めの起動したMSHVの設定は 最後に終了したMHHVの設定で起動される。
  例)サウンドとCATは最後に終了した設定。。
2)2つ目の起動はあたらにCAT, Soundの設定をする必要がある。

WSJTX,JTDXはマルチスレッドはできない。警告がでる。
winの裏技で2つ動かすことができるが 問題もでる。
問題:PSKreportをONにすると どちらか1方のレポートがPSKreporterにUp
される。これでありえないレポートになることになる。
***MSHVではこの問題は起こらない。 



 

 

 

 



2018年8月6日月曜日

本栖湖 移動??

本栖湖から8/3~8/5までのあいだに無線やる予定だったが。キャンプ場は満杯で無線は無理でした。ウインドサーフィン、花火、SUP。。。。
SUP
Win

犬もバランスをとる
SUP

Win
SUP


でかい
--

--
--

--