Date   

Re: AndFlmsg; attaching forms to text msgs? sent messages not always listed as sent

John (vk2eta)
 

Hi Ole,

Further information on this.

Your message may well have been received over SMS properly. Let me explain.

The default in Andflmsg for the setting "Force compression" is off.

This means that when sending a message the app will only compress if it saves transmission characters.

This only occurs when the size of the message reaches a sufficient size.

This explains why one liners are sent in clear text and larger multiline ones are compressed.

A compressed messages has all its data part, not the header (form and filename for a wrap format, origin  etc...) enclosed by the following strings: "[b64:start]" and "[b64:end].

As long as your received wrap message ends with [WRAP:end] it arrived complete and can be imported into Flmsg.

See example below.

Now this feature may not be desirable and can be removed for sharing messages. In fact if the format selected is Raw-Flmsg it should not be compressed anyway.

So I need to change a fee things.

Let me know if that is matching what you see.

All the best 

73, John

P.S. example of compressed message:

[WRAP:beg][WRAP:lf][WRAP:fn VK2ETA-20201019-232421Z-6.309]<flmsg>2.0.4
:hdr_fm:22 
VK2ETA 20202010143605
:hdr_ed:22 
VK2ETA 20201910232421
<ics309>
[b64:start]
AUxaTUEAAAHKXQAAQAAAHRpJxkUc2oFaGiqydn0/YEiMK9k1sYkDs5np+eAXLy1e
NkkmcwMdr3pHnojcVE0MzU0qxWqI6FbymGRx9U6x+Ovg8/PngIU4bZhr/ug1jooH
Jsnuo0i4mSPZeiLttnvJUa8yPV8x2bZZl97HbCCGWodo8fjG/7yZwxs3+0hV4hSf
lmwpDA==
[b64:end][WRAP:chksum 26C4][WRAP:end]




Re: AndFlmsg; attaching forms to text msgs? sent messages not always listed as sent

John (vk2eta)
 

Hello Ole,

I tested both the wrap and raw format with "share as plain text" and sent to another phone by SMS. I used an ics309 form and filled up 5 lines of the form, plus the incident field with data and in both cases i got a successful transfer.

My suspicion is that this is related to the limit of the number of characters which can be sent per sms (each sms can only send 170 characters and to get around this telco limitation the phones will send multiple smss and reassemble them into a single message on the receiving side).

To verify this can you please disable the compression option in the Settings/Data exchange/Use Compression.

I think the random characters you saw is the Base 64 compressed text (On by default).

With compression  off you can see what is missing in the received message.

Based on your results we can take it from there. Thanks.

73, John


Re: AndFlmsg; attaching forms to text msgs? sent messages not always listed as sent

Ole Helgerson KI7MBR
 

Hi John,

Last Thursday during our ARES "Great Shakeout" earthquake exercise, I used the AndFlmsg ICS 309 form on the Android phone to record radio communications.  I learned a couple of things

  • having a digital copy to review on a large screen provides an unforgiving review for catching typos and  omissions (whew)
  • proof reading is a good idea before sending
  • the entire form sent ok via Gmail, though one person's browser, an Apple I think, would not open the form.  On the my W10 machine, the form opened with Firefox, Chrome and Edge.
  • What about SMS?  The transmission reverted back to lots of random appearing letters and numbers with a couple of clues as to the form id. 

Had some spare time Saturday to test sending forms via SMS.  Went down the list of ICS forms on my phone, filling fields in each form with "Qwerty"  or similar.  Results: only about half or less of the forms sent the data ok via SMS, the rest sent random appearing alphanumeric characters.   The ICS 309 was curious.  I redid the test today to be sure. After filling the header and "Prepared By" then adding only one line of data at the top of "Box. 5,"  the data went ok by SMS.  With six lines of data entered, it reverted to strings of alphanumeric characters in the SMS message.  As a test address I used my own mobile number.

Dunno here what it means, but I hope useful info.

73, KI7MBR  Ole


Version 1.3.11 of AndFlmsg

Dave
 

posted at http://www.w1hkj.com/files/AndFlmsg/

and at SourceForge.

The changes from the previous version are:

