![]() ![]() Imagine no internet and phone service and you're deployed to a shelter. In regards to AndFLMSG, where I see the most practical use would be mostly for receiving bulletins and messages with nothing more than a smart phone and a VHF/UHF mobile or handheld transceiver, but I will be looking into an interface to my HF rigs as well. The performance is good as the modems now coded in native C++ code for performance and is heavily based on the Fldigi modems code. The implemented modems are the FLMSG modems (including extra modes), that is all PSK/PSKR modes, including multi-carrier modes, some of the 8PSK modes, THOR, MFSK, OLIVIA, MT-63 and Domino-Ex modes. ![]() ![]() Consult the activity log and the messages as-sent. Define and save templates for facilitating the creation of new messages. Send created messages over the radio or internet. Create new messages using any custom forms or the current set of "hard coded” forms. Copy and edit received messages for replying or further forwarding (all custom forms plus the following “hard coded forms”: Blank form, Radiogram, IARU message, Plaintext, CSV, all ICS and HICS forms at present, plus the “Picture Form”). ) or cloud services (Dropbox, Google drive.), print services (E.g. Forward any form message as-is over the radio in Flmsg format OR over the internet via email, instant messaging (Facebook, Tweeter. Receive Flmsg formatted messages (any Form). What does it do? Basically most of what the fully featured version on the PC does. The addition of images and GPS data inclusion opens the usage to practical field reporting too. The inclusion of modes like MT-63 and long interleave MFSK modes allows audio coupling to be used effectively without the need for an audio interface. The integration of Internet sharing/forwarding makes this solution attractive as a relay option, possibly a mobile or portable station in a pertinent geographical location. Rigs like the Yaesu's FT-817, Icom's 703 and Elecraft's KX3 would be the typical companions of the Android phone or tablet running AndFlmsg, thereby providing a low weight, low energy requirement, access to most Flmsg services. The main objective of this development is to provide a low power highly-portable, as in mobile or backpack, Flmsg/Fldigi solution. Hence JS8 + Directed Calling = JS8Call.AndFLMSG is a combination of Fldigi and Flmsg for portable devices running Android. JS8Call has a “directed calling” protocol laid over top the base RF transport to support free-form and directed message passing.JS8Call uses a custom FT8 modulation called JS8 (Jordan Sherer designed 8-FSK modulation).You might be asking…why is this named JS8Call? Why was it renamed from FT8Call? Why not something else, like BACON or HF Messenger? Good question! It is named this way as an homage to its heritage: JS8Call is and will always be open-source and free software (free as in beer and free as in speech, do with it what you like, for sum of exactly $0). The source code modifications are public and can be found in js8call branch of this repository: While the WSJT-X group maintains copyright over the original work and code, JS8Call is a derivative work licensed under and in accordance with the terms of the GPLv3 license. It is not supported by nor endorsed by the WSJT-X development group. JS8Call is a derivative of the WSJT-X application, restructured and redesigned for message passing using a custom FT8 modulation called JS8. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |