FreeDV communicating with radio after "Start Modem"

[Rick, W4XA]

Mooneer, 

I have noticed that FreeDV will control my ICOM marine  IC-M802 quite nicely!!

 It is unique I think,  because of the NMEA control set, when "Start Modem" is pressed,  it will actually power the radio ON if it's initially off and then when "Stop Modem" is pressed, it will power the radio OFF.

In addition,  if the radio was already ON to begin with, it will NOT power it off when stopping the modem (however it does leave it in the "REMOTE" mode) I suspect that's a left over from the Hamlib NMEA command set. In that case, I have to simply "power cycle" the radio to get back to local control.

I am using a SignaLink USB audio interface and a generic FTDI USB-A to RS-232C cable and mid 2012 Macbook Pro running (Ubuntu based)  KDE Neon 

I also have a fairly new ACER Win11 Core -i7 laptop and I use a similar FTDI USB-C to RS-232C cable interface and the SignaLink.

Both operating systems act the same.  I am using ver 2.3.1 on both.

It's pretty cool.

One irritating feature though is when it actually powers the radio on, it immediately tries to communicate with the radio via the serial connection but I suspect because the radio is not fully "booted" up, I get all the Hamlib errors in a popup that clears every time when I press "Ok" etc.

It of course does not do this if the radio was already on.

Would it be possible to add a few milliseconds  after  pressing  "Start Modem" to get a response for those radios that might need a couple of extra "moments"  to get their $hit together?

I suspect that maybe the M710 and a probably few others could fall into this category

Otherwise it works VERY well with my circa 2003 IC-M802 

Cheers, 

Rick

[Mooneer Salem]

Hi Rick,

I took a look at the Hamlib code for the IC-M802 and it seems to default to a timeout of 500ms. (FreeDV caps the timeout at 625ms and will not set anything higher than what Hamlib defaults to for the selected radio.) There are a couple of things we could do:

1. Have FreeDV set the timeout to 625ms even if the radio defaults to something lower.

2. Allow Hamlib to retry connection a certain number of times (FreeDV disables this, but we can defer the disable until after successful connection). Note: the IC-M802 seems to disable this by default as well, but we could also force a value here similar to (1) prior to connect.

Anyway, I'd be interested in hearing feedback from others on either of these options as they could impact other users as well.

Thanks,

-Mooneer K6AQ

--
You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/acfe4d25-b002-44e0-a848-7fa43a0c9030n%40googlegroups.com.

[Rick, W4XA]

Mooneer, 

Thanks for the quick reply!