- Added option to share messages with SMS application as plain text

- Messages shared from the Outbox are either moved automatically to the Sent folder if the sharing application (E.g: email or SMS app) returns a positive completion OR, if negative, prompts the user for the message to be moved from Outbox to Sent folders.

- Re-added 8PSK FEC modes up to 8PSK500FEC as they seem to be usable with the newer devices.

- Minor code clean-ups.

73, David, W1HKJ, for
    John, VK2ETA


fldigi 4.1.15 posted

Dave
 

at http:www.w1hkj.com/files/fldigi/

and at Source Forge

Includes:

    1. New meter control to assist in setting up input audio levels


    see: audio input adjustments

    2. New Frequency Measurement Test, FMT, analysis modem, see: FMT Tool

    3. New macro tags designed for W1AW style CW broadcasts.

    4. Restructure and update of on-line (html), and pdf help documents

    5. Code changes to comply with changes to C++ compiler.

This release has been tested on

  • Mint-20/64,
  • Mint-19/64,
  • Red Hat F32/64,
  • OS-X 10.7.5,
  • macOS 10.13.6, 10.14.6, 10.15.4
  • Windows 7, Windows 10

Contributions to this release were by several developers (see list below).

See you on the waterfall.

73, David, W1HKJ

Version 4.1.15
  
   * Maintenance / Update release

    - David Freese  <w1hkj@...>
      fb6be0c2d: Doxygen cleanup
      80394e316: documentation update
      7f246f123: VUmeter
      ab69c22f4: <@LOCK macro
      c30b39305: Sound Card Record
      8ef2bd201: fmt csv
      bc14a38b2: W1AW-macros
      98de9a656: xmlrpc memory leak
      67dd7b42f: County Lists
      685e4384c: fmt modem
      2a1cef26f: xmlrpc rig timeout
      75754d4fd: doc update
      f1600c636: fmt-docs
      06c2cebae: kml
      b4575f656: DXCC lookup
      df9a5978b: status locale
      a8d02cda7: Level indicator
      8915b0450: FeldHell
      209741778: hamlib NET
      cd7ec00ac: NanoIO
      f0230a8b2: feld-hell font
      e5b67ec7d: wf
      2e90a584b: exit cleanup
      3c9d07f00: debug source
      42557ed7a: cluster dupcheck
  
    - Andreas Scholz  <entwickelheini@...>
      48cd15424: ADIF Conformity
  
    - Kosta Arvanitis  <karvanitis@...>
      4887da833: XmlRpc Exit
      cba23e535: Macros
  
    - Rik van Riel  <riel@...>
      f8a29a146: Navtex

    - Richard Shaw <hobbes1069@...>
      e76e5570: NULL / nullptr
      4c7fcee2: c++17 fixes
      396712d9: FSQ
      136b6719: trx_mode
      5e882d6c: rigCAT
      08630d6c: MinGW
      b4de5199: Fix warning about boundary issue.


Re: NBEMS x 2

roland.hartmann@...
 

Hi Mike,

 

start fldigi with different parameter for config directory. In my case I have two TRX have done it in those case:

 

D:\tools\Afu\Fldigi-4.1.14\fldigi.exe --config-dir "C:\Users\rolan\fldigi-ft991a"

 

D:\tools\Afu\Fldigi-4.1.14\fldigi.exe --config-dir "C:\Users\rolan\fldigi-ic7300"

 

73 de Roland, DK4RH

 

 

Von: nbems@groups.io <nbems@groups.io> Im Auftrag von Mike Walker via groups.io
Gesendet: Samstag, 17. Oktober 2020 19:01
An: nbems@groups.io
Betreff: [nbems] NBEMS x 2

 

I have been through quite a few posts and haven't seen this one yet. I would like to run two copies of fldigi on the same computer but controlling different radios. I have tried two different versions loaded into separate directories (Win7) but every time I change a parameter in one, it is copied in the other. What I want to do is have an HF copy and a VHF copy. That way I could receive local traffic on an FM repeater, copy and paste into the HF copy and transmit on SSB and visa versa.
There are several stations in my local ARES area looking to do this. Any help, thoughts, suggestions and/or ideas would be greatly appreciated.

