开云体育

Potential enhancement request - configurable Echo Port

John, G4DRS All Messages By This Member #97941 I wonder, is it possible to have Logger32 translate the CAT data received from a connected radio before it sends it to the Echo port? I have searched the user manual, but can't see anything. That's not to say it isn't there, of course... ? The use case I have in mind is: Radio (FTdx101) connected to Logger32 via USB Amplifier (Acom 2000) connected to radio via coax and PTT cable ? At present, the amplifier automatically tunes to whatever segment it detects when I send it some RF. It is possible, however, to connect the amplifier to a serial port and have it select the appropriate band segment as the data on the serial port changes. This means the amplifier is already tuned correctly prior to RF being applied, which is probably slightly better for the amplifier. ? In a perfect world, I could connect the amplifier CAT port to the serial connector on the rear panel of the radio, but, apparently, the Acom doesn't speak FTdx101 language. Yaesu changed the format of the CAT data for the FTdx101 & FTdx10 series of radios, as I understand it. Thus, I thought a work-around could be to send the data out from the logging software via the Echo port. It would need to be translated into something more vanilla, before being sent, though- Kenwood TS2000 or Yaesu FT1000, maybe. This would compensate for the amplifier firmware's inability to communicate with the FTdx101 or FTdx10. ? Is there already a way to do this? If not, is it something that would constitute a worthwhile enhancement? Or is it only me? ? ? Cheers, ? John G4DRS
Bob All Messages By This Member #97942 Isn't that done automagically? Example, configure the primary as (say) a Yaesu whatever.? Configure the Echo port as (say) an Icom whatever. Spin the dial on the primary radio, Yaesu formatted messages are received by Logger32, decoded, and sent to the echo radio in Icom format. ? Some commands simply don't translate from one radio brand to another.? So, configure a slave port instead, and map the differences - Like CW on the primary radio CW-R on the slave. ? Or, look at section 2.5 (page 275) of the help file. ? SeventyThree(a). ? toggle quoted message Show quoted text On 04/06/2025 8:38 AM EDT John, G4DRS via groups.io <g4drs@...> wrote: ? ? I wonder, is it possible to have Logger32 translate the CAT data received from a connected radio before it sends it to the Echo port? I have searched the user manual, but can't see anything. That's not to say it isn't there, of course... ? The use case I have in mind is: Radio (FTdx101) connected to Logger32 via USB Amplifier (Acom 2000) connected to radio via coax and PTT cable ? At present, the amplifier automatically tunes to whatever segment it detects when I send it some RF. It is possible, however, to connect the amplifier to a serial port and have it select the appropriate band segment as the data on the serial port changes. This means the amplifier is already tuned correctly prior to RF being applied, which is probably slightly better for the amplifier. ? In a perfect world, I could connect the amplifier CAT port to the serial connector on the rear panel of the radio, but, apparently, the Acom doesn't speak FTdx101 language. Yaesu changed the format of the CAT data for the FTdx101 & FTdx10 series of radios, as I understand it. Thus, I thought a work-around could be to send the data out from the logging software via the Echo port. It would need to be translated into something more vanilla, before being sent, though- Kenwood TS2000 or Yaesu FT1000, maybe. This would compensate for the amplifier firmware's inability to communicate with the FTdx101 or FTdx10. ? Is there already a way to do this? If not, is it something that would constitute a worthwhile enhancement? Or is it only me? ? ? Cheers, ? John G4DRS
Bob All Messages By This Member #97943 ... Section 12.6, and 12.7 might also be enlightening. SeventyThree(s). toggle quoted message Show quoted text On 04/06/2025 9:14 AM EDT Bob <k4cy@...> wrote: ? ? Isn't that done automagically? Example, configure the primary as (say) a Yaesu whatever.? Configure the Echo port as (say) an Icom whatever. Spin the dial on the primary radio, Yaesu formatted messages are received by Logger32, decoded, and sent to the echo radio in Icom format. ? Some commands simply don't translate from one radio brand to another.? So, configure a slave port instead, and map the differences - Like CW on the primary radio CW-R on the slave. ? Or, look at section 2.5 (page 275) of the help file. ? SeventyThree(a). ? On 04/06/2025 8:38 AM EDT John, G4DRS via groups.io <g4drs@...> wrote: ? ? I wonder, is it possible to have Logger32 translate the CAT data received from a connected radio before it sends it to the Echo port? I have searched the user manual, but can't see anything. That's not to say it isn't there, of course... ? The use case I have in mind is: Radio (FTdx101) connected to Logger32 via USB Amplifier (Acom 2000) connected to radio via coax and PTT cable ? At present, the amplifier automatically tunes to whatever segment it detects when I send it some RF. It is possible, however, to connect the amplifier to a serial port and have it select the appropriate band segment as the data on the serial port changes. This means the amplifier is already tuned correctly prior to RF being applied, which is probably slightly better for the amplifier. ? In a perfect world, I could connect the amplifier CAT port to the serial connector on the rear panel of the radio, but, apparently, the Acom doesn't speak FTdx101 language. Yaesu changed the format of the CAT data for the FTdx101 & FTdx10 series of radios, as I understand it. Thus, I thought a work-around could be to send the data out from the logging software via the Echo port. It would need to be translated into something more vanilla, before being sent, though- Kenwood TS2000 or Yaesu FT1000, maybe. This would compensate for the amplifier firmware's inability to communicate with the FTdx101 or FTdx10. ? Is there already a way to do this? If not, is it something that would constitute a worthwhile enhancement? Or is it only me? ? ? Cheers, ? John G4DRS
Bob All Messages By This Member #97944 ... there are even a handful on slave radio specific macros on the Radio Control Panel that may be of interest. SeventyThree(s). toggle quoted message Show quoted text On 04/06/2025 9:21 AM EDT Bob <k4cy@...> wrote: ? ? ... Section 12.6, and 12.7 might also be enlightening. SeventyThree(s). On 04/06/2025 9:14 AM EDT Bob <k4cy@...> wrote: ? ? Isn't that done automagically? Example, configure the primary as (say) a Yaesu whatever.? Configure the Echo port as (say) an Icom whatever. Spin the dial on the primary radio, Yaesu formatted messages are received by Logger32, decoded, and sent to the echo radio in Icom format. ? Some commands simply don't translate from one radio brand to another.? So, configure a slave port instead, and map the differences - Like CW on the primary radio CW-R on the slave. ? Or, look at section 2.5 (page 275) of the help file. ? SeventyThree(a). ? On 04/06/2025 8:38 AM EDT John, G4DRS via groups.io <g4drs@...> wrote: ? ? I wonder, is it possible to have Logger32 translate the CAT data received from a connected radio before it sends it to the Echo port? I have searched the user manual, but can't see anything. That's not to say it isn't there, of course... ? The use case I have in mind is: Radio (FTdx101) connected to Logger32 via USB Amplifier (Acom 2000) connected to radio via coax and PTT cable ? At present, the amplifier automatically tunes to whatever segment it detects when I send it some RF. It is possible, however, to connect the amplifier to a serial port and have it select the appropriate band segment as the data on the serial port changes. This means the amplifier is already tuned correctly prior to RF being applied, which is probably slightly better for the amplifier. ? In a perfect world, I could connect the amplifier CAT port to the serial connector on the rear panel of the radio, but, apparently, the Acom doesn't speak FTdx101 language. Yaesu changed the format of the CAT data for the FTdx101 & FTdx10 series of radios, as I understand it. Thus, I thought a work-around could be to send the data out from the logging software via the Echo port. It would need to be translated into something more vanilla, before being sent, though- Kenwood TS2000 or Yaesu FT1000, maybe. This would compensate for the amplifier firmware's inability to communicate with the FTdx101 or FTdx10. ? Is there already a way to do this? If not, is it something that would constitute a worthwhile enhancement? Or is it only me? ? ? Cheers, ? John G4DRS
John, G4DRS All Messages By This Member #97947 Thanks for the prompt attention and the useful suggestions, Bob. I already use the Slave port to link to an SDR for a panadapter - you can't have too many screens...:) As far as I can see, the echo port only sends out what the radio sends out, I can't see a way to configure it as a different radio type. Or am I missing something? I hope so... ? 73, ? John G4DRS?
Bob All Messages By This Member #97948 Look at section 49.6.4 to see if you can't figure out a way to free up the Logger32 slave port panadaptor by using omni-rig. SeventyThree(s). toggle quoted message Show quoted text On 04/06/2025 4:51 PM EDT John, G4DRS via groups.io <g4drs@...> wrote: ? ? Thanks for the prompt attention and the useful suggestions, Bob. I already use the Slave port to link to an SDR for a panadapter - you can't have too many screens...:) As far as I can see, the echo port only sends out what the radio sends out, I can't see a way to configure it as a different radio type. Or am I missing something? I hope so... ? 73, ? John G4DRS?
John, G4DRS All Messages By This Member #97950 Thanks, Bob. I'll have a rummage around. I'll let you know if I crack it! :) ? Cheers, ? John G4DRS

Previous Topic Next Topic