I think maybe a retry would do the job after maybe a few hundred ms because if I immediately click on "OK" (or whatever it's asking) it's fine after that and of course, it only does it if FreeDV powers the radio on.   and in fact, I believe the radio may be responding about the same time as the popup

Thanks again!

Rick

[Mooneer Salem]

Hi Rick,

How does this Linux version work for you? https://github.com/drowe67/freedv-gui/actions/runs/26744105335/artifacts/7327484555 (You'll need to log into GitHub to download.)

Thanks,

-Mooneer K6AQ

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/3e963d37-a369-448c-acde-c3917acbd309n%40googlegroups.com.

[Rick, W4XA]

Mooneer, 

I was able to download 2.4.x and run  ...Thanks  

Same problem though, it seems like the app is asking for a "reply" before the radio is ready 

"Couldn't connect to Radio with Hamlib: Could not set current frequency

Communication timed out"

At the same time, I did hear the relays click commensurate with changing frequency and once I click "OK" to close the window, the radio is operating on the "new" frequency waterfall running etc!

And of course, if I simply turn it on first, everything works normally, but it would be nice if FreeDV could power the radio  and then run.  I suspect it will be the same with the new and current IC-M803 (that replaced the IC-M802)  

Anyone here have an IC-M803 they can try?  This happens with Windows, the MAC and Linux

Cheers, 

Rick

[Mooneer Salem]

Hi Rick, 

Thanks for the error message. How about this? https://github.com/drowe67/freedv-gui/actions/runs/26794559072/artifacts/7347988326

Thanks, 

-Mooneer K6AQ 

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/d2e6e6f2-1c39-47b9-9994-256d5ee0ea22n%40googlegroups.com.

[Rick, W4XA]

Mooneer, 

EUREKA!

That did the trick!

A little added time before polling the radio?

It works pretty nice now.  Powers the radio on and changes frequency to whatever is selected in the presets or type din the freq window before pressing "Start Modem"!

Thanks ! ! !

[Mooneer Salem]

Good to hear, just merged the changes. 

All: let me know if any problems come up for your setup due to the change.

-Mooneer K6AQ

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/05f83305-ca17-45e8-9d23-7db2945f5336n%40googlegroups.com.

[Rick, W4XA]

Mooneer, 

By "merged" do you mean that you incorporated those changes into 2.3.1 ??  (and I should download the "merged" version and try it?)

[Mooneer Salem]

Not 2.3.1 but in GitHub "master", which should eventually become part of the next release. Automated builds based on master are available at https://github.com/drowe67/freedv-gui/actions?query=branch%3Amaster (listed by OS) if you want to give it a try prior to the next release.

-Mooneer K6AQ

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/42d11562-b9cf-4045-867c-b122ebbb04a0n%40googlegroups.com.

[Rick, W4XA]

Got it!

Great!

Thanks!

[Vic Alger]

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/CAAzDfxPcu_36vOeUCN%2BvNFDE68v3M46Rfkeni1Cc7onyBPiihg%40mail.gmail.com.

[Rick, W4XA]

Anyone else out there in Radio-Land using either an ICOM IC-M802 or IC-803?

[Rick, W4XA]

Mooneer, 

Interesting turn of events....I launched the AppImage today and got the same message again with the ICOM Marine radio.  

Is it possible that the change you made is right at the "Ragged edge" of enough time to wait for response from the radio? (the radio shouldn't be changing how long it takes to respond I would think!) 

Same drill as before though,  I just click "OK" and everything works just fine

"Couldn't connect to Radio with Hamlib: Could not set current frequency

Communication timed out"

[Rick, W4XA]

Actually I was mistaken  about the message......

"Couldn't connect to Radio with hamlib: Could not retrieve current radio mode: Protocol error"

[Mooneer Salem]

Hi Rick, 

This is with the latest AppImage from GitHub, right? Maybe we need to increase the number of connect retries? (Currently 1, maybe it needs to go to 2 or possibly 3.)

Thanks, 

-Mooneer K6AQ 

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/0867cbf7-3999-4105-9cb6-909b7fc4f191n%40googlegroups.com.

[Rick, W4XA]

It was that link you sent me previously.

Couple of retries might be good.  as soon as I closed the error box it was fine!

I think the IC-M802 processor (and maybe the IC-M803) is an 8086! (Haw!  [probably not!])   and there's maybe a little delay in the RS-232C + FTDI cable/adapter 

All that together probably makes for a fairly slow response if it's immediately after power-up.  (although I think the cable/FTDI adapter is powered by the computer USB 2.0 side)

And of course, If the radio is already powered on, it never happens!

[Mooneer Salem]

Hi Rick,

OK, GitHub is currently building but once done, you can give the latest AppImage with retries set to 2 a try at https://github.com/drowe67/freedv-gui/actions/runs/27393195466?pr=1388 (the AppImages will be linked at the bottom if you have a GH account). Let me know how this goes.

Thanks,

-Mooneer K6AQ

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/68b9b62f-e54f-43ae-b3a3-5940dfa74b51n%40googlegroups.com.

[Rick, W4XA]

Will do!

Thanks!

[Rick, W4XA]

I looked at the link you provided and didn't see a freedv.xxx.x64.appimage

Is it still "cooking" or did I look in the wrong place?

[Mooneer Salem]

It's on the bottom of the page if you're logged in:

Direct link now that it's done building: https://github.com/drowe67/freedv-gui/actions/runs/27393195466/artifacts/7583202784

-Mooneer K6AQ 

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/5d91a9a3-61b3-4c7c-b34b-47b46b8cb351n%40googlegroups.com.

[Rick, W4XA]

Thanks Mooneer!

I thought I was logged in the first time but maybe not!

Found it this time though! 

[Rick, W4XA]

I've been trying it most of the day, 

No errors on start up!

It powers the radio on at "Start Modem" with no errors!

I think you may have found the sweet spot.

Anyone else on here using ICOM IC-M802/803 marine radios with FreeDV?

[Rick, W4XA]

Mooneer, 

Still using 2.4.0-dev-bd785 and the message is back on startup.  Powers the radio on, and I'm getting the message below. After I close the message, everything is fine including frequency and mode changing. 

"Couldn't connect to Radio with hamlib: Could not retrieve current radio mode: Protocol error"

But this time, if the radio is already powered on and I click the Start Modem button,  I got the message a couple of times, then it stopped doing it.

But if I power the radio off and the software powers the radio, the message above is back.  

I don't think I have changed anything.  Very strange.

[D Smith]

2,3,1 is still working fine

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/2443d54d-f741-4c5b-bcd0-f93e0d1bbdd4n%40googlegroups.com.

[Mooneer Salem]

Hi Rick, 

Any changes if you use a newer build? Later 2.4.0s have an updated Hamlib vs. 2.3.1.

Thanks, 

-Mooneer K6AQ 

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/2443d54d-f741-4c5b-bcd0-f93e0d1bbdd4n%40googlegroups.com.

[Rick, W4XA]

Mooneer, 

Thanks for the quick reply!

I just thought it strange that it worked so well for several days then again started acting like there wasn't enough time for the radio to respond on start-up (still fine after closing the message) 

Might be a USB issue since I have been having some problems with receive audio distortion that "fixes" by rebooting the computer.  maybe there's a slowdown someplace in the USB bus etc.

I am using the same cable for USB-A ---> RS-232C   and using USB0 (USB "zero" ) that is listed in the drop-down for control

 I can also use an entry       /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0  which is also selectable in Easy Setup but it seems to function exactly the same as USB0 (because it's likely "the same") 

And I was also seeing some strange vertical "banding" in the transmit and receive waterfall. 

I'll also try it with my Winblows 11 ACER laptop using a 2.4.xx dev version and see if it does the same thing.

Next time I see the strange waterfall bands,  I'll snap some pictures.

I'll switch to the latest Linux 2.4.xxx ApplImage and see what happens!

Thanks again!

Rick

[Rick, W4XA]

Mooneer, 

Just tried the (latest?)  dev version (266f) and it appears to be working properly.  no error messages so far. (woohoo!) 

I have noticed that I can still power the radio on from being completely shut down AND, even if the control head is removed, I can still power the radio on and control frequency, mode etc.  The only thing I cannot change is the power level which can be controlled with the control head if connected.

I suspect that the Icom's newest (IC-M803)  marine radio can be controlled similarly.

I really  like the option of being able to "PTT" by holding the space bar (or other programmable key!!)

Thanks for everything you're doing to make this stuff work for so many of us!!

73/Rick