73 de Mike AB8MW


Re: NBEMS x 2

Robert Farrington
 

 


Re: NBEMS x 2

George Blakeslee
 

Mike

It can be done but takes several steps which I did not find too clear in the manual.
It involves setting up multiple desktop short cuts AND THEN configuring the TCP-IP ports of each.
AND it has to be done in matching ports for respective FLmsg and FLamp apps.
If you like, we can sked a time to chat on the phone and I will coach you through it.

73  George  N1GB

On Sat, Oct 17, 2020 at 1:00 PM Mike Walker via groups.io <m_walker_sr=yahoo.com@groups.io> wrote:
I have been through quite a few posts and haven't seen this one yet. I would like to run two copies of fldigi on the same computer but controlling different radios. I have tried two different versions loaded into separate directories (Win7) but every time I change a parameter in one, it is copied in the other. What I want to do is have an HF copy and a VHF copy. That way I could receive local traffic on an FM repeater, copy and paste into the HF copy and transmit on SSB and visa versa.
There are several stations in my local ARES area looking to do this. Any help, thoughts, suggestions and/or ideas would be greatly appreciated.

73 de Mike AB8MW



--
George Blakeslee


Re: NBEMS x 2

Ed W3NR
 

On 10/17/20 1:00 PM, Mike Walker via groups.io wrote:
I have been through quite a few posts and haven't seen this one yet. I would like to run two copies of fldigi on the same computer but controlling different radios. I have tried two different versions loaded into separate directories (Win7) but every time I change a parameter in one, it is copied in the other. What I want to do is have an HF copy and a VHF copy. That way I could receive local traffic on an FM repeater, copy and paste into the HF copy and transmit on SSB and visa versa.
There are several stations in my local ARES area looking to do this. Any help, thoughts, suggestions and/or ideas would be greatly appreciated.

73 de Mike AB8MW
_._,_._,_

It's covered in the Help Manual.

Ed W3NR



NBEMS x 2

Mike Walker
 

I have been through quite a few posts and haven't seen this one yet. I would like to run two copies of fldigi on the same computer but controlling different radios. I have tried two different versions loaded into separate directories (Win7) but every time I change a parameter in one, it is copied in the other. What I want to do is have an HF copy and a VHF copy. That way I could receive local traffic on an FM repeater, copy and paste into the HF copy and transmit on SSB and visa versa.
There are several stations in my local ARES area looking to do this. Any help, thoughts, suggestions and/or ideas would be greatly appreciated.

73 de Mike AB8MW


How to set up received audio level

Dave
 

See answer below Chris' query regarding version 4.1.14.71.  This is an exerpt from the next fldigi manual for 4.1.15

73, David, W1HKJ

On 10/14/20 2:55 PM, Chris E., KC2RGW wrote:
Cursory run, it seems to be working well on Win10 here.

What would you say for an empty idle passband is a good level as a baseline?  I'm never quite sure if I'm "looking too far into the noise" with the settings I have.  I find where the diamond is black and where it's yellow and split the difference generally but it's always been a guess.


Receive audio

Setting the correct hardware, operating system, and fldigi received audio levels is not difficult, but it is the one setup procedure most often done incorrectly. The most commonly used sound card devices contain either a 16 or 24 bit analog to digital (a/d) converter. A 16 bit a/d can provide approximately 90 db of signal conversion. For the 16 bit converter, if the peak audio signal that the a/d can handle is +/- 1 volt then the minimum discernable signal (1 bit) will be +/- 30.5 microvolts. If more than a +/- 1 volt signal is applied to the a/d input then either one of two things may occur, (1) the audio is clipped, or (2) the audio is wrapped, large positive signals wrap to large negative signals and vice versa.

Signal decoding and signal display are two separate software processing paths:

signal_flow.png
Signal Path

The objective in adjusting the Rx audio is to use the full dynamic range of the a/d without either incurring over or under drive. fldigi provides a number of display controls to assist in setting up the Rx audio. fldigi does not attempt to control the system input mixer controls. Those must be adjusted by the operator. Mixer control access is different for each of the supported operating systems. The input signal level effects the decoder performance and the visual presentation of the signal.

