开云体育

Looks to me like you need a program designed for remote operating, and not Logger32.

No, not really. It would be something completely different. ;-)

1) Yes, broadcast of N1MM formatted radio status id fixed to the localhost address. It would (I hope) be a simple code change to read the Loggr32.INI for a different address. This would mean users would need to edit the INI and add the address manually

That would be perfect! If in Logger?s *.INI would be a line which specifies the address where UDP-radio-status-packets will be sent to. Default could be: "radiostatusip=127.0.0.1" - changeable e.g.to "radiostatusip=192.168.0.235". The same piece of code would be nice also for DX-cluster-data, which you already made available with UDP - but for localhost only, right? Choosing a different IP-address in the local network would be very good.

2) I have no idea what you're asking for. Logger32 supports only one rotator at a time, and not by UDP messages.

I asked for that to simplify the rotator-workflow, at least at my station. Maybe others could use a feature like this also - in my opinion.

The thing is: some contest-loggers do not have "native" rotor-interfaces anymore. They don?t work with serial ports. They like to do it, e.g. for a multi-station environment, with UDP. That menas there?s one software controlling the rotator by serial (e.g. pstRotatorAz) and pstRotator Az is just listening on one specific UDP-port. On this ports everyone broadcasts who wants to turn the rotator.

So, what I?m asking for is to enable L32 to broadcast rotator-information thru UDP-packages. Why? The user could run the "rotator-controller" in the background which is hooked up to the serial port of the rotator. Then it doesn?t make any differencewether L32 is broadcasting oder WinTest or DXlog or whoever. :-)

Very curious about YOUR opinion to all that, Bob! :-)

73 from Germany,
Lenz, DL8RDL

On 03/17/2025 9:19 PM EDT Lorenz Grassl, DL8RDL via groups.io <mailingliste2@...> wrote:

?

?

Hi Bob, Hi group!

?

1. Concerning the radio-status for my PA:

Recently I needed to activate UDP-broadcast of radio-status to send the QRG of my radio to an RF2K-amp in the same network as my L32-computer. In the L32 manual and other groups I found information how to activate the broadcast. I struggled a bit because my PA ( IP 192.168.0.235, UDP-port 12060) wouldn?t hear the shouts of L32, which runs on a machine at 192.168.0.232.

I think that L32 broadcasts the status just for the local machine on 127.0.0.1. Is that true? If yes, would it be possible to give an IP to L32 where the UDPs should be talked to?

?

2. Concerning UDP and rotators:

I?d like to run two rotators using L32s capability to send rotator commands thru UDP. One rotator 1 is used for HF and rotator 2 is used by another trx and for VHF. I run two instances of pstRotatorAz in the background on the same machine as L32 runs. So these broadcasts could be local ones like 127.0.0.1. Am I able to do this? Do I have to setup two rotators with two different rotator-UDP-ports? Can I assign specified ports for the two rotators?

?

Thanks for reading all this and being concerned like I am :-)

?

73 de Lenz,

DL8RDL

开云体育

1) When the next auto-update is released (I will try for April 1st - The perfect day for new software),try this:

?

Run Logger32. Turn on Enable broadcast of radio status. This will add a line at the end of the [Globals] section of the Logger32.INI like this Radio Status UDP IP=127.0.0.1. Stop Logger32. Edit the new line with your IP address. Start Logger32. With a little luck Radio status is no longer sent to the default Localhost address.

That sounds reeeeally cool! Thanks for considering the idea! I?ll give you information how it worked.

2) At this time, I have no interest in adding UDP broadcast of rotator information. I recently added support for the uHam ARCO rotator by LAN. That seems like the way to go.

Ok on that. I?m very glad that you?ve included the "Yaesu A/B-protocol" since many years. I use this protocol right now at my station. And by the way: many other (contest)loggers don?t.

73
Lenz

?

SeventyThree(s).

?

On 03/27/2025 9:59 AM EDT Lorenz Grassl, DL8RDL via groups.io <mailingliste2@...> wrote:

?

?

Hi Bob,

Sorry for the late answer...

Looks to me like you need a program designed for remote operating, and not Logger32.

No, not really. It would be something completely different. ;-)

?

1) Yes, broadcast of N1MM formatted radio status id fixed to the localhost address. It would (I hope) be a simple code change to read the Loggr32.INI for a different address. This would mean users would need to edit the INI and add the address manually

That would be perfect! If in Logger?s *.INI would be a line which specifies the address where UDP-radio-status-packets will be sent to. Default could be: "radiostatusip=127.0.0.1" - changeable e.g.to "radiostatusip=192.168.0.235". The same piece of code would be nice also for DX-cluster-data, which you already made available with UDP - but for localhost only, right? Choosing a different IP-address in the local network would be very good.

?

2) I have no idea what you're asking for. Logger32 supports only one rotator at a time, and not by UDP messages.

I asked for that to simplify the rotator-workflow, at least at my station. Maybe others could use a feature like this also - in my opinion.

The thing is: some contest-loggers do not have "native" rotor-interfaces anymore. They don?t work with serial ports. They like to do it, e.g. for a multi-station environment, with UDP. That menas there?s one software controlling the rotator by serial (e.g. pstRotatorAz) and pstRotator Az is just listening on one specific UDP-port. On this ports everyone broadcasts who wants to turn the rotator.

So, what I?m asking for is to enable L32 to broadcast rotator-information thru UDP-packages. Why? The user could run the "rotator-controller" in the background which is hooked up to the serial port of the rotator. Then it doesn?t make any differencewether L32 is broadcasting oder WinTest or DXlog or whoever. :-)

Very curious about YOUR opinion to all that, Bob! :-)

73 from Germany,
Lenz, DL8RDL

?

On 03/17/2025 9:19 PM EDT Lorenz Grassl, DL8RDL via groups.io <mailingliste2@...> wrote:

?

?

Hi Bob, Hi group!

?

1. Concerning the radio-status for my PA:

Recently I needed to activate UDP-broadcast of radio-status to send the QRG of my radio to an RF2K-amp in the same network as my L32-computer. In the L32 manual and other groups I found information how to activate the broadcast. I struggled a bit because my PA ( IP 192.168.0.235, UDP-port 12060) wouldn?t hear the shouts of L32, which runs on a machine at 192.168.0.232.

I think that L32 broadcasts the status just for the local machine on 127.0.0.1. Is that true? If yes, would it be possible to give an IP to L32 where the UDPs should be talked to?

?

2. Concerning UDP and rotators:

I?d like to run two rotators using L32s capability to send rotator commands thru UDP. One rotator 1 is used for HF and rotator 2 is used by another trx and for VHF. I run two instances of pstRotatorAz in the background on the same machine as L32 runs. So these broadcasts could be local ones like 127.0.0.1. Am I able to do this? Do I have to setup two rotators with two different rotator-UDP-ports? Can I assign specified ports for the two rotators?

?

Thanks for reading all this and being concerned like I am :-)

?

73 de Lenz,

DL8RDL