FLDIGI on Android Question
Happy New Year, Folks... :)
I tried to install FLDIGI for Android on two devices that run GrapheneOS, which is an AOSP(Android Open Source Project) Rom.? If you're not familiar, GrapheneOS has higher security built into it and as such runs Google Play in a sandbox so it doesn't have copious access to everything on the phone or tablet (basically runs as a user level app and not 'root').
I attempted to install FLDIGI on a Google Tablet running GrOS and it errored out with 'App not installed as app isn't compatiable with your phone'.? I tried installing it on my Google Pixel 8 phone running GrOS as a test and it errored with the same message.? Now I'm able to install apps from the Google Play store with no issues and even sideload from F-Droid and other repositories so I haven't seen this error with any other apps I've used so far (This is the first time seeing an error of any kind).
Is FLDIGI actually looking for a Google OEM ROM image (via a specific OS identifying string) because it seems to have a problem with an AOSP version?
The APK I attempted to install was version 1.5.0 from the Sourceforge repository.
Any ideas?
Thanks!
Steve Baetz (N2YNQ)
|
Re: FLDigi Newbie Question...
<HM> is E3 with bad spacing. 4 dits 2 dahs instead of one dit (space) 3 dits 2 dahs.
?
John VA3KOT?
|
Re: Icom IC-7100 USB Driver
Wow, Dave, some great info there.
?
With regard to recent Icom radios like the 7300, 7610, 9700, they use Silicon Labs CP210x and they are all explicitly serialized including the model of the radio and an actual serial number.? So, for example ATTRS{serial} would include something like IC-7300 12345678 A and IC-7300 12345678 B, which would be two different USB ports since they are created as a pair.? This makes it very easy to make a UDEV rule to make the radio show up as the same "friendly named" USB device every time as Dave points out.? I do not know anything about the IC-7100 specifically other than what is published on the Icom website under the IC-7100, Support/Download, Tips for the USB port settings, which says basically the same thing as I described for the other three radios.
?
I also run Linux Mint 22 and have two newer Icom radios controlled over USB using UDEV rules.? No driver required.
?
I agree with the commentary on chips.? The CH-340 seems to be the worst of the bunch and I have yet to see any serialization on a CH-340 device. Maybe it is possible and I have just not seen it.? However, I do faintly recall reading something somewhere that the CH-340 device does not support serialization.? But, I could be wrong.? It has been a minute.?
?
73,
?
Tim
KK9T
|
Re: Icom IC-7100 USB Driver
No sudo needed, just open a terminal window, and enter...
dmesg -WH? (On Debian/Ubuntu/Mint based systems at least.)
Nothing will happen, until you connect, or disconnect something, then it'll show you what it is, or was etc.
Chances are the ICOM's use something generic for the USB/Serial part of things, that does not have any unique identifier (other than the I/O "path" to it) that you could use to create a udev rule, so you could have "reliable" /dev/ttyIC9100main and /dev/ttyIC9100sub virtual serial devices each and every time.
So long as, the device hardware path to it, is fixed.
I've just given up with such Prolific, SiLab and other generic chipset based things, as on many modern PC's (some laptops especially) even the "hardware numerical path" to external devices varies each time the system is powered up, or in one case when warm rebooted!? Probably due to the use of nested internal USB Hubs, inside the PC, and the way they are enumerated too.
At least FTDI based devices (the "Genuine" ones at least) all have a unique serial number that you can use for UDEV rules.
Resulting in (for example) a nice 100% reliable each and every time /dev/ttyICR9000 device to tell the software about.
Regardless of what host computer USB orifice I plug it's lead into, be that direct on the back of the PC, or via any combination of hubs.
The rule (in /lib/udev/rulesd/99shack.rules) for that device is:-
#IC-R900
SUBSYSTEM=="tty", ATTRS{serial}=="A10NDGR5", SYMLINK+="ttyICR9K"
That serial number "A10NDGR5" is unique to that particular USB<>C-IV lead, in fact, that particular embedded USB/Serial bridge chip used in the lead assembly!
I also have, among others...
#FT-736r
SUBSYSTEM=="tty", ATTRS{serial}=="A50285BI", SYMLINK+="ttyFT736"
(Based on the embedded serial number of a FTDI based USB to TTL serial adapter board, commonly used for working with Arduino's that don't have their own USB port.)
#TM-V71
SUBSYSTEM=="tty", ATTRS{serial}=="AK06ML2R", SYMLINK+="ttyTMV71"
(Based on the embedded serial number of a commercial FTDI based cable)
All result in the same /dev/tty device each and every time, so no confusion, even after a RFI event, they come back just the same after the system re-enumerates things.
(The system default assigned /dev/ttyUSB0 or 1 etc, are still present.? If you have application software that can't, or wont accept custom port names, you can often launch such programs from a script, in which you can "readlink /dev/ttyFT736" for example, and put the resulting normal "ttyUSB4" assignment for example, into a system variable from where you can hopefully specify that on the command line that launches the program, or feed it in some other way.? I've even grep'd and replaced a config file "port value" before invoking the program in the past.)
FTDI might be more expensive than others, but you get what you pay for, and an easier life too!
In the UK, "Technofix.uk" sell such cables for sensible costs, and they always work.? (Even on windows, the update service will find the correct driver, if not already installed.)
Google "writing linux udev rules" for some background, but be aware the learning curve is steep at first, but stick with it, they really do work very well.? SO LONG AS there is something "unique" about each such USB device.
Sadly, most equipment makers take the cheap generic route.?? Even though many of those such devices can also be connected to an external EEROM, where such unique info can be stored, and will override the chip's own default when a host system enumerates it on connection / re-connection.
Many common audio codec chips (Cmedia for example) can also do that, but again most device makers don't want the expense of extra parts and the process of creating and assigning such unique ID codes.
It could be possible to "dead bug" such an additional chip, if the codec/bridge chip's needed pins are not connected to anything else. And one has the eyes of a hawk plus microsurgery soldering tools!
One day, all this might be easy, but I'm not holding my breath!
Seasons Greetings...
Dave G0WBX.
--
Created on and sent from a Unix like PC running and using open source software:
|
Re: FLDigi Newbie Question...
Thanks Bob,
?
I've seen it in both CW and RTTY, the only modes I've spent any time with. I've read about prosigns and abbreviations, assuming that's what they are. But, they seem to show up randomly and in places that don't make any sense to me, in the middle of a word or even a callsign. I've thought they were possibly typos, QRN, QSB, configuration/decoder errors, erratic keying (CW), etc.
?
Recent example (CW),
?
C? T V<HM>OZO V<HM> OZO V<HM>OZO K ) T T DE VE3OZO VE3OZO VE3OZO K T
?
The default character for the <HM> prosign is "{" which would seem to rule out typo as it's a long way from "E3" on a qwerty KB. It's somewhat consistent in the example, "E3" is being decoded as "{" in the first 3 callsign instances but correctly in the last 3, which suggests a timing issue with sending.
?
Trying to figure this out has at least made me more familiar with the program and hopefully continued use will eventually reveal the reason(s). Thanks again. -- Charles?
|
Re: Icom IC-7100 USB Driver
Robin
I have IC 705, IC 7100 and access to IC 7300. I have no issues I use Flrig for PTT; when plugged,?I'll see the drivers?listed.
ls /dev/serial/by-id? ? ? ? will help you.
73
Don Poaps
New Westminster, BC
VA7DGP DATA VA7QU ? VOICE Winlink:?va7dgp@...
Subject://wl2k ? ? ? ? ?
ALLSTAR ?530780
Hamshack Hotline5971
Mid-Island Phone Mesh 2210 2232
? ? ? ? ? ? ? ? ? ?
On Sun, Dec 29, 2024 at 10:32?AM Bob Cameron, VK2YQA via <bob3bob3= [email protected]> wrote:
Hi Robin
The short answer is that (the current) linux already has the
driver provided within the kernel, so nothing extra needs to be
done. Windows on the other hand requires a manual install. For
Icom's that is an exe download from their site.
I don't know the 7100 in detail, but the 9100 & 7300 have an
external USB hub, UART and PCM device. If you look at the kernel
log (sudo dmesg) before and after hot plugging the rig you will
see these module load. The serial/UART looks something like "usb
1-1.3.1: cp210x converter now attached to ttyUSB0" and the ALSA
base sound device "Burr-Brown from TI USB Audio CODEC"
If you don't see this detail something strange is going on.
Cheers Bob VK2YQA
On 30/12/24 05:09, Robin, KK7MSN via
wrote:
I thought I had a site providing some serious help on this
issue, but, so far, I'm still searching for that site I can't
find in the browser history.
?
So. Does anyone have some definitive information concerning
installing a usb driver for Linux? In my case, Linux Mint 22.
Apparently, Github has something named completely different and
unrecognizable regarding this issue. But again, I've lost track
of it.
?
--
Don Poaps
VA7DGP: data
VA7QU:? ?voice
|
Re: Icom IC-7100 USB Driver
Hi Robin
The short answer is that (the current) linux already has the
driver provided within the kernel, so nothing extra needs to be
done. Windows on the other hand requires a manual install. For
Icom's that is an exe download from their site.
I don't know the 7100 in detail, but the 9100 & 7300 have an
external USB hub, UART and PCM device. If you look at the kernel
log (sudo dmesg) before and after hot plugging the rig you will
see these module load. The serial/UART looks something like "usb
1-1.3.1: cp210x converter now attached to ttyUSB0" and the ALSA
base sound device "Burr-Brown from TI USB Audio CODEC"
If you don't see this detail something strange is going on.
Cheers Bob VK2YQA
On 30/12/24 05:09, Robin, KK7MSN via
groups.io wrote:
toggle quoted message
Show quoted text
I thought I had a site providing some serious help on this
issue, but, so far, I'm still searching for that site I can't
find in the browser history.
?
So. Does anyone have some definitive information concerning
installing a usb driver for Linux? In my case, Linux Mint 22.
Apparently, Github has something named completely different and
unrecognizable regarding this issue. But again, I've lost track
of it.
?
|
I thought I had a site providing some serious help on this issue, but, so far, I'm still searching for that site I can't find in the browser history.
?
So. Does anyone have some definitive information concerning installing a usb driver for Linux? In my case, Linux Mint 22. Apparently, Github has something named completely different and unrecognizable regarding this issue. But again, I've lost track of it.
?
Thanks and 73
|
Re: FLDigi Newbie Question...
Were you listening to CW (Morse code)?
Two of the ones you've listed (AS and AR) are recognized Morse
code prosigns. I'm not sure about the other two. They are sent as
Morse characters as if the two letters were run together and sent
as one. AS means 'wait a second' and AR means 'end of
transmission'. There are lots more. Fldigi recognizes them and
shows them inside angle brackets to distinguish them from the
usual random letters you often see listening to Morse. For more
info see the Wikipedia article on prosigns.
Bob W6CP
On 12/29/24 03:19, W9ARO via groups.io
wrote:
toggle quoted message
Show quoted text
In the FLDigi receive window I often see text enclosed in
open/close angle brackets such as <AS>, <AR>,
<HM>, <VE>. What are these and where can I find a
reference guide?
|
Re: FLDigi Newbie Question...
Try this
?
73
Greg Sanders KE5DXA?
|
FLDigi Newbie Question...
In the FLDigi receive window I often see text enclosed in open/close angle brackets such as <AS>, <AR>, <HM>, <VE>. What are these and where can I find a reference guide?
|
fldigi 4.2.06.17 posted for testing
Change to THOR-25 modem, increasing interleave depth to 1
second.? NOT compatible with previous test releases.? This change
should improve the decoder under NVIS conditions, such as
Mid-Latitue disturbed:
??? THOR-25
?? ?
????? * add new THOR modem with following characteristics
??????? . symlen = 320
??????? . samplerate = 8000
??????? . flushlength = 20
??????? . bandwidth = 460
??????? . interleave depth = 25, 1 second
??????? . IEEE coefficients for viterbi encode/decode
algorithms
????????? THOR_K15? 15
????????? K15_POLY1 044735
????????? K15_POLY2 063057
??????? . objective to provide highest baud within 500 Hertz
bandwidth for
????????? European amateurs
????????? .CPS test text:
???????????? "0123456789
????????????? abcdefghijklmnopqrstuvwxyz
????????????? ABCDEFGHIJKLMNOPQRSTUVWXYZ"
???????????? number chars:????? 66
???????????? overhead:???? 6.480000 sec
???????????? xmt time:???? 10.280000 sec
???????????? xmt samples:? 134080
???????????? chars/sec:??? 6.42
????? * assigned secondary RsID code 691 to THOR-25
????? * increased flush length for all THOR baud rates
????? * added configurable start and end of signal shaping to
these modem types:
??????? . dominoEX
??????? . psk
??????? . mfsk
??????? . rtty
??????? . thor
??????? . selectable on configuration tab Modem/General
????? * restored selectable paths to all THOR modem types
Bench tests with the above test parameters
produced 100% decode.
73, David
W1HKJ
|
I need to get caught up with fldigi features, it's been a while.
Thanks for the heads up re. PSM.
David KD4E
On 12/28/24 15:23, Bob Cameron, VK2YQA
via groups.io wrote:
toggle quoted message
Show quoted text
I used it extensively for beaconing a position and nmea/gpx
file, plus a through windscreen image when I was driving about
in remote VK. I used a changing script with file aging plus the
events feature. (ie each file was sent 6 times, as 3, 2, 1 as 15
min events)
Easier to do with flamp-shell now though.
Busy frequency? Use PSM (that is part of fldigi) It delays TX
until the channel is clear.
Cheers Bob VK2YQA
On 29/12/24 06:34, DavidC KD4E via
groups.io wrote:
Could this be useful for daily path-specific propagation
probing?
Send messages 3x or 4x daily to a station, or a short list of
stations.
Do so on several bands.
An app at the receiving station(s) then evaluates the
time-to-complete an
accurate transfer and responds with a report of the best-band to
use at the
moment.
The next level might be to automate mutual band-switching so as
to maintain
2-way connectivity for emcomm, etc.
QUESTION: How would the system check for a busy frequency - if
the transmissions
are automated? (And, could it automatically seek a not-busy
alternative frequency?
I'm guessing it might have to wait for a break in activity to
signal the receiving
station(s) to also change frequency. This is starting to sound
like ALE ...)
Thanks,
KD4E
|
I used it extensively for beaconing a position and nmea/gpx file,
plus a through windscreen image when I was driving about in remote
VK. I used a changing script with file aging plus the events
feature. (ie each file was sent 6 times, as 3, 2, 1 as 15 min
events)
Easier to do with flamp-shell now though.
Busy frequency? Use PSM (that is part of fldigi) It delays TX
until the channel is clear.
Cheers Bob VK2YQA
On 29/12/24 06:34, DavidC KD4E via
groups.io wrote:
toggle quoted message
Show quoted text
Could this be useful for daily path-specific propagation probing?
Send messages 3x or 4x daily to a station, or a short list of
stations.
Do so on several bands.
An app at the receiving station(s) then evaluates the
time-to-complete an
accurate transfer and responds with a report of the best-band to
use at the
moment.
The next level might be to automate mutual band-switching so as to
maintain
2-way connectivity for emcomm, etc.
QUESTION: How would the system check for a busy frequency - if the
transmissions
are automated? (And, could it automatically seek a not-busy
alternative frequency?
I'm guessing it might have to wait for a break in activity to
signal the receiving
station(s) to also change frequency. This is starting to sound
like ALE ...)
Thanks,
KD4E
|
Could this be useful for daily path-specific propagation probing?
Send messages 3x or 4x daily to a station, or a short list of stations.
Do so on several bands.
An app at the receiving station(s) then evaluates the time-to-complete an
accurate transfer and responds with a report of the best-band to use at the
moment.
The next level might be to automate mutual band-switching so as to maintain
2-way connectivity for emcomm, etc.
QUESTION: How would the system check for a busy frequency - if the transmissions
are automated? (And, could it automatically seek a not-busy alternative frequency?
I'm guessing it might have to wait for a break in activity to signal the receiving
station(s) to also change frequency. This is starting to sound like ALE ...)
Thanks,
KD4E
toggle quoted message
Show quoted text
On 12/28/24 13:54, Robert, KK5VD via groups.io wrote: Richard,
I sure it was a request by a ham operator some time ago before I took over coding FLAMP. I have made changes to the "Events" over the years making it a little more dynamic. Like many things in life, it's better to have it and not need it then needing it and not having it, or so goes the theory. I can see a use for it, (Example) a daily at 1200 noon broadcast of a specific series of messages.
Robert
|
Richard,
I sure it was a request by a ham operator some time ago before I took over coding FLAMP. I have made changes to the "Events" over the years making it a little more dynamic. Like many things in life, it's better to have it and not need it then needing it and not having it, or so goes the theory. I can see a use for it, (Example) a daily at 1200 noon broadcast of a specific series of messages.
Robert
|
For which use case is the FLAMP Events feature a solution??
?
It looks like file broadcasting, either intervals or continuous, but why do I want to do that?? Seems like a solution in search of a problem ...
|
The current release of Hamlib is now version 4.6
?
fldigi hamlib control does not work with my Yaesu FT-890.
When I click Initialize, nothing happens and hamlib becomes unchecked.
Hamlib NET rigctl does work with my SDR.
?
The Yaesu FT-890 does work with Hamlib 4.5.5.
?
I tried fldigi 4.2.06 and fldigi 4.2.06.17
I am using a Raspberry Pi 5 and Dietpi debian bookworm. I?have a USB to RS232 cable.
?
|
Re: flrig 2.0.05.75 alpha release
Hi Yip,
Things are finally beginning to settle down after my marriage in
August.? Please test version 2.0.05.90 posted at
David
On 9/17/24 17:25, VR2VRC via groups.io
wrote:
toggle quoted message
Show quoted text
Dear David
?
IC-7610 it some difference of IC-7600, Date Time CIV command
should 1A 05 01 58 & ?1A 05 01 59, and IC-9700 it miss
Time Sync funtion , hope can update in next version,
thanks!??
?
IC-7610 CIV
?
IC-9700 extra control
?
IC-9700 Date Time CIV :? 1A 05 01 79 & ?1A 05
01 80
?
73
Yip VR2VRC
|
Re: No S/SWR/Power Meter on Ten Tec 550 Pegasus
Download
from
Build and test enabling the "Trace rig class get code"
Open the "View Trace" dialog.? Run the transceiver with this
version of flrig, testing both in Rx and Tx.
Shut down and send me the trace.txt file found in $HOME/.flrig
David
On 12/26/24 12:33, Geoffrey Mitchell
Marr, W6MKA via groups.io wrote:
toggle quoted message
Show quoted text
Is there anything more I can add to help with
troubleshooting?
|
W9ARO
Don Poaps, VA7QU
Bob W6CP
Greg Sanders
Dave, W1HKJ
DavidC KD4E