fldigi displays the raw input signal in a VU style meter. This meter is accessed from one of two signal level configuration panel and on the fldigi main dialog.

configure_signal_level_menu1.png
configure_signal_level_menu2.png
configure_signal_level.png

There are two controls that adjust the visual appearance of the waterfall. These controls are below and to the left of the waterfall, "Upper signal level (dB)", and "Signal range (dB)". The "Upper signal level" control is a gain control. 0 dB == x1,-6 dB = x2. These values are dB relative to input signal level. This control will effect the Waterfall (WF), Fourier Transform (FFT), and Signal (SIG) views. The "Signal range" control will only effect the WF and FFT views.

win10-fldigi-wf-adjust.png
Waterfall level/range controls

Set the level to -20 and the range to 70. Change the waterfall display to the "Scope" view. Do this by pressing the "WF" button twice if it is currently displaying the waterfall. You can also right click once on that button. That button acts as a rotary and is left/right click sensitive. The display should show what looks like an oscilloscope view of the received audio. This is the entire audio signal and not just the signal that is currently decoded.

win10-fldigi-signal.png
Scope view

If your sound card a/d (also referred to as codec) is functioning correctly there should be no signal offset and the signal will be centered vertically about the x-axis. Set your transceiver to a portion of the band with no signals; 14.065 MHz might suffice. Adjust the audio path gain; transceiver audio, external audio codec gain, and operating system gain for a noise level that is about -50 dB on the VU meter. Then set the transceiver to an active portion of the digital band; 14.070 MHz for PSK or 14.074 MHz for JT type digital signals. Make sure that the input gain controls are not set too hot. The peak signals do should not exceed the upper/lower gray lines on the display. The diamond indicator to the left of the fldigi AFC button will be colored as follows:

  • BLACK - no signal present
  • GREEN - signals are in the correct range
  • YELLOW - signals level high, but still OK
  • RED - signals too high, danger of decode errors

The transition levels can be adjusted on the "Signal Level" configuration panel. The default settings will be good for most users. The colors can be set to suit the users' color vision.

You can then proceed to adjust the waterfall/fft appearance when you have the audio Rx level adjusted correctly. Remember that changing the WF/FFT/SIG level and range controls DOES NOT effect the decoder signal path.

The three signal views should be similar to this with the level/range controls set to -20 and 70 respectively. The waterfall palette used is "default.pal", and the received signal is about 20 dB above the noise floor.

win10-fldigi-wf.png
Waterfall
win10-fldigi-fft.png
FFT
win10-fldigi-signal.png
Scope


fldigi 4.1.1.71 alpha posted

Dave
 

at http://www.w1hkj.com/alpha/fldigi/

Added input signal level VuMeter on main dialog in the space also occupied by the Status Bar display.  Left click on either the VuMeter or the Status Bar to toggle between the two.  The VuMeter is resizable up to a maximum range of 130 dB:

73, David, W1HKJ


Re: android phone and FLDIGI

KC2UKU ED
 

On Tue, Oct 13, 2020 at 05:12 AM, vh2 wrote:
http://www.w1hkj.com/files/AndFlmsg/
Right but it can be here to so in the file this the link to w1hkj as it is fldigi there is no group for for and other digital ham groups I know I look and way going to set one up my pocket are empty so I can't set one up and the free not any good 


Re: AndFlmsg; attaching forms to text msgs? sent messages not always listed as sent

John (vk2eta)
 

Hi Ole,

Thank you for the testing. Glad it's working. 

Android is not designed as a real time o/s so the "garbage collection" (i.e. the periodic memory clean-ups) can cause temporary freezes.

Few competing apps running at the same time, plenty of memory and fast processors do minimise these effects significantly.

I will update the documentation and submit the new version this weekend for Dave to publish. It will be functionally identical to the RC2 version you tested.

Good work with the ARES groups and good luck with your presentation.

All the best,

73, John


Re: AndFlmsg; attaching forms to text msgs? sent messages not always listed as sent

Ole Helgerson KI7MBR
 

Hi John,

