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