Log4OM

Is it possible to control L4Ong 2.17 via UDP ?
I need to TELL L4Ong to:
a) set frequency to xx (or Up/Dn by xx) - MUST
b) change mode to CW (or USB/LSB) - NICE TO HAVE
c) change BAND to xx - NICE TO HAVE
Please point me to some reference and possibly examples (if exist).
Regards

Would help if you said what radio and/or software you are using to send band, mode and frequency to Log4om?

My setup is: L4Ong interfaces my RIG (G90 compatible with IC7100) via OMNIRIG and it works fine.
When I scroll mouse over VFO Freq L4Ong instructs RIG to change FREQ accordingly.
Now, I do not like mouse, I want to write UDP packet to L4Ong to set the FREQ.
Regards and thanks for swift reply.

But UDP packet from what, other software in which case what software, physical hardware again what hard ware?

I will write a program that will send UDP packets to L4Ong
Regards.

SP5NZF wrote: ↑18 Oct 2021, 13:15 I will write a program that will send UDP packets to L4Ong
Regards.

The best method would be to use the multithreading capability of Omnirig and send your commands to Omnirig then all connected programs would follow/synchronise - Full details are on the Afreet/Omnirig website

Thanks. I've looked into using omnirig but it has some con's (need to write intermediary as hamcockpit plugin or directly invoking omnirig dll). My use case (android app or micro controller app) will be better served if I can directly use UDP interface of L4Ong and this is why I try to ask for its specification- what commands can I "talk" to L4Ong UDP port - where can I find documentation ?

Is it possible to control L4Ong 2.17 via UDP ?
I need to TELL L4Ong to:
a) set frequency to xx (or Up/Dn by xx) - MUST
b) change mode to CW (or USB/LSB) - NICE TO HAVE
c) change BAND to xx - NICE TO HAVE
Please point me to some reference and possibly examples (if exist).

73, Kuba

I will ask Lele if he will consider this

Answer from Lele as follows:


"UDP remote commands... it's not complex... but i can't imagine the usage of this feature...

anyway the answer is "yes, when i put into rework the actual 'remote control' feature". Ext. first quarter of 2022 following the actual workplan."

So there is your answer, at some time next year..

Thanks for all the information. I understand you have your roadmap. Otherwise You would not build such a great software. On the other hand, if there is place to advocate for certain improvements to be considered for the roadmap: I believe exposing network API is good:
a) API offloads demand for features not on the roadmap as anyone can add his features and enrich ecosystem of the application (here L4Ong),
b) network API is good as it extends ecosystem to other languages and devices. For low latency realtime control UDP is fine. It can be written async so not to delay L4Ong itself.
c) if one could register to system events (like new call logged, radio parameters changed, QSL fetched, anything you now act on).
Another question is if omnirig shouldn't expose network API
So let me say I fully understand and support your idea on "later, maybe 2022 Q1". And thanks for great software.
73, Kuba