Got it sorted out ok. I think.

Phone version says; AndFlmsg Version 1.3.11 RC2, 2020-10-2

Tested sending ICS 213 again by; SMS, Winlink, Gmail and speaker to mic (phone to tablet)

SMS; shows up as text just like before
Winlink; opened the attachment before sending; looked like the SMS version, e.g. simple text
Gmail; Html form with all the lines and boxes showed up per usual
Phone to tablet (spkr to mic); it took three tries.  First attempt; incoming email messages on the tablet beeped and caused an error.  Second try, the phone hiccuped during tx for whatever reason; maybe something had tied up the internal processor, creating a timed out msg on the receiving tablet.  Third and fourth tries were successful with two differing forms.  Moral of that story; Android devices are generally good, but bumps in the road can happen.

Hope useful.

73, KI7MBR Ole'


On Tue, Oct 13, 2020 at 12:25 PM Ole Helgerson KI7MBR via groups.io <olehelgerson=gmail.com@groups.io> wrote:
Hi John,

Apologies.  Thought that I had loaded the latest version that you'd sent and then realized,   ...um,... maybe not. 

Will delete program from phone, load the latest and try again.  73,  Ole

On Tue, Oct 13, 2020 at 10:40 AM Ole Helgerson KI7MBR via groups.io <olehelgerson=gmail.com@groups.io> wrote:
On Fri, Oct 2, 2020 at 10:10 PM, John (vk2eta) wrote:
https://drive.google.com/file/d/1xXfMlu-IXJpkuVkH7pt3S0JuJ84OlLWu/view?usp=sharing
Good morning John,

Last night I checked into the local radio club net, apparently successfully, using SMS and Winlink to send an ICS 213 form.

The file version used was "AndFlmsg-1.3.11RC2-20201002.apk"  which shows up on the phones screen as "AndFlmsg Version 1.3.11 RC1, 2020-09-29."

On SMS,  for transmission I selected "SHARE" > "for sending as plain text (SMS...)" > "WRAP" format.  It worked. Bingo!

For Winlink (Telnet), connected phone to computer with USB cable >, opened Winlink > generated a message > attached the file by browsing > posted to the outbox > send.  Again, bingo!

Also just tested tx/rx from phone to adjoining 6" Samsung tablet (AndFlmsg Version 2017-05-05).  First attempt at full phone volume created error msg "Last_Bad_CrC_Rx' file.".  Ooops, lower the speaker volume.... Second attempt with ~3/4 speaker volume came through ok; both as text in the initial window and the full ICS213 form in the received window.

Please let me know if there is anything else I can do.  Happy to be of assistance.  I mentioned the five-way capabilities (SMS, Winlink, email, two radio) on two smaller local nets last night (local club and adjoining county ARES) and will share with Oregon ARES District #1 this week per your ok.  That ARES group encompasses a six county Portland OR greater metro area, thus want to ensure I have my facts ok.   Also, after last night's briefing on the net, got an invite from our local radio club to present a "how to" session sometime via Zoom.   As my nephew in Ottawa might say, "cool beans!"

Thanks again and 73,  KI7MBR Ole'


Re: AndFlmsg; attaching forms to text msgs? sent messages not always listed as sent

Ole Helgerson KI7MBR
 

Hi John,

Apologies.  Thought that I had loaded the latest version that you'd sent and then realized,   ...um,... maybe not. 

Will delete program from phone, load the latest and try again.  73,  Ole


On Tue, Oct 13, 2020 at 10:40 AM Ole Helgerson KI7MBR via groups.io <olehelgerson=gmail.com@groups.io> wrote:
On Fri, Oct 2, 2020 at 10:10 PM, John (vk2eta) wrote:
https://drive.google.com/file/d/1xXfMlu-IXJpkuVkH7pt3S0JuJ84OlLWu/view?usp=sharing
Good morning John,

Last night I checked into the local radio club net, apparently successfully, using SMS and Winlink to send an ICS 213 form.

The file version used was "AndFlmsg-1.3.11RC2-20201002.apk"  which shows up on the phones screen as "AndFlmsg Version 1.3.11 RC1, 2020-09-29."

On SMS,  for transmission I selected "SHARE" > "for sending as plain text (SMS...)" > "WRAP" format.  It worked. Bingo!

For Winlink (Telnet), connected phone to computer with USB cable >, opened Winlink > generated a message > attached the file by browsing > posted to the outbox > send.  Again, bingo!

Also just tested tx/rx from phone to adjoining 6" Samsung tablet (AndFlmsg Version 2017-05-05).  First attempt at full phone volume created error msg "Last_Bad_CrC_Rx' file.".  Ooops, lower the speaker volume.... Second attempt with ~3/4 speaker volume came through ok; both as text in the initial window and the full ICS213 form in the received window.

Please let me know if there is anything else I can do.  Happy to be of assistance.  I mentioned the five-way capabilities (SMS, Winlink, email, two radio) on two smaller local nets last night (local club and adjoining county ARES) and will share with Oregon ARES District #1 this week per your ok.  That ARES group encompasses a six county Portland OR greater metro area, thus want to ensure I have my facts ok.   Also, after last night's briefing on the net, got an invite from our local radio club to present a "how to" session sometime via Zoom.   As my nephew in Ottawa might say, "cool beans!"

Thanks again and 73,  KI7MBR Ole'


Re: AndFlmsg; attaching forms to text msgs? sent messages not always listed as sent

Ole Helgerson KI7MBR
 

On Fri, Oct 2, 2020 at 10:10 PM, John (vk2eta) wrote:
https://drive.google.com/file/d/1xXfMlu-IXJpkuVkH7pt3S0JuJ84OlLWu/view?usp=sharing
Good morning John,

Last night I checked into the local radio club net, apparently successfully, using SMS and Winlink to send an ICS 213 form.

The file version used was "AndFlmsg-1.3.11RC2-20201002.apk"  which shows up on the phones screen as "AndFlmsg Version 1.3.11 RC1, 2020-09-29."

On SMS,  for transmission I selected "SHARE" > "for sending as plain text (SMS...)" > "WRAP" format.  It worked. Bingo!

For Winlink (Telnet), connected phone to computer with USB cable >, opened Winlink > generated a message > attached the file by browsing > posted to the outbox > send.  Again, bingo!

Also just tested tx/rx from phone to adjoining 6" Samsung tablet (AndFlmsg Version 2017-05-05).  First attempt at full phone volume created error msg "Last_Bad_CrC_Rx' file.".  Ooops, lower the speaker volume.... Second attempt with ~3/4 speaker volume came through ok; both as text in the initial window and the full ICS213 form in the received window.

Please let me know if there is anything else I can do.  Happy to be of assistance.  I mentioned the five-way capabilities (SMS, Winlink, email, two radio) on two smaller local nets last night (local club and adjoining county ARES) and will share with Oregon ARES District #1 this week per your ok.  That ARES group encompasses a six county Portland OR greater metro area, thus want to ensure I have my facts ok.   Also, after last night's briefing on the net, got an invite from our local radio club to present a "how to" session sometime via Zoom.   As my nephew in Ottawa might say, "cool beans!"

Thanks again and 73,  KI7MBR Ole'


Re: android phone and FLDIGI

Vince N2JRS
 

They are on the w1hkj.com site:
 http://www.w1hkj.com/files/AndFlmsg/



Vince



-------- Original message --------
From: KC2UKU ED <kc2uku@...>
Date: 10/13/20 7:39 AM (GMT-05:00)
To: nbems@groups.io
Subject: [nbems] android phone and FLDIGI

I just check the files here and I didn't find anything on androids and digital this is some thing that can used old android phone I will see if I can find any information in a pdf file to shareand I working on a interface for this right now.... 


android phone and FLDIGI

KC2UKU ED
 

I just check the files here and I didn't find anything on androids and digital this is some thing that can used old android phone I will see if I can find any information in a pdf file to shareand I working on a interface for this right now.... 


flrig 1.3.51.30 posted

Dave
 

at http://www.w1hkj.com/alpha/flrig/

Fixed reported IC-705 mode change bug.

NOTE: this is an alpha release, Caveat Emptor.

73, David, W1HKJ